Mailman 3 May 2019 - Mailman-Users

Migrated Mailman to another server
by Ryan McClung 03 Jun '19

03 Jun '19

Greetings, Migrated mailman to another server and updated it. Site Admin can see the pending queue on all lists but the lists owners/administrators cannot. Running Centos7 and current build of mailman. (2.1.15) Lists have been migrated and are functioning properly. Permissions fix finds nothing. Any help appreciated. -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

3 4

Easy question for this crowd
by Chip Davis 02 Jun '19

02 Jun '19

I've supported a dozen Mailman listservers for over a dozen years. This doesn't represent much real effort most of the time. I've had to block specific users often and specific domains rarely, but this is the first time I've had to block an entire TLD. Recently I've been gifted with an inordinate amount of UCE from many different domains under the '.icu' TLD. Since Python RE's are _almost_ the same as the UNIX RE's I used many years ago, if I put ^@.*\.icu$ in discard_these_nonmembers, will it block all domains in that TLD? And not block anyone else? Thanks, -Chip Davis- Mailman 2.1.27 shared host linux 2.6.32-696.18.7.el6.x86_64 cPanel 80.0.10

4 10

question about email automation
by Fabian A. Santiago 01 Jun '19

01 Jun '19

Hello, this is unrelated to using mm itself but was wondering if anyone here had any insight they could share; i run a mailing list on mm 2.x. periodically i send out an event opening email to the list. this is typically followed by a conclusion email at the end of a specific period. in the interim period i would like to send out reminders of the event to the list but would like to automate this task. i want the reminders to be triggered by my opening email and end with my conclusion email. has anyone done this and how? i've looked at ifttt and zapier but wasn't sure. thanks. -- Fabian S. OpenPGP: 0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7

3 2

Why are mails not being sent to all users (mails seem to disappear)?
by Till Dörges 31 May '19

31 May '19

Hello all, we're using mailman-2.1.29 to operate a list where all users are moderated. The MTA used is postfix 3.2.0. Generally everything seems to be working fine. I.e. when I send out an e-mail I have several confirmations that it arrives under the addresses subscribed to the list. However, (at least) for one user the e-mail does not arrive. And I would at least like to find out the reason. But there's no trace of the address in any of the logfiles that should hold an entry (see below). Generally I'm able to send messages using my MUA to the corresponding e-mail address using the very same postfix also delivering the mailman messages. So I'm guessing it's nothing like DMARC problems or the likes. Like I said, what really puzzles me is that I cannot find the address in either /var/log/mail (postfix) or /var/lib/mailman/logs/* (mailman) /var/lib/mailman/logs/error doesn't contain any entries. /var/lib/mailman/logs/bounce does contain some addresses with a bounce score of 1.0 which are for /other/ e-mail addresses also subscribed to the list in question. /var/log/mail contains entries for /some/ of the addresses subscribed (including some bounces), but *not* for all. /var/lib/mailman/logs/smtp gives me a log entry with the original messages and claims to have sent it to 416 recips (which is correct). But overall I'm only able to find roughly half in either /var/log/mail or /var/lib/mailman/logs/*. Why are not all 416 addresses listed in /var/log/mail, assuming that mailman handed 416 mails to postfix? Do I have any chance of finding out what happened to the mails to the addresses which don't appear in any of the log files? Any hints/insights are greatly appreciated! Thanks -- Till -- PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 Wir sind wieder auf dem BSI IT-Sicherheitskongress 21.-23. Mai 2019 – Bonn

4 7

Migrating to a new server with upgraded mailman, should I copy qfiles ?
by Ian Kelling 30 May '19

30 May '19

https://wiki.list.org/DOC/How%20do%20I%20move%20a%20list%20to%20a%20differe…. The linked examples don't show copying the qfiles directory. I'm migrating a very busy server (lists.gnu.org), that always has lots of queue files in the qfiles directory. Shouldn't I copy that directory over too after shutting down mailman? -- Ian Kelling | Senior Systems Administrator, Free Software Foundation GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF https://fsf.org | https://gnu.org

