[Dovecot] Still weird UID ordering issues with maildir

[Reuben Farrelly]

Hi,

On 11/09/2005 11:12 p.m., Timo Sirainen wrote:
> On Thu, 2005-09-01 at 09:30 -0400, Todd Vierling wrote:
>> Nightly 20050829 (includes everything currently in nightly/ChangeLog):
>>
>> Sep  1 09:25:02 server dovecot: imap-login: Login: user=<tv>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.3, TLS
>> Sep  1 09:25:02 server dovecot: IMAP(tv): Maildir /home/tv/.maildir sync: UID < next_uid (1187 < 1188, file = 1125581033.7788_2.server.duh.org:2,)
>>
>> repeated every time I try to login.  I had to nuke the dovecot indexes and
>> let it reindex (which throws off the ordering of some messages).  It had
>> been working without incident since updating to 20050829, until now.
> 
> Actually deleting indexes shouldn't matter at all, since Dovecot does
> that by itself after writing that error message.
> 
> But you're still using it with NFS? Probably somehow related to that..
> The error message means that Dovecot saw a message 1187 that wasn't in
> index, but index said it already had seen message 1188. Probably means
> that the file was temporarily lost in some sync, but later seen again in
> another sync.. Dovecot isn't very forgiving if readdir() skips files.
> 
> Are there other maildir clients than Dovecot updating the maildir? That
> can cause those problems.

I'm seeing this problem occasionally too with -CVS, even on Maildirs where 
there is only one client reading the mail.  Although in this case it was 
Outlook Express, so it may have had more than one concurrent connection to the 
server:

dovecot: Sep 10 19:01:35 Error: imap(archive): Maildir /home/archive/Maildir 
sync: UID inserted in the middle of mailbox (3598 > 3597, file = 
1125940298.P27273Q0M937794.tornado.reub.net:2,)

The UID numbers always seem to be 1 out, like the one above.  I'm not using 
NFS, but am using the CVS version of dovecot-lda for local delivery.

As I had to rebuild my server a week ago, I don't have logs going back any 
further.  However, in the week since I've only had two instances of the error 
above.
Before then, the last instance was with Thunderbird, and from memory I also 
had to wipe the index to get things going.

reuben