[Dovecot] 1.0-test12

[Moe Wibble]

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 fixed

Haven't seen them anymore, seems fine.

>  - fixes for detecting changes in uidvalidity and external uidnext 
> changes

Humm. 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