Mailman 3 March 2018 - Mailman-Users

Debugging mass invitations using web page interface...
by The Mailing List Server Admin Sept. 5, 2019

Sept. 5, 2019

Dear Mailman Cognoscenti, I'm helping one of my list owners send out 5K plus invitations to students to subscribe to his mailing list. Our current configuration: Mailman v2.1.20 RHEL v5.11 Semdmail v8.13.8 Apache v2.2.3 Since this was the first time doing this, I suggested breaking the batch input into 3 groups, 50, 500, and the rest. The 50 went fine, as did the 500, but the largest batch gave him a generic web server error: > Internal Server Error > > The server encountered an internal error or misconfiguration and was > unable to complete your request. > > Please contact the server administrator, root(a)conundrum.unh.edu and > inform them of the time the error occurred, and anything you might > have done that may have caused the error. > > More information about this error may be available in the server > error log. I looked at the logs and I couldn't find anything that hinted at what went wrong. So I asked the owner to send me the last back and I'd give it a try. I wrote a script that removed folks already subscribed to his list and split the remaining subscribers up into 6 files with a thousand records each. I just tried uploading the 1st batch of 1K, with the following options: Subscribe these users now... (*) Invite Send welcome message... (*) No Send notifications... (*) No And entered a 7 line paragraph explaining the invitation. I ended up having the same error happen. Looking at the Mailman logs, I can't see any difference before or after my submission. In the HTTPD logs, I see: >> [Fri Aug 26 19:59:23 2016] [warn] [client 132.177.215.132] Timeout >> waiting for output from CGI script >> /usr/local/mailman/cgi-bin/admin, referer: >> https://lists.unh.edu/mailman/admin/campus.connection/members/add >> [Fri Aug 26 19:59:23 2016] [error] [client 132.177.215.132] >> Premature end of script headers: admin, referer: >> https://lists.unh.edu/mailman/admin/campus.connection/members/add So is there an inherent limit to the number of invites that can be submitted via the web form? As a work around, how would I do large invites on behalf of the owner from the command line, including the 'extra text' that is allowed via the web interface? -- Cordially, the UNH Mailing List Server Admins Bill Costa, senior admin (603) 862-3056

2 7

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

Spam Subscriptions
by David Andrews June 4, 2018

June 4, 2018

I have a mailman installation with over 300 lists. It is cPanel, but I am the administrator so have access to command line etc. I have just two lists that receive a bunch of spam subscribes each day -- hundreds of them, in fact. For some reason -- which is good, they are held, so don't go through, not quite sure why. Two questions -- first is there a file I can erase for each list that will get rid of all the held subscriptions, without breaking anything else. I tried once, and my installation broke -- don't know if it is related, but don't want to try again unless I do it right. Secondly, there is some commonality in the subscribe addresses, are there strings I can use to discard the subscribes so I never have to see them. Below are examples, there is a common word, or a common word, a period ., and another common word, then a plus sign + then a 4 5 or 6 character word, all alpha, and @gmail.com Here are examples: dragonommz+ jwmidnight+ nommz.naidoo+ If I could knock these out, it would be helpful. This has happened several times previously, but has always stopped after a few weeks. This time it has been a couple months. Finally, I know it is probably too late in the Mailman2 cycle to get a new feature, but in the web UI, it would be nice if you could delete all deferred subscriptions. You can do so with deferred messages, that are held, but not subscriptions. Thanks! Dave

8 18

(relatively) new DMARC issues - and Gmail
by Lindsay Haisley April 2, 2018

April 2, 2018

I've been working with a From-rewriting tool with code taken from Mailman (thanks, Mark!) and discovered a couple of things which I thought deserved posting about. I expect that they peripherally affect Mailman, too. At some point Amazon (amazon.com) started publishing a DMARC "p=quarantine" policy, which means that any email which gets redirected and hits my dmarc_shield piece is going to have its From address re- written to "postmaster(a)fmp.com" (fmp.com has a proper SPF record). I don't know what Gmail's policy is with regard to "p=quarantine" - whether it rejects such email outright or relegates it to the recipient's spam folder. I know that if the sending site publishes "p=reject", redirected email is refused by Gmail at the front door. I'll have to test the "p=quarantine" behavior. Here's the really annoying thing. My dmarc_shield processor rewrites the From header as per SOP for Mailman with the proper switch turned on. The From header address becomes "postmaster(a)fmp.com" with the original From address in the address comment (from xxx at yyz.com). If the email didn't already have a Reply-To address, the original From address is inserted as the Reply-To address. If a Gmail user replies to such an email, the reply goes to the Reply-To address, but Gmail **whitelists** the From address! Thereafter, any email which comes in with a munged From address is accepted, bypassing Gmail's otherwise pretty good spam filtering. I'm noticing a lot of spam email going out with From addresses for which a DMARC "p=reject" policy is published, which means that any such spam redirected to the Gmail user via FMP is also whitelisted. Bah! It's a fucking war zone out there! The only possible solution here would be to randomize the username portion of the rewritten From address, which makes the email look more like spam, and the Gmail user would end up with a whole lot of useless whitelisted address which would need to be deleted. Not to mention the fact that FMP's mail server might be blocked from sending ANY email to Gmail. -- Lindsay Haisley | "The first casualty when FMP Computer Services | war comes is truth." 512-259-1190 | http://www.fmp.com | -- Hiram W Johnson

4 10

Only one list not working
by Javier March 28, 2018

March 28, 2018

¡Hello to everyone! Only one of my lists does not work, the web interface of this list does. When I send an email the list after a while I receive a message with the rejected connection. In the Postfix log I don't see any errors and the telnet connection works. I don't see any errors in Mailman's logs either, but they are strangely empty. Can you think of what the mistake might be? Thank you in advance. Greetings.

2 2

Mailman backend doesn't work after domain name conversion--help wanted
by Nina Macdonald March 28, 2018

March 28, 2018

A couple of weeks ago, a website called uhills.org was split off from the listservs associated with the community. A new company took over the web site and moved it to 1and1. Because we have over 10 years of archives, taking up a lot of space, I wanted to keep the listservs (primarily one, uhills(a)uhills.org) on my server at Liquid Web. I ended up getting a new domain name, unihills.org and changing the names of the 4 listservs in multiple places to let them run on *uni*hills.org instead of uhills.org. The listservs themselves are running: emails come in and go out, but the backend does not work properly. I am getting an error with the wrong domain name in the error log fairly frequently, but yet I can't create additions to the error log; the errors look like this: Mar 25 23:37:02 2018 (24709) error opening list: uhills_uhills.org , and I have been unable to track down where else the domain name needs to be changed or what actions generate the error message. I am uncertain whether this is what is causing the following problems: * Search for member doesn't work * Changing checkboxes for members doesn't make any difference * Can't delete or approve held postings (they do self-delete after a couple of days) * The login for the private archives doesn't work We are running cpanel on CentOS at Liquid Web. I would appreciate advice. Thank you, Nina Macdonald -- Pixelloom Signature Nina Macdonald Owner & Founder, Pixelloom voicemail: 877 583-3184 cell: 949 422-9227

2 2

Help - Subscribe/unsubscribe broken
by Jeff Polasek March 27, 2018

March 27, 2018

Howdy, I recently updated from mailman 2.1.? to 2.1.26. After this update users can not subscribe or unsubscribe. Here is the error from the mailman log. Any ideas what I need to fix? It may be a database problem? Thanks Jeff Mar 27 08:57:49 2018 admin(21493): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21493): [----- Mailman Version: 2.1.26 -----] admin(21493): [----- Traceback ------] admin(21493): Traceback (most recent call last): admin(21493): File "/var/lib/mailman/scripts/driver", line 117, in run_main admin(21493): main() admin(21493): File "/var/lib/mailman/Mailman/Cgi/subscribe.py", line 113, in main admin(21493): process_form(mlist, doc, cgidata, language) admin(21493): File "/var/lib/mailman/Mailman/Cgi/subscribe.py", line 248, in process_form admin(21493): mlist.AddMember(userdesc, remote) admin(21493): File "/var/lib/mailman/Mailman/MailList.py", line 923, in AddMember admin(21493): cookie = self.pend_new(Pending.SUBSCRIPTION, userdesc) admin(21493): File "/var/lib/mailman/Mailman/Pending.py", line 85, in pend_new admin(21493): evictions = db.setdefault('evictions', {}) admin(21493): AttributeError: Message instance has no attribute 'setdefault' admin(21493): [----- Python Information -----] admin(21493): sys.version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609] admin(21493): sys.executable = /usr/bin/python admin(21493): sys.prefix = /usr admin(21493): sys.exec_prefix = /usr admin(21493): sys.path = ['/var/lib/mailman/pythonlib', '/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages', '/usr/lib/python2.7/dist-packages'] admin(21493): sys.platform = linux2 admin(21493): [----- Environment Variables -----] admin(21493): CONTENT_LENGTH: 97 admin(21493): CONTENT_TYPE: application/x-www-form-urlencoded admin(21493): HTTP_COOKIE: mml+admin=280200000069254aba5a732800000030306232313361323236663763306465363935393631613539633061313537633030623963303764; ajs_anonymous_id=%22d8f8ca92-1109-40e3-9415-0fd09ac14d87%22; _ga=GA1.2.4794311.1490733873; ajs_user_id=null; __utmz=194481448.1521488781.5.2.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided); ajs_group_id=%223ff0c525-2764-40c1-9653-b402a1c34211%22; _hp2_id.4205778290=%7B%22userId%22%3A%222302352706526137%22%2C%22pageviewId%22%3A%225888385097105288%22%2C%22sessionId%22%3A%228880360585997038%22%2C%22identity%22%3Anull%2C%22trackerVersion%22%3A%223.0%22%7D; __utmc=194481448; _gid=GA1.2.1014496654.1522088903; __utma=194481448.4794311.1490733873.1522089078.1522096859.8 admin(21493): SERVER_NAME: mopar.tamu.edu admin(21493): SERVER_PROTOCOL: HTTP/1.1 admin(21493): PYTHONPATH: /var/lib/mailman admin(21493): REMOTE_ADDR: 128.194.139.52 admin(21493): REQUEST_SCHEME: http admin(21493): SCRIPT_NAME: /mailman/subscribe admin(21493): REQUEST_METHOD: POST admin(21493): HTTP_HOST: mopar.tamu.edu admin(21493): PATH_INFO: /mml admin(21493): SERVER_PORT: 80 admin(21493): REMOTE_PORT: 57518 admin(21493): QUERY_STRING: admin(21493): REQUEST_URI: /mailman/subscribe/mml admin(21493): DOCUMENT_ROOT: /var/www/html

