Mailman-Developers January 2008

mailman-developers@python.org

3 participants
4 discussions

by Mark Sapiro

-----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-----

13 years, 1 month

Re: [Mailman-Developers] [Mailman-Users] Efficient handling of cross-posting

by Stephen J. Turnbull

Moving to Mailman-Developers: > > It should go without saying that it's very interesting; this is a FAQ [...] > Woo-hoo. That's encouraging. Well, if the only thing, that prevented the > feature from appearing by now, is lack of development resources, then I'll > get right on it. Thanks, Well, it's not a lack of development resources alone. It's one of those "in principle" things, although not a religious principle (eg, you won't get the "this is evil" response from anybody the way you would with advocating Reply-To munging). The problem, in brief, is that the design of Mailman 1 and Mailman 2 is distribution-centric. They manage rosters of subscribers on behalf of a list. What you say you want is a program that manages groups of lists on behalf of a user. But this isn't quite good enough. What you really want is ... Usenet news, except on a push basis. Doing this efficiently and maintainably is going to require a global roster of users, which is something that Mailman 3 will provide. There are some simple, not-too-unclean hacks that can be done, but I think Mark Sapiro's "sister lists" feature is about the best that can be done.

13 years, 1 month

Mailman, OpenPGP and S/MIME (was: Re: [Ssls-dev] ssls for mailman 2.1.9)

by Joost van Baal

Hi, Thanks to Mike Gerber, the patch making Mailman OpenPGP and S/MIME-aware (which once was the SURFnet Secure List Server project) is updated to Mailman 2.1.9. Beware! This code is not mature, and very likely not yet suitable for production use. Inspect the code to find out if it's good enough for you. Specs: A post will be distributed only if the PGP (or S/MIME) signature on the post is from one of the list members. For sending encrypted email, a list member encrypts to the public key of the list. The post will be decrypted and re-encrypted to the public keys of all list members. Finally, each subscriber can upload her PGP and S/MIME public key using the webinterface. The Mailman SSLS project's home is at http://non-gnu.uvt.nl/mailman-ssls/. Sources are available from http://non-gnu.uvt.nl/pub/mailman/. On Wed, Jan 16, 2008 at 12:39:40AM +0100, Mike Gerber wrote: > > 1. The patch for 2.1.7 applies fine on 2.1.9. Here's the patch, just a > little repacked for 2.1.9: <snip> > > 2. I patched the current Mailman Debian package for etch, you can find it here > (Source and Binary package for i386/etch): > <snip> > the package works fine for me. <snip> > So, that's it. Joost, would you put those files up on the ssls page? Done, see http://non-gnu.uvt.nl/pub/mailman/. I've added some quotes too. Thanks a lot for your work! I'm _very_ happy the work is being continued! Bye, Joost -- Joost van Baal http://abramowitz.uvt.nl/ Tilburg University mailto:joostvb.uvt.nl The Netherlands

13 years, 1 month

Re: [Mailman-Developers] [Mailman-Users] Email classification

by Brad Knowles

On 1/12/08, Felipe Neuwald wrote: > I'm thinking, if some user send one email to the mail list, then the > mail server reply one email to the user with one web page addres, and > then, the user classify the email (like office, home, study, etc) and > before the classification, the email is sent to the mail list. There is > some way of email classification like these? Or other ways of email > classification? Mailman does not provide any tools to do this sort of thing. You could have users put the classification in the subject line, or you could go through the process outlined in the Mailman FAQ Wizard whereby a moderator can modify a message before it is posted to the list, but as I recall that's a pretty lengthy and painful process. I'm not aware of any other options in this case. -- Brad Knowles <brad(a)shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>

13 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers January 2008