From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: Various nnimap problems
Date: Wed, 22 Sep 2010 11:57:49 -0400 [thread overview]
Message-ID: <87zkv9n536.fsf@maru.md5i.com> (raw)
In-Reply-To: <tntmxr9yeff.fsf@waterbuck.yellow.cert.org> (Michael Welsh Duggan's message of "Wed, 22 Sep 2010 11:40:36 -0400")
Michael Welsh Duggan <mwd@cert.org> writes:
[...]
> Capabilities for Cyrus 2:
> ("IMAP4" "IMAP4REV1" "ACL" "QUOTA" "LITERAL+" "NAMESPACE" "UIDPLUS" "ID" "NO_ATOMIC_RENAME" "UNSELECT" "CHILDREN" "MULTIAPPEND" "BINARY" "SORT" "THREAD=ORDEREDSUBJECT" "THREAD=REFERENCES" "ANNOTATEMORE" "IDLE" "LOGINDISABLED")
[...]
> In all scenarios I am running the following demon:
> (gnus-demon-add-handler 'gnus-demon-scan-news 10 nil)
[...]
> *) 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.
Some further information on this one. It happens when sitting in a
summary buffer for a while. I suspect it happens when a message is
added to the group behind gnus's back (via sieve).
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2010-09-22 15:57 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 [this message]
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
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=87zkv9n536.fsf@maru.md5i.com \
--to=md5i@md5i.com \
--cc=ding@gnus.org \
--cc=mwd@md5i.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).