Mailman 3 October 2011 - Mailman-Users

Re: [Mailman-Users] Blocking messages from kijiji (SENDER_HEADERS solution interferes with logging?)
by francis picabia Oct. 28, 2011

Oct. 28, 2011

On Thu, Oct 27, 2011 at 10:07 AM, francis picabia <fpicabia(a)gmail.com> wrote: > On Thu, Oct 27, 2011 at 9:54 AM, francis picabia <fpicabia(a)gmail.com> wrote: >> On Thu, Oct 27, 2011 at 9:37 AM, francis picabia <fpicabia(a)gmail.com> wrote: >>> Hello, >>> >>> We run a mailing list for staff which should not >>> receive email from outside of the list membership. >>> >>> The only non-member address allowed to post is >>> another mailing list. >>> >>> Today we received a post from post(a)kijiji.ca >>> and it made it through to the list. >>> >>> I see this in the post log file: >>> >>> Oct 26 18:21:41 2011 (2999) post to fyi from post(a)kijiji.ca, >>> size=5293, message-id=<1190302152.2079281319664066415.JavaMail.root@kj-classy012>, >>> success >>> >>> We've tested this with a second small membership and restricted >>> mailing list for our IT staff, and again a post from kijiji gets through. >>> >>> If we email from a gmail account or something, it is blocked as expected. >>> >>> In kijiji interface, they allow you to set up the sender, and this is >>> likely passing the test for the sender, but it is only >>> the sender in the envelope, which isn't reported in mailman >>> (nor Postfix in what I saw). >>> >>> We've been running the same mailman 2.1.9 from Redhat for >>> a few years and there has never been a problem like this before. >>> >>> I think we would prefer if both the sender From: and the envelope >>> sender had to match, or had to both be allowed to post. >>> >>> Adding the post(a)kijiji.ca address to the rejected senders did not block them, >>> which isn't surprising as it is looking at the other subscribed sender. >>> >>> Anyone else have experiences with that or suggested approaches? >>> >> >> I looked at older postings in this mailing list and it appears this is >> a solution: >> >> Quoting Mark Sapiro: >> >>> If this is your Mailman installation, you could try putting >>> >>> SENDER_HEADERS = (None,) >>> >>> in mm_cfg.py. This would say that the post is considered to be from a >>> member only if the envelope sender is a member." >> >> I'll try this. >> > > On second thought what we needed is similar, but probably: > > SENDER_HEADERS = ('from') > > Would there be problems "from" this? > > For internal emails we already use canonical_maps in > postfix to standardize the from address into something > predictable. > This works, but of course it has caught someone using another unconventional list with a problem of the sort: "but it always worked this way before". I check out the /var/log/maillog area for signs the user is caught by this change, but oddly, nothing is appearing in the logs. It appears than restricting the SENDER_HEADERS this way causes no logging on the mailman end. Is there a way to fix this?

2 2

Virtual Hosting Query
by Drew Ferguson Oct. 28, 2011

Oct. 28, 2011

Hi I am trying to get virtual hosting working in Mailman 2.1.14 with Postfix Documentation at http://list.org/mailman-install/postfix-virtual.html specifies setting POSTFIX_STYLE_VIRTUAL_DOMAINS to list the virtual domains required in mm_cfg.py However, doing this does not seem to have the desired effect with list creation reporting Error: Unknown virtual host on create list Google points to an old mail http://mail.python.org/pipermail/mailman-users/2004-February/034943.html which says to put a line like add_virtualhost('web.domain.com','smtp.domain.com') in mm_cfg.py and doing so allows the creation of the list Have I missed something fundamental or should this be in the documentation? Ta -- Drew

3 7

Outlook and priority messages to Mailman
by Christopher Adams Oct. 27, 2011

Oct. 27, 2011

Hello, If an individual sends a priority message via Outlook to a Mailman list, does it assume that it is a bcc? I was able to verify that the person sent the message directly to the list, but the message was sent to the administrator with the "implicit destination" tag. I realize that I can control this behavior at the list or system level, but just looking for verification of this behavior. Thanks. -- Christopher Adams adamsca(a)gmail.com

