Mailman 3 August 2014 - Mailman-Users

Re: [Mailman-Users] Second step in SA
by Mark Sapiro 14 Aug '14

14 Aug '14

On 08/14/2014 02:28 PM, Timothy Murphy wrote: > > I read most of the mailman lists I am subscribed to on gmane. > Why is it I can reply to some of them on the newsgroup, > while others must be replied to by email? > > Is this a mailman option, or is it up to gmane? I'm not sure what the issue is. I know in some cases people read and attempt to post to mailman-users(a)python.org from gmane, and the post comes to the list From: and address which is not a list member, and this particular list does not accept non-member posts. The only Mailman options are what to do with posts From: non-subscribers. If gmane sends the post with your address in From: and that address is a list member, it should be accepted. It is possible that a particular list admin doesn't like gmane and has set header_filter_rules to detect some header indicating the post is from a gmane server and treat it specially. There is a list option in gmane to allow or not allow posting. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Second step in SA
by Timothy Murphy 14 Aug '14

14 Aug '14

Having got SA working at last on my CentOS-7 home server, I'm thinking of improving its use for me (no-one else). 1) What is the simplest way to reject mail in chinese, russian and turkish? 2) I get some email wrongly marked spam - always from the same site. I'm tried marking this as ham (and running "sa-learn --ham") but this has surprisingly little effect. 3) Bizarrely, I seem to be getting a lot of spam from Brazil - at least I assume that is where *.br lives? I guess 1% of email from Brazil might be legit, but losing it would be a small sacrifice. I guess I could look at the sites - there may be only a couple. What is the easiest way to define email from a given site as spam? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 2

Changing configure default paths
by Chris Miller 14 Aug '14

14 Aug '14

Having previously used RPM installations of mailman, we've run into issues in getting configure to put things in the places we would like to see them. We can specify --prefix=/usr/lib/mailman and --with-var-prefix=/var/lib/mailman but we seem to be unable to specify a log directory such as /var/log/mailman, a config directory such as /etc/mailman (this one may really be an RPM post install script thing that creates symlinks to /usr/lib/mailman/Mailman). I've also seen some differences in terms of where some directories are located, sometimes in /usr/lib/mailman, sometimes in /var/lib/mailman. The ultimate goal here is to utilize a sane and consistent directory layout across the hosts we have mailman installed on. Any thoughts or suggestions are appreciated. -- Regards, Chris Chris Miller President - Rocket Scientist ScratchSpace Inc. (831) 621-7928 http://www.scratchspace.com

2 1

Reducing steps to confirm email address
by Rachelle Annechino 14 Aug '14

14 Aug '14

Hi, I have created a list that requires email confirmation. Right now, a new subscriber receives an confirmation email, clicks on the confirmation link, and is sent to a page where they must click on "Subscribe to list" to confirm their address. I would prefer it if subscriptions were confirmed immediately upon clicking the confirmation link. Any suggestions would be appreciated. Thanks -

2 1

Subscriber list
by Russell Woodford 14 Aug '14

14 Aug '14

