From: "JJ" <ding_gnus.org@sumou.com>
To: ding@gnus.org
Subject: Re: Fatal error: No such file... closed GnuTLS connection, two nnimap processes
Date: Wed, 13 Oct 2010 11:34:21 -0400 (EDT) [thread overview]
Message-ID: <13542.90.180.128.43.1286984061.squirrel@mail.hcoop.net> (raw)
In-Reply-To: <m3hbgrio54.fsf@quimbies.gnus.org>
> Anyway, the means that the problem is that the IMAP server is saying
> "* BYE" and closing the connection. Why would it be doing that?
I've opened a bug about this on hcoop and the admin seems to thinks it's a
problem with Gnus after the recent changes.
Is there any way that Gnus would be forcing a hangup?
I.e. is there a way I can get a full trace of the sessing with Gnu Emacs
Gnus, since it doesn't have this problem? I.e. why is the server not
closing the connection there, as it's the same Gnus init setup etc.?
--
JJ
next prev parent reply other threads:[~2010-10-13 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 19:23 JJ
2010-10-07 20:13 ` Lars Magne Ingebrigtsen
2010-10-10 18:54 ` JJ
2010-10-10 20:46 ` Lars Magne Ingebrigtsen
2010-10-11 13:02 ` Ted Zlatanov
2010-10-11 18:24 ` Lars Magne Ingebrigtsen
2010-10-12 1:25 ` JJ
2010-10-12 12:36 ` Lars Magne Ingebrigtsen
2010-10-13 15:34 ` JJ [this message]
2010-10-13 18:27 ` Lars Magne Ingebrigtsen
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=13542.90.180.128.43.1286984061.squirrel@mail.hcoop.net \
--to=ding_gnus.org@sumou.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).