Trying to understand the mailman.cfg from the virtualenv installation guide
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?
[mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1
What is the background of these recommendations?
Thank you for your help! Greetings unite42
On Sun, Sep 8, 2024 at 11:26 AM unite42--- via Mailman-users < mailman-users@mailman3.org> 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?
[mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1
What is the background of these recommendations?
Please take a look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.c...
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
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
Hi Mark,
ср, 11 сент. 2024 г., 06:26 Mark Sapiro <mark@msapiro.net>:
On 9/8/24 01:04, unite42--- via Mailman-users wrote:
[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.
Is there any downsides of using it, so it's not enabled by default?
TIA
Danil
On 9/11/24 01:44, Danil Smirnov via Mailman-users wrote:
Hi Mark,
ср, 11 сент. 2024 г., 06:26 Mark Sapiro <mark@msapiro.net>:
On 9/8/24 01:04, unite42--- via Mailman-users wrote:
[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.
Is there any downsides of using it, so it's not enabled by default?
With verp_delivery_interval set to 1, Mailman delivers a separate VERPed message to the MTA for each recipient whereas without this, Mailman delivers one or a few messages with multiple recipients each. This can have a performance impact.
This is not a consideration for confirmations or personalized deliveries as those messages have only one recipient per message in any case. I.e., there is no performance impact from setting
verp_confirmations: yes verp_personalized_deliveries: yes
This is not the default because there can be issues with some MTAs dealing with the VERPed envelope sender.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Danil Smirnov -
Mark Sapiro -
Odhiambo Washington -
unite42＠disroot.org