Mailman 3 March 2014 - Mailman-Users

handler to auto detach attachment and link it to a website?
by Sylvain Viart 16 Apr '14

16 Apr '14

Hi, I've a project to setup a mailman for newsletter. I've found many interesting links about it. I will post them as a reminder at the end of this message, as it can help someone else. My question is: Is there any handler that I can setup in the pipeline to: * detach an attachment * post it to a webservice (or run a script uploading it to an online storage) * modify the content of the mail, linking it to the online stored attachment ? Or a good base to program it. The goal to achieve, is to permit restricted sender to write mail with attachment but do not replicate it to all member of the list. Also for non technical writer, uploading the attachment and linking may be too painful. Regards, Sylvain. Reference links, some may be pretty old. newsletter : How do I create a newsletter/announcement/one-way list? http://wiki.list.org/pages/viewpage.action?pageId=4030685 personalisation VERP exemple de mail, simple piste : https://mail.python.org/pipermail/mailman-users/2003-February/026008.html 4.48. How can I change the HTML (or .txt) templates used by my mailing lists? http://wiki.list.org/pages/viewpage.action?pageId=4030605 4.33. How do I put a subscribe form for my list on a web page? <http://wiki.list.org/pages/viewpage.action?pageId=4030596> 3.40. I want to completely customize the look and feel of Mailman – how do I do that? <http://wiki.list.org/pages/viewpage.action?pageId=4030560> What is the largest list Mailman can run? <http://wiki.list.org/pages/viewpage.action?pageId=4030518> [Mailman-Users] Keeping the Publich_HTML subscription page from popping up. <http://www.mail-archive.com/mailman-users%40python.org/msg24296.html> [Mailman-Users] Editing confirm page <http://www.mail-archive.com/mailman-users%40python.org/msg32261.html> Mailman processes incoming messages through a pipeline of handlers which each do parts of the message processing <http://wiki.list.org/pages/viewpage.action?pageId=7602227>

4 12

building a new mailman server
by Bruce Harrison 28 Mar '14

28 Mar '14

We are currently running an old mailman instance and am planning to bring up the newest version of mailman and migrate to it. Current system uses sendmail. Since I now have a chance to change things, what is the best mail server to run on my mailman box? It will be talking to an exchange 2010 frontend server (current mailman system is doing that now). I can install sendmail or go with postfix or ??? This is running on a debian box. Bruce Harrison UT Martin

10 13

HTML to Text-Only
by Peter Fiala - WCASA 26 Mar '14

26 Mar '14

One of the listservs I manage sends text-only messages though I have that option unchecked under content filtering. This happens to this list and not any others, though the option is the same for all lists I manage. Should Mailman convert text/html parts to plain text? This conversion happens after MIME attachments have been stripped. (Edit convert_html_to_plaintext)<http://lists.wcasa-blog.org/admin.cgi/regional_ta_sc-wcasa-blog.org/?VARHEL…> No Yes Wondering if anyone has any solutions. Thanks. Peter Sent from my iPad

2 1

There are no pending requests
by rex 26 Mar '14

26 Mar '14

