Mailman 3 July 2016 - Mailman-Users

delay between delivery to mailman post command and sending out to list
by Nicolas July 28, 2016

July 28, 2016

Hi, I’m running Mailman version 2.1.14 on an Ubuntu 12.04.5 LTS build, with Postfix MTA. I recently noticed up to one hour delays between Postfix delivering messages to command "/var/lib/mailman/mail/mailman post [listname]", and Mailman effectively sending out the message to list members (as evidenced in Postfix log file, email headers, and Mailman logs). The delays are consistent in that each posted message, to any list and with any number of subscriptions (between 1 and 250), is delayed by at least 20 minutes. The Mailman "post" log file /var/log/mailman/post does not indicate the message being posted, until the message is finally being sent out up to one hour after the post. However, the list’s archives, as well as the list’s digest.mbox file, DO contain the posted message immediately after posting, confirming that Mailman did instantly receive the message from Postfix. Similarly, email notifications to admin (new list, memberships, …) suffer from the same delays. There are no errors found in the qrunner, mischief, or smtp log files that give pointers as to why this happens. The system is not under any load to speak of, and Postfix is running fine otherwise, delivering mail to local users and remote recipients instantly. The mail queue is virtually empty. Would running separate, verbose instances of qrunner possibly give me any insight, and how should I go about this? Any input is appreciated. Regards, Nicolas

2 2

Sending mails to all list administrators
by Martin Stein July 28, 2016

July 28, 2016

Hi, I'm looking for an easy way, as site administrator, to send a message to all list administrators. Is there any possibility to set up a autogenerated list with all list administrators of the site or another smooth solution? Regards, Martin -- Martin Stein Attac Deutschland Webteam Attac Deutschland Münchener Str. 48 60329 Frankfurt am Main Mail: martin.stein(a)attac.de

4 5

Is mailman vulnerable to the httpoxy bug?
by Perry E. Metzger July 24, 2016

July 24, 2016

https://httpoxy.org/ seems to impact any python program (among many others) that runs under cgi. Does it cause trouble for mailman? What is a reasonable mitigation? Perry -- Perry E. Metzger perry(a)piermont.com

6 15

Yahoo policy on list messages
by Christian F Buser July 24, 2016

July 24, 2016

I have received several bounce notices for subscribers of my list with the following contents: Action: failed Final-Recipient:rfc822;ekxxxxxka@yahoo.com Status: 5.0.0 Remote-MTA: dns; mta7.am0.yahoodns.net Diagnostic-Code: smtp; 554 5.7.9 Message not accepted for policy reasons. Seehttps://help.yahoo.com/kb/postmaster/SLN7253.html Action: failed Final-Recipient:rfc822;mail@xxxxx-xxxx.info Status: 5.0.0 Remote-MTA: dns; mxcluster1.one.com Diagnostic-Code: smtp; 550 5.7.1 The messages violates the DMARC policy of yahoo.com (eb9fcd83-501a-11e6-b513-b82a72d854f0) Action: failed Final-Recipient:rfc822;mxxxxxw@yahoo.de Status: 5.0.0 Remote-MTA: dns; mx-eu.mail.am0.yahoodns.net Diagnostic-Code: smtp; 554 5.7.9 Message not accepted for policy reasons. Seehttps://help.yahoo.com/kb/postmaster/SLN7253.html I asked my provider for help about this, and he wrote back: "from what I can see from the text files you sent me, it's a matter of the mailing list configuration. The sender ( From: ) needs to be set as the mailing list address and not as the original sender (eg, ekxxxxxka(a)yahoo.com) Read here: https://help.yahoo.com/kb/postmaster/SLN7253.html - but all mailing lists I know usually have the original sender's name in the From-field... So what am I doing wrong here? My list runs on the cPanel 56.0.28 version of Mailman 2.1.20 Thank you, Christian -- Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) Hilfe für Strassenkinder in Ghana: http://www.chance-for-children.org

3 2

DMARC problems
by Richard Johnson July 21, 2016

July 21, 2016

I've been running a number of mailing lists for quite a while and never noticed any problems until I setup one which has some yahoo and hotmail addresses on it. Now I have to deal with the DMARC problem. :( Looking at: https://wiki.list.org/DEV/DMARC I see it says: > In 2.1.16 a from_is_list feature was implemented which if enabled by a site configuration option would offer a list admin the ability to either: > > • Rewrite (Munge) the From: header with the posters name 'via the list' and the list's address and merge the poster's address into Reply-To: or > • Wrap the message as a message/rfc822 sub-part in a MIME format outer message with From: and Reply-To: as above. I'm running 2.1.17 and the only thing I see which seems related to this is the "anonymous list" option under General Options. Is this what's being referred to here, or is there some other "site configuration" (i.e., per-site configuration?) method somewhere? /raj

3 6

Support for Internationalized Domain Names and Email Addresses
by Russ Housley July 21, 2016

July 21, 2016

