[Mailman-Users] Removing the option to delete a list on the Postorious interface
Hi, I have a question on the Postorious web interface in Mailman 3. I have found that a list owner can delete a list through the Postorious interface if they have the role of owner to the list. I wanted to have it either disabled or removed but I am not sure where to look to make changes to it. I would rather remove it from the interface totally so it would be done from the command line. Any help would be greatly appreciated. wesley -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Removing the option to delete a list on the Postorious interface
On 6/14/22 10:55, Wong, Wesley wrote:
Hi, I have a question on the Postorious web interface in Mailman 3. I have
found that a list owner can delete a list through the Postorious interface if
they have the role of owner to the list. I wanted to have it either disabled or
removed but I am not sure where to look to make changes to it. I would rather
remove it from the interface totally so it would be done from the command line.
Any help would be greatly appreciated.
The simplest change would be to edit
postorius/templates/postorius/menu/list_nav.html and remove the line.
```
{% trans 'Delete' %}
```
In addition to the above, you could edit postorius/urls.py and remove
the line
```
re_path(r'^delete$', list_views.list_delete, name='list_delete'),
```
or in older Postorius versions
```
url(r'^delete$', list_views.list_delete, name='list_delete'),
```
to render the `delete` URL unknown.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] What can cause "Munge From" (from_is_list) to have no effect?
I'm having trouble with a Mailman install which I maintain for a charity (2.1.39_1 on FreeBSD 12.3-p5) In diagnosing a DMARC "FAIL" reported in Gmail I notice that some settings are having absolutely no effect: from_is_list dmarc_moderation_action dmarc_quarantine_moderation_action dmarc_none_moderation_action So in my testing today, at no point have I been able to get Mailman to "Munge From" or "Wrap Message" in any way. Other nearby settings work, so I am able to change the config; it's the correct list etc. I've also tried re-starting. Logs in /usr/local/mailman/log aren't showing any errors or hints. As some feedback, an FAQ [*] mentions ALLOW_FROM_IS_LIST; setting this has no impact, not suprising as the source code doesn't seem to mention this string anyway. Reading more carefully, I can see this doesn't apply to the current version; perhaps someone with Wiki access might consider the manner it's written, whilst technically correct, is a little backward/confusing, or removing old information. [*] https://wiki.list.org/DOC/What%20can%20I%20do%20about%20members%20being%20unsubscribed%20by%20bounces%20of%20Yahoo%20user%27s%20posts%20for%20DMARC%20policy%20reasons%3F Many thanks -- Mark -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: What can cause "Munge From" (from_is_list) to have no effect?
On 6/14/22 15:07, Mark Hills wrote: In diagnosing a DMARC "FAIL" reported in Gmail I notice that some settings are having absolutely no effect: from_is_list dmarc_moderation_action dmarc_quarantine_moderation_action dmarc_none_moderation_action So in my testing today, at no point have I been able to get Mailman to "Munge From" or "Wrap Message" in any way. Do you have a definition of `GLOBAL_PIPELINE` in mm_cfg.py or a setting for `pipeline` in the list's config.pck. If so, do these include the `WrapMessage` handler? Other nearby settings work, so I am able to change the config; it's the correct list etc. I've also tried re-starting. Logs in /usr/local/mailman/log aren't showing any errors or hints. As some feedback, an FAQ [*] mentions ALLOW_FROM_IS_LIST; setting this has no impact, not suprising as the source code doesn't seem to mention this string anyway. Reading more carefully, I can see this doesn't apply to the current version; perhaps someone with Wiki access might consider the manner it's written, whilst technically correct, is a little backward/confusing, or removing old information. I changed the line ``` 1) If you have Mailman 2.1.16 or later, set ``` to ``` 1) If you have Mailman 2.1.16 or 2.1.17, set ``` Does that help? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
