From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: nnimap woes again
Date: Mon, 23 Jul 2001 17:42:40 -0500 [thread overview]
Message-ID: <q6mzo9ve07z.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <vaf3d7ncmsf.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 24 Jul 2001 00:18:08 +0200")
>>>>> On Tue, 24 Jul 2001 00:18:08 +0200,
>>>>> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> (kg) writes:
kg> On 23 Jul 2001, Doug Alcorn wrote:
>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>>
>>> When nnimap hangs, can you kill the according Gnus server buffer?
>>> Name might be ` *nnimap*' or ` *server foo **nnimap*' or similar,
>>> with a leading space.
>>
>> I can kill the buffer; but it doesn't do anything to alleviate the
>> problem.
kg> Hm. Is the corresponding process also killed? (M-x list-processes RET)
Occasionally I've noticed that the ssl session (via stunnel) to our
IMAP server will hang. I then have to `pkill openssl' and then do a
`g' in my *Group* buffer. Usually this will cause me to login again
via ssl and things are peachy.
Just recently I noticed stunnel-3.15 was released, and from what I
read about it there was some mention of not handling timeouts well?
Was going to try that and see if it helped, that is until we can get
ourselves upgraded to Cyrus 2.X.
--
Amos
next prev parent reply other threads:[~2001-07-23 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 21:30 Doug Alcorn
2001-07-23 22:03 ` Kai Großjohann
2001-07-23 22:01 ` Doug Alcorn
2001-07-23 22:18 ` Kai Großjohann
2001-07-23 22:42 ` Amos Gouaux [this message]
2001-07-24 4:04 ` Doug Alcorn
2001-07-24 4:23 ` Amos Gouaux
2001-07-24 13:57 ` nnimap woes again (more details) Doug Alcorn
2001-07-24 9:01 ` nnimap woes again Kai Großjohann
2001-07-24 9:38 ` Christoph Rohland
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=q6mzo9ve07z.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/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).