On Sun, 2003-01-19 at 21:30, Alexey Melnikov wrote: > > RENAME a b > > CREATE a > > DELETE a > > RENAME b a > Ideally each server must preserve UIDVALIDITY on RENAME, until an older > incarnation of the same mailbox had a bigger UIDVALIDITY. > (In reality most of the servers do the first part, but not the second). In the > latter case the server has to assign a new UIDVALIDITY bigger than > max (current_uidvalidity, previous_uidvalidity).
I don't see any requirement for UIDVALIDITY to grow. Probably easiest way to handle this would be to guarantee a different UIDVALIDITY for each created mailbox, then it wouldn't matter how they were renamed. Using timestamp as UIDVALIDITY works pretty well in practise, unless client creates multiple mailboxes at once. Hmm. Wonder if I should bother fixing this in my server..
