Mailman 3 December 2007 - Mailman-Developers

Mailman 2.1.10b1 Released
by Mark Sapiro 02 Feb '08

02 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am happy to announce the first beta release of Mailman 2.1.10. This is a security and bug fix release and it is highly recommended that all sites upgrade to this version. Mailman 2.1.10 also adds support for two new language translations, Hebrew and Slovak and a few new features. 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, including download links, please see: http://www.list.org http://mailman.sf.net http://www.gnu.org/software/mailman Special thanks are due to Barry Warsaw and Tokio Kikuchi for much coding and support, Moritz Naumann for help with security issues and Jim Tittsler for a significant patch. Here's a list of the major changes. Security - The 2.1.9 fixes for CVE-2006-3636 have been enhanced. In particular, many potential cross-site scripting attacks have are now detected in editing templates and updating the list's info attribute via the web admin interface. Thanks again to Moritz Naumann for assistance with this. New Features - Changed cmd_who.py to list all members if authorization is with the list's admin or moderator password and to accept the password if the roster is public. Also changed the web roster to show hidden members when authorization is by site or list's admin or moderator password (1587651). - Added the ability to put a list name in accept_these_nonmembers to accept posts from members of that list (1220144). - Added a new 'sibling list' feature to exclude members of another list from receiving a post from this list if the other list is in the To: or Cc: of the post or to include members of the other list if that list is not in the To: or Cc: of the post (Patch ID 1347962). - Added the admin_member_chunksize attribute to the admin General Options interface (Bug 1072002, Partial RFE 782436). Internationalization - Added the Hebrew translation from Dov Zamir. This includes addition of a direction ('ltr', 'rtl') to the LC_DESCRIPTIONS table. The add_language() function defaults direction to 'ltr' to not break existing mm_cfg.py files. - Added the Slovak translation from Martin Matuska. - -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD4DBQFHVjjPVVuXXpU7hpMRArQHAJ9NE4Fj8b2rpWaXX6+BFa27wWB2MACWIGqJ 1wxPhA7ZBRVG9gSiEhTb2A== =vzXz -----END PGP SIGNATURE-----

2 3

Patches for true Virtual Hosting -- download site?
by Stephen J. Turnbull 30 Dec '07

30 Dec '07

barryc(a)quicksilverdragon.com writes: > As another aside, as noted in entry 4.47 in the Mailman FAQ ( > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.047.htp ) > CPanel apparently has patched this functionality into Mailman, but decline > to give back their changes. Given that Mailman is normally distributed > under the GPL, the only way that could be kosher That turns out not to be the case. The GPL does *not* require giving back (and according to the free software definition, a license that requires giving back is *non-free*). What the GPL requires is "giving forward" (ie, to the users of the software). It seems that the users of the software are the owners of the hardware on which it runs (the so-called "ASP loophole"). So what you need to do is find a cPanel licensee who has requested source from cPanel. At least one person possessing cPanel source has posted to the list in the last year or so, but there didn't seem to be much excitement about it.

1 0

Patches for true Virtual Hosting -- download site?
by barryc＠quicksilverdragon.com 30 Dec '07

30 Dec '07

There have been several conversations in the past about the fact that even across virtual domains, all lists must have unique names, and ways to fix this. In March of 2006, there was a large discussion which culminated in Hans Ulrich Niedermann posting links to the patches he was working on in this message: http://mail.python.org/pipermail/mailman-developers/2006-March/018629.html Unfortunately, neither the machine hosting the download page nor the one hosting the Git repository are responding to connections. Does anybody know if Hans made more progress on the patches after he made that post? And more importantly, since neither Google nor Archive.org happened to crawl the patch files, does anyone have copies? As another aside, as noted in entry 4.47 in the Mailman FAQ ( http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.047.htp ) CPanel apparently has patched this functionality into Mailman, but decline to give back their changes. Given that Mailman is normally distributed under the GPL, the only way that could be kosher is if they made a deal to distribute it under a different license. Would anyone be able to speak to whether or not that is the case?

1 0

Re: [Mailman-Developers] [Mailman-Users] Mailman error when sending a message
by Mark Sapiro 07 Dec '07

07 Dec '07

Kory Wheatley wrote: >I received this below error on one of our lists. I'm running Mailman >2.1.6. Do you know the cause of the below python error. > >Dec 07 09:07:59 2007 (19091) SHUNTING: >1197043677.7637711+7717478d0c42f9abb211298207f5ffa813512bae >Dec 07 09:53:22 2007 (19091) Uncaught runner exception: unpack list of >wrong size >Dec 07 09:53:22 2007 (19091) Traceback (most recent call last): > File "/home/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop > self._onefile(msg, msgdata) > File "/home/mailman/Mailman/Queue/Runner.py", line 167, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in >_dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in >_dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 92, in process > send_digests(mlist, mboxfp) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 133, in >send_digests > send_i18n_digests(mlist, mboxfp) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 315, in >send_i18n_digests > msg = scrubber(mlist, msg) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 266, in process > url = save_attachment(mlist, part, dir) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 411, in >save_attachment > filename = Utils.oneline(msg.get_filename(''), lcset) > File "/home/mailman/pythonlib/email/Message.py", line 724, in get_filename > filename = self.get_param('filename', missing, 'content-disposition') > File "/home/mailman/pythonlib/email/Message.py", line 607, in get_param > for k, v in self._get_params_preserve(failobj, header): > File "/home/mailman/pythonlib/email/Message.py", line 554, in >_get_params_preserve > params = Utils.decode_params(params) > File "/home/mailman/pythonlib/email/Utils.py", line 337, in decode_params > charset, language, value = decode_rfc2231(EMPTYSTRING.join(value)) > File "/home/mailman/pythonlib/email/Utils.py", line 284, in decode_rfc2231 > charset, language, s = parts >ValueError: unpack list of wrong size > >Dec 07 09:53:22 2007 (19091) SHUNTING: >1197046400.9411609+1cf11358e8862eae84391721d8fe3f1fae53d614 This problem has been 'partially avoided' since Mailman 2.1.7 and fixed since 2.1.9. See the thread that starts at <http://mail.python.org/pipermail/mailman-users/2007-August/058021.html> for a fairly complete description of the issue and see the post at <http://mail.python.org/pipermail/mailman-users/2007-July/057768.html> for information on what how to edit this list's digest.mbox file to clear this problem (until the next time). After editing the digest.mbox, you can run bin/unshunt to finish processing the shunted messages, but before doing this, it is a good idea to run bin/show_qfiles on qfile/shunt/* and delete any messages you don't want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Developers] [Mailman-Users] Changing the subscribers moderation flag
by Mark Sapiro 05 Dec '07

05 Dec '07

Kory Wheatley wrote: > >Every week we have a Mailman Mailing list that automatically has the >subscribers refreshed with a list in a file. There's a step that I >would like to add in this automated process and wonder if its possible. >Would it be possible to write a procedure to uncheck the moderate flag >in the mailing list for seven email subscriber addresses which are >authorized to send to the list? We only want a selected number to be >able to send emails without moderation but this has to be done to these >7 email addresses once a week after the list is refreshed with the >automated new subscriber list. The easy answer is use bin/sync_members to refresh the list and you won't have this problem. >Can I use "withlist" and a python script >to do this. I've written Python scripts but for this one I don't know >what options to change on the users subscribed configuration. See <http://www.msapiro.net/scripts/set_mod.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/set_mod.py>) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0