Differences

This shows you the differences between two versions of the page.

--- docs:tips_n_tricks:dovecot.html [27.10.2017 15:26 CEST] – [Monitoring] peter
+++ docs:tips_n_tricks:dovecot.html [01.02.2019 13:36 CET] (current) – [Remediation] peter
@@ Line 12: / Line 12: @@
   doveadm replicator status <username pattern>
 //<username pattern>// is something like ''*@example.com'', ''user@example.com'', ''u*'' or just ''*''
+Run
+  doveadm replicator status '*' | fgrep ' y'
+to find failing mailboxes.
 Times shown are the time passed since last fast/full sync.
@@ Line 18: / Line 24: @@
 Accepts a username pattern as well, but works without it.
-  doveadmin replicator replicate -f <username pattern>
+  doveadm replicator replicate -f <username pattern>
 triggers a new full sync. (Needs to be called twice sometimes?)
-:!: ''doveadm force-resync'' is not related to replication!
+<note tip>''doveadm force-resync'' is not related to replication!</note>
 Credits:
   * https://wiki.dovecot.org/Replication
+==== Deduplication ====
+Sometimes, root cause of replication troubles seem to be duplicated emails. Those might be cleaned up in mailboxes //INBOX// and //Spam// for account //user@example.com// by
+<code bash deduplicate.sh>
+while doveadm deduplicate -u user@example.com mailbox INBOX OR mailbox Spam
+do
+  fgrep -c Message-ID: example.com/user/mail/Spam xid.at/xen/mail/INBOX
+  echo "++++ `date` +++++"
+done
+</code>
+This will run forever ans should be stopped when numbers do not change any more.
 ==== Monitoring ====
-//This solution is for nagios-like montitoring systems//
+//This solution is for nagios-like monitoring systems//
 This needs a //sudo// entry to allow //nagios// running ''doveadm'' as //dovecot//
@@ Line 75: / Line 94: @@
 {{entry>imap}}
 {{entry>email}}
-{{entry>dovect}}
+{{entry>dovecot}}