[Dovecot] Maildir files in cur without info
Hi,
I have tried to use the same Maildir dovecot uses with another program and encountered the problem that Dovecot seems to move files from new to cur in maildir-sync.c::maildir_scan_dir without adding an info part. On the page http://cr.yp.to/proto/maildir.html is written that mails have to be renamed to uniq:info when moved to the cur directory.
Could this be a bug in dovecot?
-- http://reboot.animeirc.de http://sylpheed-claws.sourceforge.net/
On Mon, 2004-05-03 at 22:10, Christoph Hohmann wrote:
I have tried to use the same Maildir dovecot uses with another program and encountered the problem that Dovecot seems to move files from new to cur in maildir-sync.c::maildir_scan_dir without adding an info part. On the page http://cr.yp.to/proto/maildir.html is written that mails have to be renamed to uniq:info when moved to the cur directory.
Could this be a bug in dovecot?
So it seems. I hadn't noticed that "have to" part. Here's a fix: http://dovecot.org/patches/maildir.patch
Timo Sirainen tss@iki.fi wrote:
I have tried to use the same Maildir dovecot uses with another program and encountered the problem that Dovecot seems to move files from new to cur without adding an info part.
So it seems. I hadn't noticed that "have to" part. Here's a fix: http://dovecot.org/patches/maildir.patch
Applied it to 0.99.10.4, had to modify the variable names to make it build, tested it and seems to work fine now, thanks.
-- http://reboot.animeirc.de http://sylpheed-claws.sourceforge.net/
Christoph Hohmann wrote:
Hi,
I have tried to use the same Maildir dovecot uses with another program and encountered the problem that Dovecot seems to move files from new to cur in maildir-sync.c::maildir_scan_dir without adding an info part. On the page http://cr.yp.to/proto/maildir.html is written that mails have to be renamed to uniq:info when moved to the cur directory.
Could this be a bug in dovecot?
I've found that placing the files inside of the new directory instead of the cur forces the files to be indexed as the MUA "sees" them as new messages (which in theory, they are to that user/folder).
Not sure if this addresses what you're looking for, but it's how I've gotten around the issue for now.
-Rick
-- Rick Johnson, RHCE #807302311706007 - rjohnson@medata.com Linux/Network Administrator - Medata, Inc. PGP Public Key: https://mail.medata.com/pgp/rjohnson.asc
participants (3)
-
Christoph Hohmann
-
Rick Johnson
-
Timo Sirainen