Aha! I've managed to reproduce the UIDVALIDITY problem using dovecot-stable-20050411. Sure enough, it appears to be simply that dovecot hasn't updated the UID-NEXT field, so UW-IMAP (actually mailutil) spots larger UIDs, complains, and resets the UIDVALIDITY.
So the fix in dovecot-stable-20050422 should work (which in my limited testing, it does!).
Now, we just need to find out why it's syncing so many messages when it reads a new one. Let me know if there's any more i_info lines I could stick in to find out what's going on.
Does uid=0 (i.e. "sync_loop 0") mean something special? When it was doing all that logging it looks like it sometimes went through the whole mailbox twice. I had a look at the mbox-sync.c file and soon got lost :(
Best Wishes, Chris
Chris Wakelin wrote:
I'm not sure quite why it's happening. I haven't been able to reproduce it on demand yet. The new UIDVALIDITY seem to indicate it's changing as part of the mailutil command (at about 7:15am - UW-IMAP uses time(0) as the value).
I've been using 1.0-stable from yesterday (2005-04-22) and it didn't happen to my AutoSpam folder this morning.
I let you know if I find the cause!
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094