In August 2010, the IETF published the specifications for Internationalized Domain Names (IDNs) as RFCs 5890 through 5894. In February 2012, the IETF published the specifications for Email Address Internationalization (EAI) as RFC 6530. As far as I can tell, Mailman will not let me include an email address that uses IDN or EAI as a mail list recipient. Has anyone figure out how to use either one of these? Thanks in advance, Russ

4 4

Problems with Membership List and Extraneous Characters in URL
by Mark Graves July 19, 2016

July 19, 2016

I'm running Mailman version 2.1.21. On the web interface Membership Management/Membership List, if I use the Find member and get too many results to show on one screen, the lettered links at the top do not work correctly. The problem is an extraneous U. Here's an example: https://listserv.acog.org/mailman/admin/coding/u'https://listserv.acog.org/mailman/admin/coding/members?letter=b&findmember=…<https://listserv.acog.org/mailman/admin/coding/u'https:/listserv.acog.org/mailman/admin/coding/members?letter=b&findmember=acog.org>' and here's the source from the link on the page: <a href="u'https://listserv.acog.org/mailman/admin/coding/members?letter=b&findmember=…'">B</a>   Is this a bug? I found someone else complaining about this in 2003, but nothing since. Any ideas?

2 2

Error while searching the archives
by Odhiambo Washington July 19, 2016

July 19, 2016

Hi everyone, I have a strange problem here. When I try a search on my list archives, I see this on the browser: Bug in Mailman version 2.1.22 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. And in the error log I see the details here ->: http://gw.kictanet.or.ke/~wash/error.txt Kindly advise what the problem could be. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

2 4

From http to https
by Teijo July 17, 2016

July 17, 2016

Hello, I have Mailman 2.1.22 installed. Web pages are at addresses starting with http, and I'd like to move to https so that all content would be updated to use https. No need to change domain name. Is there any documentation for this (unfortunately I did not find)? Best, Teijo

2 2

Re: [Mailman-Users] MailMan won't send list emails
by Caesar Samsi July 16, 2016

July 16, 2016

Sorry, fixed below ... > On Jul 15, 2016, at 3:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 07/15/2016 11:03 AM, Caesar Samsi wrote: >> Results below, it seems to still translate yugi.us <http://yugi.us> to mail >> >> POSTFIX_MAILMAN_LOCAL_DOMAIN = 'localhost' > > > No! > > VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' > > and then run Mailman's bin/genaliases and verify that the entries in > /var/lib/mailman/data/virtual-mailman are like > > test(a)yugi.us test@localhost > ... > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Result: <test@localhost>: Host or domain name not found. Name service error for name=localhost type=AAAA: Host not found Reporting-MTA: dns; mail.samsi.us <http://mail.samsi.us/> X-Postfix-Queue-ID: 27A383FFFD X-Postfix-Sender: rfc822; caesar(a)samsi.us <mailto:caesar@samsi.us> Arrival-Date: Fri, 15 Jul 2016 16:11:39 -0700 (PDT) Final-Recipient: rfc822; test@localhost Original-Recipient: rfc822;test(a)yugi.us <mailto:test@yugi.us> Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=localhost type=AAAA: Host not found From: Caesar Samsi <caesar(a)samsi.us <mailto:caesar@samsi.us>> Subject: test Date: July 15, 2016 at 4:11:35 PM PDT To: test(a)yugi.us <mailto:test@yugi.us> test mm_cfg.py ======== # -*- python -*- # Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA # 02110-1301 USA """This is the module which takes your site-specific settings. From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example.""" ####################################################### # Here's where we get the distributed defaults. # from Defaults import * ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # #------------------------------------------------------------- # The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'yugi.us' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'mail.samsi.us' #------------------------------------------------------------- # Required when setting any of its arguments. #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'en' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.Exim4.Debian or # /usr/share/mailman/postfix-to-mailman.py) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. MTA='Postfix' SMTPHOST = 'localhost' SMTPPORT = 25 #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us'] VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' virtual-mailman ============ # This file is generated by Mailman, and is kept in sync with the binary hash # file virtual-mailman.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you # know what you're doing, and can keep the two files properly in sync. If you # screw it up, you're on your own. # # Note that you should already have this virtual domain set up properly in # your Postfix installation. See README.POSTFIX for details. # LOOP ADDRESSES START mailman-loop(a)yugi.us mailman-loop@localhost # LOOP ADDRESSES END # STANZA START: test # CREATED: Fri Jul 15 16:09:03 2016 test(a)yugi.us test@localhost test-admin(a)yugi.us test-admin@localhost test-bounces(a)yugi.us test-bounces@localhost test-confirm(a)yugi.us test-confirm@localhost test-join(a)yugi.us test-join@localhost test-leave(a)yugi.us test-leave@localhost test-owner(a)yugi.us test-owner@localhost test-request(a)yugi.us test-request@localhost test-subscribe(a)yugi.us test-subscribe@localhost test-unsubscribe(a)yugi.us test-unsubscribe@localhost # STANZA END: test

2 2