23 Apr
2010
23 Apr
'10
10:26 p.m.
Hello,
In what situations will Dovecot 1.2.11 rebuild its uidlist? I am using the maildir storage format, and I am also modifying the uidlist manually (so it's possible I could jack* things up). I have found some related code in maildir-uidlist.c: maildir_uidlist_next.
- Blank filename or UID 0
- Any UID not being greater than the proceeding UID
- Any UID being greater than ~4 billion.
- Any UID being greater than the suggested next uid.
- If a filename contains a /
- General header line sanity checking.
Are there any other sections of the code that do sanity checks on dovecot-uidlist (for Maildir type storage)?
And optionally do you agree that maildir_uidlist_set_corrupted is the best place to watch to see if I have mangled the uidlist?
Thanks in advance, Pat
- I insert into dovecot-uidlist manually when I deliver new messages, or discover a message that is not in uidlist for some reason. For compatability reasons I maintain a completely separate cache. If there is a better way to keep the uidlist up to date when the user isn't necessarily accessing the account via dovecot imap, I'm open to suggestions. However my situation is fairly unique I think.