Repair broken mailboxes
doveadm [-Dv] force-resync [-S socket_path] mailbox
doveadm [-Dv] force-resync [-S socket_path] -Amailbox
doveadm [-Dv] force-resync [-S socket_path] -u user mailbox
Under certain circumstances it may happen, that dovecot(1) is unable to automatically solve problems with mailboxes. In such situations the force-resync command may be helpful. It tries to fix all problems. For sdbox and mdbox mailboxes the storage files will be also checked.
Global doveadm(1) options:
-D
Enables verbosity and debug messages.
-v
Enables verbosity, including progress counter.
Command specific options:
-A
If the -A option is present, the command will be performed for all users. Using this option in combination with system users from userdb { driver = passwd } is not recommended, because it contains also users with a lower UID than the one configured with the first_valid_uid setting.
When the SQL userdb module is used make sure that the iterate_query setting in /etc/dovecot/dovecot-sql.conf.ext matches your database layout. When using the LDAP userdb module, make sure that the iterate_attrs and iterate_filter settings in /etc/dovecot/dovecot-ldap.conf.ext match your LDAP schema. Otherwise doveadm(1) will be unable to iterate over all users.
-Ssocket_path
The option's argument is either an absolute path to a local UNIX domain socket, or a hostname and port (hostname:port), in order to connect a remote host via a TCP socket.
This allows an administrator to execute doveadm(1) mail commands through the given socket.
-uuser/mask
Run the command only for the given user. It's also possible to use '*' and '?' wildcards (e.g. -u *@example.org).
When neither the -A option nor -uuser was specified, the command will be executed with the environment of the currently logged in user.
mailbox
The name of the mailbox to fix. With mdbox all of the mailboxes are fixed, so you can use for example INBOX as the name.
Fix bob's INBOX:
doveadm force-resync -u bob INBOX
Report bugs, including doveconf -n output, to the Dovecot Mailing List <[email protected]>. Information about reporting bugs is available at: http://dovecot.org/bugreport.html