http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes to work without reading the main index file more than once. Are maildir syncing problems finally fixed now? :) I think the "message sequence out of range" problems are fixed now too. Rest of the important known problems are mostly related to mmap_disable=yes or fcntl_locks_disable=yes settings. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20040524/7ff556d8/attachment-0001.bin>
On Mon, May 24, 2004 at 06:16:39AM +0300, Timo Sirainen wrote:> http://dovecot.org/test/I've upgraded to test12. First glance: May 24 12:32:40 sp dovecot: Dovecot v1.0-test12 starting up May 24 12:32:51 sp dovecot: imap-login: Login: moe [127.0.0.1] May 24 12:32:51 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085306036 -> 1081606448) May 24 12:32:51 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085306036 -> 1081780899) May 24 12:33:00 sp dovecot: imap(moe): Transaction log file /home/moe/Maildir/.INBOX.pureftpd/dovecot.index.log: invalid indexid (1085306036 != 1085394780) May 24 12:33:00 sp dovecot: imap(moe): Transaction log file /home/moe/Maildir/.INBOX.rhythmbox/dovecot.index.log: invalid indexid (1085306036 != 1085394780) May 24 12:34:06 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085306036 -> 1081606459) May 24 12:34:19 sp dovecot: imap-login: Login: moe [127.0.0.1] May 24 12:34:19 sp dovecot: imap(moe): Transaction log file /home/moe/Maildir/.INBOX.gd/dovecot.index.log: invalid indexid (1085306036 != 1085394859)> - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should > be fixedHaven't seen them anymore, seems fine.> - fixes for detecting changes in uidvalidity and external uidnext > changesHumm. I get a lot of these now: May 24 13:48:36 sp dovecot: imap(moe): Maildir sync: UIDVALIDITY changed (1085308074 -> 1081682554) May 24 13:48:43 sp dovecot: imap-login: Login: moe [127.0.0.1] May 24 13:49:06 sp dovecot: imap(moe): file mail-index.c: line 138 (mail_index_mmap): assertion failed: (map->buffer == NULL) May 24 13:49:06 sp dovecot: child 28181 (imap) killed with signal 6> Are maildir syncing problems finally fixed now? :) I think the "message > sequence out of range" problems are fixed now too.> Rest of the important known problems are mostly related to > mmap_disable=yes or fcntl_locks_disable=yes settings.They're both on default for me (commented out). best regards
Hi Timo and list, On May 24, 2004, at 5:16 AM, Timo Sirainen wrote:> > ? - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should > be fixed > ? - fixes for detecting changes in uidvalidity and external uidnext > changes > ? - several fixes and cleanups in index file handling. less code than > before and now changes to index header also go through transaction log. > that should mean that soon I can get mmap_disable = yes to work without > reading the main index file more than once. > > Are maildir syncing problems finally fixed now? :) I think the "message > sequence out of range" problems are fixed now too. > > Rest of the important known problems are mostly related to > mmap_disable=yes or fcntl_locks_disable=yes settings.With test 12 I get a lot of these errors on my test box (using NFS & both settings above set to yes, so this is probably known):> May 24 15:43:57 fruttel dovecot: imap(user at domain.tld): > file_try_lock() failed with file > /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ > dovecot.index.tmp: Operation not supported > May 24 15:43:57 fruttel dovecot: imap(user at domain.tld): file > mail-transaction-log.c: line 710 (mail_transaction_log_file_map): > assertion failed: (start_offset <= end_offset) > May 24 15:43:57 fruttel dovecot: child 1710 (imap) killed with signal 6 > May 24 15:44:02 fruttel dovecot: imap-login: Login: user at domain.tld > [172.31.5.186] > May 24 15:44:02 fruttel dovecot: imap(user at domain.tld): > file_try_lock() failed with file > /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ > dovecot.index.tmp: Operation not supported > May 24 15:44:06 fruttel dovecot: imap-login: Login: user at domain.tld > [172.31.5.186] > May 24 15:44:06 fruttel dovecot: imap(user at domain.tld): > file_try_lock() failed with file > /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ > dovecot.index.tmp: Operation not supportedI can log in and read mail using pop3, but imap won't work using apples "mail.app" or microsofts "outlook express". pop3 stops working after I have tried to log in using imap, until I remove the index* files from the .INBOX/ folder. Pop3 only checked manually, don't know enough of imap's syntax to try manually. My mail.app claims "select" is going wrong. Kind regards, Maikel Verheijen Ladot Nederland BV.
Timo Sirainen <tss at iki.fi> writes:> http://dovecot.org/test/BTW, is NAMESPACE planned for 1.0? -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
Timo Sirainen wrote:> Are maildir syncing problems finally fixed now? :) I think the "message > sequence out of range" problems are fixed now too.I'm not sure if it counts as a problem but after the delivery of some email tonight (again only a few messages arrive every day) I got the following noise from -test12: May 25 03:08:27 myriad dovecot: imap(andrew): Maildir sync: UIDVALIDITY changed (1085364928 -> 1084812656) May 25 03:18:27 myriad dovecot: imap-login: Login: andrew [192.168.0.2] May 25 03:18:27 myriad dovecot: imap(andrew): Transaction log file /home/andrew/Maildir/.INBOX/dovecot.index.log: invalid indexid (1085364928 != 1085451507) I configured dovecot with --debug-enable so perhaps that accounts for the noise? It didn't result in imap dying in the way that my previously reported problem did with -test11 anyway. Andrew