[Dovecot] Maildir, imap and newness of messages
I'm using the standard Dovecot 0.99.14 on Fedora Core 4, with a Maildir++ mailbox. I've noticed what I think is an oddity in the way dovecot handles messages:
According to the Maildir specification, a message in Maildir/new is a truly new message, which has not yet been touched by any reader. From an IMAP viewpoint, such a message should have the flag RECENT. However, if a message exists in Maildir/cur, then it means that the message is no longer new (because some other reader has opened the Maildir, and moved the message from new to cur). From an IMAP viewpoint, such a message should NOT have the RECENT flag.
However, dovecot seems to get this wrong. For example, if I have a message in Maildir/new, and I use mutt (a console-based maildir-aware mail client) to open the Maildir, then mutt moves the messages from Maildir/new to Maildir/cur (note here that I haven't actually read the message yet, just opened the Maildir with mutt). I expect that when I now open this Maildir with dovecot imap, and do a "select inbox", it should report "1 EXISTS" and "0 RECENT". However, dovecot reports this as "1 EXISTS" and "1 RECENT".
In my opinion, this is a bug in Dovecot. Would any of the developers like to comment?
Anand
Anand Buddhdev wrote:
I'm using the standard Dovecot 0.99.14 on Fedora Core 4, with a Maildir++ mailbox. I've noticed what I think is an oddity in the way dovecot handles messages:
My first suggestion would be to check the Change Logs between this (very old) version, and the current to see if this has already been addressed.
Even though I still run 0.99.14, it's not recommended - the latest 1.0beta is the current best option.
-- Curtis Maloney cmaloney@cardgate.net
On 10.2.2006 00:02, "Anand Buddhdev" arb@anand.org wrote:
However, dovecot seems to get this wrong. For example, if I have a message in Maildir/new, and I use mutt (a console-based maildir-aware mail client) to open the Maildir, then mutt moves the messages from Maildir/new to Maildir/cur (note here that I haven't actually read the message yet, just opened the Maildir with mutt). I expect that when I now open this Maildir with dovecot imap, and do a "select inbox", it should report "1 EXISTS" and "0 RECENT". However, dovecot reports this as "1 EXISTS" and "1 RECENT".
In my opinion, this is a bug in Dovecot. Would any of the developers like to comment?
I'm pretty sure this has been fixed to work correctly in 1.0betas.
On Fri, Feb 10, 2006 at 05:12:00PM +0200, Timo Sirainen wrote:
Hi Timo,
However, dovecot seems to get this wrong. For example, if I have a message in Maildir/new, and I use mutt (a console-based maildir-aware mail client) to open the Maildir, then mutt moves the messages from Maildir/new to Maildir/cur (note here that I haven't actually read the message yet, just opened the Maildir with mutt). I expect that when I now open this Maildir with dovecot imap, and do a "select inbox", it should report "1 EXISTS" and "0 RECENT". However, dovecot reports this as "1 EXISTS" and "1 RECENT".
In my opinion, this is a bug in Dovecot. Would any of the developers like to comment?
I'm pretty sure this has been fixed to work correctly in 1.0betas.
I just compiled 1.0b3, and tested, and this bug has been fixed. Thank you for your response.
Anand
participants (3)
-
Anand Buddhdev
-
Curtis Maloney
-
Timo Sirainen