Mailman Core sometimes switches config files without good reason
This was reported on mailman-users@mailman3.org: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/TOBACYQS7VVI3LGPLN7WX6OZAKFYZJ46/
When you run mailman info
in two subsequent runs, mailman changes from using the /etc/mailman3/mailman.cfg
to creating anew config file at $WORKING_DIR/var/etc/mailman.cfg
without any changes.
~/Documents/mm3/core(master) » mailman info
GNU Mailman 3.3.3b1 (Tom Sawyer)
Python 3.9.0 (default, Oct 6 2020, 00:00:00)
[GCC 10.2.1 20200826 (Red Hat 10.2.1-3)]
config file: /etc/mailman3/mailman.cfg
db url: sqlite:////home/maxking/Documents/mm3/core/var/data/mailman.db
devmode: ENABLED
REST root url: http://localhost:8001/3.1/
REST credentials: restadmin:restpass
~/Documents/mm3/core(master) » mailman info
GNU Mailman 3.3.3b1 (Tom Sawyer)
Python 3.9.0 (default, Oct 6 2020, 00:00:00)
[GCC 10.2.1 20200826 (Red Hat 10.2.1-3)]
config file: /home/maxking/Documents/mm3/core/var/etc/mailman.cfg
db url: sqlite:////home/maxking/Documents/mm3/core/var/data/mailman.db
devmode: DISABLED
REST root url: http://localhost:8001/3.1/
REST credentials: restadmin:restpass
While the contents of the mailman.cfg
don't have any layout
configuration, we still should be consistent in picking up the config file.
» cat -p /etc/mailman3/mailman.cfg maxking@angel
[devmode]
enabled: yes
testing: yes
recipient: you@yourdomain.com
[mta]
smtp_port: 9025
lmtp_port: 9024
incoming: mailman.testing.mta.FakeMTA
[archiver.mhonarc]
enable: yes
[archiver.mail_archive]
enable: yes
[archiver.prototype]
enable: yes[mailman]
devmode: enabled