From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: Various nnimap problems
Date: Wed, 22 Sep 2010 14:31:30 -0400 [thread overview]
Message-ID: <87fwx1mxz1.fsf@maru.md5i.com> (raw)
In-Reply-To: <m3d3s5em69.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 22 Sep 2010 19:13:34 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <mwd@cert.org> writes:
>
>> *) On Cyrus 2, I am spuriously seeing an odd behavior when I am in a
>> summary buffer reading messages. Sometimes when going to the next
>> message, it appears to have vanished from the server (marked with
>> G). When this happens, usually all articles in the summary buffer
>> exhibit the same behavior. Exiting the group (carefully unmarking
>> the G articles) and reentering allows me to read those messages
>> again.
>
> It sounds like something changed the current group behind your back, and
> selecting a new article didn't change it back again. Which is odd,
> since the first thing `nnimap-request-article' does is change the group
> back.
>
> When this happens (when you get the first "G"), could you pop over to
> the *nnimap <server> ...* buffer and see what in there? Looking in the
> *imap log* buffer may also hold clues.
14:26:56 32587 UID FETCH 113674 BODY.PEEK[]
32587 OK Completed (0.000 sec)
But the messages before the FETCH were from a demon, and it changed the
group using SELECT. I think the fix you mentioned elsewhere in this
thread may handle this.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2010-09-22 18:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 15:40 Michael Welsh Duggan
2010-09-22 15:57 ` Michael Welsh Duggan
2010-09-22 16:39 ` Julien Danjou
2010-09-22 17:09 ` Julien Danjou
2010-09-22 17:16 ` Lars Magne Ingebrigtsen
2010-09-22 17:23 ` Lars Magne Ingebrigtsen
2010-09-22 17:13 ` Lars Magne Ingebrigtsen
2010-09-22 17:46 ` Michael Welsh Duggan
2010-09-22 18:45 ` Lars Magne Ingebrigtsen
2010-09-22 18:31 ` Michael Welsh Duggan [this message]
2010-09-22 18:36 ` Lars Magne Ingebrigtsen
2010-09-22 21:06 ` Michael Welsh Duggan
2010-09-22 21:33 ` Lars Magne Ingebrigtsen
2010-09-22 22:49 ` Michael Welsh Duggan
2010-09-22 22:53 ` Michael Welsh Duggan
2010-09-26 18:25 ` Michael Welsh Duggan
2010-09-26 18:57 ` Lars Magne Ingebrigtsen
2010-09-22 17:58 ` Lars Magne Ingebrigtsen
2010-09-24 15:06 ` Michael Welsh Duggan
2010-09-24 16:04 ` Lars Magne Ingebrigtsen
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=87fwx1mxz1.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).