Mailman 3 July 2014 - Mailman-Users

Mailman Stats
by Peter Knowles July 25, 2014

July 25, 2014

Hi, Does anyone know of any good statistics scripts that either can email detailed stats to list admins, or even offer stats from within the admin itself? We're using Mailman 2.1.18-1 Thanks in advance! Best Regards, Peter Knowles TPN Solutions Email: pknowles(a)tpnsolutions.com Phone: 604-229-0715 Skype: tpnsupport Website: http://www.tpnsolutions.com

2 1

New install of mailman -- web links point to non-working https address
by James Riemermann July 24, 2014

July 24, 2014

Hi, I just installed mailman on a Centos 6.5 server with Apache, and find that all the links on the web interface are broken because they point to an https:// address with /cgi-bin/ in the address rather than an http:// address that works. The Defaults.py config includes the following line: DEFAULT_URL_PATTERN = 'http://%s/mailman/' rather than the folloowing: DEFAULT_URL_PATTERN = 'https://%s/mailman/cgi-bin/' which was recommended on one web tutorial I have been using for setup. While I wouldn't mind having it work at the SSL/https address, I don't have a working SSL certificate, won't be purchasing one, and would rather not use a self-signed one that pops up security prompts every time someone visits. So, I'm inclined to stick with the less secure http:// I've tried configuring it both ways, changing the DEFAULT_URL_PATTERN and restarting mailman, but either way the site works at http://www.mysite.com/mailman/listinfo/, but all the web links are to https://www.mysite.com/cgi-bin/listinfo/. I've also checked the config files "mm_cfg.py" and "mailman.conf" and don't see anything that is pointing to an https:// address. Any suggestions? I am a novice and appreciate your patience. James

3 2

Re: [Mailman-Users] {Disarmed} Re: unable to access admin interface
by Mark Sapiro July 24, 2014

July 24, 2014

On 07/22/2014 01:56 PM, Chad Rebuck wrote: > I see a related email from a google seach where you pointed someone to > the lock files directory. I suppose this isn't normal? Too many lock > files? > > [root@pogo locks]# pwd > /var/lib/mailman/locks > [root@pogo locks]# ll > total 100K > -rw-rw-r-- 2 http mailman 52 Jul 22 2014 a2-16v-list.lock > -rw-rw-r-- 1 http mailman 52 Jul 20 18:10 a2-16v-list.lock.pogo.19620.0 > -rw-rw-r-- 2 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20307.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20309.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20311.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20312.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20313.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20316.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20323.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20351.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20519.0 > -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20598.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 22:38 a2-16v-list.lock.pogo.20648.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 22:40 a2-16v-list.lock.pogo.20663.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 22:44 a2-16v-list.lock.pogo.20674.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 22:48 a2-16v-list.lock.pogo.20699.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 22:57 a2-16v-list.lock.pogo.20827.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 23:16 a2-16v-list.lock.pogo.20980.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 23:19 a2-16v-list.lock.pogo.20989.0 > -rw-rw-r-- 1 http mailman 52 Jul 20 23:54 a2-16v-list.lock.pogo.21944.0 > -rw-rw-r-- 1 http mailman 50 Jul 21 00:16 a2-16v-list.lock.pogo.406.0 > -rw-rw-r-- 1 http mailman 50 Jul 21 00:20 a2-16v-list.lock.pogo.435.0 > -rw-rw-r-- 1 http mailman 50 Jul 21 00:31 a2-16v-list.lock.pogo.484.0 > -rw-rw-r-- 2 mailman mailman 46 Jul 23 2014 master-qrunner > -rw-rw-r-- 2 mailman mailman 46 Jul 23 2014 master-qrunner.pogo.341 There is definitely a locking issue. It's not that there are too many per se, it's that the list is locked by a defunct process and the lock will never be relinquished. If you cat /var/lib/mailman/locks/a2-16v-list.lock the contents will be the file name of the active lock. Judging from the link count, it's this one -rw-rw-r-- 2 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20307.0 do 'ps -fww 20307' or whatever the PID of the active lock is. If that PID doesn't exist, do rm /var/lib/mailman/locks/a2-16v-list.lock.pogo.19620.0 and wait a few seconds. If all the locks don't clear, repeat until they do. If a PID with the lock does exist, ps -fww will show what it is which may help identfy why it is hung with the list locked. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 16

