Mailman 3 June 2011 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett 07 Nov '22

07 Nov '22

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman works". We also object to having to teach people how to fix their mailman installations because it's not documented in the current manual. This is *exactly* like Sendmail 14 years ago. We didn't accept it then, and Sendmail fixed the problem. RESOLUTION: Mailman default installation should not backscatter in a default configuration. 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup. 2. Discard or hold messages from non-subscribers by default. I would think that it would be perfectly reasonable to have documentation on how to enable the 1980s-style -request / -subscribe etc aliases. However this documentation should have a note that this is against the AUP of nearly every network provider, and enabling it will likely cause them to get listed in various blacklists as a backscatter source. FYI: I know that this goes against the instincts of many old-time mailing list advocates here. But after dealing with a 10k/hour backscatter DoS my tolerance for this problem is understandably limited. Yes, it was a sweet day back in the 1980s. I was running a mailing list server and several UUCP gateways at the time, so I remember them well. But those days are past, and we need to deal with the reality of today. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

21 168

Mailman 2.x Virtual Hosting
by Pavel Šimerda 09 Jul '11

09 Jul '11

Hello, I've just started playing with Mailman on a virtual hosting solution. I decided to write about it in the 'developers' mailing lists because I am ready to make some changes to the code and publish them. I know you're working on Mailman 3.x series but it's not ready yet (correct me if I'm wrong) and I would like to have a solution now. First thing that surprised me is that Mailman doesn't support virtual hosting. The second one was that documentation claimes it does. Even the simplest test, creation of lists with same names under different domains shows 2.x vhost support is simply broken. There are several modified versions of Mailman that claim to support vhosts. Mark Sapiro's version didn't work for me (most commands resulted in errors). It could have been broken by merging upstream code. https://code.launchpad.net/~msapiro/mailman/vhost There is a pretty good resource with patches at koumbit.net (in French): https://wiki.koumbit.net/VirtualMailman I tried to apply the 2.1.13 patch to Debian Squeeze's Mailman installation. And it sort of works. You can at least create the mailing lists now, which is good. Postfix virtual alias generator doesn't work. Mails are usually sent with wrong list e-mail addresses (the translated ones, not the public ones), so it's rather broken. But sending and recieving mail works. I would like to know if there's anyone else interested in getting Mailman 2.x to support a feature the documentation already claims to support. Testing, links to resources, code, and help with getting it official is welcome. Pavel Šimerda

3 6

MailMan Usage
by Aamir Khan 27 Jun '11

27 Jun '11

Mailman Developers, I would like to dedicate a email lets say help(a)example.com where you can send emails and depending upon the Text written inside the Mail..(doing some Regexp matching)...I have to call different actions like retrieving data from DB and then answering the query etc... So i would like to know whether Mailman is suitable for my problem to be solved...if not, can you suggest me the open source solution that can fulfill my need. -- Aamir Khan Indian Institute of Technology Roorkee, Roorkee, Uttarakhand, India , 247667 Phone: +91 9557647357 email: aamiruec(a)iitr.ernet.in ak4u2009(a)gmail.com

6 6

Mockup for New Design
by Andrew 24 Jun '11

24 Jun '11

Hi, I am sure very free software developer has the Mailman mailing list web page imprinted into their mind, however after looking at it for the thousandth time, I thought that there is a lot of uneeded information on a page where there doesn't need to be. Anyway I tried to improve it and the results are here http://and471.deviantart.com/art/GNU-Mailman-New-Design-214023110 I would love to hear your comments on it :) Thanks -- Andrew

5 11

[Mailman GSoC] Archive UI Web Framework
by Dushyant Bansal 24 Jun '11

24 Jun '11

Hi all, I was looking for a web framework for Pipermail UI. I have decided to use Pylons. Anna and benste wanted to know the reasons for choosing pylons over Django (As benste is already using Django for mailman WebUI). So, I thought I should discuss it with all of you. Andrew is working on converting Pipermail to use Storm/SQLite instead of pickles to save data. So, the framework needs to have support for Storm ORM. Django has its own ORM and Storm cannot be used with it natively (Though storm is said to have support <http://blogs.gnome.org/jamesh/2008/09/19/django-support-landed-in-storm/> for django, I could not find anything further to try/test Storm with Django). Pylons doesn't provide any ORM and I have tested a small application using Storm. Please give your feedback. Regards, Dushyant

5 6

Re: [Mailman-Developers] Mockup for New Design
by Andrew 21 Jun '11

21 Jun '11

On 21/06/11 09:31, David Andrews wrote: > I presume the page is "graphical" because as a blind, screen reader > using person, I got nothing out of it. Remember accessibility! Sure absolutely, this is just a image mockup to see what everyone thinks, it goes without saying that accessibility would have to be of paramount importance -- Andrew

3 2

FreeBSD 8.2, Python2.7, Exim-4 and MM3
by Odhiambo Washington 20 Jun '11

20 Jun '11

Hello everyone, This is my first post to this list so please bear with me. I am not a developer and as such I request you again to bear with me. My only endeavor is be able to get MM3 running on FreeBSD with Python2.7 and Exim 4 as the MTA. So far I have hit a deadlock, hence my coming to you. I have Python2.7 and py-sqlite3 installed from the ports. These are the latest versions on the FreeBSD ports tree. I have downloaded and installed MM-3.0 (mailman-3.0.0a7) and closely followed the instructions. So far, I've gotten stuck on one of the tests - `bin/mailman info`. Let me start with the output of bin/test -vv (I've truncated it to just the top and the bottom bits): <top bits> bin/test -vv Running tests at level 1 Running mailman.testing.layers.ConfigLayer tests: Set up mailman.testing.layers.MockAndMonkeyLayer in 0.000 seconds. Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/usr/local/mailman-3.0.0a7/src/mailman/testing/layers.py", line 120, in setUp initialize.initialize_2() File "/usr/local/mailman-3.0.0a7/src/mailman/core/initialize.py", line 145, in initialize_2 database.initialize(debug) File "/usr/local/mailman-3.0.0a7/src/mailman/database/stock.py", line 61, in initialize self._create(debug) File "/usr/local/mailman-3.0.0a7/src/mailman/database/stock.py", line 96, in _create database = create_database(url) File "/usr/local/mailman-3.0.0a7/eggs/storm-0.18-py2.7-freebsd-8.2-STABLE-i386.egg/storm/database.py", line 460, in create_database return factory(uri) File "/usr/local/mailman-3.0.0a7/eggs/storm-0.18-py2.7-freebsd-8.2-STABLE-i386.egg/storm/databases/sqlite.py", line 177, in __init__ raise DatabaseModuleError("'pysqlite2' module not found") DatabaseModuleError: 'pysqlite2' module not found Running mailman.testing.layers.SMTPLayer tests: Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/usr/local/mailman-3.0.0a7/src/mailman/testing/layers.py", line 91, in setUp initialize.initialize_1(INHIBIT_CONFIG_FILE) File "/usr/local/mailman-3.0.0a7/src/mailman/core/initialize.py", line 116, in initialize_1 mailman.config.config.load(config_path) File "/usr/local/mailman-3.0.0a7/src/mailman/config/config.py", line 105, in load self._post_process() File "/usr/local/mailman-3.0.0a7/src/mailman/config/config.py", line 125, in _post_process Switchboard.initialize() File "/usr/local/mailman-3.0.0a7/src/mailman/queue/__init__.py", line 87, in initialize 'Duplicate qrunner name: {0}'.format(name)) AssertionError: Duplicate qrunner name: retry Running mailman.testing.layers.RESTLayer tests: Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/usr/local/mailman-3.0.0a7/eggs/zope.testrunner-4.0.3-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/usr/local/mailman-3.0.0a7/src/mailman/testing/layers.py", line 91, in setUp initialize.initialize_1(INHIBIT_CONFIG_FILE) File "/usr/local/mailman-3.0.0a7/src/mailman/core/initialize.py", line 116, in initialize_1 mailman.config.config.load(config_path) File "/usr/local/mailman-3.0.0a7/src/mailman/config/config.py", line 105, in load self._post_process() File "/usr/local/mailman-3.0.0a7/src/mailman/config/config.py", line 125, in _post_process Switchboard.initialize() File "/usr/local/mailman-3.0.0a7/src/mailman/queue/__init__.py", line 87, in initialize 'Duplicate qrunner name: {0}'.format(name)) AssertionError: Duplicate qrunner name: retry </top bits> <bottom bits> Ran 134 tests with 0 failures and 0 errors in 0.728 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. Tests with errors: Layer: mailman.testing.layers.ConfigLayer Layer: mailman.testing.layers.SMTPLayer Layer: mailman.testing.layers.RESTLayer Total: 134 tests, 0 failures, 3 errors in 1.142 seconds. </bottom bits> So I can see the failures but have no clue of how to fix them. Now, when I invoke `bin/mailman info`, this is what I get: mail# bin/mailman info Traceback (most recent call last): File "bin/mailman", line 20, in <module> mailman.bin.mailman.main() File "/usr/local/mailman-3.0.0a7/src/mailman/bin/mailman.py", line 98, in main initialize(config_file) File "/usr/local/mailman-3.0.0a7/src/mailman/core/initialize.py", line 174, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/mailman-3.0.0a7/src/mailman/core/initialize.py", line 145, in initialize_2 database.initialize(debug) File "/usr/local/mailman-3.0.0a7/src/mailman/database/stock.py", line 61, in initialize self._create(debug) File "/usr/local/mailman-3.0.0a7/src/mailman/database/stock.py", line 96, in _create database = create_database(url) File "/usr/local/mailman-3.0.0a7/eggs/storm-0.18-py2.7-freebsd-8.2-STABLE-i386.egg/storm/database.py", line 460, in create_database return factory(uri) File "/usr/local/mailman-3.0.0a7/eggs/storm-0.18-py2.7-freebsd-8.2-STABLE-i386.egg/storm/databases/sqlite.py", line 177, in __init__ raise DatabaseModuleError("'pysqlite2' module not found") storm.exceptions.DatabaseModuleError: 'pysqlite2' module not found There is no py-sqlite2 port on FreeBSD 8.2 at the moment. Is there something I can do to get past this deadlock? The second part of my problem is how to integrate MM3 with Exim4. I am informed that things have greatly changed from the way Exim4 was configured with MM2 (2.1.x). I am hoping that there are Exim gurus here, who have already worked on a configuration for MM3+Exim and have documented the bits required for both exim.conf and mailman.cf. Thanks. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.

4 11

Change to MM3 REST API
by Barry Warsaw 16 Jun '11

16 Jun '11

Hi everyone. This is just a quick heads up, especially for the folks working on the Django web ui or other REST API clients for Mailman 3, that I've made a change to the API. The IMailingList attribute ``host_name`` has been changed to ``mail_host`` for consistency. (LP: #787599) This change is pushed to the bzr trunk and will be released with 3.0a8. Cheers, -Barry

1 0

Re: [Mailman-Developers] [Bug 283751] Re: feature request: fetch archived emails
by Richard Wackerbarth 15 Jun '11

15 Jun '11

This seems "out of place" for MM, per se. Providing this material is something that is intimately tied to the archiver. As I see it, the only thing that MM can do is to provide a "pass thru" conduit to whatever archiver the installation has chosen. Wacky On Jun 13, 2011, at 1:11 PM, Barry Warsaw wrote: > I think we'll probably do something like this in Mailman 3, but also, > I'm much more fond of providing a Gmane-like NNTP interface to the > archives. I find myself subscribing to fewer mailing lists these days > and just reading (and replying!) to them via Gmane. Works great. > > -- > You received this bug notification because you are a member of Mailman > Coders, which is subscribed to GNU Mailman. > https://bugs.launchpad.net/bugs/283751 > > Title: > feature request: fetch archived emails

2 1

Administrivia bug with 'set'
by Mark Sapiro 14 Jun '11

14 Jun '11

I recently noticed (by looking at code) that since the format of the email set command changed from set <option> {on|off} <password> to things like set authenticate <password> set <option> {on|off} in going from Mailman 2.0.x to 2.1, Mailman.Utils.is_administrivia() was never updated to account for the new formats, and therefore, valid set commands are never recognized as administrivia. I filed a bug at <https://bugs.launchpad.net/mailman/+bug/796836>. Please see the last paragraph of the bug report and let me know if you have an opinion. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0