From: Doug Alcorn <doug@lathi.net>
Subject: nnimap timeout issues
Date: 27 Apr 2001 11:15:21 -0400 [thread overview]
Message-ID: <87g0eu5q7q.fsf@balder.seapine.com> (raw)
I'm not exactly sure which IMAP server I'm running. I'm pretty sure
it's not the cygnus one. Previously I had posted about how my
firewall was dropping connections and causing nnimap to get confused.
However, I don't think it's the firewall that's doing it. When I
connect from home both the server and my client are on the same side
of the firewall. I'm often having "hung" nnimap connections at home
too. Seems like nnimap is not able to detect a dropped connection
properly.
--
(__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543
|_/ If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
reply other threads:[~2001-04-27 15:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87g0eu5q7q.fsf@balder.seapine.com \
--to=doug@lathi.net \
/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).