ALLOW_FROM_IS_LIST, FROM_IS_LIST and http://wiki.list.org/pages/viewpage.action?pageId=17891458
Mark,
A suggestion, you might want to change this page:
http://wiki.list.org/pages/viewpage.action?pageId=17891458
...to something like:
"If you have Mailman 2.1.16 or newer, set
ALLOW_FROM_IS_LIST = Yes
in mm_cfg.py and then restart mailman. The from_is_list setting will then appear on the Admin / General page. Set the list's from_is_list setting to either [...]"
I didn't want to edit mm_cfg.py and restart mailman until I knew what I needed to change for from_is_list. I did a fair bit of googling and tail chasing, only finding discussions about ALLOW_FROM_IS_LIST, until I found a page (the dreamhost mailman wiki) that explicitly said from_is_list should show up on General/Admin. Then I guessed that editing mm_cfg.py and restarting might make it show up.
-- Steven J. Owens stevenjowens@gmail.com puff@darksleep.com 412-401-8060
On 07/13/2014 11:04 AM, Steven Owens wrote:
A suggestion, you might want to change this page:
http://wiki.list.org/pages/viewpage.action?pageId=17891458
...to something like:
"If you have Mailman 2.1.16 or newer, set
ALLOW_FROM_IS_LIST = Yes
in mm_cfg.py and then restart mailman. The from_is_list setting will then appear on the Admin / General page. Set the list's from_is_list setting to either [...]"
I have changed it to
If you have Mailman 2.1.16 or newer, set
ALLOW_FROM_IS_LIST = Yes
in mm_cfg.py and then set the list's from_is_list setting on the web admin General Options page to either 'Mung From' or 'Wrap Message'. Even though you will see and can set the setting in the web admin GUI, it is still necessary to restart Mailman after changing mm_cfg.py for the setting to be effective.
Thanks for the input.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
On Sun, Jul 13, 2014 at 6:52 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 07/13/2014 11:04 AM, Steven Owens wrote:
A suggestion, you might want to change this page:
http://wiki.list.org/pages/viewpage.action?pageId=17891458
...to something like:
"If you have Mailman 2.1.16 or newer, set
ALLOW_FROM_IS_LIST = Yes
in mm_cfg.py and then restart mailman. The from_is_list setting will then appear on the Admin / General page. Set the list's from_is_list setting to either [...]"
I have changed it to
If you have Mailman 2.1.16 or newer, set
ALLOW_FROM_IS_LIST = Yes
in mm_cfg.py and then set the list's from_is_list setting on the web admin General Options page to either 'Mung From' or 'Wrap Message'. Even though you will see and can set the setting in the web admin GUI, it is still necessary to restart Mailman after changing mm_cfg.py for the setting to be effective.
To be clear, are you saying that the from_is_list will appear as soon as you save the changed copy of mm_cfg-py, regardless of whether you restart mailman or not?
Thanks for the input.
Thanks for the awesome software.
-- Steven J. Owens stevenjowens@gmail.com puff@darksleep.com 412-401-8060
On 07/13/2014 05:48 PM, Steven Owens wrote:
To be clear, are you saying that the from_is_list will appear as soon as you save the changed copy of mm_cfg-py, regardless of whether you restart mailman or not?
Yes, I'm saying that and that you will be able to set from_is_list via the web GUI as soon as you have updated mm_cfg.py with "ALLOW_FROM_IS_LIST = Yes", but you still have to restart Mailman before the setting becomes effective.
The reason for this is the code which processes the from_is_list setting also checks the ALLOW_FROM_IS_LIST setting and this code is in a handler which runs as part of IncomingRunner which is a persistent process and which won't re-import mm_cfg unless Mailman is restarted, but the web admin CGI is a new process invoked by the web server for each interaction, so it always gets the current mm_cfg.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, Jul 13, 2014 at 9:01 PM, Mark Sapiro <mark@msapiro.net> wrote:
Yes, I'm saying that and that you will be able to set from_is_list via the web GUI as soon as you have updated mm_cfg.py with "ALLOW_FROM_IS_LIST = Yes", but you still have to restart Mailman before the setting becomes effective.
The reason for this is the code which processes the from_is_list setting also checks the ALLOW_FROM_IS_LIST setting and this code is in a handler which runs as part of IncomingRunner which is a persistent process and which won't re-import mm_cfg unless Mailman is restarted, but the web admin CGI is a new process invoked by the web server for each interaction, so it always gets the current mm_cfg.
Cool. Is there a doc anywhere that explains the mailman internals?
-- Steven J. Owens stevenjowens@gmail.com puff@darksleep.com 412-401-8060
On 07/13/2014 06:59 PM, Steven Owens wrote:
Is there a doc anywhere that explains the mailman internals?
Not really for Mailman 2.1. There is a high level description of message flow in comments in Mailman/Queue/IncomingRunner.py, and you can learn a lot by reading Mailman/Defaults.py, but the actual architecture is not well documented.
Mailman 3 is much better in this respect. The distribution contains a fairly complete set of reStructuredText docs for the core and these can be processed by Sphinx into HTML, but it is enough different that an understanding of Mailman 3 internals won't go far in helping understand 2.1.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Steven Owens