2 1

DMARC message wrapping not working
by Matthew Pounsett 22 May '19

22 May '19

I've got a mailman 2.1.26 install I've taken over. I've attempted to turn on DMARC message wrapping by setting DEFAULT_DMARC_MODERATION_ACTION in my mm_cfg.py file, but it doesn't seem to have had the desired effect. I'm still seeing messages from p=reject domains going out with their original headers, and subscribers being blocked as a result of the bounces. These are the (non-comment) contents of my mm_cfg.py, with the mail domain anonymized: from Defaults import * DEFAULT_URL_HOST = 'lists.example.com' VIRTUAL_HOSTS.clear() add_virtualhost('lists.example.com', 'lists.example.com') DEFAULT_URL_PATTERN = 'https://%s/mailman/' DEFAULT_DMARC_MODERATION_ACTION = 2 The docs say this sets a minimum bar for the per-list configurations, but when I go to look at those they're all still set to 0/Accept, and in the web UI the full range of options is still available. There is a distinct possibility I've got my hands on the wrong config file. This install isn't using the version from the system package manager.. it's a manually compiled install that looks like it has an install prefix of /usr/local/mailman. This file is /usr/local/mailman/Mailman/mm_cfg.py. I don't see an obvious way to get mailman to spit out the full path it's actually checking for the file, but the output of mailman-config suggests it's probably looking in the right place. % ./mailman-config -h Configuration and build information for Mailman Mailman version: 2.1.26 Build Date: Wed May 2 13:10:19 UTC 2018 prefix: /usr/local/mailman var_prefix: /usr/local/mailman mailman_user: mailman mailman_group: mailman mail_group: mail cgi_group: www-data configure_opts: "--with-mail-gid=mail --with-cgi-gid=www-data" I see no mention of mm_cfg.py in the mailman logs.. so nothing clearly indicating it's failing to find the file (nor positive feedback that it has found the file). But I'm not convinced that's the problem anyway, since mailman clearly is picking up the virtual host and list URL settings. Any suggestions for what else I should be looking at to get Mailman to pick up this config change? Thanks!

2 4

Soft deactivation of Digest mode
by per.starback＠lingfil.uu.se 18 May '19

18 May '19

