[Mailman-Users] Order of operation - config files

Beu, Ed (DOA) ed.beu at alaska.gov
Wed May 4 13:48:27 EDT 2016

Hi, I got it working... <comments below>

From: Beu, Ed (DOA)
Sent: Wednesday, May 04, 2016 8:49 AM
To: 'mailman-users at python.org' <mailman-users at python.org>
Subject: Order of operation - config files


We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10. Production version will be running on CentOS.

Since most of our lists are 'Announcement' type lists, I have put the following in the mm_cfg.py file:

>>> The double DEFAULT_DEFAULT on this variable appears to be the only doubled default in the Defaults.py file. And, using it in the same manner in the MM_CFG.py file appears to be the only way to get it to work when creating a new list.

For the occasional 'discussion' list I have created a config file (discuss.config) to import into the new list to change 'Member Moderation' to No, but it does not take effect.

For example, I'm using this command: .../bin> ./newlist -q testdiscuss ed.beu at alaska.gov<mailto:ed.beu at alaska.gov> 12345678;./config_list -i discuss.config testdiscuss
>>> I change the entry in the MM_CFG.py file to:
DEFAULT_DEFAULT_MEMBER_MODERATION = 1            (1 rather than Yes)

>>> used the following statement in my discuss.config file - and it's working now
default_member_moderation = 0

Is it not possible to override the mm_cfg.py file entries with a config_list -i command?
>>> apparently the config_list -i does run after mm_cfg.py!!

Thanks in advance for any assistance!


Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
?Fax: (907)269-6719
* ed.beu at alaska.gov<mailto:ed.beu at alaska.gov>
" http://www.doa.alaska.gov/ets/

More information about the Mailman-Users mailing list