Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: new (?) version of the old nnml problem
Date: Fri, 20 Oct 2017 10:45:47 -0700	[thread overview]
Message-ID: <87vaj94ss4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86tvytzqtp.fsf@zoho.com>

Emanuel Berg <moasen@zoho.com> writes:

> Eric Abrahamsen wrote:
>
>> my guess is there's something slightly wrong
>> with the pop.zoho.com certificate, something
>> that openssl is letting slide, but socat and
>> gnutls aren't happy about.
>
> What exactly is openssl? Can I use that instead
> of gnutls?

My understanding (and again, I know very little about these things) is
that the two programs are roughly equivalent: they handle creating and
checking TLS certificates, and creating and handling TLS-encrypted
connections to remote servers.

I actually was just assuming you are using gnutls, you can probably
check the libgnutls-version. You can also try setting gnutls-log-level
to 3 or 4 and fetching mail, and see if anything interesting pops up in
*Messages*.

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.

Otherwise, I might be fresh out of helpful!

Eric




  reply	other threads:[~2017-10-20 17:45 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 [this message]
2017-10-20 18:40               ` Emanuel Berg
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=87vaj94ss4.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).