Hi Timo, I tried the patch and duplicate uid are always there.
Look at this: Sep 6 10:51:30 10.97.1.33 dovecot: lmtp(29909, xxxxxx@unict.it): save: box=INBOX, uid=133197, msgid=<20100906104944.Q92185@>, size=7414, from= Sep 6 10:51:30 10.97.1.33 dovecot: lmtp(29909, xxxxxx@unict.it): T8gcJIyphEzVdAAA27qniQ: msgid=20100906104944.Q92185@pongo.fi.infn.it: saved mail to INBOX Sep 6 10:51:31 10.97.1.33 dovecot: imap(xxxxxx@unict.it): Warning: /virtual1/unict.it/g/xxxxxx//Maildir/dovecot-uidlist: Duplicate file entry at line 883: 1277948239.M332097P873 3.mailcl-mbox1,S=7903,W=8024:2,S (uid 132318 -> 133198) Sep 6 10:51:31 10.97.1.33 dovecot: imap(xxxxxx@unict.it): Warning: /virtual1/unict.it/g/xxxxxx//Maildir/dovecot-uidlist: Duplicate file entry at line 884: 1277952980.M167558P112 43.mailcl-mbox1,S=11228,W=11393:2,S (uid 132319 -> 133199) Sep 6 10:51:31 10.97.1.33 dovecot: imap(xxxxxx@unict.it): Warning: /virtual1/unict.it/g/xxxxxx//Maildir/dovecot-uidlist: Duplicate file entry at line 885: 1277966013.M655255P280 93.mailcl-mbox1,S=23709,W=24249:2,S (uid 132320 -> 133200) Sep 6 10:51:31 10.97.1.33 dovecot: imap(xxxxxx@unict.it): Warning: /virtual1/unict.it/g/xxxxxx//Maildir/dovecot-uidlist: Duplicate file entry at line 886: 1277969233.M852614P116 56.mailcl-mbox1,S=4496,W=4604:2,S (uid 132321 -> 133201) Sep 6 10:51:31 10.97.1.33 dovecot: imap(xxxxxx@unict.it): Warning: /virtual1/unict.it/g/xxxxxx//Maildir/dovecot-uidlist: Duplicate file entry at line 887: 1277970140.M285747P169 43.mailcl-mbox1,S=7601,W=7845:2,RS (uid 132322 -> 133202)
It seems that LMTP process duplicate UID or something related to it. But, duplicate occurs sometime during LMTP delivery and sometime after LMTP delivery with IMAP or POP3.
I hope this helps.
Luca On 09/03/2010 04:59 PM, Timo Sirainen wrote:
On Fri, 2010-09-03 at 15:57 +0100, Timo Sirainen wrote:
On Fri, 2010-09-03 at 15:44 +0100, Timo Sirainen wrote:
The maildir code hasn't changed much since v1.2. Hmm. Except that maildir filenames are now tried to be preserved when copying, so copying messages elsewhere and back does sound like it could cause this (although there is code to prevent it)..
You could try with attached patch to disable this feature and see if it helps.. dsync mirroring will break with it though.
Whops, that patch wasn't enough. This one is. :)