Mailman 3 July 2018 - Mailman-Users

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

spam filter setting to hold makes sender filters useless
by Christoph Groth July 6, 2018

July 6, 2018

Hello, In the mailing list that I administrate I've set a spam filter rule that rejects all mail that matches the header X-Spam-Level: \*{5,} Any messages that match X-Spam-Level: \*{2,} are set on hold. We do this in order to avoid rejecting legitimate mail. However this causes problems with addresses on the discard_these_nonmembers list (that is populated by the mailman message-on-hold page). If a message arrives that is set on hold due to the second spam filter rule, it won't be checked against discard_these_nonmembers, and the list admins are annoyed by it being put on hold. The only solution that I see is to manually create spam filter rules for the most notorious names on the discard_these_nonmembers list. Is there a better way to keep graded response to spam and at the same time use discard_these_nonmembers? Thanks, Christoph

2 1

Unable to start mailman due to time travel
by Phil Stracchino July 4, 2018

July 4, 2018

I have mailman-2.1.26 installed on my Gentoo 17.0 application server, which I just rebooted to update from kernel 4.15.15 to 4.16.13. After rebooting, mailman would not start, logging the following errors: Jul 04 14:43:58 2018 mailmanctl(15743): Traceback (most recent call last): Jul 04 14:43:58 2018 mailmanctl(15743): File "bin/mailmanctl", line 556, in <module> Jul 04 14:43:58 2018 mailmanctl(15743): main() Jul 04 14:43:58 2018 mailmanctl(15743): File "bin/mailmanctl", line 391, in main Jul 04 14:43:58 2018 mailmanctl(15743): lock = acquire_lock(force) Jul 04 14:43:58 2018 mailmanctl(15743): File "bin/mailmanctl", line 215, in acquire_lock Jul 04 14:43:58 2018 mailmanctl(15743): lock = acquire_lock_1(force) Jul 04 14:43:58 2018 mailmanctl(15743): File "bin/mailmanctl", line 203, in acquire_lock_1 Jul 04 14:43:58 2018 mailmanctl(15743): if not force or qrunner_state(): Jul 04 14:43:58 2018 mailmanctl(15743): File "bin/mailmanctl", line 187, in qrunner_state Jul 04 14:43:58 2018 mailmanctl(15743): os.kill(pid, 0) Jul 04 14:43:58 2018 mailmanctl(15743): OSError : [Errno 1] Operation not permitted This looks like it's failing to acquire a lock file. Investigating, I discovered this: minbar:root:/var/lib/mailman/logs:18 # ls -l /var/lib/mailman/locks total 8 -rw-rw-r-- 2 mailman mailman 49 Jul 5 2018 master-qrunner -rw-rw-r-- 2 mailman mailman 49 Jul 5 2018 master-qrunner.minbar.4623 The server itself is pretty clear that today is July 4: minbar:root:/var/lib/mailman/logs:23 # date Wed Jul 4 14:50:09 EDT 2018 After I deleted the errant lock files, mailman started up without hesitation ... and AGAIN created lock files timestamped in the future: minbar:root:/var/lib/mailman/logs:22 # ls -l /var/lib/mailman/locks total 8 -rw-rw-r-- 2 mailman mailman 50 Jul 5 2018 master-qrunner -rw-rw-r-- 2 mailman mailman 50 Jul 5 2018 master-qrunner.minbar.15895 Does anyone have any idea what's going on here? -- Phil Stracchino Babylon Communications phils(a)caerllewys.net phil(a)co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958

2 2