Mailman 3 July 2015 - Mailman-Users

Re: [Mailman-Users] Nightly Messages Show Problems
by Steve Matzura July 7, 2015

July 7, 2015

This should have gone to the list instead of where it went. On Sat, 04 Jul 2015 07:45:07 -0700, Mark Shapiro <mark(a)msapiro.net> wrote: >These occur because you have installed a crontab which has been >formatted as a system crontab and intended to be installed in a place >like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron. Interesting. I followed the directions at http://www.gnu.org/software/mailman/mailman-install/node41.html which say: If your version of crontab supports the -u option, you must be root to do this next step. Add $prefix/cron/crontab.in as a crontab entry by executing these commands: % cd $prefix/cron % crontab -u mailman crontab.in >System crontabs have an extra field between the days/times and the >command which is the user to run as. In this case, that user (mailman) >is interpreted as part of the command because the crontab is installed >for a user. Should I remove the mailman ones and install it as root instead? >The four are all permissions issues. Since check_perms thinks the >permissions are OK, the issue could be that the user as which the crons >are running is not in the 'mailman' group, or it could be a SELinux or >other policy manager issue. mailman is not a group in root's passwd record. Sounds like the crontab.in needs editing to remove the mailman username from it? >It seems there are at least two mailman crontabs. One is a user crontab >in /var/spool/cron/mailman (or maybe /var/spool/cron/crontabs/mailman or >??) that is not formatted as a user crontab and is responsible for the >/bin/sh: mailman: command not found messages. The other is probably in >/etc/cron.d/mailman and is the one giving the permission exceptions. > >What are the contents of these crontabs? You only want one of these. >Which may be important if there are SELinux issues, but otherwise, it >doesn't matter as long as the one is correct. The two in /etc/cron.d and /var/spool/cron are identical. Here's the contents with the comment lines removed: MAILTO=sm(a)noisynotes.com 0 8 * * * mailman /usr/lib/mailman/cron/checkdbs 0 9 * * * mailman /usr/lib/mailman/cron/disabled 0 12 * * * mailman /usr/lib/mailman/cron/senddigests 0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds 27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip 30 4 * * * mailman /usr/lib/mailman/cron/cull_bad_shunt

2 7

Can't "close" a list
by Bernie Cosell July 7, 2015

July 7, 2015