2 1

Mailman on Debian with Lighttpd ans Postfix
by Andreas Stein Oct. 24, 2011

Oct. 24, 2011

Hello, probably my problem is very simple, but after some days of research, I´m stucked. I tried to install mailman 1.2.11 on Debian 5.0 with lighttpd 1.4.29 and postfix 2.5.5. Everything went fine, but I can´t call the site listen.domain.com. There is no error, but a blank/white page with a http code 200 (curl -I). So no error at all, but nothing to see. sometimes, when I restart lighttpd I got to see the normal listinfo page, but if I reload it, I got again only a blank page. After registering a new mailinglist the mail-owner get´s a mail, so I think, that postfix is normally configured. The question for me is: Where to look? In mailman logs there are no errors at all and lighttpd seems also to work. So where I could search for the error? Thanks! Andreas LIGHTTPD Config ======================== server.modules += ( "mod_cgi" ) $HTTP["host"] == "listen.domain.com" { server.document-root = "/usr/lib/cgi-bin/mailman" accesslog.filename = "/var/log/lighttpd/mailman/access.log" server.name = "listen.domain.com" # make sure that no-one can list our directory contents server.dir-listing = "disable" alias.url += ( "/mailman/" => "/usr/lib/cgi-bin/mailman/", "/pipermail/" => "/var/lib/mailman/archives/public/", "/images/mailman/" => "/usr/share/images/mailman/", ) cgi.assign = ( "/admin" => "", "/admindb" => "", "/confirm" => "", "/create" => "", "/edithtml" => "", "/listinfo" => "", "/options" => "", "/private" => "", "/rmlist" => "", "/roster" => "", "/subscribe" => "") url.rewrite = ( "^/$" => "/mailman/listinfo", "^/mailman/$" => "/mailman/listinfo" ) } =================================== the mm_cfg.py looks like that ================================== # -*- python -*- # Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA # 02110-1301 USA """This is the module which takes your site-specific settings. >From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example.""" ####################################################### # Here's where we get the distributed defaults. # from Defaults import * ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # #------------------------------------------------------------- # The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'listen.domain.com' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'listen.domain.com' #------------------------------------------------------------- # Required when setting any of its arguments. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'de' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.Exim4.Debian or # /usr/share/mailman/postfix-to-mailman.py) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. #MTA='Postfix' MTA = None # No MTA alias processing required # alias for postmaster, abuse and mailer-daemon DEB_LISTMASTER = 'postmaster(a)listen.domain.com' #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. ============================

3 4

throttling mailman for a relay smtp server
by Anne Wainwright Oct. 24, 2011

Oct. 24, 2011

Hello, My isp decided to close his Mailman server, so you know the bit about fools and angels... Following the link below I got my list up and running only to find Mailman can send so many posts in so short a time that I overloaded my isp's smtp server with dire results :( http://www.freesoftwaremagazine.com/articles/running_gnu_mailman_at_home (I found you have to add forwarding addresses and aliases for list-bounces which this article ignores) So Mailman 2.1.12 on ubuntu with fetchmail, postfix, smtp relay via isp OK, i have more names than a family list, so investigating ideas for throttling I am left confused. 1. I read Mailman FAQ 4.51 "How do I limit the rate (throttle) at which Mailman sends mail?" 2. I see the policyd link but this look a little complex (and scary) for my needs (<2000 members, outgoing posts only, one per month tops, maybe switch on postfix/fetchmail/mailman only when needed) 2. I see a patch for SMTPDirect that looks like it might be good and perhaps an easier route 3. Then I see Mailman FAQ 4.72 "How do I configure Mailman to use an external SMTP server?" 4. confusion because this says "In mm_cfg.py add or modify: DELIVERY_MODULE = 'SMTPDirect' SMTPHOST = 'mail.example.com' " and they are not in my mm_cfg.py and anyway we are running with postfix ??? does SMTPDirect replace having postfix do the smtp-ing? ??? the patch patches SMTPDirect so it won't do anything if I do not explicitly declare it in mm_cfg.py? ??? what will happen then? ??? should I just patch it anyway and it will go for me? Someone please illuminate me a bit here on the true path ahead. thanks for any and all comments Anne

2 3

Installation on GoDaddy servers?
by Carlos Palomino Oct. 24, 2011

Oct. 24, 2011

Hello all, I'm new here, and new to mailman. Please forgive the basic question. I'm mainly curious if you believe it would be possible to install mailman on a GoDaddy deluxe account? I've asked their support, but received a rather vague reply (shocker). I learned python is supported; however, they weren't familiar with mailman and thus, couldn't answer any further queries. So, any ideas on what may or may not work as far as installing on a shared web host? Thank you for any feedback. C.

2 1

Footer as attachment in Outlook problem.
by Serving Soon Oct. 24, 2011

Oct. 24, 2011

Hello, I followed the old discussions regarding how Outlook shows footer as attachment. I read the FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030707 I wonder if someone has found a more recent solution then what is out there? The solutions provided are years old and they pertain to older versions. I know it is an Outlook problem not mailman's. I hope there is a solution like the workarounds of IE browsers quirks and bugs. Any advise on how to get Outlook to show footers properly would be greatly appreciated. :) Serving None

4 6

Incorrect timezone in mailman-generated messages
by Ivan Kuznetsov Oct. 24, 2011

Oct. 24, 2011

Hello! After the local timezone rules change the mailman sends messages with incorrect timezone in Date: header. Acording to the Russian Govnerment statement Russia is abolishing daylight saving time from this year. E.g. Moscow time (which daylight saving was GMT+4) will now has standard GMT+4. To adopt this we install new timezone calculation rules (tzdata-2011l). Now the mailman thinks that timezone is GMT+3. All the mailman-generated messages (moderation requests, errors, reminders and so on) looks like the time is +1h in future. E.g. Return-Path: <mailman-bounces(a)domain.ru> Received: from gate2.solvo.ru (gate2-vlan10.solvo.ru [172.16.80.4]) by hippo.solvo.ru (Cyrus v2.2.12-Invoca-RPM-2.2.12-8.1.RHEL4) with LMTPA; Thu, 20 Oct 2011 15:54:42 +0400 X-Sieve: CMU Sieve 2.2 Received: from gate2.solvo.ru (localhost.localdomain [127.0.0.1]) by gate2.solvo.ru (Postfix) with ESMTP id 2ADCC52E802D for <listmaster(a)solvo.ru>; Thu, 20 Oct 2011 15:54:42 +0400 (MSK) Subject: =?koi8-r?b?7sXEz9PUwdfMxc7Oz8UgydrXxd3FzsnFIM/CIM/bycLLxQ==?= From: mailman-bounces(a)solvo.ru To: all-owner(a)solvo.ru MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0258393610==" Message-ID: <mailman.20.1319111680.3169.all(a)solvo.ru> Date: Thu, 20 Oct 2011 15:54:40 +0300 Precedence: bulk X-BeenThere: all(a)solvo.ru X-Mailman-Version: 2.1.14 List-Id: =?koi8-r?b?6c7Gz9LNwcPJ0SDEzNEg19PFyCDTz9TS1cTOycvP1yDz7+z37w==?= <all.solvo.ru> X-List-Administrivia: yes Errors-To: mailman-bounces(a)solvo.ru Sender: mailman-bounces(a)solvo.ru Local time in mailman logs are still correct: /var/log/mailman/smtp: Oct 20 15:54:42 2011 (3173) <mailman.20.1319111680.3169.all(a)solvo.ru> smtp to all for 1 recips, completed in 0.102 seconds /var/log/mailman/bounce: Oct 20 15:54:40 2011 (3169) all: bounce message w/no discernable addresses: <35292842.20111020185427(a)87.subnet125-163-181.speedy.telkom.net. Oct 20 15:54:40 2011 (3169) all: forwarding unrecognized, message-id: <35292842.20111020185427(a)87.subnet125-163-181.speedy.telkom.net.id> We are using mailman for years without such a problem before. All other software run at this host now have the correct understanding the local time as MSK standard time = GMT+4 [root@gate2 mailman]# date '+%Z %::z' MSK +04:00:00 I found the similar mailman bug #266314 (https://bugs.launchpad.net/mailman/+bug/266314) but it was years ago and was fixed at version 2.1.7. Now we run mailman 2.1.14 with Python 2.4.3 under Oracle Enterprise Linux 5 (a clone of RHEL5) -- Regards, Ivan Kuznetsov SOLVO ltd St.Petersburg, Russia

4 8

Digests and HTML-enhanced email
by Lindsay Haisley Oct. 22, 2011

Oct. 22, 2011

I host a list for about 700 autoharp musical enthusiasts on Mailman 2.1.12. The subscribers are by and large somewhat elderly and non techie, and to most of them an explanation of the difference between HTML-enhanced email and plain text email would be unintelligible geek-speak. I recently received the following email from one of the subscribers: > "Scrubbed" messages as they appear in my cyberpluckers DIGESTS: > This type of problem is perhaps a bit over 6 months old, and evidently > is caused by the manner in which some people have tried to attach > their message to their cyberplucker posting. > > How can this problem be resolved? THANKS ... Drew Smith > ******************************************************* > > Message: 25 > Date: Fri, 7 Oct 2011 08:42:29 -0700 > From: "foo bar" <.......> > To: Cyberpluckers(a)autoharp.org > Subject: Re: [CP] Intro > Message-ID: <a0ffed34-525e-40a5-88c6-4b78dbef2df8@blur> > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: > http://www.autoharp.org/mailman/blah/blah/..../attachment.html > > ... <snip> ... other examples I took a look at the list archive and indeed the email appears in the archives also with only a link to the attachment, which is the HTML-enhanced message, visible as HTML code. There's no plain text version in the archive. I explained to the subscriber, and to the list admins, that this (and similar) posts were probably HTML-only posts, and that, absent a plain text rendering in a multipart email, the list server had no way to generate a plain text version, and that including multiple HTML-enhanced emails in a digest was problematic and not going to work very well, if at all. The list admins are aware that plain text is the appropriate format for posting to a mailing list, but subscribers come and go from this list, and as I said, many don't understand such things, and it seems that there are a number of mail programs out there which will generate an HTML-enhanced email without an accompanying MIME text/plain version. The list is configured with mime_is_default_digest set to MIME, which I assume sends digests with each post as a separate attachment (I've never subscribed to the digest for this list, so I don't really know). I had assumed that this might address this problem, but apparently not. One of two things needs to happen. Either the list server should refuse and bounce posts with no MIME text/plain part, or some more intelligent configuration of Mailman needs to be available so that posts within a digest will render properly under these circumstances. Maybe a more recent version of Mailman can do this, I don't know. Any suggestions would be appreciated. I rather dislike HTML-enhanced email (to put it gently). There's no fixed standard for it, and what renders one way in one mail reader renders some other way in another mail reader, and it confuses the hell out of list servers. But people will use it, increasingly it seems, and insist on doing so, so somehow this kind of problem needs to be dealt with. -- Lindsay Haisley | "Real programmers use butterflies" FMP Computer Services | 512-259-1190 | - xkcd http://www.fmp.com |

5 5

FAQ 4.12 "What about Verp" as applicable to sending to a relay host
by Anne Wainwright Oct. 21, 2011

Oct. 21, 2011

Hello, Not that I am going to switch on Verp, but ... I read this, and interesting sums there too. I note that Defaults.py still carries SMTP_MAX_RCPTS = 500 despite good conclusions in the FAQ based upon a statistical analysis of a large mailing list user base that the sweet spot is likely between 2 and 5. In my case where I am relaying to the isp's smtp server I indeed do have all my posts to one domain and so I presume that a larger value could be appropriate? Given that they limit me to 100 recipients per smtp session it would seem that I should adjust this downwards to <100 (in mm_cfg.py) to avoid breaking this rule. Please tell me that I'm heading in the right direction here. bestest Anne

2 2