Re: Can't access local imap account: GNUTls error

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Dan Christensen <jdc@uwo.ca> writes:

> 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.

Your sacrifice is appreciated :)

> 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.)

I haven't been able to trick Gnus into connecting, no matter how I go
about it. I can go into the *Server* buffer and hit "O" on the server,
and it says it's open, but then trying to access it gives me
"nnimap-send-command: Output file descriptor of *nnimap* is closed".
Using the equivalent of your "3 g" just gives me the same errors.

So pretty clearly it's not going to connect. I have to assume a
misconfiguration somewhere, as it's only this one account out of four,
and I have the identical problem on two separate computers. But I don't
know where else to look!

Thanks,
Eric