I am aware of this, and I am aware that I should use the purge only for
optimizing iops use. But currently I purge every 2 months or so, so it is
easier to use this to recover with an accidental delete.
If then on the server an archive runs that moves messages, it is annoying that
these
That particular feature seems to work for me as documented. People have to
play first-name games with mass-marketed emails, and clients crash for
various reasons.
On Wednesday, November 30, 2022 9:23:44 AM AKST, Aki Tuomi wrote:
The reason is that MOVING a mail is same COPYING and EXPUNGING
a
The reason is that MOVING a mail is same COPYING and EXPUNGING a mail. mdbox
format retains deleted messages, even if they result from moving. It's not a
queue as such.
With mdbox format you are supposed to run purge periodically in any case.
I am not sure what justina is again rambling
Mails stored as individual files in a "Maildir/" can conceivably be "moved"
within the O/S file system rather than copied, but the default flatfile
Mailbox format does require a copy-and-purge, as far as I know.
/etc/postfix/main.cf:
# DELIVERY TO MAILBOX
#
# The home_mailbox
I think it would be nice to have an option where the moving of messages between
namespaces (by automated server scripts) would not result in messages ending up
in the 'purge' queue.
Currently when you move these copied messages, they end up in the purge queue
combined with messages that users