2 1

two problems with Mailman 2.1
by Dave Stevens March 26, 2018

March 26, 2018

I?m having a couple of problems with a Mailman 2.1 list. I want to add several addresses as new subscribers so as a first step I added one of them using the mass subscription facility in membership management. Mailman accepted the data but when I subsequently checked the subscriber list it wasn?t there. This has been the case for two days now. Today I checked manually that the recipient address was in fact working and decided to resubscribe using the same method. I enter the data in the text box (I?ve done this several times) then click on the "submit your changes" button below and get this message, ?Error: The form lifetime has expired. (request forgery check)? This happens without any special delay on my part, not more than a few minutes. Please advise. Dave -- "As long as politics is the shadow cast on society by big business, the attenuation of the shadow will not change the substance." -- John Dewey

2 3

Sending domain does not exist but it actually does?
by Jayson Smith March 22, 2018

March 22, 2018

Hi, Lately I've been getting some bounced mail from people at the provider/server plus.com. I've redacted addresses, but this is the error message: <<< 550 #5.1.8 Domain of sender address <xxxxxxx-bounces(a)xxxxxxx.com> does not exist 554 5.0.0 Service unavailable Obviously, the sending domain *does* exist, so I assume it's their problem. Is there anything at all I can do about this? Not all mail to these users bounces. Thanks, Jayson

4 7

Mailman email suffix
by Falk, Fredrik March 22, 2018

March 22, 2018

Hello, I am currently moving a mailman installation from one machine to another, using the same 2.1.15 version. I’ve copied all the configs over; lists, data, archives as well as the Apache & Postfix configs. However, I am a bit surprised that the two systems don’t behave identical. When I create a new list on both systems, I get the welcome email. On the old system the e-mail I receive is coming from listname-bounces.suffix(a)domain.com<mailto:listname-bounces.suffix@domain.com> on behalf of mailman-owner(a)domain.com<mailto:mailman-owner@domain.com> And in the e-mail body there is also the e-mail address present listname-request.suffix(a)domain.com<mailto:listname-request.suffix@domain.com> Now on the new system the e-email is coming from listname-bounces(a)domain.com<mailto:listname-bounces@domain.com> on behalf of mailman-owner(a)domain.com<mailto:mailman-owner@domain.com> In the e-mail body the e-mail is listname-request(a)domain.com<mailto:listname-request@domain.com> So you see, I am missing the “.suffix” part I have not found any setting which would change the behavior like this. Anyone has any idea what I am missing? Thanks! Kind Regards, Fredrik ----------------- Siemens Industry Software GmbH; Anschrift: Franz-Geuer-Str. 10, 50823 Köln; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Urban August, Daniel Trebes; Sitz der Gesellschaft: Köln; Registergericht: Amtsgericht Köln, HRB 84564

2 1