we recently had major problems with a disk system, and had to roll files back from tape.
running "reconstruct -f -r user" mostly did the trick, but some users had issues with the clients not showing them new e-mail messages. what has happened, I think, is that they had messages 1,2,3 in their inbox. then backup runs. then they get another couple of message. their Eudora downloads their headers. then the server crashes, and we get data back from tapes. luckily(?), the backup was consistent, so Cyrus didn't have to recreate cyrus.header etc. however, this also means that UIDVALIDITY didn't change. so, when new messages arrives, message numbers 4 and 5 will be reused, messages Eudora thinks it knows everything about, already. assuming my understanding is correct, I think we need a flag to reconstruct to force bumping up UIDVALIDITY. (a good thing Cyrus uses a timestamp for this -- we don't have to worry about bumping it far enough, it just will.) I'm still at Cyrus 2.1.11. -- Kjetil T.
