Hi,
running 2.4.16 we noticed something that clearly isn't right. Somehow a
user managed to rename (or rather move) a folder twice at the same time.
The result is an invalid entry in mailboxes.db without the corresponding
folder in the file system. Here's what happened:
Jan 24 18:07:36
Hmf, I should've read the release notes first :( It's fixed in 2.4.17:
Fixed bug #3696: can no longer rename the same mailbox twice, which left
things in a corrupted state if you caught the race.
Sorry for the noise.
I've also filed a bug report:
Interesting, this might solve my problem, too (delayed delete makes
two copies of the mailbox in the DELETED tree). So I'm just going to
have to upgrade.
--Janne
Lainaus Sebastian Hagedorn haged...@uni-koeln.de:
Hmf, I should've read the release notes first :( It's fixed in 2.4.17:
