Mailman 3 December 2012 - Mailman-Developers

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

08 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

RELEASED: GNU Mailman 3.0 beta 3
by Barry Warsaw 01 Jan '13

01 Jan '13

Hello friends of Mailman! I said I played this song so many times before That the melody keeps repeating Time for my usual "sneak one in before the new year" release! I'm happy to announce the third beta release of the core Mailman 3.0 engine. Mailman 3.0b3 is code named "Here Again". You can download GNU Mailman 3.0b3 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman The GNU Mailman documentation is available online at: http://packages.python.org/mailman Alpha releases of Postorius, our new web ui are available at: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius You might also like to take a look at the new archiver project called Hyperkitty: https://launchpad.net/hyperkitty GNU Mailman, Postorius, and Hyperkitty are all distributed under the GNU General Public License version 3 or later. Detailed changes in Mailman 3.0b3 are available here: http://tinyurl.com/adgeuwg Here's a summary of the most user and developer visible changes: * Python 2.7 is now required. Python 2.6 is no longer officially supported. * The canonical resource for a mailing list in the REST API now uses its list-id by default instead of its posting address. For backward compatibility, you can still reference a mailing list by its posting address. However the list-id is more stable since it will not change. * REST API change: The JSON representation for held messages has changed to a more flat representation. * You can now specify a list style to use when creating a mailing list through the REST API. * The `subject_prefix` attribute of mailing lists can be get/set through the REST API. Thanks to Terri Oda. * Membership change moderation (subscriptions and unsubscription requests) are available through the REST API. * `list_id` is added to the JSON representation for a mailing list. Thanks to Jimmy Bergman. * User resources are expanded in the REST API. You can change a user's display name or password, and you can now verify their password through REST by posting the plain text password and checking the HTTP response code. * Addresses can now be verified and unverified through the REST API. * Some changes have been made to the configuration file format. - [passlib]path is renamed to [passlib]configuration - [mta]configuration names a separate file to configure Postfix - The default style is now called `legacy-default`, and a `legacy-announce` style has been added. You can select the system default style through via the [styles]default configuration. * More database schema cleanups, in both the ban table and the mailinglist table. * Changes in the options for the `bin/mailman aliases` command. * Lots of other bug fixes. Enjoy, and Happy New Year, -Barry

1 0

(no subject)
by Sandesh Agrawal 29 Dec '12

29 Dec '12

I have trying to inject many messages into lmtp queue using : ./bin/mailman inject abc(a)xyz.com -f message_file -q lmtp But whenever i see the number of messages using: >>> from mailman.testing.helpers import get_queue_messages >>> items = get_queue_messages('lmtp') >>> len(items) it always display 1 , and on executing : >>>print items[0].msg.as_string() only the latest message is being displayed, where are other older messages going ?

1 0

Re: [Mailman-Developers] New to mailman
by Barry Warsaw 22 Dec '12

22 Dec '12

On Dec 22, 2012, at 01:02 PM, Sandesh Agrawal wrote: >I am using python 2.7.3 and bin/py interpreter prompt to run : > >>>> master = TestableMaster() >>>> master.start() > >But the following error occurs : >-------------------------------------------------------------------------- >Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/home/sandesh/mail_man/mailman-3.0.0b2/src/mailman/testing/helpers.py", >line 186, in start > self.start_runners(runners) > File "/home/sandesh/mail_man/mailman-3.0.0b2/src/mailman/bin/master.py", >line 385, in start_runners > for runner_config in config.runner_configs: > File "/home/sandesh/mail_man/mailman-3.0.0b2/src/mailman/config/config.py", >line 215, in runner_configs > for section in self._config.getByCategory('runner', []): >AttributeError: 'NoneType' object has no attribute 'getByCategory' >------------------------------------------------------------------------ > >should i not use bin/py or anything else need to be done. Remember that I said bin/py is just the Python interpreter with sys.path set up correctly, but no initializations done? That's what's happening here. None of the configuration system is set up by bin/py. You want `bin/mailman shell` which will give you an interpreter prompt with all the system initializations performed. Cheers, -Barry

