On Wed, 5 Mar 2003, Andreas Aardal Hanssen wrote: > Is also says that UIDVALIDITY must stay as is or _increase_ for one > mailbox even if the mailbox is deleted and then recreated later on. Some > servers reset UIDVALIDITY when a mailbox is deleted. Those servers are > incompliant with the protocol.
That depends on how you define "reset". If "reset" means "set to zero", then yes. > Today, UIDVALIDITY is delegated through a time(NULL) call, but it should > just be set to 1, then 2, then 3 etc.. In order to guarantee that a > mailbox always receives a higher UIDVALIDITY than what it had before, the > bincimap-<mailbox>-uidvalidity file must be left as "unused" metadata in > the root Maildir. The last time I checked, time was still monotonically increasing. How does "time(NULL)" not guarantee that a UIDVALIDITY of a recreated mailbox is greater than UIDVALIDITY of the previous incarnation of the mailbox? (Probably a related question) Why can't uidvalidity files be kept inside the maildir? -- Charlie
