Mailman 3 November 2015 - Mailman-Users

Upgrade instructions
by G. Armour Van Horn June 7, 2025

June 7, 2025

I have a couple of Mailman lists on a server happily running 2.1.9 but I am also a moderator on a very active list that's running on 2.1.12. I do not host this list, just volunteer because I have some experience with Mailman. That list has started to get some significant bounces due to the DMARC issue that isn't addressed in this older version. The host intends to upgrade so that we can address that but they report that they haven't been able to make archives searchable in their experimentation with 2.1.16. I don't know if that search function is part of the more recent versions of Pipermail or if they've installed something else. I'm nervous about attempting to upgrade, given the paucity of documentation for that, particularly the fact that it tells me to use the same configuration options I used for the current install and I haven't a clue what those might have been. If I could find some more robust upgrade docs I'd like to try the upgrade in case I could contribute anything to the problem with the large list. Today I had to clear the bounce flags on 47 members. Not all that hard, but tedious. Van -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! http://www.qotd.org/subscribe.html For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ -----------------------------------------------------------

4 4

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

Using cronjob to remove and add members to a mailing list
by Jerry Barnabee Aug. 10, 2022

Aug. 10, 2022

I want to be able to run a cronjob on my server that uses a php script to add new users and/or remove users from a mailing list. Not having any luck finding any simple examples. My thought is that the php script would get email addresses from a database (which I can do) and then feed them to a mailman command line to either add or remove a user. The cronjob is entered via Cpanel. Have several cronjobs that modify databases but have never tried something that would actually execute a unix command. Thanks, Pineyscripter

3 3

Add "sender's name/email" to BODY of mail as header?
by Mal Feb. 17, 2021

Feb. 17, 2021

I want all mails sent to the list to come from the list's email address... But, in this case, if the user forgets to sign their name at the bottom of their mail body, effectively the mail to the list is anonymous...! Is there a way to add the user name (or email address) to the top of each mail so that the mails have the name of the sender, while the mail itself comes from the list address? I have looked high and low for an answer, but noone seems to have the solution. Thank you! Mal

9 14

Mailman CGI Error-Group mismatch error
by Wang, Mary Y Sept. 10, 2020

Sept. 10, 2020

Hi, I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error? "Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Group mismatch error. Mailman expected the CGI wrapper script to be executed as group "nobody", but the system's web server executed the CGI script as group "apache". Try tweaking the web server to run the script as group "nobody", or re-run configure, providing the command line option `--with-cgi-gid=apache'." Thanks Mary

3 3

changing domains on Mailman implementation
by Keith Seyffarth Sept. 20, 2018

Sept. 20, 2018

Is there an efficient way to change the domain name that mailman is affiliated with? I have two mailing lists that were created for an organization before that organization had their own domain. At the time the organization was sure they did not want their own domain and would not be getting a domain. Since then, they have chosen to get a domain and set up a web site. I would like to move their mailing lists onto their domain. It looks like the process for this is: 1) get the list of subscribers 2) delete the mailing list from the one domain (losing the archives) 3) create the mailing list on the new domain 4) subscribe the list of subscribers This process doesn't seem too difficult, but I would prefer to keep the archives, if possible. Both domains are on the same server, running CentOS7 and PLESK 12.5, if that makes a difference. Thanks, Keith

2 2

DMARC hack
by Allan Hansen April 10, 2016

April 10, 2016

Hi, I have waited almost a year for AOL and Yahoo to admit that they messed up and to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at me because I won’t let them post. A number now have two subscriptions, one for posting (from GMail) and another for receiving the messages. So against my better judgement, I included this hack in Cleanse.py; 22c22 < from email.Utils import formataddr, parseaddr — >from email.Utils import formataddr 69,74d68 < < # Added to deal with DMARC issuej < name, addrs = parseaddr(msg.get('from')) < addrs += '.invalid' < del msg['from'] < msg['from'] = formataddr((name, addrs)) \ No newline at end of file I found it in the discussion list. I don’t get compile errors, but Cleanse.pyc is not being updated. I have stopped and restarted Mailman and I have also rebooted, but same non-action. I have not tried ‘compileall’ and am not eager to, either (permissions, where to invoke, etc). Any suggestions? The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14 Yours, Allan

5 15

utf-8 subjects; extended "." regexp really necessary?
by Adrian Pepper Dec. 3, 2015

Dec. 3, 2015

(Mailman 2.1.12, some local mods, but not around topics...) I had a utf-8 subject I was having difficulty matching with a topic regexp. Eventually I concluded the subject still had newlines in it when it was matched against the regexp. (That is the continuation lines were not joined before matching). And "." would not match the newline character(s)). So, for test purposes... Farmers[_ ]Weekly[\s\S\n\r]*Ac seemed to match my particular test subject. While the following did not. Farmers[_ ]Weekly.*Ac Am I correct in my conclusion that .* won't match newline characters, but <space-chars><not-space-chars><linefeed><carriage-return> will ? (And also, that that is the character class I created). For production I might need to put [\s\S\n\r]* between every pair of characters after a reasonable point in the expression. Unless I can enumerate the possibilities more precisely. (Which will probably result in an even longer looking character class). Empirically I see ?=\n =?utf-8?q?_ after "Weekly" and before "Ac". (And it seems the matching is done on the incoming subject, not the one formatted for resending, which, with my tag, and the utf-8 of an incoming tag pushes the expression entirely onto the second line where I think the ".*" variant (or even [_ ]) would match. More generally, my question applies to any potentially long subject, but utf-8 subjects seem to get longer more easily. There is no header-equivalent line in the body (it's mime anyway). Adrian Pepper

3 2