From: Tim Landscheidt <tim@tim-landscheidt.de>
To: ding@gnus.org
Subject: Re: ssl problems
Date: Wed, 07 Jul 2010 18:28:06 +0000 [thread overview]
Message-ID: <m3630ri1u1.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <14564.8104175509$1278524335@news.gmane.org>
Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> I recently updated from debian lenny to squeeze, and have found that
> connecting to gmail's pop servers via ssl has become extremely dicey. I
> have four email addresses, all of them gmail, and on any given mail
> check three of them will tell me "POP SSL connexion failed". It can be
> very hard to get all my email. My emacs/gnus versions and setup did not
> change (still emacs 23.3.1 and gnus 5.13), all that changed was my linux
> installation. I'm accessing gmail on port 995 with ":ssl t", and I have
> "starttls-use-gnutls" set to true. My gnutls version is 2.8.6, which I
> see isn't the latest version, but 2.10 isn't in the debian repos and
> besides this was working smoothly under lenny, which presumably had the
> same gnutls version.
> Is there anything I can do to further debug this? I'm not an expert with
> using gnutls-cli from the command line, but so far as I can tell it
> connects fine (gnus only fails *most* of the time, anyway…). Is there a
> way to get gnus to tell me *why* the POP SSL connection failed?
For me, it helped to increase nnheader-read-timeout (and
pop3-read-timeout to be on the safe side) to 2.0.
Unfortunately, the whole SSL shebang with separate pro-
cesses, not to speak of two different clients, seems to be
*very* fragile. It would be *really* nice if it could be
included properly in Emacs.
Tim
next prev parent reply other threads:[~2010-07-07 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:38 Eric Abrahamsen
2010-07-07 18:28 ` Tim Landscheidt [this message]
2010-07-07 18:33 ` Ted Zlatanov
2010-07-07 18:53 ` Eric Abrahamsen
2010-07-07 19:15 ` Tim Landscheidt
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=m3630ri1u1.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--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).