Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
Subject: nnimap connection timeout problem
Date: 06 Sep 2000 17:39:38 -0400	[thread overview]
Message-ID: <76snrdryhx.fsf@newjersey.ppllc.com> (raw)


Since upgrading from XEmacs 21.1.8 to 21.1.12 and upgrading all my packages
at the same time, I am having problems with nnimap connection.  Everything is
fine and dandy if, after establishing the initial connection I continue to
check my mail fairly regularly.  But if I wait for an extended period of
time, the Exchange Server times out the connection and I can no longer
reconnect.  It is not even sufficient for me to shut down gnus.  I have to
exit and restart my entire XEmacs session.

This first happened to me, BTW, about two weeks ago when I tried updating to
the latest packages while still running 21.1.8.  Immediately upon having done
this, my imap connection would freeze after the initial download done by
gnus.  I immediately restored my packages directory, on the assumption that
perhaps the latest packages require the latest XEmacs, and all was well
again.  Now I have the latest of everything and still no joy.

TIA!

-- 
Jake Colman                     

Principia Partners LLC                  Phone: (201) 946-0300
Harborside Financial Center               Fax: (201) 946-0320
902 Plaza II                           Beeper: (800) 928-4640
Jersey City, NJ 07311                  E-mail: colman@ppllc.com
                                       E-mail: jcolman@jnc.com
                                          web: http://www.ppllc.com

microsoft: "where do you want to go today?"
linux:     "where do you want to go tomorrow?"
BSD:       "are you guys coming, or what?"



                 reply	other threads:[~2000-09-06 21:39 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=76snrdryhx.fsf@newjersey.ppllc.com \
    --to=colman@ppllc.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).