Mailman 3 March 2023 - Mailman-Users

Editing Mailman's text files
by Pete Bell May 8, 2024

May 8, 2024

Hi. I'm a new member of this group but have been running an email list with Mailman for a long time. I am now setting a list up again and want to give a "look and feel" to the list which has more branding of my user group as a whole, and less of a Mailman-feel. I seem to remember that besides editing the public HTML pages, it is possible to edit the text files which Mailman automatically sends out for certain needs (such as 'approve.txt', 'adminsubscribeack.txt', 'invite.txt', and so on). A. Is this still the case? B. If so, where can I find them? (in case they've changed from the ones I have from long ago). C. Where do they need putting, so that Mailman can use them again? It's important that I should tell you that Mailman on my webhosts servers is a "server-wide" installation, and I don't get to edit anything which other clients to their servers need. This would be only for my own use, and as such I need to know where these files go in my own webspace, and how to get Mailman to use them instead of the default ones. I should also say that I have done this before, so unless the facility to do this has been ditched in recent years, I *should* still be able to do it ! Does Mailman perhaps look for these files somewhere in my webspace (which I have to give a specific name), and if it doesn't find them it goes on to find its default versions of these files? Thanks in advance for your help. Pete Bell, UK

3 3

Running two list with same email prefix
by Andrea Cappelli Feb. 27, 2024

Feb. 27, 2024

Hi all, I'm running a mail server with Debian Lenny, MTA is Postfix and i will use postfix-to-mailma.py script to run list I would set up Mailman for running mailing list with same email prefix on different domains, obvious with different list names For example we have ml.domain1.com and ml.domain2.net, i would like to have LISTADDRESS LISTNAME tech(a)ml.domain1.com tech-ml.domain1.com tech(a)ml.domain.2.net tech-ml.domain2.net In this way i can have the same address on differente domains and Mailman (my version is 2.1.11) can distinguish between lists because the list name is different. The list name will be also used to access web interface, so we have http://ml.domain1.com/mailman/admin/tech-ml.domain1.com http://ml.domain2.net/mailman/admin/tech-ml.domain2.net Is possible to accomplish this task? Any idea?

4 5

Hide list address?
by Ricardo Kleemann Nov. 17, 2023

Nov. 17, 2023

Hi, Is there any way to configure Mailman such that, for an announcement-only type list, when a message is sent to the list, the To: shows the member's address, rather than the list address? Some list software allows the ability to hide the list address itself, so that address is not advertised. I couldn't find any configuration specific to that.

7 6

Hevy resource footprint forces backdrop to mailman 2.1
by Martin Lorenz Aug. 5, 2023

Aug. 5, 2023

Greetings, after many years of smoothly running a mailman2 instance I had to migrate my virtual server to a new provider. There I found, that mailman2 was no longer supported and tried to migrate to mailman3 .. with much pain and no success. Mailman3 keeps crashing my v-server and swallows almost every mail sent to any of the migrated lists. So I wanted to switch back to mailman 2.1.39 by installing from the source package and found that this also fails due to missing python2 support. How to solve this? Thank you very much

7 22

Weird spate of AOL and Yahoo 'undeliverable' bounces
by Johnson, Bruce E - (bjohnson) April 23, 2023

April 23, 2023

We sent a message out to our alumni mailing list and got a whole bunch of bounces like this: The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: https://xxxxxxxxxxx/mailman/admin/alumni/bounce From: MAILER-DAEMON(a)yahoo.com<mailto:MAILER-DAEMON@yahoo.com> Subject: Failure Notice Date: March 16, 2023 at 1:57:17 PM MST To: alumni-bounces@lx<mailto:alumni-bounces@lists.pharmacy.arizona.edu>xxxxxxxxxx I'm afraid I wasn't able to deliver the following message. This is a permanent error; I've given up. Sorry it didn't work out. Subject: [Alumni] REMINDER: Join Us | APhA Annual Meeting & Exposition Alumni and Friends Reception Complete with the weird background color Strangely EACH and every one of them was a yahoo or AOL address (Yahoo now owns AOL) Could they be bouncing this based on SPF, DMARC or DKIM issues and just not telling us? -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs

3 2

Yahoo blocking their emails
by annette carter March 11, 2023

March 11, 2023

Please help. Where do I go to stop Yahoo and all of it's associated ISPs from blacklisting my subscribers, please? Annette -

5 7

