Re: [Dovecot] 1.0-stable loses flag changes sometimes?

On Fri, 2005-05-13 at 15:21 +0100, Chris Wakelin wrote:

It seems similar to the 1.0-stable issue, only the spurious FETCH responses seem to give the wrong flags then (but I can't reproduce this on demand).

I think the basic idea is this:

• Update the flags for the last message --> because of lazy-writing Dovecot just marks the message dirty
• New message arrives on the mailbox --> Dovecot re-reads the last message, forgets the dirty state
• close the mailbox --> Because the dirty state is forgotten, the flag is never written to mbox

Fixed in CVS now for both 1.0-test and 1.0-stable.