Mailman 3 October 2016 - Mailman-Users

Start qrunner on ElCapitan (MacOS X Server)
by Matthias Schmidt 23 Oct '16

23 Oct '16

Hello, I’m trying to start mailman on startup with ElCapitan. I tried a plist in LaunchDaemons - that was working in the past with the command: /usr/local/mailman/bin/mailmanctl -s start this produces now the error: Service only ran for 2 seconds. Pushing respawn out by 8 seconds the error log says: The master qrunner lock could not be acquired because it appears as if another master qrunner is already running So it starts, creates a lock as localhost … and then it tries to start again. than I created a startup script as described here: https://developer.apple.com/library/content/documentation/MacOSX/Conceptual… and it does … nothing the only thing which works currently is starting it manually with sudo and this is kind of inconvenient I installed mailman manually without using macports or something like that. I hope someone on the list can share some insight here. thanks Matthias

3 6

Recipient disabled due to bounces
by Christian F Buser 21 Oct '16

21 Oct '16

Good morning I just gor a message from Mailman that a list subscription has been disabled because of too many bounces. This is quite okay, I think - but when I look at the Mailman management page, the user is still there as a subscribe. The only difference is the check mark and a "B" in the area "no message (reason)". Of course, he does not receive any more messages, and the "B" probably means because messages have bounced. But why isn't he unsubscribed completely? Thank you for clarifying. Christian -- Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland) Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org

2 1

deleting an accidentally accepted spam posting
by Matt Morgan 21 Oct '16

21 Oct '16

When moderating posts, I forwarded several to myself all at once, saw they were fine, then went back and "accepted" them all at once. Just as I clicked Submit, I saw that one was a new message I hadn't reviewed, and it looked like spam. Too late; I clicked Submit. Fortunately, this list is 100% digest-only with the exception of mail-archive.com, and their spam filtering seems to have killed it there. I loaded digest.mbox with mutt and deleted the offending message, so (I believe) it won't be in the next digest. Is that all I have to do to wipe this from my server? What else? Thanks! Matt

2 1

Message.UserNotification vs Message.OwnerNotification in Handlers/Hold.py
by Jim Popovitch 21 Oct '16

21 Oct '16

SO... I've digging further into Mailman code looking to further improve problems with DMARC. I've noticed that Mailman "hold" notifications (to:list-owner@) fail DMARC (if the mailing list domain has a _dmarc RR) because of a simple code issue..... (not calling it a bug at this point) In Handlers/Hold.py, "held for moderation" notices to posters correctly uses Message.UserNotification() to craft and send the poster a notification. However, notification to list-owners (it really should be list moderators...) also uses Message.UserNotification() rather than Message.OwnerNotification(tomoderators=1). Any thoughts on why?

3 8

What log file do I check for successful transmission to the SMTP server?
by Dominik Hoffmann 15 Oct '16

15 Oct '16

So, all of my testing has so far been with email addresses that have their destination on the same system as the one, on which Mailman is running. I just tried a list that has all external destinations. What log files should I look at to see, what might be going wrong?

2 5

Administrative requests page for migrated lists uses wrong old server fqdn for data submission
by Dominik Hoffmann 15 Oct '16

15 Oct '16

My mailing lists were migrated from a machine running Mac OS X Server 10.6 (Snow Leopard) [let's refer to it by the fdqn old-server.domain.com], where mailman was supplied and supported out of the box. The destination was an OS X Server 10.11 (El Capitan) system running Server 5.2 [let's refer to it by the fdqn new-server.domain.com], which required the manual installation of mailman from source. I copied the requisite directories archives, data, lists and qfiles from /var/mailman/ to /usr/local/mailman/. I then ran /usr/local/mailman/bin/check_perms -f which made sure that these were given the proper permissions for the new system. Let's say my mailing list is named "family." I can now bring up https://new-server.domain.com/mailman/admin/family I can change all settings to my heart's content, and they all take. However, when I try to "Tend to pending moderator requests" and click on the Submit All Data button on https://new-server.domain.com/mailman/admindb/family it directs me to http://old-server.domain.com/mailman/admindb/family which has been decommissioned. When editing the list settings, there were references to "old-server.domain.com" in the host_name field on the General Options page, and I changed that to "new-server.domain.com". What do I need to fix, in order for the button submission to go through properly?

