[Dovecot] read/unread flags broken in rc19 ?
Hi,
I'm posting to relate that on debian unstable dovecot imap 1.0rc19 I'm experiencing exactly the same as seen on this thread: http://www.dovecot.org/list/dovecot/2007-January/018937.html All mail dating from last sunday (only that day it seems) gets reset to unread after I mark them as read after a period of time. This with thunderbird. Thanks for any help on this topic :)
Stéphane Epardaud
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel.
Hi,
I'm posting to relate that on debian unstable dovecot imap 1.0rc19 I'm experiencing exactly the same as seen on this thread: http://www.dovecot.org/list/dovecot/2007-January/018937.html All mail dating from last sunday (only that day it seems) gets reset to unread after I mark them as read after a period of time. This with thunderbird. Thanks for any help on this topic :)
Stéphane Epardaud
On Wed, Jan 31, 2007 at 08:56:31PM -0500, lenny@edpausa.com wrote:
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel.
As a temporary work-around, you can turn off lazy writes.
There is something broken in RC19 that corrupts read/unread counts when lazy writes are enabled.
At least it worked for me.
-- Dean Brooks dean@iglou.com
tried that. no effect.
On Wed, Jan 31, 2007 at 08:56:31PM -0500, lenny@edpausa.com wrote:
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel.
As a temporary work-around, you can turn off lazy writes.
There is something broken in RC19 that corrupts read/unread counts when lazy writes are enabled.
At least it worked for me.
-- Dean Brooks dean@iglou.com
On Thu, Feb 01, 2007 at 08:34:11AM -0500, lenny@edpausa.com wrote:
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel.
As a temporary work-around, you can turn off lazy writes.
There is something broken in RC19 that corrupts read/unread counts when lazy writes are enabled.
At least it worked for me.
tried that. no effect.
Be sure that you didn't just comment out the lazy_write config entry.
Lazy writes are on by default, so you have to uncomment the config entry and explicitly set it to 'no':
mbox_lazy_writes = no
-- Dean Brooks dean@iglou.com
that's what I'd done, but it made no difference at all.
mbox_lazy_writes = no
On Thu, Feb 01, 2007 at 08:34:11AM -0500, lenny@edpausa.com wrote:
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel.
As a temporary work-around, you can turn off lazy writes.
There is something broken in RC19 that corrupts read/unread counts when lazy writes are enabled.
At least it worked for me.
tried that. no effect.
Be sure that you didn't just comment out the lazy_write config entry.
Lazy writes are on by default, so you have to uncomment the config entry and explicitly set it to 'no':
mbox_lazy_writes = no
-- Dean Brooks dean@iglou.com
I take it back. It did fix the read/unread flags, but the reply flags are still broken.
that's what I'd done, but it made no difference at all.
mbox_lazy_writes = no
On Thu, Feb 01, 2007 at 08:34:11AM -0500, lenny@edpausa.com wrote:
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel.
As a temporary work-around, you can turn off lazy writes.
There is something broken in RC19 that corrupts read/unread counts when lazy writes are enabled.
At least it worked for me.
tried that. no effect.
Be sure that you didn't just comment out the lazy_write config entry.
Lazy writes are on by default, so you have to uncomment the config entry and explicitly set it to 'no':
mbox_lazy_writes = no
-- Dean Brooks dean@iglou.com
You could try reverting the last CVS update before rc19, http://www.dovecot.org/list/dovecot-cvs/2007-January/007505.html as suggested in the earlier threads:
http://www.dovecot.org/list/dovecot/2007-January/018937.html http://www.dovecot.org/list/dovecot/2007-January/019048.html
It seems to have helped me with read/unread flags, but I've still seen some oddities. Reply flags also seem broken. Time for more testing!
Chris
lenny@edpausa.com wrote:
I take it back. It did fix the read/unread flags, but the reply flags are still broken.
that's what I'd done, but it made no difference at all.
mbox_lazy_writes = no
On Thu, Feb 01, 2007 at 08:34:11AM -0500, lenny@edpausa.com wrote:
same here. rc19 on solaris 9. sparc. read/unread/replied flags disappear, reappear and don't work. test in tbird and squirrel. As a temporary work-around, you can turn off lazy writes.
There is something broken in RC19 that corrupts read/unread counts when lazy writes are enabled.
At least it worked for me. tried that. no effect. Be sure that you didn't just comment out the lazy_write config entry.
Lazy writes are on by default, so you have to uncomment the config entry and explicitly set it to 'no':
mbox_lazy_writes = no
-- Dean Brooks dean@iglou.com
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Chris Wakelin wrote:
Reply flags also seem broken. Time for more testing!
Yep, broken they are (mbox, Solaris 8, lazy-writes enabled etc.)
. FETCH 815 FLAGS
- 815 FETCH (FLAGS (\Seen)) . OK Fetch completed. . STORE 815 +FLAGS (\Answered)
- 815 FETCH (FLAGS (\Seen)) . OK Store completed. . CHECK . OK Check completed. . FETCH 815 FLAGS
- 815 FETCH (FLAGS (\Seen)) . OK Fetch completed.
- rc18
. FETCH 815 FLAGS
- 815 FETCH (FLAGS (\Seen)) . OK Fetch completed. . STORE 815 +FLAGS (\Answered)
- 815 FETCH (FLAGS (\Answered \Seen)) . OK Store completed. . CHECK . OK Check completed. . FETCH 815 FLAGS
- 815 FETCH (FLAGS (\Answered \Seen)) . OK Fetch completed.
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Chris Wakelin wrote:
You could try reverting the last CVS update before rc19, http://www.dovecot.org/list/dovecot-cvs/2007-January/007505.html as suggested in the earlier threads:
http://www.dovecot.org/list/dovecot/2007-January/018937.html http://www.dovecot.org/list/dovecot/2007-January/019048.html
It seems to have helped me with read/unread flags, but I've still seen some oddities. Reply flags also seem broken. Time for more testing!
Chris
I meant reverting:
http://www.dovecot.org/list/dovecot-cvs/2007-January/007509.html
not 007505, but, as it happens, reverting 007505 as too seems to fix the Reply flags as well, at least in my "debug" imap client (telnet - well, actually "openssl s_client")
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
On 1.2.2007, at 18.10, Chris Wakelin wrote:
http://www.dovecot.org/list/dovecot-cvs/2007-January/007509.html
not 007505, but, as it happens, reverting 007505 as too seems to
fix the Reply flags as well, at least in my "debug" imap client (telnet -
well, actually "openssl s_client")
I don't know why reverting 007509 would fix it, but 7505 was the real
cause. Fixed here:
http://dovecot.org/list/dovecot-cvs/2007-February/007580.html
Timo Sirainen wrote:
On 1.2.2007, at 18.10, Chris Wakelin wrote:
http://www.dovecot.org/list/dovecot-cvs/2007-January/007509.html
not 007505, but, as it happens, reverting 007505 as too seems to fix the Reply flags as well, at least in my "debug" imap client (telnet - well, actually "openssl s_client")
I don't know why reverting 007509 would fix it, but 7505 was the real cause. Fixed here: http://dovecot.org/list/dovecot-cvs/2007-February/007580.html
I'm don't think 7509 did fix it after all, as I had lost some \Seen flags, just not as easily reproducible. I've put back 7505/7509 and applied 7580 and it looks good so far. Certainly \Answered flag is now kept, but in view of my thinking that reverting 7509 had fixed the problems, I'll wait a few days before saying 7580 has done the trick :)
Best Wishes, Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
participants (5)
-
Chris Wakelin
-
Dean Brooks
-
lenny＠edpausa.com
-
Stef Epardaud
-
Timo Sirainen