Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnimap woes again
Date: Tue, 24 Jul 2001 11:01:53 +0200	[thread overview]
Message-ID: <vafy9peu2da.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <q6mzo9ve07z.fsf@spartacus.utdallas.edu> (Amos Gouaux's message of "Mon, 23 Jul 2001 17:42:40 -0500")

On Mon, 23 Jul 2001, Amos Gouaux wrote:

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

I've seen something similar with ssh: if the remote end drops the
connection, you don't see that until you type a command into your
local ssh client.  Only then does the local ssh client tell you that
the connection is down.

Gnus looks whether the connection is up before sending a command, but
once it has determined that the connection is up, it expects the
connection to be up and doesn't check again.

Maybe Gnus could be changed to see when it sent the last command.  If
that has been more than a configurable number of seconds ago, it sends
a no-op command to the remote end to see if the connection is still
up.  But nobody has implemented that, I'm afraid.

kai
-- 
~/.signature: No such file or directory


  parent reply	other threads:[~2001-07-24  9:01 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
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         ` Kai Großjohann [this message]
2001-07-24  9:38         ` nnimap woes again 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=vafy9peu2da.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).