Mailman-Users August 2016

mailman-users@python.org

31 participants
33 discussions

Add "sender's name/email" to BODY of mail as header?

by Mal

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

4 months, 1 week

Mailman CGI Error-Group mismatch error

by Wang, Mary Y

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

9 months, 2 weeks

Debugging mass invitations using web page interface...

by The Mailing List Server Admin

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

1 year, 9 months

changing domains on Mailman implementation

by Keith Seyffarth

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 years, 9 months

mailman not respecting /etc/postfix/transport ???

by Steve Wehr

I have about 100 mailing lists all using the domain name tunedinweb.com. All the commands to subscribe, etc, come to something(a)tunedinweb.com which come to my server and are processed by mailman. But I also have real email boxes @tunedinweb.com. Those are hosted off my server. So in order to make both mailman and my email work I have postfix configured with tunedinweb.com listed in the mydomains file, but have setup a transport file to tell postfix to redirect any email for something(a)tunedinweb.com to the server where that email is hosted. With lines in transport that look like this: steve(a)tunedinweb.com smtp:mx.emailsrvr.com stevew(a)tunedinweb.com smtp:mx.emailsrvr.com This is all working fine. The issue is that my email address steve(a)tunedinweb.com is also a member of several mailing lists. When mailman tries to send to steve(a)tunedinweb.com I see this error message in the postfix log /var/log/maillog: Jun 6 17:02:08 166941-web1 postfix/smtpd[25836]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 <steve(a)tunedinweb.com>: Recipient address rejected: User unknown in local recipient table; from=<tunedin-temp-bounces+steve=tunedinweb.com(a)tunedinweb.com> to=<steve(a)tunedinweb.com> proto=ESMTP helo=<166941-web1.tunedinweb.com> So it seems that mailman is not respecting the /etc/postfix transport file settings. I want mailman to send mail for those addresses specified in the transport file to the server where that email is hosted. I must be missing something. Can someone explain what is going wrong. Thanks again for your help. _____________________ Steve Wehr Tunedin Web Design <http://www.tunedinweb.com/> 845-246-9643

4 years, 9 months

unsubscriptions due to automatic bounce processing

by Matt Morgan

I recently took over a lot of pre-existing mailman lists for a new client. At least one list was pretty messy. They had automatic bounce processing turned on, but the threshold was high, and reset time was shorter than the typical length of times between postings (it's an announce-only list that goes out about once monthly). So there were a lot of bad addresses. I decided to set it up to clean out the cruft fast, and then I'd temper it back a little. So I set it up like this: bounce_processing: yes bounce_score_threshold: 2.0 bounce_info_stale_after: 63 bounce_you_are_disabled_warnings: 0 bounce_you_are_disabled_warnings_interval: 7 bounce_unrecognized_goes_to_list_owner: no bounce_notify_owner_on_disable: yes bounce_notify_owner_on_removal: yes It appears to have worked, but what I'm confused about is this: the last mailing went out on August 11th, and the list owners got 750 automatic unsubscribes yesterday. "bounce_you_are_disabled_warnings" set to zero is supposed to mean that people are removed "immediately" ... but maybe that means "immediately, once some scheduled script or job runs"? Let me know what controls that, or if I'm maybe going the wrong direction here. I.e., does bounce processing only happens once every few weeks, perhaps? Thanks, Matt

4 years, 10 months

Mailman 2.1.23 release and fix for CVE-2016-6893

by Mark Sapiro

I am pleased to announce the release of Mailman 2.1.23. Python 2.4 is the minimum supported, but Python 2.7 is strongly recommended. This release contains a fix for CVE-2016-6893 which is also attached here as a patch. It also has new features, a few i18n updates and some bug fixes. See the attached README for details. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/ http://mirror.list.org/ Mailman 2.1.23 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Hire consultant to install Mailman 3 on Dreamhost

by Jason Glazer

I am interested in hiring a consultant to install Mailman 3 on a Dreamhost server and migrate a bunch of existing Mailman 2.1.17 mailing lists to Mailman 3. If you are interested, or you know someone that might be able to provide this service, please contact me off list. Thanks Jason Glazer jglazer(a)gard.com -- Jason Glazer, P.E., GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

4 years, 10 months

AOL rejecting connections from mailman servers for DMARC Munging.

by Ted Hatfield

Hey all, Recently my mailman server was flagged by AOL and my messages were rejected with this error. SMTP DATA-2 protocol error: 521 5.2.1 : AOL will not accept delivery of this message. When I queried the AOL Postmaster about this issue this was my response. Few mails from IP xxx.xxx.xxx.xx were getting rejected from one of filters as Reply-to address is same as the TO address. This is caused as one of our filters triggered these emails as spam. I have added protection for your IP. As a good mailing practice, please use a different email address for your reply-to address. It seems to me that since dmarc munging adds the senders address to the reply-to header, if a user receives a copy of their own postings this is the result. Can anyone else confirm that this has happened to them and if so what else can someone do except to wrap the message from senders that implement dmarc rejection as in dmarc_moderation_action? Is there a recommended policy regarding this issue? Ted Hatfield

4 years, 10 months

Update advisory (how to install?)

by Caesar Samsi

Hi there, I recall there was an advisory to update Mailman due to something (security issue?). When is this happening and where can I get the update and how to install it? Thanks, Caesar.

4 years, 10 months