From: Emanuel Berg <moasen@zoho.com>
To: ding@gnus.org
Subject: Re: new (?) version of the old nnml problem
Date: Fri, 20 Oct 2017 20:40:21 +0200 [thread overview]
Message-ID: <86lgk5zmqy.fsf@zoho.com> (raw)
In-Reply-To: <87vaj94ss4.fsf@ericabrahamsen.net>
Eric Abrahamsen wrote:
> the two programs are roughly equivalent: they
> handle creating and checking TLS
> certificates, and creating and handling
> TLS-encrypted connections to remote servers.
OK, then how do I specify openssl should be
used instead? Worth a shot... A search with
`apropos-value' and "gnutls" reveals
starttls-gnutls-program
"gnutls-cli"
tls-program
("gnutls-cli --insecure -p %p %h" "gnutls-cli
--insecure -p %p %h --protocols ssl3" "openssl
s_client -connect %h:%p -no_ssl2 -ign_eof")
Neither set by me, but can be incorrect anyway,
of course. Eheh.
> I actually was just assuming you are using
> gnutls, you can probably check the
> libgnutls-version.
If you mean ... then:
$ gnutls-cli --version
gnutls-cli 3.3.8
> You can also try setting gnutls-log-level to
> 3 or 4 and fetching mail, and see if anything
> interesting pops up in *Messages*.
This does, over and over again:
gnutls.c: [3] ASSERT: gnutls_buffers.c:547
gnutls.c: [3] (Emacs) retry: Resource temporarily unavailable, try again.
gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again.
gnutls.c: [3] ASSERT: gnutls_buffers.c:1104
> The bad news is that I tried this:
>
> gnutls-cli --port 995 pop.zoho.com
>
> And it connected just fine. You might try
> that, and going through with the
> login procedure.
Login procedure works, the rest seems fine (?).
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-10-20 18:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 14:27 Emanuel Berg
2017-10-20 14:42 ` Emanuel Berg
2017-10-20 14:51 ` Emanuel Berg
2017-10-20 15:38 ` Eric Abrahamsen
2017-10-20 15:46 ` Emanuel Berg
2017-10-20 15:48 ` Emanuel Berg
2017-10-20 16:08 ` Eric Abrahamsen
2017-10-20 17:11 ` Emanuel Berg
2017-10-20 17:36 ` Eric Abrahamsen
2017-10-20 15:57 ` Emanuel Berg
2017-10-20 16:11 ` Eric Abrahamsen
2017-10-20 17:12 ` Emanuel Berg
2017-10-20 17:45 ` Eric Abrahamsen
2017-10-20 18:40 ` Emanuel Berg [this message]
2017-10-20 21:20 ` Eric Abrahamsen
2017-10-21 8:53 ` Emanuel Berg
2017-10-23 5:51 ` Emanuel Berg
2017-10-23 15:32 ` Eric Abrahamsen
2017-10-23 18:31 ` Emanuel Berg
2017-10-23 19:17 ` Adam Sjøgren
2017-10-25 15:36 ` Emanuel Berg
2017-10-25 19:02 ` Eric Abrahamsen
2017-10-25 19:41 ` Emanuel Berg
2017-10-25 21:22 ` Eric Abrahamsen
2017-10-26 17:17 ` Emanuel Berg
2017-10-26 22:55 ` Eric Abrahamsen
2017-11-06 15:49 ` Ted Zlatanov
2017-11-06 16:11 ` Robert Pluim
2017-11-06 16:20 ` Adam Sjøgren
2017-11-06 16:32 ` Robert Pluim
2017-11-07 23:53 ` Emanuel Berg
2017-11-08 0:28 ` Emanuel Berg
2017-10-23 22:33 ` Eric Abrahamsen
2017-10-24 18:45 ` Emanuel Berg
2017-10-20 15:44 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86lgk5zmqy.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).