best pratice - set default MM settings and make them update-save
Dear mailman-experts,
we're running Mailman Core Version 3.3.5 Mailman Core API Version 3.1 Mailman Core Python Version 3.10.4
on Ubuntu 22 with a python venv.
Until now, I modified several files manually to adjust mailmans behavior and have to check several boxes when new lists are created. Is this still the only way to go or are there ways i can make all this more update "save" and kind of default settings?
a, I removed content of /opt/mailman/venv/lib/python3.10/site-packages/mailman/templates/de/list:member:generic:footer.txt
b, I set ... in /opt/mailman/venv/lib/python3.10/site-packages/mailman/styles/base.py mlist.default_member_action = Action.discard mlist.default_nonmember_action = Action.discard mlist.subscription_policy = SubscriptionPolicy.moderate mlist.send_welcome_message = False mlist.archive_policy = ArchivePolicy.never
c, I always have to check the follwing manually in mailman web-interface on new lists:
Settings-->List Idendity -> remove Subject Prefix Settings-->Message Acceptance -> accept immediately DMARC-Mitigation -> replace from ... unconditionally YES
Thank you.
Stefan
I gotta get back to work, but there was a recent (this week or last) thread on exactly this question. You can add a plugin which allows you to create "styles", and then choose them in the list creation form. I think a HyperKitty search for "styles" should bring them up.
Stefan Bauer writes:
Dear mailman-experts,
we're running Mailman Core Version 3.3.5 Mailman Core API Version 3.1 Mailman Core Python Version 3.10.4
on Ubuntu 22 with a python venv.
Until now, I modified several files manually to adjust mailmans behavior and have to check several boxes when new lists are created. Is this still the only way to go or are there ways i can make all this more update "save" and kind of default settings?
a, I removed content of /opt/mailman/venv/lib/python3.10/site-packages/mailman/templates/de/list:member:generic:footer.txt
b, I set ... in /opt/mailman/venv/lib/python3.10/site-packages/mailman/styles/base.py mlist.default_member_action = Action.discard mlist.default_nonmember_action = Action.discard mlist.subscription_policy = SubscriptionPolicy.moderate mlist.send_welcome_message = False mlist.archive_policy = ArchivePolicy.never
c, I always have to check the follwing manually in mailman web-interface on new lists:
Settings-->List Idendity -> remove Subject Prefix Settings-->Message Acceptance -> accept immediately DMARC-Mitigation -> replace from ... unconditionally YES
Thank you.
Stefan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Thank you. That works pretty good. I just made all my settings in base.py and have an eye on that file.
If doing a mass subscribe, nowadays i have to check
Pre Verified If checked, users will not have to verify that their email address is valid.
Is there also a way to have this box checked by default or do not request a verifcation at all? Could not find any flag in base.py.
Thanks.
Stefan
On 5/16/22 07:16, Stefan Bauer wrote:
Is there also a way to have this box checked by default or do not request a verifcation at all? Could not find any flag in base.py.
To have the box checked by default would require a patch to Postorius like this. ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): pre_verified = forms.BooleanField( label=_('Pre Verified'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, users will not have to verify that their ' ``` Not requiring verification at all would require patching Mailman core but would be a bad idea as it could allow someone to subscribe anyone without that person's consent. -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you very much. But this is a _new_ mailman behavior. In previous versions, there was no checkbox at all and mass-subscription was done without any confirmation. Stefan Am Mo., 16. Mai 2022 um 18:35 Uhr schrieb Mark Sapiro <mark@msapiro.net>:
On 5/16/22 07:16, Stefan Bauer wrote:
Is there also a way to have this box checked by default or do not
request a
verifcation at all? Could not find any flag in base.py.
To have the box checked by default would require a patch to Postorius like this. ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form):
pre_verified = forms.BooleanField( label=_('Pre Verified'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, users will not have to verify that their ' ``` Not requiring verification at all would require patching Mailman core but would be a bad idea as it could allow someone to subscribe anyone without that person's consent.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 5/16/22 22:50, Stefan Bauer wrote:
Thank you very much. But this is a _new_ mailman behavior. In previous versions, there was no checkbox at all and mass-subscription was done without any confirmation.
Yes, this was changed in Postorius 1.3.2, see https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-6.
Also see the discussion at https://gitlab.com/mailman/postorius/-/issues/203.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Teilnehmer (3)
-
Mark Sapiro -
Stefan Bauer -
Stephen J. Turnbull