Best method to interface Mailman3 from custom web application
by ML mail July 24, 2014

July 24, 2014

Hello, I have built a simple mail control panel in PHP where I would like to be able to create new mailing lists, subscribe/unsubscribe members, etc. Now I was wondering what would be the best method for my control panel to do that? I am aware of the following methods: - using SQL to directly speak with mailman3 database - using the REST API What would you recommend and are there any other alternatives? Regards ML

3 3

Approve/Deny moderated posts via email - my failure to understand how
by David July 22, 2014

July 22, 2014

I have the same question as here: Re: [Mailman-Users] Approve/Deny moderated posts via email - my failure to understand how https://www.mail-archive.com/mailman-users@python.org/msg64564.html After reading Mark's reply, I understand a little more, but I still do not have success. The message I receive back is: *Bad approval password given. Held message is still being held.* What is the list password that is required? I have tried the list admin password and the list moderators password. Either those are not the required password or I am putting them in the wrong location in the message. Appreciate any help. Thanks. Regards, David

2 1

Moving Archive Lists
by McGregor, Donald (Don) (CIV) July 22, 2014

July 22, 2014

I had a server blow up on me. It’s dead, Jim, but I have backups of the /usr/local/mailman directory, and I’m attempting to bring it up on a new box with a yum-supplied copy of mailman rather than the old-fashioned hand install. I’ve got the yum-supplied version configured, and can create new lists. But the old archive lists, in the same directory with the same permissions, are not showing up. The yum-supplied new mailman version is not the same as the version on the old server, and I can’t really bring up the old server without some heroic measures. Is there some pck database file I need to upgrade or massage to have the old lists be recognized?

3 5

unable to access admin interface
by Chad Rebuck July 22, 2014

July 22, 2014

I'm not able to access the admin interface. I don't reach the page where I can enter my admin password. The mailman error log doesn't show anything. I'm running mailman 2.1.18-1. This message appears: Gateway Timeout The gateway did not receive a timely response from the upstream server or application.

3 4

Senders' email addresses not in archives
by Conrad G T Yoder July 22, 2014

July 22, 2014

[Using 2.1.17] I just realized that with the DMARC mitigation “Mung From” option turned on, the senders’ email addresses are not showing up in the archives. So, basically impossible to contact them unless replying to the whole list, and/or the original sender put their address somewhere in the body of the message. Is there a way to have their email addresses get into the archives and still have the Mung From option turned on? -Conrad -- Is there a suspect in your family? Contact the Ministry of Information. Ring 100 00 00.

3 4

Need help with mailman bug
by iva.vianello＠crorec.hr July 22, 2014

July 22, 2014

Hello, I desperately need your help. We've been using Mailman newsletter lists for over 4 years now and it always worked fantastic. This morning we've moved to a different hosting / server and Mailman displays this bug: --- 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. -- This message pops up in administration panel when I try to access the page where I usually confirm to send out or delete newsletters. Can you help me? I can't send any newsletters out. Thanks, Iva

2 1

Yahoo webmail stripping out headers in digests
by Conrad G T Yoder July 22, 2014

July 22, 2014

Another episode in the “Just Noticed” saga: In Yahoo’s webmail, they are stripping out the headers of each email in the digests, so that you can’t even tell where a new message starts in the digest, let alone who actually sent it. Anyone had experience with this and know of a way to get all the individual headers shown again? -Conrad -- Truth is information.

1 0