Mailman 3 October 2020 - Mailman-Users

Another Bug in Mailman version 2.1.29 Error
by summersan＠nclack.k12.or.us Oct. 15, 2020

Oct. 15, 2020

Hello, I've been working on migrating an old Mailman 2.1 server over to a new server. I'm currently using Mailman 2.1.29 for the new server. The new server is a CentOS 8 server. The Mailman package that is being used is mailman-3:2.1.29-4.module_el8.0.0+34+0459d3d0.x86_64. When I try to visit the following link in a web browser: server.com/mailman/listinfo, I get the following error: "Bug in Mailman version 2.1.29 / We're sorry, we hit a bug!" with a specific error of: IOError: [Errno 13] Permission denied: '/var/log/mailman/error'. I think this issue is very similar to this past email question: https://mail.python.org/pipermail/mailman-users/2005-December/048349.html But even after setting the group to "mailman" and setting the permissions as suggested in that other post for /var/log/mailman and the files within, I still get the same error. I've tried restarting the server to see if that would help (after reading this: https://bugzilla.redhat.com/show_bug.cgi?id=1733359#c16), and yesterday that seemed to work (because I then got another type of error with Mailman). But when I try to restart the server today, I still get the same Errno 13 error. I think I've even tried setting the /var/log/mailman files to 777 to see if that would temporarily fix the permissions issue, with the same result. I have then tried to disable selinux to see if that would change anything. Surprisingly, I'm able to successfully view Mailman on the server when selinux is disabled. So it works when selinux is disabled! Is there a way that I can keep selinux enabled and still have Mailman work as expected? In answer to that question, it looks like this informational page explains how to allow Mailman to work while selinux is enabled: https://wiki.list.org/DOC/SELinux%20errors%20after%20upgrade%20-%20RedHat I ran the following steps: sudo yum update selinux-policy sudo restorecon -R -v /var/lib/mailman sudo restorecon -R -v /usr/lib/mailman When I re-enabled selinux and tried visiting Mailman on the new server, it appeared to work! Hope this helps someone in the future.

1 0

Help with Topics
by Chip Davis Oct. 13, 2020

Oct. 13, 2020

I'm trying to set up Topics for a Mailman 2.1.33 list I administer, and I'm a tad confused. There appears to be no combination of options to allow a member of a list to see _only_ non-topic-specific postings. If you select one or more topics of interest, you will receive the postings under those topics. You will not receive any _topic-specific_ postings that do not match your selections. Furthermore, if you have also set "Do you want to receive messages that do not match any topic filter?" to 'Yes', you will also receive all messages that are _not_ associated with a topic. Otherwise, you will receive _only_ the postings associated with your selected topics. (This appears to function as expected.) However, if you have not selected any topics, you will receive all postings, whether topic-specific or not, regardless the setting of "Do you want to receive messages that do not match any topic filter?". I would like to offer the members of my lists the option of receiving: 1. All of the postings to the list [All topic categories selected + no-match filter=Yes] 2. Specific topics and all non-topic postings [At least one topic category selected + no-match filter=Yes] 3. Specific topics only [At least one topic category selected + no-match filter=No] 4. Only _non-topic_ postings [No topic categories selected + no-match filter=No] Apparently that is not the heuristic being applied. If no topic categories are selected, the no-match filter setting is ignored (i.e. defaults to 'Yes') effectively delivering all listserver traffic to that user, and eliminating option 4. This is "as documented" and embarrassingly empirically demonstrated. :-/ There seems to be no obvious way to say "I want to see only those postings that are not topic-specific". If I put the list's subject_prefix in as the Topic1 regexp (escaped as necessary), would the member be able to select it and specify 'no-match filter=No' to receive _only_ the non-topic-specific postings? (I would test this question myself, but see "embarrassingly empirically demonstrated", above.) If this question has already been addressed in a document somewhere, please point me to it. Thanks! -Chip-

1 0

"Bug in Mailman version 2.1.29"
by Thomas Gramstad Oct. 5, 2020

Oct. 5, 2020

This is the error message I get when I try to update a picture URL with its current URL, in the file https://mailman.gramstad.no/mailman/edithtml/enag-mausoleum/listinfo.html : Bug in Mailman version 2.1.29 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs. ---- It seems that ANY change of that web page, no matter how trivial, triggers the error message. Thomas Gramstad

2 1

List settings change from mailman admin panel do not apply
by nsk.kuzmich＠gmail.com Oct. 2, 2020

Oct. 2, 2020

Hello, i have set send_reminders to "No" in admin panel, but reminders are still being sent, and according to config_list -o - mylist these settings did not apply: # /usr/lib/mailman/bin/config_list -o - mylist |grep send_ send_reminders = True send_welcome_msg = True send_goodbye_msg = True digest_send_periodic = True On my other server these settings are applied correctly. Permissions on /var/lib/mailman/lists/mylist/config.pck are correct too. What could be the cause of this behavior?

2 1