From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: Exchange, nnimap, and lock-ups
Date: Tue, 08 Feb 2011 13:38:07 -0500 [thread overview]
Message-ID: <87ipwunzhs.fsf@maru.md5i.com> (raw)
In-Reply-To: <87aai7k4na.fsf@member.fsf.org> (Tassilo Horn's message of "Mon, 07 Feb 2011 20:48:09 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
> Michael Welsh Duggan <md5i@md5i.com> writes:
>
> Hi Michael,
>
>>> I can verify this:
>>>
>>> 14:29:09 958 EXAMINE "shared.teams.netsa.logs.svn"
>>> 14:29:09 959 UID FETCH 14536:* FLAGS
>>> 14:29:09 960 NOOP
>>> 14:29:09 961 NOOP
>>
>> I should note that I am connected to two separate IMAP servers, an
>> Exchange server and a Cyrus server. In this particular case, it makes
>> it all the way through the exchange server, and it locks up _after_
>> the last group of the Cyrus server. I.e., it did make it through a
>> full scan of both servers before the hanging NOOPs.
>
> Ditto here. And the problematic server on my side is also a Cyrus
> server:
>
> * OK mail Cyrus IMAP4 v2.2.12 server ready
As a further data point, I did the following:
(cancel-timer nnimap-keepalive-timer)
(setq nnimap-keepalive-timer t)
After this, I have not seen any problems, so it's very likely a problem
of sorts with the NOOP processing.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2011-02-08 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 19:06 Michael Welsh Duggan
2011-02-07 19:13 ` Tassilo Horn
2011-02-07 19:35 ` Michael Welsh Duggan
2011-02-07 19:43 ` Michael Welsh Duggan
2011-02-07 19:48 ` Tassilo Horn
2011-02-08 18:38 ` Michael Welsh Duggan [this message]
2011-02-14 3:03 ` Lars Ingebrigtsen
2011-02-15 20:03 ` Michael Welsh Duggan
2011-02-08 22:16 ` Michael Welsh Duggan
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=87ipwunzhs.fsf@maru.md5i.com \
--to=md5i@md5i.com \
--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).