From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Can't access local imap account: GNUTls error
Date: Fri, 04 Mar 2016 20:59:22 -0500 [thread overview]
Message-ID: <874mcl65xh.fsf@uwo.ca> (raw)
In-Reply-To: <8737s5elwk.fsf@uwo.ca>
On Mar 4, 2016, Dan Christensen <jdc@uwo.ca> wrote:
> I have noticed something that might be the same bug. I have a remote
> IMAP server that is set up like this:
>
> (add-to-list 'gnus-secondary-select-methods
> '(nnimap "foo"
> (nnimap-address "foo.com")
> (nnimap-stream shell)
> (nnimap-shell-program "ssh %s /usr/lib/dovecot/imap")
> ))
>
> However, when I start Gnus and try to open a group nnimap+foo:mygroup
> that uses this server, it usually tries to connect via tls. Then I
> fiddle around for a while, kill Gnus and restart a few times, and
> eventually it works. I haven't figured out the pattern, but it seems
> to not see my server definition and fall back onto a default. Maybe
> the same is happening for you.
>
> The good news is that once it works, it stays working for that Gnus
> session. Luckily I leave Gnus running for weeks at a time...
Just for you, I exited Gnus (gasp) to test this a bit more. If I start
Gnus and try to activate a group on that server with `M-g', it tries to
use tls and fails. But if I instead do `3 g' to activate all groups at
level 3, it works. (The only groups I have from that server are on
level 3, and I start Gnus with `(gnus 2 t)', which is like
gnus-no-server, only activating groups up to level 2.)
Dan
next prev parent reply other threads:[~2016-03-05 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 2:44 Eric Abrahamsen
2016-03-04 8:07 ` Eric Abrahamsen
2016-03-05 1:47 ` Dan Christensen
2016-03-05 1:59 ` Dan Christensen [this message]
2016-03-05 2:31 ` Eric Abrahamsen
2016-03-05 4:28 ` Dan Christensen
2016-03-05 8:21 ` Andreas Schwab
2016-03-05 23:58 ` Dan Christensen
2016-03-08 1:54 ` Eric Abrahamsen
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=874mcl65xh.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).