Mailman 3 July 2018 - Mailman-Users

Mailman 2.1.29 Release
by Mark Sapiro July 24, 2018

July 24, 2018

I am not so pleased to announce the release of Mailman 2.1.29. It turned out there was a bug in the security fix in 2.1.28 that broke the web admin and listinfo overview pages. This is fixed in Mailman 2.1.29. The patch referred to below has been corrected to fix this bug. There is also a patch attached to <https://bugs.launchpad.net/mailman/+bug/1783417> which applies to 2.1.28 to fix this issue. Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended. Mailman 2.1.28 was a minor security fix release. It also has some i18n updates and a couple of bug fixes and adds the ability to edit list specific templates through the web admin UI in a supported language other than the list's default. See the attached README.txt for details. For details of the security issue, see the report at <https://bugs.launchpad.net/mailman/+bug/1780874> which also includes a patch for those who want to fix this issue without upgrading. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ Mailman 2.1.29 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Mailman Migration 2.1.X to 3.2
by Ryan McClung July 24, 2018

July 24, 2018

Hey All, Looking to migrate 2.1.15 to 3.2. Right now we have a lot of lists and pretty big archives. Is there a best practices for the migration or can anyone offer scripts that have worked for them? Info: 1 -- Mailman 2 server 1 -- Mailman 3 server Both are on the same network.

1 0

Mailman 2.1.28 Security Release
by Mark Sapiro July 23, 2018

July 23, 2018

I am pleased to announce the release of Mailman 2.1.28. Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended. This is a minor security fix release. It also has some i18n updates and a couple of bug fixes and adds the ability to edit list specific templates through the web admin UI in a supported language other than the list's default. See the attached README.txt for details. For details of the security issue, see the report at <https://bugs.launchpad.net/mailman/+bug/1780874> which also includes a patch for those who want to fix this issue without upgrading. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ Mailman 2.1.28 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

enabling reCAPTCHA for older lists
by Jim Popovitch July 23, 2018

July 23, 2018

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I've crossed over into reCAPTCHA hell (voluntarily!).... currently looking for a savior. I have followed all the instructions in Defaults.py, and I have created the google account and setup the site-key and secret-key in mm_cfg.py, and restated MM. (this is v2.1.27) Everything works fine on newly created lists. HOWEVER, older existing lists (from years ago) present the following browser error to the user: reCAPTCHA validation failed: missing-input-response along with the following browser console debug warning: A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept- charset=utf-8 on the form element. I've done diff's of the config-text of a new and old list, and the diff output shows nothing more than domains, filters, privacy differences between each list. What could be set for an older list that would break reCAPTCHAs? - -Jim P. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAltU370ACgkQJxVetMRa JwWWew//dYfSy1wZynpgC0wwqPlDb7utAx+C8vUd1OPsqmalaqucVxSuktu6ltjA EC2Dv96Qh4JJojONwjQOV0mR6dmYOJJhpnJ4+FwV3kL7J8qaKzIMKA6Qjgt5hOiK FpjIQC/+6OOLfdVlTUTMX9o0A1SuhDf2CSgnLcSBSgTJVFgBKI0wyKiZ4KKgsHyg edbU5I4UaS+SsxWW5aN8zyizcCxi08Bh+paG+pFTCRiDKxrGXA0jIyttvX6l6LDj t3hfWfEKmFnXtyNeL0SIA0cKf7yID+RHNF/6Fa57kZ3Co7A/h2e+T3VmDCqs7Kfk LE+hcg5XdSep2eKwAK/kG8rpwMTvT539EN9rFHZMZsYUhQt9BziL9P5jYQZG/MC/ Ue3Xz+O5Qx9wji/3ubtn0d9/NimA7Yvu29WIbyKyKv81Zjyg/iAruJByNJU5wY+L DC2wsk2T4/Bmfs6vvqTcmKqSxuTx3ugHuwwUM9mNAVY/w25M7vF4rfSuQuQ/5Ar3 ln2DY4FsfGx65jIdzH33OPAZA41aynWdh1fdV1AmfZB0rdntexZf0m9oCMIQjzCS PbxFmXdIal1np2IIYW52eaD5hEgyiDi82UaI/lK/A087ZGrFUA0ffeJl30O7p5A7 +zyUqCNUc9YZb/STosMtQ1hP9r/+eCaMzbxg3KDJslW0lCcsjcs= =kXCI -----END PGP SIGNATURE-----

