mirror of
https://github.com/mjl-/mox.git
synced 2025-07-10 07:54:40 +03:00
fix bug in imapserver with rename of inbox, and add consistency checks
renaming inbox is special. the mailbox isn't renamed, but its messages moved to a new mailbox. we weren't updating the destination mailbox uidnext with the new messages. the fix not only sets the uidnext correctly, but also renumbers the uids, starting at 1. this also adds a consistency check for message uids and mailbox uidnexts, and for mailbox uidvalidity account nextuidvalidity in "mox verifydata". this also adds command "mox fixuidmeta" (not listed) that fixes up mailbox uidnext and account uidvalidity. and command "mox reassignuids" that will renumber the uids for either one or all mailboxes in an account.
This commit is contained in:
2
doc.go
2
doc.go
@ -390,6 +390,8 @@ on-disk message file and there are no unrecognized files. If option -fix is
|
||||
specified, unrecognized message files are moved away. This may be needed after
|
||||
a restore, because messages enqueued or delivered in the future may get those
|
||||
message sequence numbers assigned and writing the message file would fail.
|
||||
Consistency of message/mailbox UID, UIDNEXT and UIDVALIDITY is verified as
|
||||
well.
|
||||
|
||||
Because verifydata opens the database files, schema upgrades may automatically
|
||||
be applied. This can happen if you use a new mox release. It is useful to run
|
||||
|
Reference in New Issue
Block a user