Modifying Templates
by Odhiambo Washington March 9, 2023

March 9, 2023

My MM2 is installed in /usr/local/mailman2 I have edited two files in /usr/local/mailman2/templates/en/ - archtoc.html and archtocnombox.html However, my changes don't seem to reflect when I access the archives page at: https://lists.kictanet.or.ke/pipermail/kictanet/ Is there something else I need to do? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 2

mass ban
by Francesco Potortì March 7, 2023

March 7, 2023

I manage a distribution list. Sometimes people ask to be unsubscribed. I would like to ban them so they are not subscribed again by mistake. Would it be possible to add a mass banning interface to Postorius? Would it be possible to automatically ban users who write to the -leave address?

2 1

posts building up in /var/spool/mailman/in
by ssaini March 6, 2023

March 6, 2023

Hi, We are running mailman version 2.1.29 [root@listserver in]# rpm -qa|grep mailman mailman-2.1.29-10.module_el8.3.0+548+3169411d.x86_64 In the past 2 days we have noticed mailman posts queueing considerably in the /var/spool/mailman/in directory and some of the posts are either not being processed or very slowly come through after a delay. [root@listserver in]# pwd /var/spool/mailman/in [root@listserver in]# ls -ls | wc -l 991 The runners are running as part the systemctl start mailman command [root@listserver in]# ps -ef|grep runners root 4904 2591 0 11:58 pts/0 00:00:00 grep --color=auto runners [root@listserver in]# ps -ef|grep mailman mailman 1954 1 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/mailmanctl -s start mailman 1956 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 1957 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 1958 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 1959 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 1960 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 1961 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 1962 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 1963 1954 0 11:49 ? 00:00:00 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s root 4907 2591 0 11:58 pts/0 00:00:00 grep --color=auto mailman I've tried to increase Incoming runners from 1 to 2 presuming this may increase processing, which had no effect. qrunner logs doesn't show anything out of the ordinary, only when I stop start the service it logs.w Mar 02 11:47:48 2023 (198033) Master watcher caught SIGTERM. Exiting. Mar 02 11:47:48 2023 (198034) ArchRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:48 2023 (198034) ArchRunner qrunner exiting. Mar 02 11:47:48 2023 (198041) RetryRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:48 2023 (198041) RetryRunner qrunner exiting. Mar 02 11:47:48 2023 (198035) BounceRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:48 2023 (198035) BounceRunner qrunner exiting. Mar 02 11:47:48 2023 (198036) CommandRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198036) CommandRunner qrunner exiting. Mar 02 11:47:48 2023 (198037) IncomingRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:48 2023 (198038) NewsRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198038) NewsRunner qrunner exiting. Mar 02 11:47:49 2023 (198033) Master watcher caught SIGTERM. Exiting. Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198034, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198035, sig: None, sts: 15, class: BounceRunner, slice: 1/1) Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198041, sig: None, sts: 15, class: RetryRunner, slice: 1/1) Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198036, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Mar 02 11:47:48 2023 (198039) OutgoingRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198039) OutgoingRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198039) OutgoingRunner qrunner exiting. Mar 02 11:47:48 2023 (198040) VirginRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198040) VirginRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198040) VirginRunner qrunner exiting. Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198038, sig: 15, sts: None, class: NewsRunner, slice: 1/1) Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198039, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198040, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Mar 02 11:47:49 2023 (198037) IncomingRunner qrunner caught SIGTERM. Stopping. Mar 02 11:47:49 2023 (198037) IncomingRunner qrunner exiting. Mar 02 11:47:49 2023 (198033) Master qrunner detected subprocess exit (pid: 198037, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Mar 02 11:49:59 2023 (1956) ArchRunner qrunner started. Mar 02 11:49:59 2023 (1963) RetryRunner qrunner started. Mar 02 11:49:59 2023 (1960) NewsRunner qrunner started. Mar 02 11:49:59 2023 (1961) OutgoingRunner qrunner started. error logs have this Mar 02 11:38:57 2023 (189330) Unable to retrieve data from https://publicsuffix.org/list/public_suffix_list.dat: <urlopen error [Errno 97] Address family not supported by protocol> Mar 02 11:38:57 2023 (189331) Unable to retrieve data from https://publicsuffix.org/list/public_suffix_list.dat: <urlopen error but I think this is related to some posts to unknown domains. Could I get some advice to find out what else I should be looking into to debug this issue. Kind Regards ssaini

3 3