2 2

Changing the senders name in the From line in confirmation mails
by Andre Tann July 22, 2018

July 22, 2018

Hi folks, I've been googling now for a while, but could not find a hint if the following can be done: The sender's name in the from line of a confirmation mail should be changed/inserted. Example: This line: From: newsletter-confirm+7f07b5deb0843fad9ab40ead51ac7e7541cf22d6(a)example.com should be changed to From: My-Company <newsletter-confirm+7f07b5deb0843fad9ab40ead51ac7e7541cf22d6(a)example.com> I found tons of hints how to tweak the subject line, and I already did that BTW. But no clue how to change the name. Any hints? Thanks -- Andre Tann

2 2

digest_send_periodic not sending digests daily when set to Yes
by Scott Neader July 19, 2018

July 19, 2018

Hi all. Running Mailman v2.1.26 on CentOS 6. When the list has digest_send_periodic set to Yes, and a size of 100kb, users are seeing digests with upwards of a week's worth of mail, if the list has been quiet. i.e. it seems to be respecting the 100kb limit, but not the digest_send_periodic setting as Yes (to send the digest daily, no matter the size.) I've confirmed that the senddigests cron runs every day at Noon. Any ideas on other things to check? - Scott

2 1

Can the following be done and as an option contractors available to do it?
by Steven Jones July 13, 2018

July 13, 2018

Hi We have a requirement to move 301 lists (minus defunct lists) on a RHEL6 server and want to migrate to RHEL7 and change our domain name at the same time. Our users email addresses would also need changing from the old domain to the new domain. Moving archives, we would like to move these if possible. We also want to run on https and use something like failtoban to reduce bruteforce attacks we are suffering from. >From what I can read in theory most of this if not all of it is quite possible to move lists? and also this other work? Finally assuming we dont have time or capability to do this in-house where do I go hunting for an external contractor who can do this and document the work in an "as-built" document. regards Steven

2 1

Is there a way to determine which lists are defunct?
by Steven Jones July 13, 2018

July 13, 2018

We have 301 lists on a RHEL6 server and want to migrate to RHEL7 and change our domain name at the same time. So as above, Is there a way to determine which lists are defunct? regards Steven

4 5

Mailman 2.1.18 Security fix release
by Mark Sapiro July 11, 2018

July 11, 2018

This is a heads up. There is a recently identified minor security issue in Mailman 2.1.27 and earlier. This is not something that allows permanent compromise or information leak from your site, but is something that needs to be fixed. This issue has been given CVE ID CVE-2018-13796. I plan to release Mailman 2.1.28 on 24 July, 2018 along with details of the issue and a patch to apply to earlier releases. This is just notification of that plan for those that need to plan ahead. Also, if you are a Mailman translator and you have any updates to your translation, please submit them in some form prior to 24 July so they can be incorporated in the release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 2

Moderation impossible. Debian 9
by Jacques Lavignotte July 6, 2018

July 6, 2018

Hello, is there anything related with Debian 8 to 9 upgrade ? now : mailman 1:2.1.23-1+deb9u2 Moderation in now impossible. I tried to check perms : sudo -u list /var/lib/mailman/bin/check_perms -f -v vérification du gid et du mode pour /var/lib/mailman/locks Mauvais gid pour /var/lib/mailman/locks (Obtenu: root, Attendu list) (réparation) vérification du gid et du mode pour /var/lib/mailman/icons Mauvais gid pour /var/lib/mailman/icons (Obtenu: root, Attendu list) (réparation) Traceback (most recent call last): File "/var/lib/mailman/bin/check_perms", line 391, in <module> checkall() File "/var/lib/mailman/bin/check_perms", line 204, in checkall os.path.walk(d, checkwalk, STATE) File "/usr/lib/python2.7/posixpath.py", line 231, in walk func(arg, top, names) File "/var/lib/mailman/bin/check_perms", line 126, in checkwalk os.chown(path, -1, MAILMAN_GID) OSError: [Errno 1] Operation not permitted: '/var/lib/mailman/icons' Anything I can do ? Thanks, Jacques -- GnuPg : C8F5B1E3 WeUsePGP Because privacy matters http://weusepgp.info/

2 2