Sorry to be posting another incredibly dumb question, but after my last go-round [wherein I learned that I had the RE just right but my #@#%$@#$% ISP runs spam assassing *after* mailman] I decided to try "closing" the list. So I checked thet FAQs and the manuals and did what I thought should do the job. In my otherwise empty 'sender filters' I changed: Action to take for postings from non-members for which no explicit action is defined. to "hold" The membership list consists of a single address, and I sent a message to the list from a different address and I was very surprised that it just went through. So I tried a more brute-force thing for my test: I changed List of non-member addresses whose postings will be automatically rejected. to "^.*" And it came right through: From: "Bernie Cosell" <bpcosell(a)email.vccs.edu> Organization: Fantasy Farm Fibers To: testlist(a)cosell.net Date: Mon, 06 Jul 2015 15:38:20 -0400 Is there something else I need to enable or set or something other than the settings on the "sender filters" page to get outsiders blocked? THANKS! /bernie\ -- Bernie Cosell Fantasy Farm Fibers mailto:bernie@fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--

2 2

spam filter not working
by Bernie Cosell July 7, 2015

July 7, 2015

I've looked through the FAQs and the archives and my spam filters *OUGHT* to work. But it seems they're not and I don't know why. I have a spam filter set to 'hold': X-Spam-Level:\s*\*\*\* And a message with these headers just got blasted out to the list: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on box913.bluehost.com X-Spam-Level: ******** X-Spam-Status: No, score=8.0 required=10.0 tests=BAYES_50,HELO_DYNAMIC_IPADDR, HK_RANDOM_REPLYTO,RCVD_IN_PSBL,RDNS_NONE,SPF_NEUTRAL shortcircuit=no autolearn=no version=3.3.2 Do I have the RE wrong somehow? THANKS! /b\ -- Bernie Cosell Fantasy Farm Fibers mailto:bernie@fantasyfarm.com Pearisburg, VA --> Too many people, too few sheep <--

3 6

Unsure what to do with web page "Bug in Mailman version 2.1.20"
by Teijo July 7, 2015

July 7, 2015

Hello, After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only page content I seem to get is "Bug in Mailman version 2.1.20". No matter if I navigate to my Mailman's main page or to the given list's page. One problem is that there seems to be nothing useful in error log, although I set loglevel to debug. I have chrooted Apache some years ago, and it's still chrooted. I have not noticed any other problems with Mailman after server update. Best, Teijo

3 5

merging 2 mailing lists
by Laura Creighton July 7, 2015

July 7, 2015

2 somebodies I know want to merge their mailing lists. They are both lists for recipes for people who have impaired kidney function. A complication is that these lists are hosted on different machines, with completely different names, etc. But picking a third name and setting things up so that posters to both old names get their mail sent to the third place, while receiving a message informing them to use the new address seems to work in testing. The problem is with the archives. They want to change the footers in each of the old list messages to say 'this was posted to old_list, use new_list instead if you want to post a new message' and point to the new archives. I can write a script to do that. But then, having modified the footers they want to store the 2 past archives as 1 archive, so that people who search the thing will get hits wherever the old article was posted. I don't see any out-of-the-box solutions, am I missing something? Laura

5 4

Full List of Lists
by McNutt Jr, William R July 6, 2015

July 6, 2015

Is there a report or accepted technique that I can use to get a list of all the lists on my server, even the unadvertised ones? Bill

2 1

maiman3 demo and VM?
by Sylvain Viart July 5, 2015

July 5, 2015

Hi, Could you point me to some mailman3 online demo, please? I would like to play with turnkey <https://www.turnkeylinux.org/> VM image, I discovered recently, may be it will be a good challenge to have a working mailman3 image in that format? Is there a wiki page or something uptodate with such way how to quickly setup such visualized environment? Regards, Sylvain.

1 0

Unable to access Mailman Web interface
by Steve Matzura July 4, 2015

July 4, 2015

If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the following: Bug in Mailman version 2.1.18-1 Bug in Mailman version 2.1.18-1 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. If that's supposed to be /var/log/mailman/error, the only thing in there is what I posted in my previous message. Maybe the two are related?

3 10

Nightly Messages Show Problems
by Steve Matzura July 4, 2015

July 4, 2015

I guess things are getting better with my new mailman implementation, as I received nine messages overnight I've never gotten before. four are Errno 13 permission denied, five only contain one line: /bin/sh: mailman: command not found The subject fields of these five all begin with the same text telling me they're from Mailman at my node, etc. The rest of the subject field for each message was this: /usr/lib/mailman/cron/cull_bad_shunt /usr/lib/mailman/cron/checkdbs /usr/lib/mailman/cron/disabled /usr/lib/mailman/cron/senddigests /usr/lib/mailman/cron/nightly_gzip Here are the four Errno13 messages: Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/nightly_gzip From: "(Cron Daemon)" <mailman(a){mydomain.com}> Date: Sat, 4 Jul 2015 03:27:02 +0000 (UTC) Traceback (most recent call last): File "/usr/lib/mailman/cron/nightly_gzip", line 158, in <module> main() File "/usr/lib/mailman/cron/nightly_gzip", line 114, in main mlist = MailList.MailList(name, lock=0) File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/usr/lib/mailman/Mailman/MailList.py", line 655, in Load dict, e = self.__load(file) File "/usr/lib/mailman/Mailman/MailList.py", line 620, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/mailman/config.pck' Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/checkdbs From: "(Cron Daemon)" <mailman(a){mydomain.com}> Date: Sat, 4 Jul 2015 08:00:02 +0000 (UTC) Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 211, in <module> main() File "/usr/lib/mailman/cron/checkdbs", line 87, in main mlist = MailList.MailList(name) File "/usr/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock self.__lock.lock(timeout) File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lock/mailman/mailman.lock.{mynode}.Mydomain.com}.3681.0' Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/disabled From: "(Cron Daemon)" <mailman(a){mydomain.com}> Date: Sat, 4 Jul 2015 09:00:02 +0000 (UTC) Traceback (most recent call last): File "/usr/lib/mailman/cron/disabled", line 227, in <module> main() File "/usr/lib/mailman/cron/disabled", line 150, in main mlist = MailList.MailList(listname) File "/usr/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock self.__lock.lock(timeout) File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.4471.0' Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/senddigests From: "(Cron Daemon)" <mailman(a){mydomain.com}> Date: Sat, 4 Jul 2015 12:00:02 +0000 (UTC) Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 106, in <module> main() File "/usr/lib/mailman/cron/senddigests", line 84, in main mlist = MailList.MailList(listname, lock=0) File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/usr/lib/mailman/Mailman/MailList.py", line 655, in Load dict, e = self.__load(file) File "/usr/lib/mailman/Mailman/MailList.py", line 620, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/mailman/config.pck' Thinking a run of check_perms might help, I did so and got (then fixed) this one error, which I reran with -f to fix: /usr/lib/mailman/Mailman/mm_cfg.pyc bad group (has: root, expected mailman) (fixing) Not wanting to overload the list with diagnostics, hope this is sufficient to start. More info on request of course.

2 1

Mailman 2.1.18-1 not respecting add_virtualhost
by Chris Miller July 3, 2015

July 3, 2015

Hello, we recently updated our (vhost patched) Mailman installation from 2.1.14 to 2.1.18-1 (https://launchpad.net/~msapiro) in order to workaround Yahoo's recent change to their SPF policy that this version addresses. Virtual mailing list hosting worked fine up until this upgrade. Here is an example of our mm_cfg.py : VIRTUAL_HOSTS.clear() DEFAULT_EMAIL_HOST = 'list.ourdomain.com' DEFAULT_URL_HOST = 'list.ourdomain.com' DEFAULT_URL_PATTERN = 'http://%s/mailman/' VIRTUAL_HOST_OVERVIEW = On add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost('list.customerdomain.com', 'customerdomain.com') If we change the default values above and run the below command, the available mailing lists move from the old default to the new. bin/withlist -l -a -r fix_url -- All add_virtualhost configuration lines are ignored. Since withlist is able to read the changes in our mm_cfg.py, this does not strike me as an issue with our configure options which were limited : ./configure --prefix=/usr/lib/mailman --with-var-prefix=/var/lib/mailman --with-cgi-gid=apache I am unaware of a method we can use to further debug this, such as a command that would effectively dump out Mailman's configuration options, thus validating if it is even reading the add_virtualhost configuration lines. -- Regards, Chris Chris Miller President - Rocket Scientist ScratchSpace Inc. (831) 621-7928 http://www.scratchspace.com

2 11