From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: (fake) unread messages using nnimap.
Date: Tue, 26 Oct 2010 00:07:06 +1100 [thread overview]
Message-ID: <m2eibefmkl.fsf@rimspace.net> (raw)
In-Reply-To: <874ocaioc0.fsf@gilgamesch.quim.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> I wrote about this some time ago but never saw my mail posted. Just in case
> again: I am using Xemacs 21.4.22 Mule, nognus 0.11 and the nnimap backend
> for reading my mail. My mail I receive using offlineimap and running the
> dovecot server on my Laptop. That is why I don't use the agent any more.
>
> However in every session gnus indicates in several nnimap groups unread
> message, where in fact there are not. When visiting the group *no* unread
> messages are shown and after leaving that group in fact the indication of
> the unread messages disappears.
>
> Does anybody know about this problem and what to do?
It could be any number of things, but one of the common issues with
offlineimap that I have is:
When you add a new message to a group on the "client" side of an IMAP <=> IMAP
sync pair, offlineimap will upload it to the server, delete it from the
client, then add a new copy with an extra header.
Flags are preserved, though, so the message will show an a "new" item, but
already be read when Gnus looks at it. This would show in any folder where
you added messages with IMAP on the client side.
offlineimap with a mutable client side (eg: Maildir) doesn't show this problem
because it doesn't need to delete and add a message to add the extra header.
Regards,
Daniel
--
✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
next prev parent reply other threads:[~2010-10-25 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 10:00 Uwe Brauer
2010-10-25 13:07 ` Daniel Pittman [this message]
2010-10-25 13:38 ` Uwe Brauer
2010-10-26 4:48 ` Daniel Pittman
2010-10-25 14:21 ` Richard Riley
2010-10-25 14:45 ` Uwe Brauer
2010-10-25 15:54 ` Richard Riley
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=m2eibefmkl.fsf@rimspace.net \
--to=daniel@rimspace.net \
--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).