(I'm using Mailman 2.1.29.) I would like to eventually remove Digest mode from a couple of lists, but I don't want to interfere with users who currently use it. Can I remove the choice for new members, but still keep the digests working? I guess just removing the lines about it in the listinfo page and the personal member page for regular subscribers would suffice for me, if that can be achieved. -- Per Starbäck <starback(a)stp.lingfil.uu.se>

2 1

Training Mailman to find email address from NDR
by Andrew Hodgson 16 May '19

16 May '19

Hi, As part of some upgrade projects I am testing using a transactional email service (Sendgrid) and have eventually got bounce forwarding working. However Mailman is not seeing the address in the bounce so is forwarding it to the list owner. I am probably not going to use Sendgrid long-term, as they seem to have a worse reputation than our static IPs, but wanted to know if I could get Mailman to process this bounce somehow? Here is the bounce message, I know I can enable VERP and this problem should go away, but I wanted to see if I could get this working without VERP as we have a large mail traffic on the list. Thanks. Andrew. Received: from o198-37-151-26.outbound-mail.sendgrid.net ([198.37.151.26]) by samwise.hodgsonfamily.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <no-reply(a)sendgrid.net>) id 1hQs8e-0000Nl-9y for bcab-bounces(a)lists.bcab.org.uk; Wed, 15 May 2019 12:32:07 +0100 Date: Wed, 15 May 2019 11:00:09 +0000 To: bcab-bounces(a)lists.bcab.org.uk From: no-reply(a)sendgrid.net Subject: Undelivered Mail Returned to Sender X-Spam-Score: -0.3 (/) X-Spam-Report: BAYES_00=-1.9, HELO_STATIC_HOST=-0.001, INVALID_DATE=1.096, MISSING_MID=0.497, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable --66728b7fa14ce3ed Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Description: Notification This is an automatically generated message from SendGrid. We are sorry to tell you that your email was unable to be delivered to one of its intended recipients. If you require assistance with this, please contact SendGrid support. [TSS04] Messages from 167.89.106.6 temporarily deferred due to user complaint= s - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html --66728b7fa14ce3ed Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Description: Delivery Report X-SendGrid-Sender: bcab-bounces(a)lists.bcab.org.uk Arrival-Date: 2019-05-05 11-00-00 Final-Recipient: rfc822; redacted(a)yahoo.com Original-Recipient: rfc822; redacted(a)yahoo.com Action: failed Status: 4.7.0 Diagnostic-Code: 421 4.7.0 [TSS04] Messages from 167.89.106.6 temporarily def= erred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postm= aster/SLN3434.html --66728b7fa14ce3ed Content-Type: message/rfc822; name=3D"66728b7fa14ce3ed" Content-Disposition: inline; filename=3D"66728b7fa14ce3ed" Content-Transfer-Encoding: binary Content-Description: Undelivered Message DKIM-Signature: v=3D1; a=3Drsa-sha1; c=3Drelaxed/relaxed;=20 d=3Dlists.bcab.org.uk;=20 h=3Dfrom:subject:to:reply-to:mime-version:content-type:content-transfer-enco= ding:list-id:list-unsubscribe:list-archive:list-help:list-subscribe;=20 s=3Ds1; bh=3DHSwHQmEzYnh8RVhCdSgx3+oQCI4=3D; b=3DqbnxUiQh9/93x0IvtPJnds+ UzsUGMTysX0jwFGtM3/aaJ2DkmCOa9RaIOHjhFopdNp2jEdDCN3PvxQeCps2t86G 3s2XXATdnbyBklvfuFDnoZ7kDoDbJbbyh4xKFTdBGWjMhYa1qg6Lz6A4Ey3SYeOr m1uhNPykiWFEriAFs0Bw=3D DKIM-Signature: v=3D1; a=3Drsa-sha1; c=3Drelaxed/relaxed; d=3Dsendgrid.info; = h=3Dfrom:subject:to:reply-to:mime-version:content-type:content-transfer-enco= ding:list-id:list-unsubscribe:list-archive:list-help:list-subscribe;=20 s=3Dsmtpapi; bh=3DHSwHQmEzYnh8RVhCdSgx3+oQCI4=3D; b=3DvLaOMgJkVx4gOD/ISt q2+4i+yYm+BPygXDX+oQSBYKFqD8m6xiSDL6szf/9ggGawmmE7SZXURlPoBd/iEG iL7oUIdYMFmhw7hpf8weXvet3pHpSYjDm/V8x01v5j4e9nldPkIqa0UNRPd/2BaN ggsr2TCLKTtlTmHMm/kJJUGTw=3D Received: by filter0033p3las1.sendgrid.net with SMTP id filter0033p3las1-1221= 3-5CD7FCB8-37 2019-05-12 11:00:09.005418638 +0000 UTC m=3D+233538.834188040 Received: from samwise.hodgsonfamily.org (samwise.hodgsonfamily.org [213.138.= 110.233]) by ismtpd0002p1lon1.sendgrid.net (SG) with ESMTP id z_pYT4dYT-eVrj9RAaq_jQ Sun, 12 May 2019 11:00:08.469 +0000 (UTC) Received: from [::1] (helo=3Dsamwise.hodgsonfamily.org) by samwise.hodgsonfamily.org with esmtp (Exim 4.89) (envelope-from <bcab-bounces(a)lists.bcab.org.uk>) id 1hPmD9-0001xg-KD; Sun, 12 May 2019 12:00:07 +0100 From: bcab-request(a)lists.bcab.org.uk Subject: Bcab Digest, Vol 444, Issue 7 To: bcab(a)lists.bcab.org.uk Reply-To: bcab(a)lists.bcab.org.uk Date: Sun, 12 May 2019 11:00:09 +0000 (UTC) Message-ID: <mailman.1.1557658803.7540.bcab(a)lists.bcab.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: 7bit X-BeenThere: bcab(a)lists.bcab.org.uk X-Mailman-Version: 2.1.29 Precedence: list List-Id: BCAB Discussion List <bcab.lists.bcab.org.uk> List-Unsubscribe: <https://lists.bcab.org.uk/options/bcab>, <mailto:bcab-request@lists.bcab.org.uk?subject=3Dunsubscribe> List-Archive: <https://lists.bcab.org.uk/pipermail/bcab/> List-Help: <mailto:bcab-request@lists.bcab.org.uk?subject=3Dhelp> List-Subscribe: <https://lists.bcab.org.uk/listinfo/bcab>, <mailto:bcab-request@lists.bcab.org.uk?subject=3Dsubscribe> Errors-To: bcab-bounces(a)lists.bcab.org.uk X-SG-EID: CdqM+Q1xrT/kSH2coGhbodTclTkyEKQEtO7KLouUOI9+psGGnYF6zXb7HRiZwFI6WBd= pZoQ+G2T2gJ PFi38sgTGhL9o9OeuLakXU5N+LB7ojKmPXJAXw+RJO/rqiCjQwOgxjJ65jrwb1pFdv1g+rgeWpSP= D4 TRJYSwUf9eT74JrfEt3RStrhQgSdkn8r3XNU7nG7mWZlCBBZpZkPiZlN+g=3D=3D [...] --66728b7fa14ce3ed-- =00

