<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 04.03.2019 um 22:19 schrieb Francis via dovecot <<a href="mailto:dovecot@dovecot.org" class="">dovecot@dovecot.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Le lun. 4 mars 2019 à 12:48, Gerald Galster via dovecot <<a href="mailto:dovecot@dovecot.org" target="_blank" class="">dovecot@dovecot.org</a>> a écrit :<br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class=""><br class=""></div><div class="">Hallo Francis,</div><div class=""><br class=""></div><div class="">have you tried removing the account from your ldap? If dovecot has no information about a particular user, it won't replicate.</div><div class=""><br class=""></div><div class="">Then you would have to delete the mailbox (on both cluster nodes) from the filesystem (rm -rf /path/to/mailbox)</div><div class="">During testing you could move the mailbox somewhere else instead of deleting it, just in case something does not work as expected.</div><div class=""><br class=""></div><div class="">Deleting files on another server could be automated with ssh (ssh keys).</div><div class=""><br class=""></div></div></blockquote></div></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div class="">I'm also using single instance storage for attachments. Because of that, I think I can't just remove the mdbox storage with rm because I'll be stuck with attachments from removed mailboxes. Am I wrong?</div></div></div></div></blockquote><div><br class=""></div><div>you may be right. I don't know if any tools like doveadm deduplicate will check for orphans. </div><div>On a new server you could disable sis and use a filesystem with deduplication instead (e.g. vdo)</div><div><br class=""></div><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_quote"><div class="">This is why I first use doveadm flags/expunge to mark as removed all messages then I use doveadm purge to remove them from storage. I can't use theses commands on deleted/disabled user, I get an error saying the user cannot be found, so I can't remove them from LDAP first.</div></div></div></blockquote></div><div class=""><br class=""></div><div>you could try to stop replication for the user you are deleting:</div><div>doveadm replicator remove [-a replicator_socket_path] username</div><div><br class=""></div><div class="">Best regards</div><div class="">Gerald</div></body></html>