The Mailman web page to approve messages held for approval always has the message: "There are no pending requents," even when there are messages in /var/lib/mailman/data/heldmsg-mynewlist-1.pck Running Mailman 2.1.15 under Debian Wheezy with a new list that has never existed on any local machine. 1) Mail that does not require approval is posted to the list normally. 2) All web pages with the exception of the one below function normally. 3) Mail from moderated subscribers produces the usual notice to the list admin, but when the page: http://myserver.net/cgi-bin/mailman/admindb/mynewlist is visited, this message appears: "There are no pending requests. Click here to reload this page." Reloading the page makes no difference. I tried the hold_again script from here: http://fog.ccsf.edu/~msapiro/scripts/ When the hold_again script is run, this is the result: root@ /usr/lib/mailman/bin# ./hold_again -n -v -l mynewlist Requeueing message from file heldmsg-mynewlist-1.pck The held message is in the data directory: root@:/var/lib/mailman/data# ls -l -rw-r----- 1 root list 41 May 3 2013 adm.pw -rw-rw---- 1 root list 1997 Nov 6 2012 aliases -rw-rw---- 1 list list 12288 Nov 6 2012 aliases.db [...] -rw-rw-r-- 1 list list 775 Mar 25 16:11 heldmsg-mynewlist-1.pck [...] -rw-rw-r-- 1 root list 10 Jul 13 2012 last_mailman_version -rw-r--r-- 1 root list 14100 Jun 16 2012 sitelist.cfg -rw-rw---- 1 root list 1831 Nov 6 2012 virtual-mailman -rw-rw---- 1 list list 12288 Nov 6 2012 virtual-mailman.db The hold_again command results in a new notice to the list admin re the held message, but revisiting the web page shows the same "There are no pending requests" message. Responding via email to the list admin message with an "Approved: listadminpswd" header" results in a copy of the sent message being sent to the list admin, but no action re the held message; it's still held, with the same timestamp. The server is running apache 2.4.6-3. The mailman.conf file in /etc/apache2/sites-available has: # Sample configuration for Debian mailman with Apache # We can find mailman here: ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ # And the public archives: Alias /pipermail/ /var/lib/mailman/archives/public/ # Logos: Alias /images/mailman/ /usr/share/images/mailman/ # Use this if you don't want the "cgi-bin" component in your URL: # In case you want to access mailman through a shorter URL you should enable # this: #ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ # In this case you need to set the DEFAULT_URL_PATTERN in # /etc/mailman/mm_cfg.py to http://%s/mailman/ for the cookie # authentication code to work. Note that you need to change the base # URL for all the already-created lists as well. <Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted </Directory> <Directory /var/lib/mailman/archives/public/> Options FollowSymlinks AllowOverride None Require all granted </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Require all granted </Directory> I've spent hours trying to resolve this problem. Any help would be much appreciated. TIA, -rex --

2 1

Q : Has anyone successfully deployed Mailman over a Plesk-based Linux system ?
by Jacques Setton 25 Mar '14

25 Mar '14

Hi, We continue to experience serious difficulties in getting Mailman to fully operate as expected on a Plesk- packaged Linux server system. The list management web interface works fine but we definitely can't get messages addressed to Mailman-related list accounts be correctly processed. We'd therefore like to know whether anyone ever succeeded in deploying Mailman over Plesk and, if so, what was done to have it work satisfactorily. For information, the relevant configuration details of the VPS we are using are : - CentOS 6.4 - Apache 2.2.15 - Plesk Panel 11.5.30 - Postfix 2.8.14 - Mailman 2.1.12 - Python 3.3.1 We'd appreciate any feedback / guidance with respect to such environment. Regards, Jacques Setton <mailto:jsetton@waycast.com> jsetton(a)waycast.com

2 6

Unable to remove invalid e-mail address
by Tim H. 22 Mar '14

22 Mar '14

Somehow an e-mail address with the below form was subscribed to one of my lists: "user(a)domain.tld /" The e-mail address does not show up in the web interface, nor does it show in "list_members", "find_members", or "list_members -i". I also tried using withlist. Essentially, I tried everything on this page: http://wiki.list.org/pages/viewpage.action?pageId=4030544 But, the e-mail address persists. Does anyone know of another method for removing this address? I've been trying to use dumpdb to dump the config.pck to a text file, and manually edit them out. However, the config_list command does not like the format of the dumpdb txt file. I found this e-mail address because 'disabled' reports it as "Mailman.Errors.NotAMemberError" every morning :/ Thanks, Tim H.

2 2

Re: [Mailman-Users] Reducing false positives with spam markings with Gmail, etc.
by Cedric Knight 21 Mar '14

21 Mar '14