4 6

Re: [Mailman-Users] utf-8 error with all lists
by Jason Morrill 13 May '19

13 May '19

Realizing I didn't respond to the list. So scroll down for my response. Then come back here to continue reading. Now that I have my Python-fu working I'm retesting Mark's suggestion: webserv:~# python Python 2.7.13 (default, Sep 26 2018, 18:42:22) [GCC 6.3.0 20170516] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import string >>> string.lowercase 'abcdefghijklmnopqrstuvwxyz' >>> It appears that lowercase does return an apparent properly lowercased string of letters. So, I'm uncertain why the hand-edited code would function differently. Thanks, Jason Morrill IT Director Child and Family Agency 860-443-2896 x1422 http://www.childandfamilyagency.org/ ________________________________________ From: Jason Morrill Sent: Monday, May 13, 2019 10:29 AM To: Mark Sapiro Subject: RE: [Mailman-Users] utf-8 error with all lists Mark, Thanks for the suggestions and link to the remainder of that prior message thread. I too get the same results related to Python and lowercase. Now, I'm not a Python programmer but can certainly stumble through to sort things out. Here's what I'm seeing: webserv:~# python Python 2.7.13 (default, Sep 26 2018, 18:42:22) [GCC 6.3.0 20170516] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import string >>> lowercase Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'lowercase' is not defined >>> string <module 'string' from '/usr/lib/python2.7/string.pyc'> >>> Per your suggestion I modified /var/lib/mailman/Mailman/Archiver/pipermail.py to set lowercase = 'abcdefghijklmnopqrstuvwxyz' And indeed the issue worked itself out. No more errors and I was able to clear the qfiles/shunt folder too. Per the Python docs, and your info, the string returned by lowercase should be a-z. And it depends upon the locale of the server. Something I've never purposefully changed. In Debian it looks at /etc/locale.gen In that file I see my locale set to be en_US ISO-8859-1 Could that somehow be related to this issue? Thanks, Jason Morrill IT Director Child and Family Agency 860-443-2896 x1422 http://www.childandfamilyagency.org/ ________________________________________ From: Mailman-Users [mailman-users-bounces+morrillj=childandfamilyagency.org(a)python.org] on behalf of Mark Sapiro [mark(a)msapiro.net] Sent: Saturday, May 11, 2019 2:13 PM To: mailman-users(a)python.org Subject: Re: [Mailman-Users] utf-8 error with all lists On 5/10/19 12:37 PM, Jason Morrill wrote: > Since the beginning of May I've had a problem with all messages going through Mailman. They are being delivered to the lists properly but copies are staying in qfiles/shunt > > The errors appearing in the Mailman error.1 log file indicate > " > May 05 10:16:29 2019 (1167) Uncaught runner exception: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte ... > File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor > while i>0 and (L[i-1][0] in lowercase or > UnicodeDecodeError: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte > > May 05 10:16:29 2019 (1167) SHUNTING: 1557065787.914554+25c37ef6e662cc98d41ac9d45855fe04f151e11a > > " > > This is on Debian 9.6 with Python 2.7.13 and Mailman 2.1.23 , all installed from the Debian package manager. > > I've spent several hours hunting around for a potential solution. Then stumbled upon this: > https://mail.python.org/pipermail/mailman-users/2019-March/084243.html If you read the entire thread (which is split in the archive with the second part beginning at <https://mail.python.org/pipermail/mailman-users/2019-March/084266.html>), you will see that I think the issue is that whatever changed in your system at the beginning of May is causing the Python from string import lowercase in /var/lib/mailman/Mailman/Archiver/pipermail.py to import a lowercase object which should be the string 'abcdefghijklmnopqrstuvwxyz', but in fact is longer and has non-ascii accented characters following 'z'. The OP in that thread couldn't verify that that was the case, but I am convinced that it is. There doesn't seem to be a Debian patch to mailman 1:2.1.23-1+deb9u4 that would affect this so it is apparently something in Python or the OS. I am certain that if you start with the base /var/lib/mailman/Mailman/Archiver/pipermail.py and change from string import lowercase at line 13 to lowercase = 'abcdefghijklmnopqrstuvwxyz' the problem will be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/morrillj%40childandfa…