1 0

Re: [Mailman-Developers] New to mailman
by Sandesh Agrawal 22 Dec '12

22 Dec '12

I am using python 2.7.3 and bin/py interpreter prompt to run : >>> master = TestableMaster() >>> master.start() But the following error occurs : -------------------------------------------------------------------------- Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/sandesh/mail_man/mailman-3.0.0b2/src/mailman/testing/helpers.py", line 186, in start self.start_runners(runners) File "/home/sandesh/mail_man/mailman-3.0.0b2/src/mailman/bin/master.py", line 385, in start_runners for runner_config in config.runner_configs: File "/home/sandesh/mail_man/mailman-3.0.0b2/src/mailman/config/config.py", line 215, in runner_configs for section in self._config.getByCategory('runner', []): AttributeError: 'NoneType' object has no attribute 'getByCategory' ------------------------------------------------------------------------ should i not use bin/py or anything else need to be done.

1 0

Re: [Mailman-Developers] New to mailman
by Barry Warsaw 22 Dec '12

22 Dec '12

On Dec 22, 2012, at 12:04 AM, Sandesh Agrawal wrote: >Yes i was using python's default interpreter which was causing >problems. /bin/py worked. Cool. >While making "class FakeArgs" for starting master process in mailman, > i am doing config = make_config(), > which gives the following error : make_config() is only useful for tests. Are you writing a unittest or doctest? Note that make_config() requires that the test live in the ConfigLayer or higher (zope.testing layers are a confusing construct since they don't follow normal Python inheritance rules, but for now, we're stuck with it.) Look at TestStart in commands/test/test_control.py. Note that doctests by default live in the SMTPLayer, which is higher than ConfigLayer and thus acceptable. >------------------------------------------------------------------------------------------------------------- >[config_file = os.path.join(os.path.dirname(config.filename), new_config) > File "/usr/lib/python2.6/posixpath.py", -----------------------^^^ Although this is probably not your problem, Python 2.7 is now required for Mailman 3. Cheers, -Barry

1 0

Re: [Mailman-Developers] New to mailman
by Barry Warsaw 22 Dec '12

22 Dec '12

On Dec 21, 2012, at 02:49 PM, Sandesh Agrawal wrote: >from mailman.commands.tests.test_control import make_config > >i got the following error: > >------------------------------------------------------------------------------------------- >Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "mailman/__init__.py", line 50, in <module> > from mailman.core.i18n import initialize > File "mailman/core/i18n.py", line 31, in <module> > from flufl.i18n import PackageStrategy, registry >ImportError: No module named flufl.i18n > >----------------------------------------------------------------------------------------------------- > flufl.i18n is present in "eggs" directory which is above the mailman >directory in hierarchy , so just mentioning "from flufl.i18n" can not >detect the required python module. > >How can this problem be fixed ? Did you type this into the interpreter prompt? If so, how did you start Python? Where exactly did you "run this"? Note that the standard Python interpreter doesn't have its sys.path set up to import from the eggs directory. Use bin/py for that. (If you're wondering what the difference is between `bin/py` and `bin/mailman shell`, it's that the latter does all the Mailman initializations necessary to operate Mailman. E.g. it inits the log system, the ZCA, etc.) Cheers, -Barry

2 1

Re: [Mailman-Developers] Wiki woes
by Paul Boddie 21 Dec '12

21 Dec '12

