Re: Messages moved from /new to /cur

[Andrew Biggadike <biggadike@xxxxxxxxxxxxxx>]

Jon,

"set mark_old=no" in your .muttrc doesn't change anything, does it?

It sounds like you've narrowed it down pretty well to OfflineIMAP
changing from cur/ to new/, but I thought I'd throw it out there
anyhow.  All the messages in cur/ without the S flag show up as new
(N) for me in Mutt.

Andrew

Jon Riddle <list@xxxxxxxxxxxxxxxxx> wrote:
> It's not a "problem", per se - just an annoyance.  When I have new
> messages (N) in a folder, I can hit c to change folders and Mutt fills
> in the folder for me (saves, maybe 10 keystrokes?).  It doesn't treat
> old messages (O) the same way.  That actually may be a Mutt preference,
> but I haven't dug into it.  I just don't see why OfflineIMAP should
> change the flags at all - it isn't a mail client.  It's a synchronizer.
> Like I said, not a problem - just an annoyance :-)
> 
> Jon
> 
> 
> > On Fri, Mar 17, 2006 at 08:19:55PM -0600, Jon Riddle wrote:
> > > It seems that, as of 3.99.2, OfflineIMAP moves messages from /new to
> > > /cur whenever it syncs.  The changelog entry states that this occurs
> > > "when flags have changed on the server", but in my case, this is
> > > happening anytime OfflineIMAP syncs my account.  Is this correct?
> > > According to the Maildir spec (actually, the official man page),
> > > messages are supposed to be moved to /cur when a mail client has seen
> > > the messages, and the S flag appended when the user has read the
> > > messages.  Is OfflineIMAP considered a mail client?  If so, can this
> > 
> > It's a gray area.  I don't believe it is really documented anywhere what
> > the proper behavior should be; the Maildir spec obviously does not
> > consider the case where the flags for a message have changed remotely.
> > 
> > Does it actually cause you a problem?  It seems that most mail readers
> > don't expect files in new to have been read.
> > 
> > -- John
> > 
> 
>