Mailman 3 January 2003 - Mailman-Developers

[ mailman-Patches-645297 ] Add PGP support
by SourceForge.net Jan. 4, 2003

Jan. 4, 2003

Patches item #645297, was opened at 2002-11-28 14:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_i… Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Ben Laurie (benl) Assigned to: Nobody/Anonymous (nobody) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. ---------------------------------------------------------------------- Comment By: David Shaw (dmshaw) Date: 2003-01-04 19:59 Message: Logged In: YES user_id=606006 Another vote of support. I actually submitted an enhancement request earlier today for exactly this. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:37 Message: Logged In: YES user_id=147905 Adding a vote of support for this patch. Please add it as soon as it's appropriate! I've been waiting a long time for this functionality and I'd hate to see the patch bitrot. :-) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-12 03:56 Message: Logged In: YES user_id=12800 I have to defer this patch until after MM2.1 since we're about ready for the first release candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_i…

1 0

[ mailman-Feature Requests-662277 ] Encryption feature
by SourceForge.net Jan. 4, 2003

Jan. 4, 2003

Feature Requests item #662277, was opened at 2003-01-04 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Encryption feature Initial Comment: A feature that would allow a listmember to submit a PGP/GnuPG key to Mailman and thereafter all mail sent to that listmember would be encrypted with that key. Obviously, this would imply individual mail delivery to that user as it would no longer be possible to send the same mail to everyone. Also obviously, this would only really be possible for list servers with some spare CPU cycles... ---------------------------------------------------------------------- Comment By: Matthew Davis (big-dog) Date: 2003-01-04 13:59 Message: Logged In: YES user_id=34240 Take a look at http://sourceforge.net/tracker/index.php?func=detail&aid=645297&group_id=10… I think it's for one of the beta's. But it should get you pointed in the right direction. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_i…

1 0

[ mailman-Feature Requests-662277 ] Encryption feature
by SourceForge.net Jan. 4, 2003

Jan. 4, 2003

Feature Requests item #662277, was opened at 2003-01-04 18:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Encryption feature Initial Comment: A feature that would allow a listmember to submit a PGP/GnuPG key to Mailman and thereafter all mail sent to that listmember would be encrypted with that key. Obviously, this would imply individual mail delivery to that user as it would no longer be possible to send the same mail to everyone. Also obviously, this would only really be possible for list servers with some spare CPU cycles... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_i…

1 0

[ mailman-Bugs-662163 ] Autoreplies confirm subscription invitations
by SourceForge.net Jan. 4, 2003

Jan. 4, 2003

Bugs item #662163, was opened at 2003-01-04 11:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Autoreplies confirm subscription invitations Initial Comment: I'm not sure of the exact circumstances (maybe personalization needs to be on), bu t i fyou "invite" people to join a mailing list, or, presumably, if someone sends a message to list-join, and there is an autoresponder at that address, the address is subscribed to the list without the subscriber being aware of it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_i…

1 0

[ mailman-Bugs-662127 ] Race condition with summary modification screen
by SourceForge.net Jan. 4, 2003

Jan. 4, 2003

Bugs item #662127, was opened at 2003-01-04 14:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Race condition with summary modification screen Initial Comment: I just upgraded to 2.1 and noticed an interesting race condition with the summary version of the moderation page. Take this timeline: 1) user(a)example.com sends 3 messages to the list 2) moderator visits summary moderation page and sees the 3 messages 3) user(a)example.com sends another message to the list 4) moderator clicks "discard" and submits The end result is that Mailman discards 4 messages, including the latest one that the moderator did not get to see. This does not happen with the old-style "details" version of the moderation page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_i…

1 0

[ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11
by SourceForge.net Jan. 4, 2003

Jan. 4, 2003

Bugs item #563336, was opened at 2002-06-01 12:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_i… Category: (un)subscribing Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 1 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-04 02:15 Message: Logged In: YES user_id=12800 I lowered the priority in a ham-handed approach to concentrating on MM2.1 bugs. I simply don't have the time to continue to support the 2.0 branch for anything other than critical security problems (which this isn't). Plus, you should at least upgrade to 2.0.13, the latest stable release of the 2.0 branch! :) This is very likely fixed in 2.1 as the entire mail command handler (and so much else :) has been rewritten. I'm closing this as won't fix. I recommend upgrading to 2.1. ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-01-03 09:56 Message: Logged In: YES user_id=38966 Hmm. Looks as if Barry lowered the priority for this with no comment. I think that's unfortunate. I just ran into this as well. If this is truly just some user getting their password wrong, why isn't the exception trapped, and the user allowed to try again? This is the reason this puzzles me so: putting in the wrong password is a common thing to do. I myself sometimes trip up the password to my list admin areas. So when mailman goes out of its way to send me an e-mail with such a traceback, it makes me wonder whether something especially nasty is going on. A better message would help a lot. I'd be grateful for some note on this open issue from the developers, at least. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_i…

1 0

RELEASED Mailman 2.1 - final
by barry＠python.org Jan. 3, 2003

Jan. 3, 2003

After nearly two years of development, we are happy to announce the release of GNU Mailman 2.1. Mailman is free software that enables users to manage email mailing lists and e-newsletters. Its integrated web interface provides easy-to-use access for list members and list administrators. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, spam filters, and more. Mailman 2.1 is fully internationalized, supporting 17 languages out-of-the-box. A summary of additional new features in Mailman 2.1 is outlined below. The NEWS file in the source distribution contains more details about all the new features. For more information on Mailman, including downloading and installation instructions, please visit one of the following mirror sites: http://www.list.org http://www.gnu.org/software/mailman http://mailman.sf.net The Mailman developers wish to thank Control.com for their sponsorship of several Mailman 2.1 features, Zope Corporation for their support, and the entire Mailman community for their contributions. -Barry Warsaw Pythonlabs, Zope Corporation -------------------- snip snip -------------------- - Multi-lingual support for all web pages and Mailman generated email notices, with languages selectable on a per-site, per-list, and per-user basis. - Through-the-web list creation and removal; (with automatic support depending on the MTA) - "Real name" support for members - Improved simple user-task operation (e.g. no passwords required for subscription and unsubscription). - Support for personalized deliveries and VERP-like message delivery for foolproof bounce detection - Emergency moderation - MIME-based content-filtering, with demime/stripmime-like options - Regular expression based topic-filtering - Better membership management, including searching - Re-organized administrative requests pages - Moderated newsgroup support - A new architecture for the mail delivery subsystem, removing dependence on cron, resulting in improved responsiveness and scalability - New moderation and privacy controls - Invitations - Autoresponse governors - Users can now change some delivery options globally, for all lists at a site, including their password, delivery status, real name, and more. - Improved MIME and I18n support in the archiver - Addition of a separate "list moderator" role - Urgent: header support (bypasses digests to reach all users immediately).

2 1

[ mailman-Patches-644810 ] Sendmail mailer in Python
by SourceForge.net Jan. 3, 2003

Jan. 3, 2003

Patches item #644810, was opened at 2002-11-27 16:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion <dgc(a)uchicago.edu> which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-01-03 18:19 Message: Logged In: YES user_id=75166 the mm_mailer script in mailer-2.1-0.2.patch now handles VERP'ed return addresses in bounced mail which I missed in the original implementation ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:34 Message: Logged In: YES user_id=75166 mailer-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 12:16 Message: Logged In: YES user_id=75166 mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds the case of listname and servername for compaiblity with MMs naive belief that listnames are case all lower case. case "(Email addresses are not case sensitive, but they are sensitive to almost everything else :-)" ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:37 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:36 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_i…

1 0

[ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11
by noreply＠sourceforge.net Jan. 3, 2003

Jan. 3, 2003

Bugs item #563336, was opened at 2002-06-01 16:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_i… Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-01-03 14:56 Message: Logged In: YES user_id=38966 Hmm. Looks as if Barry lowered the priority for this with no comment. I think that's unfortunate. I just ran into this as well. If this is truly just some user getting their password wrong, why isn't the exception trapped, and the user allowed to try again? This is the reason this puzzles me so: putting in the wrong password is a common thing to do. I myself sometimes trip up the password to my list admin areas. So when mailman goes out of its way to send me an e-mail with such a traceback, it makes me wonder whether something especially nasty is going on. A better message would help a lot. I'd be grateful for some note on this open issue from the developers, at least. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_i…

1 0

more on that password crash.
by Chuq Von Rospach Jan. 3, 2003

Jan. 3, 2003

I think I found it. Turns out a couple of things weren't compiling right on MacOS X (the japanese and chinese language additions). that turns out to be a minor bug in how MacOS X ships a python config file. More details here: <http://www.plaidworks.com/chuqui/blog/000150.html#000150> (maybe this should get faqqed?) -- Chuq Von Rospach, Architech chuqui(a)plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek

3 3