Hello, I was just reading the discussion about Wiki migration from Confluence to MoinMoin on this list (mailman-developers). When this topic was first raised, a mailing list was set up along with some other resources for collaboration: http://lists.bjdean.id.au/cgi-bin/mailman/listinfo/mmwiki http://moinmo.in/ConfluenceConverter I was under the impression that people would be following the dedicated mailing list for this work (mmwiki), but it would appear that this is not the case. The last message I sent on this topic was this one: http://lists.bjdean.id.au/pipermail/mmwiki/2012q3/000095.html In fact, it touches upon the very issue that seems to be causing problems now: Confluence appears to have changed and useful functionality has been removed. Although this affects Confluence users in a negative way, it may have an impact on the exported form used in any migration work as well. If you would like a summary of the work I have done so far to migrate the content, take a look at the following mail: http://lists.bjdean.id.au/pipermail/mmwiki/2012q2/000092.html There's another mail (cross-posted to moin-user) which references the content repository used as the basis of this effort, too: http://lists.bjdean.id.au/pipermail/mmwiki/2012q2/000094.html As far as I know, the volunteer to whom I was responding has not done any work on this. In short, after Bradley Dean's initial research, I have written something which can convert Confluence content, although there will undoubtedly be things that need finishing, and if you take a look at the ConfluenceConverter pages, you may also be able to identify functionality that needs deploying or implementing in MoinMoin depending on the project's needs. So, I would recommend that you don't start from scratch on this. If you like, I can even make an example of the migrated content available on the Internet so that you can see what needs doing, but you will, of course, need to let me know. I was going to mail this list (mailman-developers), given that the other one (mmwiki) seems dormant, and apologise for not having done so earlier, but this initiative really needs input from the actual Wiki users to be worthwhile, in my opinion. Please let me know if you want to take this work any further. Paul

5 13

Re: [Mailman-Developers] New to mailman
by Barry Warsaw 21 Dec '12

21 Dec '12

On Dec 21, 2012, at 01:29 AM, Sandesh Agrawal wrote: >1. I was going through ~/runners/lmtp.py in mailman 3 source code and >found a line "from zope.component import getUtility" but there is no >folder named zope anywhere, am i missing something ? After you've done the buildout steps, you'll notice a directory at the root called 'eggs'. These are a Python packaging format, which can be directories or zip (.egg) files though we only use directories. If you look in there, you'll see a zope.component egg directory which buildout grabbed from PyPI. When you run scripts in the bin directory, buildout will have set up all the magic so that imports from the eggs directory Just Work. Note that once we get to deploying this, we won't use buildout eggs. Most likely, dependencies such as zope.component will come from your OS vendor. Or alternatively, if you use virtualenv, those would also be downloaded from PyPI, although the mechanism to make them available to Python code is somewhat different. You can always test this out interactively: $ bin/py Python 2.7.3 (default, Dec 12 2012, 19:00:09) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import zope.component >>> zope.component.__file__ '/home/barry/projects/mailman/3.0/eggs/zope.component-4.0.1-py2.7.egg/zope/component/__init__.pyc' >>> >2. Where are the definition of all the functions of classes defined in >/mailman/interfaces in mailman 3 source code present ? These you do have to hunt around for. Many are defined in the various src/mailman/model/*.py classes, but those are only the Storm ORM classes. Others can be defined almost anywhere. Some of the interfaces define "utilities", essentially singleton instances implementing an interface. If you look at src/mailman/config/configure.zcml, you'll see the zope.component definition file hooking those interfaces up to the classes that implement the utilities. Others are "adapters", which take one interfaces and wrap them up into other interfaces. E.g. if you have an IMailingList and want to get an IBanManager from it, you "adapt it" in zope.component parlance. Inside configure.zcml, you'll see where the class implementing the adapter (a.k.a. the "factory") is defined. Some interfaces can have multiple instances, and the classes implementing them can live anywhere. There's no registration service for such things because they usually aren't instantiated by interface name, so they are harder to find. Examples include the IRule instances (which live in src/mailman/rules/*.py) or the IHandlers (src/mailman/handlers/*.py). It's helpful to have a good support from your text editor or file system to find things, such as a class browser, tags, or for Emacs users bzr-tools-grep. Cheers, -Barry

2 1

Re: [Mailman-Developers] New to mailman
by Terri Oda 21 Dec '12

21 Dec '12

On 12/10/2012 10:51 AM, Sandesh Agrawal wrote: > Hey Terri, i would really like to make a written transcript while i learn > about the architecture. Writing them as soon as i learn would be much > easier, for that i would require the write access to wiki. > > I created my launchpad account with email id: sakuag333(a)gmail.com > I am not sure which username are you talking about. That would be great! The wiki has a separate account system from launchpad, sadly, and can be found here: http://wiki.list.org

2 2