On 9/8/24 01:04, unite42--- via Mailman-users wrote:
Hello,
I'm trying to install Mailman3 following the Virtualenv Installation guide. I would like to understand why the configurations in the displayed mailman.cfg are recommended.
Especially the following two:
[archiver.prototype] enable: yes
"The prototype archiver stores messages individually in var/archives/prototype/LIST_NAME/." https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
Do I need this, when using hyperkitty? Is this a fail-safe recommendation?
The prototype archiver is separate from and independent of HyperKitty. If you are using HyperKitty as an archiver, you don't need the prototype archiver. Note however that if the prototype archiver is not enabled, it can't be used at all, but if it is enabled, it can still be enabled or disabled on a per-list basis.
[mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1
What is the background of these recommendations?
These settings enable VERP for all list messages. This results in more reliable bounce processing.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan