Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: (fake) unread messages using nnimap.
Date: Mon, 25 Oct 2010 15:38:40 +0200	[thread overview]
Message-ID: <87pquy5r4v.fsf@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <m2eibefmkl.fsf@rimspace.net>

>> Regarding Re: (fake) unread messages using nnimap.;
>> Daniel Pittman <daniel@rimspace.net> adds:

   >> 
   >> 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.

But isn't this also a dovecot issue then?

It seems that you use such a configuration. I have set up my
dovecot offlineimap configuration more than a year ago and
don't remember the details. Could I change the setting? Can
you tell me how.

Thanks 



Uwe Brauer





  reply	other threads:[~2010-10-25 13:38 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
2010-10-25 13:38   ` Uwe Brauer [this message]
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=87pquy5r4v.fsf@gilgamesch.quim.ucm.es \
    --to=oub@mat.ucm.es \
    --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).