You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently, the current way of encrypting mails from legacy users as we do it in bin/mailcrypt-encrypt-maildir is error-prone. In particular, using doveadm fs put crypt ... seems to be dangerous. First, it injects the new mail into the Maildir "outside of dovecot". Second, if you do that at all, the file streaming should happen in /tmp first and the files be moved to /cur or /new only at the very end of altering the file.
According to user feedback, a better solution would be to use doveadm sync -1, e.g. doveadm sync -1 -R -u [email protected] maildir:...old_unencrypted/Maildir
The text was updated successfully, but these errors were encountered:
Apparently, the current way of encrypting mails from legacy users as we do it in
bin/mailcrypt-encrypt-maildir
is error-prone. In particular, usingdoveadm fs put crypt ...
seems to be dangerous. First, it injects the new mail into the Maildir "outside of dovecot". Second, if you do that at all, the file streaming should happen in/tmp
first and the files be moved to/cur
or/new
only at the very end of altering the file.According to user feedback, a better solution would be to use
doveadm sync -1
, e.g.doveadm sync -1 -R -u [email protected] maildir:...old_unencrypted/Maildir
The text was updated successfully, but these errors were encountered: