Mailman 3 May 2014 - Mailman-Developers

Fixing DMARC problems with .invalid munge
by John Levine May 7, 2014

May 7, 2014

I realize I'm a bit late to this party, but this is a technique that I don't think has been addressed here. On my lists I've fixed the DMARC bounces by rewriting From: lines of DMARC'ed domains like this on the way out: From: Marissa <mmeyer(a)yahoo.com> to From: Marissa <mmeyer(a)yahoo.com.invalid> Before you tell me I'm nuts, hear me out. I've actually implemented this, and it works. Advantages: * Really fixes DMARC problems * Everyone can still post to lists * Doesn't change the way users in non-DMARC'ed domains work * Leaves the author's address in the headers, so you can reply and use MUA sorting rules, give or take usenet-style unmunging. (This is a reason we dislike putting the list address in the From: line.) * Code is simple * Gives people a hint of where the actual problem lies R's, John PS: I use .invalid because RFC 6761 promises it will never be allocated to anyone.

7 24

Mailman 2.1.18 final release
by Mark Sapiro May 6, 2014

May 6, 2014

A critical incompatibility between the Mailman 2.1.18 final release and Python versions older than 2.6.5 or thereabouts affecting the DMARC Wrap Message action was discovered and fixed. This incompatibility also existed in the 2.1.16 and 2.1.17 releases. Thus, I have released Mailman 2.1.18-1 with a fix for this incompatibility. Please use 2.1.18-1 and not 2.1.18. These releases have new features to help with mitigation of the impacts of DMARC on mailing lists as well as fixing several bugs. Python 2.4 is the minimum supported, but Python 2.7 is recommended. There are significant new i18n strings associated with the DMARC mitigation features. If you are interested in helping with the translations of these strings, see <http://wiki.list.org/x/MQ>. There is also a new dependency associated with these features. Namely, the new Privacy options -> Sender filters -> dmarc_moderation_action feature requires that the dnspython <http://www.dnspython.org/> package be available in Python. See the attached README for more details. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see: http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.18-1 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Mailman 2.1.18 final release
by Mark Sapiro May 6, 2014

May 6, 2014

I'm pleased to announce the final release for Mailman 2.1.18. This release has new features to help with mitigation of the impacts of DMARC on mailing lists as well as fixing several bugs. Python 2.4 is the minimum supported, but Python 2.7 is recommended. There are significant new i18n strings associated with the DMARC mitigation features. If you are interested in helping with the translations of these strings, see <http://wiki.list.org/x/MQ>. There is also a new dependency associated with these features. Namely, the new Privacy options -> Sender filters -> dmarc_moderation_action feature requires that the dnspython <http://www.dnspython.org/> package be available in Python. See the attached README for more details. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see: http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.18 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 1

mailman-bundler-3.0b2: WSGI server error with zope.interface
by Tim Marx May 6, 2014

May 6, 2014

Hello, I wanted to test the new mailman-bundler-3.0b2 and ran into a problem I could not solve. I'm not sure if it's a problem with the mailman-bundler or with my machine. So I'm sorry for bothering you if the problem might be only on my server. I installed the latest revision (#13) of the branch lp:~abompard/mailman-bundler/mailman-bundler in a fresh virtualenv with flag --no-site-packages (because of earlier install attempts that failed) located under /var/tmp/mailman. I've created a user and a group ('mailman') who own the directory /var/tmp/mailman and I've added the user 'www-data' to the group 'mailman' so there might be no permission problem in my opinion. I followed the steps in START.rst (as 'production' installation) and everything worked fine so far. Then I wanted to setup the Postorius/Hyperkitty frontend access with Apache and mod_wsgi (3.3). I used the supplied ~/deployment/apache.conf as basis and added VirtualHost directives and custom logging and so on but I didn't change the WSGI... directives. Now when I try to access the configured domain I see always a "Server Error (500)" and the following stacktrace in my error log: ------------------------------------------------------------------------------------- ERROR 2014-05-05 23:46:03,342 base 5588 140076680513280 Internal Server Error: / Traceback (most recent call last): File "/var/tmp/mailman/mailman-bundler/eggs/Django-1.6.4-py2.7.egg/django/core/handlers/base.py", line 90, in get_response response = middleware_method(request) File "/var/tmp/mailman/mailman-bundler/eggs/HyperKitty-0.1.7-py2.7.egg/hyperkitty/middleware.py", line 67, in process_request store = kittystore.get_store(settings) File "/var/tmp/mailman/mailman-bundler/eggs/KittyStore-0.1.7-py2.7.egg/kittystore/__init__.py", line 52, in get_store from kittystore.storm import get_storm_store File "/var/tmp/mailman/mailman-bundler/eggs/KittyStore-0.1.7-py2.7.egg/kittystore/storm/__init__.py", line 11, in <module> from .store import StormStore File "/var/tmp/mailman/mailman-bundler/eggs/KittyStore-0.1.7-py2.7.egg/kittystore/storm/store.py", line 30, in <module> from kittystore.scrub import Scrubber File "/var/tmp/mailman/mailman-bundler/eggs/KittyStore-0.1.7-py2.7.egg/kittystore/scrub.py", line 26, in <module> from mailman.utilities.string import oneline File "/var/tmp/mailman/mailman-bundler/eggs/mailman-3.0.0b4-py2.7.egg/mailman/utilities/string.py", line 39, in <module> from zope.component import getUtility File "/var/tmp/mailman/mailman-bundler/eggs/zope.component-4.2.1-py2.7.egg/zope/component/__init__.py", line 19, in <module> from zope.interface import named ImportError: cannot import name named --------------------------------------------------------------------------------------- I have already found out, that this error occurs in zope.interface < 4.1.0, but I've definitly installed version 4.1.1. One interesting fact is, when I start the Django development server (with activated virtualenv) with './bin/mailman-web-django-admin runserver' this error doesn't occur. Thank you very much for any ideas and help! Tim Marx

2 1

Re: [Mailman-Developers] [Bug 1130957] Re: Unicode errors in mailman3
by Barry Warsaw May 5, 2014

May 5, 2014

On Apr 30, 2014, at 09:38 PM, Tim Marx wrote: >I'm using mailman 3.0.0b4 (with mailman-bundler) and ran into the same >problem as described above. Luckily I found this bug report and could manage >to fix it with the patches above. > >May I ask anybody (with more bazar-knowledge than me) to merge this two >patches into the mailman 3 branch? Thank you! I think we just need some test cases. Tim, can you provide any details on how you it the bug?

2 1

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Stephen J. Turnbull May 5, 2014

May 5, 2014

Tom Browder writes: > I think this GSoC project might be the place to at least start with > the option of choosing a list "style" such as a defined "read-only" > mailing list. Ah, OK, I see what you're getting at now. I think this is out of scope for the CLI project, although it's possible that providing some kind of scriptable interface (even a simple way to store a sequence of commands acting on the "current" list should suffice, where "current list" is a concept his proposal already includes) would allow it to be implemented relatively easily. I'll discuss that with Rajeev later. Still, I would expect that the "right" place to expose a "list style" capability is in Postorius. Most list admins are not even going to have access to the CLI, most likely, because we have *no* security model for it yet, except shell access to the list host. The CLI is going to be a "power user's" and sysadmin feature more than "the" way to manage lists for most people, AIUI. (Again, this is negotiable with the student.) Also, list "styles" probably should be "stored" in the Mailman core so they can be accessed from any client (which is what takes it right out of the scope of this GSoC IMO, although that's negotiable, again according to Rajeev's interest). HTH, Steve

2 2

Handling non-standard or obfuscated DSNs for DMARC rejects
by Stephen J. Turnbull May 5, 2014

May 5, 2014

It just occurred to me that (at the expense of a DNS query) many sites can distinguish DMARC rejects pretty well by doing a DNS query for the >From address (which I think we should be able to get, at least most of the time). This may not help much if you have most of your users posting from p=reject sites (you can't easily distinguish an obfuscated DMARC reject from a broken recipient address), but could save some of your users trouble if you have enough non-reject posters, or those users have standard DSNs that specify a DMARC reject. Of course you'd want to cache the result, I guess -- and actually, it would already available from when you accepted the post in the first place (if you have a non-null dmarc_moderation_action).

1 0

Re: [Mailman-Developers] Mailman-Suite demo server
by Aurelien Bompard May 5, 2014

May 5, 2014

> Currently there is no links to migrate between postorius(the mailman3 web > ui) and hyperkitty(the archiver). Yeah, and that's something I'll fix as soon as I'm done squashing the main bugs I have in my pile. Aurélien

1 0

Re: [Mailman-Developers] Mailman-Suite demo server
by Sylvain Viart May 4, 2014

May 4, 2014

Hi, On 04/05/2014 09:12, Abhilash Raj wrote: > I have setup a mailman-suite demo server here https://mailman.asynchronous.in/archives/ > All are invited to poke around ;-) No registration form? Is it a default setup? Regards, Sylvain.

2 1

Mailman-Suite demo server
by Abhilash Raj May 4, 2014

May 4, 2014

Hi all, I have setup a mailman-suite demo server here[1]. It uses the latest packages at pypi for postorius, mailman and hyperkitty. I have deployed using mailman- bundler and used its latest code from launchpad. All are invited to poke around ;-) thanks, Abhilash [1]: mailman.asynchronous.in

1 0