FWIW... the Defaults.py files for Mailman 2.1.20 and 2.1.12 are not identical.
The following statements, including the one I was troubleshooting, do not exist in version 2.1.12. DEFAULT_BOUNCE_NOTIFY_OWNER_ON_BOUNCE_INCREMENT = No DEFAULT_DMARC_WRAPPED_MESSAGE_TEXT = '' DEFAULT_EQUIVALENT_DOMAINS = '' DEFAULT_REGULAR_EXCLUDE_IGNORE = True DEFAULT_RESPOND_TO_POST_REQUESTS = Yes DEFAULT_SUBSCRIBE_AUTO_APPROVAL = [] DEFAULT_SUBSCRIBE_OR_INVITE = No ~Ed -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+ed.beu=alaska....@python.org] On Behalf Of Mark Sapiro Sent: Monday, May 23, 2016 6:20 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Mm_cfg.py not setting attribute On 05/23/2016 05:24 PM, Beu, Ed (DOA) wrote: > > We currently have two instances of Mailman running for test purposes. The > newlist command along with a customized mm_cfg.py file is producing different > results on the two systems. > > Configurations are as follows on these two test systems. > > T1 > Solaris 10 > Mailman 2.1.20 (csw package) > > T2 > CentOS 6.7 (Final) > Mailman 2.1.12 (yum package) > > On the T1 system I am adding the following statement to the mm_cfg.py file: > DEFAULT_RESPOND_TO_POST_REQUESTS = No > > Then, when I run "./newlist -q listname > my.em...@domain.com<mailto:my.em...@domain.com<mailto:my.em...@domain.com%3cmailto:my.em...@domain.com>> > 12345678" the list setting is as desired (respond_to_post_request = No). > > On the T2 system using the same scenario above, the "respond_to_post_request" > attribute does not change from the Defaults.py setting of Yes. It should if you spelled it correctly. > On the T2 system I have tried changing the attribute from > DEFAULT_RESPOND_TO_POST_REQUESTS to just RESPOND_TO_POST_REQUESTS, changed No > to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A number of > combinations, and none work on the CentOS machine. No, no, 0 and False are all essentially equivalent in mm_cfg.py. Changing the name is the same as commenting it or leaving it out. Every setting that Mailman references is defined in Defaults.py. Anything you set in mm_cfg.py that is not a setting mentioned in Defaults.py is ignored. > Do you have any suggestions or recommendations? Our goal is to use the CentOS > system for production, so getting this worked out will be very helpful. Exactly what mm_cfg.py file are you editing on CentOS. I *think* the CentOS package has an mm_cfg.py in /etc/mailman and there is a symlink from /usr/lib/mailman/Mailman/mm_cfg.py to /etc/mailman/mm_cfg.py, but I may be mistaken about that which is why you should see the FAQ article at <https://wiki.list.org/x/12812344>. -- Mark Sapiro <m...@msapiro.net<mailto:m...@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org<mailto:Mailman-Users@python.org> https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/ed.beu%40alaska.gov ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org