Stephen J. Turnbull <stephen at xemacs.org> wrote on Wed Nov 20 2013: > Steven Clift writes: > > Thanks Stephen. > > > > Are most mailman hosts finding their mail in Gmail heading to the > > "Promotions" tab or "Forums" optional tab? > > I don't receive any Mailman mail at my Gmail address, so I can't say. > But hold that thought ... if you don't get any response, I'll ping > some of my gmail subscribers and ask them. (Remind me after a week or > so, I've been unreliable at remembering promises recently.) Reminder? I've had complaints about this specifically with list *confirmation emails* being being misclassified under "promotions", resulting in some users assuming they are subscribed when they haven't actually confirmed. There are hints about this change at Gmail at <http://groupserver.org/groups/development/messages/topic/iYuRUBysGQMMbZ98m7…>, that it might be a result of the "Precedence: bulk" header added to administrivia messages. Any more evidence? Do any standards help decide if Gmail or Mailman is wrong? CK

3 3

Re: [Mailman-Users] Messages addressed to Mailman lists are systematically diverted to predefined default email account
by Jacques Setton 21 Mar '14

21 Mar '14

MEMO RESENT with minor corrections -----Message d'origine----- De : Jacques Setton [mailto:jsetton@waycast.com] Envoyé : vendredi 21 mars 2014 00:26 À : 'Mark Sapiro' Cc : 'mailman-users(a)python.org' Objet : RE: [Mailman-Users] Messages addressed to Mailman lists are systematically diverted to predefined default email account Hi Mark, Thank you for your appreciated comments to which I responded individually : see the embedded annotations further below... I did modify some of the parameters you highlighted. Unfortunately, at best the previously observed problem still persists despite the modifications made. In other instances, some modifications cause the alteration of Postfix' operation which results in a non-delivery of all emails... To further investigate the issue, I have decided to use two separate domains attached to same VPS machine as follows : 1) 'domain.info' for incoming & outgoing messages addressed to and from mails solely related to Mailman lists. 2) 'domain.net' for all non-Mailman lists incoming & outgoing regular messages. The test results show - see the 1st attachment - that all messages addressed to Mailman accounts (like testlist(a)domain.info and testlist-request(a)domain.info ) are systematically diverted to the previously specified default account admin(a)domain.fr . Whereas messages addressed to standard email accounts (for ex. admin-lists(a)domain.net ) get through without any problem... In conclusion, it turns out that even domain differentiation does not solve the problem. It thus seems as if Plesk's supervision of Postfix does not cope well with the standard operation Mailman's lists. This is very puzzling as Parallels claims that Mailman is officially supported by Plesk V10+ . On such configured systems, Mailman is even activated directly from Plesk's Control Pannel - see their Manual section about this in the second attachment. So my ultimate question will simply be : has anyone ever succeeded in adequately deploying Mailman over a Plesk-based Linux server ? If this is the case, I would invite anyone who has done it before to let us know how they managed to make it work as expected. Many thanks in advance for your and others help on this, as I have spent an enormous amount of time trying to resolve the case without any success so far... Kind regards, Jacques Setton jsetton(a)waycast.com -----Message d'origine----- De : Mark Sapiro [mailto:mark@msapiro.net] Envoyé : vendredi 14 mars 2014 03:13 À : mailman-users(a)python.org Objet : Re: [Mailman-Users] Messages addressed to Mailman lists are systematically diverted to predefined default email account On 03/13/2014 11:59 AM, Jacques Setton wrote: > > For example, in the below maillog trace we see that the memo initially > addressed to myslist(a)domain.net by admin-europe(a)waycast.eu is finally > delivered to the default account admin(a)domain.net instead of being > processed by '/usr/lib/mailman/mail/mailman post mylist' as it should > normally be the case : >> But we don't see why? Strangely enough, there is no Postfix log entry saying anything about the redirect from orig_to=<mylist(a)domain.net> to to=<admin(a)domain.fr>. Also, there is a 2 and a half minute delay between receipt of the message and delivery (delays=0.1/0.01/60/90) of which 60 seconds is connection setup time including DNS, HELO and TLS; and 90 seconds is message transmission time. Does this seem OK? I am not sure why there a such long delay before mail rejection and rerouting. As previously indicated, this behavior seems to result from an non recognition of a Mailman related recipient account which requires a different treatment, as opposed to standard user email accounts. >> Anyway, this can occur if there is a virtual mapping from >> mylist(a)domain.net to admin(a)domain.fr that is taking priority over >> /etc/mailman/virtual-mailman To my knowledge, such mapping is not established. The only mapping that I am aware of, in this respect, is one depicted in the 'aliases' file located in the /var/spool/postfix/plesk directory and which contains the following mapping : drweb admin(a)domain.fr kluser admin(a)domain.fr postmaster admin(a)domain.fr root admin(a)domain.fr anonymous admin(a)domain.fr drweb-daemon admin(a)domain.fr mailer-daemon admin(a)domain.fr > - - - > [root@vps12345 ~]# more /usr/local/psa/var/log/maillog | grep > 1A52911616E > > Mar 11 23:12:27 vps12345 postfix/smtpd[19763]: 1A52911616E: > client=relay6-d.mail.gandi.net[217.70.183.198] > > Mar 11 23:12:27 vps12345 postfix/cleanup[19767]: 1A52911616E: > message-id=<!&!AAAAAAAAAAAYAAAAAAAAAHqVdj4TMlNNnKyTMxcTrDTCgAAAEAAAABD > lMhHAh > X9PqvkRNi1Uq10BAAAAAA==(a)waycast.eu> > > Mar 11 23:12:27 vps12345 postfix/qmgr[19671]: 1A52911616E: > from=<admin-europe(a)waycast.eu>, size=17420, nrcpt=1 (queue active) > > Mar 11 23:14:57 vps129345 postfix/smtp[19770]: 1A52911616E: > to=<admin(a)domain.fr>, orig_to=<mylist(a)domain.net>, > relay=mx1.ovh.net[213.186.33.29]:25, delay=150, delays=0.1/0.01/60/90, > dsn=2.0.0, status=sent (250 ok 1394576096 qp 28763) > > Mar 11 23:14:57 vps12345 postfix/qmgr[19671]: 1A52911616E: removed > > [root@vps12345 ~]# > > - - - > > Despite skimming through this Mailman-Users list and many other source > publications, I haven't yet been able to figure out the exact origin > of this abnormal behavior. Though I suspect a poorly defined Postfix 'transport' > specification (see item 7 further below), but this remains to be confirmed. >> The transport involved should be local. I have removed all transport definitions, meaning that we fallback to the default values applied for Postfix. > Please note that I am using a hosted VPS running CentOS with, among > other things, Plesk, Postfix and Mailman. All software versions and > configuration details are communicated below. Another piece of useful > information : the 'admin(a)domain.fr' default account has been specified > at Plesk's web admin interface level. >> See the FAQ at <http://wiki.list.org/display/DOC/Mailman+and+Plesk> I have already seen this as well as other published docs, and have applied all the recommendations applicable to using Mailman with Plesk, including the related Admin Guide. > 2. Mailman Configuration File relevant excerpts (mm_cfg.py located in > /usr/lib/mailman/Mailman/) > > { . } > > DEFAULT_URL_HOST = 'lists.vps12345.ovh.net' > > DEFAULT_EMAIL_HOST = 'vps12345.ovh.net' > > MTA = 'Postfix' > > VIRTUAL_HOSTS.clear() > > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > > add_virtualhost('lists.domain.net', domain.net') > > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.net'] > > VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost' >> You may or may not need this, but if you do, you may need Mailman's bin/genaliases to update virtual-mailman. I have removed the 'VIRTUAL_MAILMAN_LOCAL_DOMAIN' above setting. > # STANZA START: mylist > > # CREATED: Mon Feb 24 21:00:44 2014 > > mylist(a)domain.net mylist >> With VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost', these should be >> mylist(a)domain.net mylist@localhost >> and so on. This is no longer applicable, since I am no longer using the 'VIRTUAL_MAILMAN_LOCAL_DOMAIN' setting. However, after removing this parameter, no improvement was noticed... > # *** Added 'virtual-mailman' reference in 'virtual_alias_maps' > > virtual_alias_maps = $virtual_maps, > hash:/var/spool/postfix/plesk/virtual, > hash:/etc/mailman/virtual-mailman >> virtual_alias_domains = domain.net When I apply this setting, the regular Postfix mail operation stops to function while this still does not resolve the previously reported problem... > # *** Added Postfix Transport location to 'transport_maps' parameter >> Why? This is probably only for postfix_to_mailman. I am not using the postfix_to_mailman scheme. The related section was/is left commented in the 'master.cf' configuration file. > virtual_transport = plesk_virtual >> This makes plesk_virtual the transport for all virtual mailbox domains. For normal mail operation, the transport has to be 'plesk-virtual' (see the 1st attached document). Otherwise, I don't see what else could be specified here which won't break the normal mail operation... > plesk_virtual_destination_recipient_limit = 1 > > mailman_destination_recipient_limit = 1 >>This is for postfix_to_mailman As previously indicated, we are not using the 'Postfix_to_Mailman' scheme. Hence, this parameter has been dropped, however without seeing any improvement of the original problem. > 7. Postfix Added Transport Table scheme (transport and transport.db > located in /etc/postfix/) > > The below-specified transports remained commented out because they > cause a transport failure when uncommented. It seems that the > specifications used are probably invalid. These will need to be > reworked and we'd welcome suggestions as to what to specify instead... >> See the FAQ at <http://wiki.list.org/x/EYDt>, in particular the paragraph postfix_to_mailman.py is an alternative to and is incompatible with Mailman delivery via aliases. If you are configuring both Mailman aliases and postfix_to_mailman.py, you are making a mistake. I have read mots FAQs on the subject and followed all related recommendations. In addition, I restate that it was not, and is still not, our intention to use the 'postfix_to_mailman.py' scheme... -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Non-Members Get Messages
by Peter Fiala - WCASA 21 Mar '14

