Gnus development mailing list
 help / color / mirror / Atom feed
From: "Steven E. Harris" <seh@panix.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Mon, 16 Aug 2004 12:43:28 -0700	[thread overview]
Message-ID: <jk43c2mq36n.fsf@W003275.na.alarismed.com> (raw)
In-Reply-To: <87r7q7hqya.fsf@ion.xlipstream.com> (Chris Green's message of "Mon, 16 Aug 2004 14:34:53 -0400")

Chris Green <cmg@dok.org> writes:

> When the session times out, I have to M-g to get nnimap to reconnect
> to the server.

I have similar trouble using nnimap with openssl and starttls on
Cygwin. There seems to be some problem with how Gnus or XEmacs detects
that a connection dropped.

Sometimes when I go to check for new messages in an nnimap group, I'll
try, say, "1-g" to check groups at level one. That will hang, so I'll
hit C-g to cancel (sometimes it takes many tries), then place my
cursor on the group in question and hit M-g. That /sometimes/ checks
the messages again with the same dropped or corrupted connection, so I
have to stop Gnus again, go to the Server buffer, and try to close the
supposedly open connection there. Of course, trying to close the
connection makes Gnus hang again, so several more M-g attempts may
finally yield Gnus recognizing that it has no open connection to this
server. Only at that point can I tell Gnus to open a fresh connection
to check if I have any new messages. This whole process usually takes
close to a minute and around 50 keystrokes.

I don't notice the same problems, at least to the same degree, with
direct connections to the IMAP servers. It's those programs in between
Gnus and the IMAP servers such as openssl and starttls that aggravate
these flaky connection problems.

Even worse is trying to quit Gnus. I notice that for around the last
year of keeping up to date with CVS, Gnus does not quit cleanly if any
of its open connections had dropped. I have to manually kill some or
all of the openssl and starttls processes, as well as hit C-g many
times, to get Gnus to shut down. I can't tell if this problem is
directly related to nnimap or not.

-- 
Steven E. Harris



  reply	other threads:[~2004-08-16 19:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12  2:11 ` Kevin Greiner
2004-08-12 15:13   ` Steven E. Harris
2004-08-12 15:46     ` Simon Josefsson
2004-08-12 16:08       ` Steven E. Harris
2004-08-12 16:48         ` Simon Josefsson
2004-08-12 17:26           ` Steven E. Harris
2004-08-12 19:31             ` Simon Josefsson
2004-08-16 15:02               ` Steven E. Harris
2004-08-16 15:11                 ` Steven E. Harris
2004-08-16 15:31                 ` Simon Josefsson
2004-08-16 16:45                   ` Steven E. Harris
2004-08-16 16:59                     ` Simon Josefsson
2004-08-16 17:50                       ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03                         ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17  3:13                   ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17  8:23                     ` Simon Josefsson
     [not found]                       ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59                         ` Jochen Küpper
2004-08-17 15:50                       ` Steven E. Harris
2004-08-17 16:40                         ` Simon Josefsson
2004-08-12 19:49       ` Mats Lidell
2004-08-12 20:35         ` Simon Josefsson
2004-08-20 22:09           ` Mats Lidell
2004-08-12 21:30       ` Kevin Greiner
2004-08-12 22:28         ` Simon Josefsson
2004-08-16 17:45       ` Ted Zlatanov
2004-08-16 18:34         ` Chris Green
2004-08-16 19:43           ` Steven E. Harris [this message]
2004-08-16 19:54         ` Steven E. Harris
2004-08-17 11:39         ` Steinar Bang

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=jk43c2mq36n.fsf@W003275.na.alarismed.com \
    --to=seh@panix.com \
    /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).