3 2

Re: [Mailman-Users] unshunt does nothing
by Jason Morrill 13 May '19

13 May '19

I believe this issue is related to my other trouble with utf-8. https://mail.python.org/pipermail/mailman-users/2019-May/084435.html Once I hand-edited /var/lib/mailman/Mailman/Archiver/pipermail.py, per the suggestion in that message. I restarted Mailman and ran the unshunt command again. The shunted messages cleared out and no errors appeared. Though there was no positive affirmation the shunted messages were cleared either. Is the 'shunt' command meant to display anything? ==== Per Mark No. All unshunt does is move the .pck files from the shunt queue to the original queue from which they were shunted. It does this silently. The requeued entry is then processed again by the respective qrunner, and this process either succeeds or possibly throws the same exception that caused the shunting in the first place, in which case the message is shunted again. ===== Thanks, Jason Morrill IT Director Child and Family Agency 860-443-2896 x1422 http://www.childandfamilyagency.org/ ________________________________________ From: Mailman-Users [mailman-users-bounces+morrillj=childandfamilyagency.org(a)python.org] on behalf of Mark Sapiro [mark(a)msapiro.net] Sent: Saturday, May 11, 2019 1:45 PM To: mailman-users(a)python.org Subject: Re: [Mailman-Users] unshunt does nothing On 5/10/19 12:46 PM, Jason Morrill wrote: > I have messages accumulating in the qfiles/shunt folder. > > Running unshunt does nothing. Literally. > > No error message, no progress message. The only change I see is the timestamp on the shunted messages is updated to when I ran the unshunt command. This is because the message is restored to it's original queue and processed and throws the same exception that occurred before and is shunted again. Are there new entries in Mailman's error log when you unshunt? > This is on Debian 9.6 with Python 2.7.13 and Mailman 2.1.23 , all installed from the Debian package manager. > > BTW - I've been using Mailman for 10+ years on this machine. It's not a new install and these are not new lists. What changed? Was the Debian package updated? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/morrillj%40childandfa…

1 0