21 Mar '14

Mailman Community, I've been a Mailman user for a few years but have never been able to figure out this mystery, which may be completely obvious I realize. Someone emails me and requests to be taken off the list. I go to remove them and they are not members. They confirm that they are not on the list under any other email address. How could this possibly happen? Thanks anyone for your help. Peter Peter Fiala Technology & Events Coordinator Wisconsin Coalition Against Sexual Assault (WCASA) 2801 W. Beltline Hwy., Ste 202, Madison, WI 53713 Telephone: 608-257-1516; Direct: 608-284-5494 Fax: 608-257-2150 Website: www.wcasa.org<http://www.wcasa.org/> Creating the Social Change Necessary to End Sexual Violence Please consider a holiday gift to help us continue our important work into 2014. You can make donations to WCASA directly online by visiting our website<http://www.wcasa.org/>.

4 3

Can confirmation messages use custom Received: headers?
by Yan Juras 15 Mar '14

15 Mar '14

Hi. I've searched the archives several different ways about this and not found anything, so... We run Mailman v2.1.4 on SuSE Enterprise v11 SP3 using Sendmail. The box is a virtual machine and pretty much dedicated to the purpose of being a listserver, at least at present. We recently got a slew of Spamcop complaints about confirmation emails we sent as a result of subscription requests submitted via the web interface. These emails clearly state that the confirmation emails are a result of subscription requests submitted from a specific IP address. Clearly from the user's POV these emails are spam and I totally understand why the users are submitting the complaints in this instance. However, I also don't think that my mail system should be held responsible for sending these emails. (Consider that I am not held responsible for damage caused by my car if the person driving the car stole it from me.) I was looking at the Spamcop FAQ and noticed a brief comment about the Received headers that some webmail interfaces add that list the IP address of the client that used HTTP to submit the email via a webmail GUI, for example: Received: from 66.191.176.186 by webmail-d137.sysops.aol.com (149.174.18.27) with HTTP (WebMailUI); Sat, 13 Apr 2013 08:07:55 -0400 The Spamcop FAQ kind of implies that Spamcop will consider the source of the HTTP (in this example, 66.191.176.186) as the sender, rather than the email server that converted the HTTP to SMTP. I've not checked this at all, so I may be reading into the FAQ. So my question is this: can Mailman be configured in some straightforward way to add a Received: header with the IP address of the host that requested the subscription? I am not a Python programmer, but I am capable of making code changes if necessary. Comments? -- Yan Juras Manager of Systems Engineering Office of Converging Technologies, I Bldg room 100 Queens College / 65-30 Kissena Blvd / Flushing NY 11367 (718)997-5906 / FAX: (718)997-5678 Need Assistance? Call The OCT Help Desk at (718) 997-4444 OCT will never ask for your personal information or password. Never share this information with anyone.

2 2