Gnus development mailing list
 help / color / mirror / Atom feed
From: Doug Alcorn <doug@lathi.net>
Subject: detecting disconnects with nnimap
Date: 25 Apr 2001 15:36:54 -0400	[thread overview]
Message-ID: <87zod4hiuh.fsf@balder.seapine.com> (raw)

My firewall drops all tcp connections if they are idle for some period
of time.  Unfortunately I think that time period is less than what
nnimap uses.  So, I find myself often during the day having to do
something that causes nnimap to try and communicate with the server.
It then hangs indefinitely and I have to C-g it.  Then I re-do the
command and nnimap automatically reconnects to me server without any
problem.  Is there any good way for me to fix this?
-- 
 (__) 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-25 19:36 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=87zod4hiuh.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).