2 4

Understanding the flow of outgoing mails
by Henrik Rasmussen 15 Oct '16

15 Oct '16

I am trying to understand the Mailman mailflow and I am aware that stopping a mail from being distributed is not a trivial task. I've looked around and found this*) ,but it doesn't really explain the problem I am facing. By accident, a list admin released a bunch of mail-replies to the list-address from people wanting to unsubscribe. The list contains 9000+ members. To quickly work around the problem, I set a filter in Postfix rejecting all mails containing the particular subject and moved all outgoing mails from /var/spool/mailman/out to out.org, and thought I was home safe, but it seems that the list keeps putting mails with subject Unsubscribe in the out directory. Does Mailman have another queue that I need to empty or filter out? *) https://mail.python.org/pipermail/mailman-users/2014-September/077857.html Henrik Rasmussen

2 3

one mailing list shunting messages
by Knight, Eric 14 Oct '16

14 Oct '16

I am not sure what to do about this message in error log, any help appreciated. Oct 13 11:47:30 2016 (12368) SHUNTING: 1476372076.1651051+54a50f9eb22730094aba33728b8cee7136dad7e2 Oct 13 11:47:30 2016 (12368) Uncaught runner exception: local variable 'bodylen' referenced before assignment Oct 13 11:47:30 2016 (12368) Traceback (most recent call last): File "/usr/server/sulists/Mailman/Queue/Runner.py", line 119, in _oneloop self._onefile(msg, msgdata) File "/usr/server/sulists/Mailman/Queue/Runner.py", line 190, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/server/sulists/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/server/sulists/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/server/sulists/Mailman/Handlers/Hold.py", line 187, in process if bodylen/1024.0 > mlist.max_message_size: UnboundLocalError: local variable 'bodylen' referenced before assignment Oct 13 11:47:30 2016 (12368) SHUNTING: 1476376331.709368+f252c549b5b457fe876963e4dba623dd2047e456 E.S. Knight Sr. Systems Programmer Technology Services 205-726-2594 | office esknight(a)samford.edu www.samford.edu 800 Lakeshore Drive, Birmingham, AL 35229

2 1

Cron has issues with gate_news
by Dominik Hoffmann 14 Oct '16

14 Oct '16

There are still a few of things to mop up, after an otherwise successful installation of Mailman on OS X El Capitan with Server 5.2. Every 5 min my admin user account on the server gets an email from the Cron Daemon that has this line: IOError: [Errno 13] Permission denied: '/usr/local/mailman/locks/gate_news.lock.ipheion.hoffmann.homeunix.net.54220.0' Here are my observations: 1. I currently have no file at /usr/local/mailman/locks/ whose name starts with "gate_news". 2. My root Crontab has these lines: # Every 5 mins, try to gate news to mail. You can comment this one out # if you don't want to allow gating, or don't have any going on right now, # or want to exclusively use a callback strategy instead of polling. # 0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python -S /usr/local/mailman/cron/gate_news In other words, the gate_news cron job is commented out. 3. I have run /usr/local/mailman/bin/check_perms -f, but that has had no impact.

2 2

Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman
by Dominik Hoffmann 13 Oct '16

13 Oct '16

Hi: I have followed Allan Herman's March 29, 2013, instructions for installing Mailman on OS X Mountain Lion. The difference is that my system is OS X El Capitan running Server 5.2. Nonetheless, I have not run into any contradictions. It appears that the choices for the locations of the various configuration files made when transitioning from Mac OS X Snow Leopard to Mac OS X Lion to OS X Mountain Lion have remained stable. However, I am now banging my head against the wall, because my server's SMTP logs contain these lines: Oct 11 16:04:04 i----on local[56963]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or directory Allan installs his Mailman deployment in /usr/local/, and I have learned that in one of the more recent iterations of OS X, Apple chose to lock down /usr/share/, so that even the sudo command does not make modifications possible, which I learned, when I tried to create a simlink there. I kept getting the "Operation not permitted." error. I learned that this is due to System Integrity Protection (SIP), introduced in OS X El Capitan. I am now on a quest to locate from where the call to mailman originates, so that I can edit the corresponding configuration file, replacing "/usr/share/" with "/usr/local/". Any pointers would be much appreciated. Dominik Hoffmann

3 9