How do I get a full list of subscribers via the Mailman web control panel (sadly 2.1.15 because Namecheap still haven't upgraded)? Sorry for such a newbie question, but the arguments with my shared hosting service have turned my brain to jelly. I can see the subscribers 100 at a time, but I want to get a full list, preferrably with everyone's settings, and ideally as a text file or download. I am forced to move my list because the host has decided that they will count each outbound message from the list as a separate email, so I violate the 200 per hour limit every time someone posts or responds ... we have over 900 active members. Russell Woodford Geelong Australia

5 6

Permission Denied Error after List Migration
by Sascha Rissel 14 Aug '14

14 Aug '14

Hello, I just tried migrating a list from an old to a new server. Basically I copied /var/lib/mailman/lists/<listname> and copied the private archive as well. Afterwards I - regenerated the archives using "/var/lib/mailman/bin/arch [listname]" and - fixed the urls with ""withlist -l -r fix_url [listname]"" When trying to login into the admin panel, I get "Bug in Mailman version 2.1.15" and in the logs there are the log entries found below: (N.B: All file permissions are set according to my previous server's, but I also tried: "chown -R list.list /var/lib/mailman/lists/"" Can you help me? Regards, Sascha. > Aug 05 19:53:33 2014 (21848) Failed config.pck write, retaining old state. > [Errno 13] Permission denied: '/var/lib/mailman/lists/rcworms-ah/config.pck.tmp.euve51864.serverprofi24.de.21848' > Aug 05 19:53:33 2014 admin(21848): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > admin(21848): [----- Mailman Version: 2.1.15 -----] > admin(21848): [----- Traceback ------] > admin(21848): Traceback (most recent call last): > admin(21848): File "/var/lib/mailman/scripts/driver", line 112, in run_main > admin(21848): main() > admin(21848): File "/var/lib/mailman/Mailman/Cgi/admin.py", line 227, in main > admin(21848): mlist.Save() > admin(21848): File "/var/lib/mailman/Mailman/MailList.py", line 573, in Save > admin(21848): self.__save(dict) > admin(21848): File "/var/lib/mailman/Mailman/MailList.py", line 528, in __save > admin(21848): fp = open(fname_tmp, 'w') > admin(21848): IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/rcworms-ah/config.pck.tmp.euve51864.serverprofi24.de.21848' > admin(21848): [----- Python Information -----] > admin(21848): sys.version = 2.7.3 (default, Mar 13 2014, 11:03:55) > [GCC 4.7.2] > admin(21848): sys.executable = /usr/bin/python > admin(21848): sys.prefix = /usr > admin(21848): sys.exec_prefix = /usr > admin(21848): sys.path = ['/var/lib/mailman/pythonlib', '/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] > admin(21848): sys.platform = linux2 > admin(21848): [----- Environment Variables -----] > admin(21848): HTTP_COOKIE: > admin(21848): SERVER_SOFTWARE: Apache > admin(21848): SCRIPT_NAME: /mailman/admin > admin(21848): SERVER_SIGNATURE: <address>Apache Server at lists.euve51864.serverprofi24.de Port 80</address> > admin(21848): > admin(21848): REQUEST_METHOD: GET > admin(21848): PATH_INFO: /rcworms-ah > admin(21848): SERVER_PROTOCOL: HTTP/1.1 > admin(21848): QUERY_STRING: adminpw=AH_MAILAdmin > admin(21848): HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 > admin(21848): HTTP_CONNECTION: keep-alive > admin(21848): SERVER_NAME: lists.euve51864.serverprofi24.de > admin(21848): REMOTE_ADDR: 95.88.111.84 > admin(21848): PATH_TRANSLATED: /var/www/vhosts/default/htdocs/rcworms-ah > admin(21848): SERVER_PORT: 80 > admin(21848): SERVER_ADDR: 62.75.175.182 > admin(21848): DOCUMENT_ROOT: /var/www/vhosts/default/htdocs > admin(21848): PYTHONPATH: /var/lib/mailman > admin(21848): SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/admin > admin(21848): SERVER_ADMIN: webmaster(a)rc-worms.de > admin(21848): HTTP_DNT: 1 > admin(21848): HTTP_HOST: lists.euve51864.serverprofi24.de > admin(21848): REQUEST_URI: /mailman/admin/rcworms-ah?adminpw=AH_MAILAdmin > admin(21848): HTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > admin(21848): GATEWAY_INTERFACE: CGI/1.1 > admin(21848): REMOTE_PORT: 50425 > admin(21848): HTTP_ACCEPT_LANGUAGE: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3 > admin(21848): HTTP_ACCEPT_ENCODING: gzip, deflate

5 6

Mailman digest issues
by Henrik Rasmussen 13 Aug '14

13 Aug '14

I am using Mailman version 2.1.12. One of my list admins have complained that he's list does not send out digest mails, which is most likely because he set digest_size_threshhold to 1000. But he also complains that no digest mails are being sent when he set _send_digest_now to Yes. He also set digest_send_periodic to Yes. We're confused that the digest_send_periodic text is saying "Should a digest be dispatched daily when the size threshold isn't reached?" as he wants the digest to be sent weekly as set in digest_volume_frequency. The /var/log/cron shows that the /usr/lib/mailman/cron/senddigests is being run daily at noon. 1) Where can I see if digest mails are in fact being sent out? 2) Where will Mailman log digest issues? 3) Does the digest_send_periodic daily affect the digest_volume_frequency weekly? Yours faithfully Henrik Rasmussen Systemadministrator, Core Services UNIVERSITY OF COPENHAGEN Corporate IT, Operation & Support Nørregade 10, P.O. Box 2177 DK1017 Copenhagen K Tel: +45 35322626 Dir: +45 35322704 Fax: +45 35322707 Email: her(a)adm.ku.dk<mailto:her@adm.ku.dk> Web: it.ku.dk<http://it.ku.dk/> [KU-logo_UK]

3 7

New To Mailman
by Anthony (N2KI) 13 Aug '14

13 Aug '14

Hi, I am new to the list and new to mailman. I have Mailman extracted to its own file on Ubuntu but I do not know how to setup the software or to start it. I reviewed the GNU Mailman - List Admin Manual but did not see how to start the software. I have Ubuntu running on a virtual drive. Any help is appreciated. Regards, Anthony (N2KI)

5 7

Scrub_nondigest removing html message text
by Peter Shute 13 Aug '14

13 Aug '14

We've discovered that if scrub_nondigest is set to Yes, the text of html messages (perhaps html-only?) is removed and replaced with a link to it. When users follow the link, the html tags in the text are visible because the angle brackets have been replaced with html codes. Is there a way to prevent scrub_nondigest removing these message parts? Is there a way to at least stop the angle brackets getting converted to codes? Peter Shute

2 4

Re: [Mailman-Users] Mailman digest issues
by Henrik Rasmussen 12 Aug '14

12 Aug '14

Further info on the problem is that the list admin just released 47 mails 30 minutes ago (please note that the digest_size_threshhold is now = 0, was previously 1000). Until now the list have sent 22 digest-mails with a single mail in each digest mail, all named Volume 20, but with increasing Issue number from 1 to 22. The numbering is expected, but the mails should've been send as a collection, not as individual mails. Right now the settings are nondigestable = True scrub_nondigest = False digestable = True digest_is_default = 1 mime_is_default_digest = 0 digest_size_threshhold = 0 digest_send_periodic = 1 digest_header = '' digest_volume_frequency = 3 There is no /var/lib/mailman/lists/LISTNAME/digest.mbox for the list in question, or any other list. Though I don't know which other lists do send digest mails. The list admin now have Emergency-moderated the list. I guess this is just to stop all incoming traffic from being sent out, and have no effect on what the list admin do release, right? Henrik Rasmussen -----Oprindelig meddelelse----- Fra: Henrik Rasmussen Sendt: 12. august 2014 09:32 Til: Mark Sapiro; mailman-users(a)python.org Emne: SV: [Mailman-Users] Mailman digest issues On 08/12/2014 03:00 AM, Mark Sapiro wrote: >On 08/11/2014 06:15 AM, Henrik Rasmussen wrote: >> I am using Mailman version 2.1.12. >> >> But he also complains that no digest mails are being sent when he set _send_digest_now to Yes. >Did he press "Submit Your Changes" after setting _send_digest_now to Yes? If so, and if there were digested messages and digest members with delivery enabled, something else is wrong. Yes he did. I did too, afterwards. >What response did he get when pressing "Submit Your Changes" after setting _send_digest_now to Yes? What's in Mailman's error log. I got the message "There was no digest to send". No messages regarding this list in /var/log/mailman/error (or any other log in this directory for that matter). The smtp log show that the list do send message (to normal-members I guess), but I can't verify if messages are sent to digest-members. The list admin say no mails are sent to digest-members. >> He also set digest_send_periodic to Yes. > > >> We're confused that the digest_send_periodic text is saying "Should a digest be dispatched daily when the size threshold isn't reached?" as he wants the digest to be sent weekly as set in digest_volume_frequency. >digest_volume_frequency has nothing to do with how often periodic digests are sent. It only controls how often the vvv is incremented and ii is reset in the "List_name Digest, Vol vvv, Issue ii" >Subject: header of the digest. I am still confused, even after reading section 2.6 in http://www.gnu.org/software/mailman/mailman-admin.pdf. In my understanding, (and I know I'm wrong here) if the volume number is changed weekly, but digest mails are sent daily, all digests will contain the same volume number all week long. What is the difference between volume number and issue number, and when do Mailman send what? >> 1) Where can I see if digest mails are in fact being sent out? >Your MTA logs and Mailman's smtp log. Also, digest messages are accumulated in lists/list_name/digest.mbox, and when a digest is sent, this file is removed. How can I tell normal from digest? Will the digest mails mention Digest I the SMTP log. If so, no digests have been sent. >> 2) Where will Mailman log digest issues? >Mailman's error log and in the output from cron/senddigests (for periodic digests. No errors in the error log. Cron/senddigests -l LISTNAME. However, shows [root(a)mailman.example.com]# /usr/lib/mailman/cron/senddigests -l Sci-diku-imageworld 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 626, in Load raise Errors.MMUnknownListError Mailman.Errors.MMUnknownListError >Note, that often the output, if any, from Mailman's cron jobs is mailed to the 'mailman' user which happens to be the site list. If the site list is not configured to accept non-member posts, and the >site admin is not a member of the site list, this output is often lost. >You can either set the site list as above or add a MAILTO= directive with a deliverable address to Mailman's crontab. Thanks. >-- >Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, Henrik Rasmussen

2 1