From noreply at sourceforge.net Thu Jan 1 10:40:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 1 10:40:50 2004 Subject: [ mailman-Feature Requests-415137 ] CSS for webpage design. Message-ID: Feature Requests item #415137, was opened at 2001-04-10 08:00 Message generated for change (Comment added) made by bourdeau You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=415137&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: CSS for webpage design. Initial Comment: It would be very nice to be able to change the looks of the web pages by using CSS. Ie, include a Feature Requests item #868838, was opened at 2004-01-01 10:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=868838&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert H. Bourdeau (bourdeau) Assigned to: Nobody/Anonymous (nobody) Summary: More variables for use in templates Initial Comment: When a template is rendered, only selected variables are included- ones that we're imagined as necessary for the default Mailman templates. All variables that are not "template-specific" should be made available to every template. For example, when rendering the "article" template to present a single message in a list archive, the variable 'listinfo' is not in the dictionary for use by the template. However, 'listinfo' IS available for use to in "archtoc" template. 'listinfo' can be used to create a hyperlink from an article BACK to the list information page. Better yet, some additional URL variables would be helpful. I'd really rather link from an article back to the 'archtoc' page (set to the same sort order as when the user chose the article to view). That would be useful to always have in a variable. Basic principle here is that the SafeDict object that is used to render a template should always be as fully populated as possible. This gives the Mailman administrator (and list administrator) many more options for designing web pages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=868838&group_id=103 From noreply at sourceforge.net Fri Jan 2 10:14:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 10:15:05 2004 Subject: [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:14 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:39 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:40 Message: Logged In: YES user_id=75166 exitstatus-2.1.2-0.1.patch is a revision of the patch for MM 2.1.2 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 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=644797&group_id=103 From noreply at sourceforge.net Fri Jan 2 10:20:56 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 10:21:02 2004 Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 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 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: 2004-01-02 15:20 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:33 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:31 Message: Logged In: YES user_id=75166 mailer-2.1.2-0.1.patch.gz removes support for MM 2.0.13 mail aliases from the mailer and is MM 2.1.2 compatible ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- 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_id=103 From noreply at sourceforge.net Fri Jan 2 10:23:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 10:23:56 2004 Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 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 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: 2004-01-02 15:23 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.2.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:20 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:33 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:31 Message: Logged In: YES user_id=75166 mailer-2.1.2-0.1.patch.gz removes support for MM 2.0.13 mail aliases from the mailer and is MM 2.1.2 compatible ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- 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_id=103 From noreply at sourceforge.net Fri Jan 2 10:28:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 10:28:44 2004 Subject: [ mailman-Patches-760567 ] moderation request message content Message-ID: Patches item #760567, was opened at 2003-06-25 15:25 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: moderation request message content Initial Comment: This patch makes per-list configurable the inclusion of the body of messages that require moderation in the request messages sent to list moderators. This patch has similar objectives to those of patch #593674 but is a simpler implementation. This adds one list attribute, which can be set or unset via the web admin GUI, and which controls whether the moderated message body is included in the moderator request. Apply the attached patch file with the MM build directory as the current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:28 Message: Logged In: YES user_id=75166 modinc-2.1.4-0.1.patch is a MM 2.1.4 compatible veriosn of this patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 17:29 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1.5 since I don't want to add any new list attributes at this late date. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:43 Message: Logged In: YES user_id=75166 modinc-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-25 17:21 Message: Logged In: YES user_id=75166 Missed one changed file from initial patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 From noreply at sourceforge.net Fri Jan 2 10:32:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 10:32:56 2004 Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch Message-ID: Patches item #820723, was opened at 2003-10-09 16:19 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.3-0.6.patch better supports the use of MHonArc -saveresources option. Also fixes minor HTML syntax error in mhonarc.mrc and author.mrc that affected generated date and author index pages. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-14 05:49 Message: Logged In: YES user_id=75166 With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself defined in Defaults.py is the empty string and, until this is changed, the option to select MHonArc instead of pipermail for per-list archiving is not offered on the web admin GUI. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-10 17:51 Message: Logged In: YES user_id=75166 Under some circumstances, when a single message is passed to MHonArc for archiving via a pipe, MHonArc may finish its processing and exit, closing its STDIN before the Mailman process that invoked it has finished output of the message to the pipe. Mistakenly, the patched pipermail code treated this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 From noreply at sourceforge.net Fri Jan 2 11:53:42 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 11:53:49 2004 Subject: [ mailman-Patches-869394 ] Enhanced logging for filter rule discards Message-ID: Patches item #869394, was opened at 2004-01-02 10:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869394&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Enhanced logging for filter rule discards Initial Comment: I started playing with the filter rules to automatically discard messages that had relatively high spam scores. I noticed, however, that the logging when a message is discarded was rather poor. So, I hacked together a bit of code to improve the logging. NOTICE: I am not a Python programmer ... so I can't gaurantee that this patch is without error. It seems to work on my system, but that's all I can say. This is a patch on Mailman 2.1.4! The vette log entry will look something like this: Jan 02 10:43:04 2004 (7665) testlist post from root@linux.midrange.com discarded, msgid: <200401021643.i02Gh3B2007694@linux.xxxxx.com>: Message discarded by filter rule match ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869394&group_id=103 From noreply at sourceforge.net Fri Jan 2 18:24:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 18:24:06 2004 Subject: [ mailman-Patches-869638 ] Postfix XVERP support, Mailman 2.1.4 cut Message-ID: Patches item #869638, was opened at 2004-01-03 00:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869638&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix XVERP support, Mailman 2.1.4 cut Initial Comment: I have found Colin Palmer's patch to support XVERP with Postfix at http://sourceforge.net/tracker/index.php? func=detail&aid=731100&group_id=103&atid=300103 to be quite useful. Unfortunately, it no longer applies to Mailman 2. 1.4, so I have updated it. Find the updated version attached. Thanks, Colin! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869638&group_id=103 From noreply at sourceforge.net Fri Jan 2 18:24:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 18:24:48 2004 Subject: [ mailman-Patches-731100 ] Postfix XVERP support for SMTPDirect.py Message-ID: Patches item #731100, was opened at 2003-05-02 03:44 Message generated for change (Comment added) made by m-a You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix XVERP support for SMTPDirect.py Initial Comment: This patch adds support for Postfix's XVERP ESMTP extension for doing VERP on delivery instead of requiring Mailman to inject the message once per recipient when VERPing. This patch is against Mailman 2.1.2 To make it work, add: VERP_STYLE = 'Postfix' POSTFIX_XVERP_OPTS = '+=' to mm_cfg.py And to go back to Mailman's way of doing VERP, you can set VERP_STYLE = 'Mailman' ---------------------------------------------------------------------- Comment By: Matthias Andree (m-a) Date: 2004-01-03 00:24 Message: Logged In: YES user_id=2788 I have updated the patch for 2.1.4, find it at http://sourceforge.net/tracker/index.php? func=detail&aid=869638&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 From noreply at sourceforge.net Fri Jan 2 18:45:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 18:45:56 2004 Subject: [ mailman-Patches-869644 ] Fix: Error accessing priv. roster/arch w/ non-member address Message-ID: Patches item #869644, was opened at 2004-01-03 00:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Fix: Error accessing priv. roster/arch w/ non-member address Initial Comment: Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. This patch solves the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 From noreply at sourceforge.net Fri Jan 2 18:47:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 18:47:49 2004 Subject: [ mailman-Patches-869644 ] Fix: Error accessing priv. roster/arch w/ non-member address Message-ID: Patches item #869644, was opened at 2004-01-03 00:45 Message generated for change (Settings changed) made by berndts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Fix: Error accessing priv. roster/arch w/ non-member address Initial Comment: Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. This patch solves the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 From noreply at sourceforge.net Fri Jan 2 18:48:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 18:48:25 2004 Subject: [ mailman-Bugs-869647 ] Error when accessing priv. roster/arch w/ non-member address Message-ID: Bugs item #869647, was opened at 2004-01-03 00:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Error when accessing priv. roster/arch w/ non-member address Initial Comment: Barry removed to much code while trying to correct bug #864676. : ( So Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. One possible solution is patch #869644. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 From noreply at sourceforge.net Fri Jan 2 18:48:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 18:48:42 2004 Subject: [ mailman-Bugs-869647 ] Error when accessing priv. roster/arch w/ non-member address Message-ID: Bugs item #869647, was opened at 2004-01-03 00:48 Message generated for change (Settings changed) made by berndts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Error when accessing priv. roster/arch w/ non-member address Initial Comment: Barry removed to much code while trying to correct bug #864676. : ( So Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. One possible solution is patch #869644. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 From noreply at sourceforge.net Fri Jan 2 19:02:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 19:02:06 2004 Subject: [ mailman-Patches-869644 ] Fix: Error accessing priv. roster/arch w/ non-member address Message-ID: Patches item #869644, was opened at 2004-01-02 18:45 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Fix: Error accessing priv. roster/arch w/ non-member address Initial Comment: Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. This patch solves the problem. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-02 19:02 Message: Logged In: YES user_id=12800 Are you sure you're looking at version 2.20.2.2 of SecurityManager.py? Here's what the AuthUser clause looks like: elif ac == mm_cfg.AuthUser: if user is not None: try: if self.authenticateMember(user, response): return ac except Errors.NotAMemberError: pass This doesn't match patch the patch, so I'm wondering if your files are out of date? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 From noreply at sourceforge.net Fri Jan 2 19:03:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 19:03:13 2004 Subject: [ mailman-Bugs-869647 ] Error when accessing priv. roster/arch w/ non-member address Message-ID: Bugs item #869647, was opened at 2004-01-02 18:48 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Error when accessing priv. roster/arch w/ non-member address Initial Comment: Barry removed to much code while trying to correct bug #864676. : ( So Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. One possible solution is patch #869644. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-02 19:03 Message: Logged In: YES user_id=12800 Please see the comment in patch 869644. BTW, it's fine if you have a patch that specifically fixes a bug, to attach the patch to the bug report directly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 From noreply at sourceforge.net Fri Jan 2 19:09:53 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 19:09:57 2004 Subject: [ mailman-Patches-869644 ] Fix: Error accessing priv. roster/arch w/ non-member address Message-ID: Patches item #869644, was opened at 2004-01-03 00:45 Message generated for change (Comment added) made by berndts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Fix: Error accessing priv. roster/arch w/ non-member address Initial Comment: Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. This patch solves the problem. ---------------------------------------------------------------------- >Comment By: Stephan Berndts (berndts) Date: 2004-01-03 01:09 Message: Logged In: YES user_id=129854 That's a completely different position in the file!? I am in function __checkone, not in Authenticate. Your comment does not match my patch :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-03 01:02 Message: Logged In: YES user_id=12800 Are you sure you're looking at version 2.20.2.2 of SecurityManager.py? Here's what the AuthUser clause looks like: elif ac == mm_cfg.AuthUser: if user is not None: try: if self.authenticateMember(user, response): return ac except Errors.NotAMemberError: pass This doesn't match patch the patch, so I'm wondering if your files are out of date? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 From noreply at sourceforge.net Fri Jan 2 20:14:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 20:14:06 2004 Subject: [ mailman-Bugs-869647 ] Error when accessing priv. roster/arch w/ non-member address Message-ID: Bugs item #869647, was opened at 2004-01-02 18:48 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Error when accessing priv. roster/arch w/ non-member address Initial Comment: Barry removed to much code while trying to correct bug #864676. : ( So Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. One possible solution is patch #869644. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-02 19:03 Message: Logged In: YES user_id=12800 Please see the comment in patch 869644. BTW, it's fine if you have a patch that specifically fixes a bug, to attach the patch to the bug report directly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=869647&group_id=103 From noreply at sourceforge.net Fri Jan 2 20:15:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 2 20:15:39 2004 Subject: [ mailman-Patches-869644 ] Fix: Error accessing priv. roster/arch w/ non-member address Message-ID: Patches item #869644, was opened at 2004-01-02 18:45 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Fix: Error accessing priv. roster/arch w/ non-member address Initial Comment: Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. This patch solves the problem. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-02 20:15 Message: Logged In: YES user_id=12800 Someone I downloaded an older SecurityManager.py.patch. I grabbed it again and now see what you're talking about. Here's one way the bug can be manifest: if you were a member when you logged in to read the archives, but got subsequently removed before your cookie expired (i.e. your browser exited). Is there another way this crash can happen? ---------------------------------------------------------------------- Comment By: Stephan Berndts (berndts) Date: 2004-01-02 19:09 Message: Logged In: YES user_id=129854 That's a completely different position in the file!? I am in function __checkone, not in Authenticate. Your comment does not match my patch :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-02 19:02 Message: Logged In: YES user_id=12800 Are you sure you're looking at version 2.20.2.2 of SecurityManager.py? Here's what the AuthUser clause looks like: elif ac == mm_cfg.AuthUser: if user is not None: try: if self.authenticateMember(user, response): return ac except Errors.NotAMemberError: pass This doesn't match patch the patch, so I'm wondering if your files are out of date? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 From noreply at sourceforge.net Sat Jan 3 04:16:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 3 04:18:00 2004 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd patch -p1 < ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-03 09:16 Message: Logged In: YES user_id=75166 htdig-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-12-15 16:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.5.patch modifies htdig.py and private.py; the security changes introduced by htdig-2.1.3-0.2 patch to these scripts incorrectly blocked access to the listname.mbox/listname.mbox file. The 0.5 revision of the patch corrects this error. This problem and a suggested fix were pointed out to me in a private email by Stephan Berndts stb-mm at spline.de ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:55 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.4.patch provides minor improvements in handling of HTTP request handled by htidg.py which lead to the user receiving an authentication challenge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-19 21:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.3.patch.gz add minor private archive security improvements to the patch for MM 2.1.3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:14 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:47 Message: Logged In: YES user_id=75166 last comment should have read: htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:45 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 19:00 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz adds some minor performance improvement in template handling in MM 2.1.2 You should consider also applying this bug-fis patch: [ 730769 ] template access hierarchy is broken http://sourceforge.net/tracker/index.php? func=detail&aid=730769&group_id=103&atid=100103 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 15:44 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:46 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 compatibility. It also incoporates a previosuly unpublished change to overcome a potential problem with htdig excluced urls - see the INSTALL.htdig-mm file for more information ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 18:29 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch handling multi-page search results from htsearch. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 17:54 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is rasing an excpetion because it has had a problem running htsearch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-20 14:10 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.2.patch.gz close a security exploit which allows leakage of information held in htdig's per-list search indexes to users not authorized to view private list archives. Read file INSTALL.htdig-mm installed by this patch for details and instructions for upgrading MM installations using earlier versions of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:50 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-05 18:12 Message: Logged In: YES user_id=75166 It seems it is possible, if this patch is installed, for a list's htdig conf file and the list specific htdig index db files to be read directly through the web interface for list archives. Even if this patch isn't installed it seems a list's pipermail.pck file can also be read directly through the web interface for list archives. This seems to be true for accesses via /pipermail for public lists and via /mailman/private for private lists. The problem does not occur for htdig search results accessed via /mailman/htdig as the htdig.py script is more protective than private.py Broadly speaking the data affected is availble to a user in normal operation which is why I do not consider the issue to be a security breach as such. Adding the following RewriteRule to Apache's httpd.conf prevents the situation, assuming you got the RewriteEngine On: RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.html [F] RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.htm l [F] You could, of course, substitute an R flag for the F flag on the RewriteRules and be more hacker friendly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-22 14:20 Message: Logged In: YES user_id=75166 htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope that all of them! Stops use of obsolete config variable DEFAULT_HOST in several files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:18 Message: Logged In: YES user_id=75166 htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with an adverse interaction between htdig.py and a bug in $prefix/scripts/driver (see #668685 for a patch to fix this). It also improves the content type and security handling by htdig.py for MM 2.1 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:14 Message: Logged In: YES user_id=75166 Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt. Should have been htdig-2.0.13-0.4.patch which improves the content type and security handling by htdig.py for MM 2.0.13 version of patch. Please ignore mailer-2.0.13-0.4.patch file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:09 Message: Logged In: YES user_id=75166 mailer-2.0.13-0.4.patch improves the content type and security handling by htdig.py for MM 2.0.13 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:07 Message: Logged In: YES user_id=75166 htdig-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:48 Message: Logged In: YES user_id=75166 htdig-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-04 10:53 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.3.patch corrects a minor typo in text appearing in the list TOC after the patch is applied. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:24 Message: Logged In: YES user_id=75166 htdig-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 11:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 16:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 14:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 11:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 16:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 15:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply at sourceforge.net Sat Jan 3 04:20:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 3 04:20:10 2004 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-01-03 09:20 Message: Logged In: YES user_id=75166 indexing-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:10 Message: Logged In: YES user_id=75166 indexing-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:37 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz no longer needs patch #661138 to be applied as that patch was incorporated in the MM 2.1.2 release ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:34 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 compatibility. Before applying thisversion of the patch you must also apply Bug fix patch #728836 to the source distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:53 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:52 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Sat Jan 3 08:02:16 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 3 08:02:22 2004 Subject: [ mailman-Patches-869644 ] Fix: Error accessing priv. roster/arch w/ non-member address Message-ID: Patches item #869644, was opened at 2004-01-03 00:45 Message generated for change (Comment added) made by berndts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Fix: Error accessing priv. roster/arch w/ non-member address Initial Comment: Mailman 2.1.4 is producing a bug if one tries to login to a private roster or archive with an email address which is not a member of the respective mailing list. This patch solves the problem. ---------------------------------------------------------------------- >Comment By: Stephan Berndts (berndts) Date: 2004-01-03 14:02 Message: Logged In: YES user_id=129854 I should have included a traceback -- sorry. The error occurs even if you already have a Mailman cookie for another mailing list and try to login to a private roster/ archive afterwards. (With another address?) The linenumbers may differ from a fresh Mailman 2.1.4 installation as I applied some patches. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 141, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 311, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: someaddress ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-03 02:15 Message: Logged In: YES user_id=12800 Someone I downloaded an older SecurityManager.py.patch. I grabbed it again and now see what you're talking about. Here's one way the bug can be manifest: if you were a member when you logged in to read the archives, but got subsequently removed before your cookie expired (i.e. your browser exited). Is there another way this crash can happen? ---------------------------------------------------------------------- Comment By: Stephan Berndts (berndts) Date: 2004-01-03 01:09 Message: Logged In: YES user_id=129854 That's a completely different position in the file!? I am in function __checkone, not in Authenticate. Your comment does not match my patch :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-03 01:02 Message: Logged In: YES user_id=12800 Are you sure you're looking at version 2.20.2.2 of SecurityManager.py? Here's what the AuthUser clause looks like: elif ac == mm_cfg.AuthUser: if user is not None: try: if self.authenticateMember(user, response): return ac except Errors.NotAMemberError: pass This doesn't match patch the patch, so I'm wondering if your files are out of date? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=869644&group_id=103 From noreply at sourceforge.net Sat Jan 3 14:09:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 3 14:09:34 2004 Subject: [ mailman-Bugs-870028 ] html in listinfo is quoted Message-ID: Bugs item #870028, was opened at 2004-01-03 14:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: html in listinfo is quoted Initial Comment: If you enter html into the 'info' text area, the listinfo page sees that html as quoted, not as valid html. This is a result of the XSS hole closure in 2.1.4, but some innocent tags should be allowed back in. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 From noreply at sourceforge.net Sun Jan 4 10:50:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 4 10:50:51 2004 Subject: [ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement! Message-ID: Bugs item #815297, was opened at 2003-09-30 19:42 Message generated for change (Settings changed) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None >Priority: 8 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking signatures in message/rfc822 attachement! Initial Comment: Mailman _must_ not touch MIME-parts which are nested more deeply in the mail. As tested with Mailman 2.1.2, header lines will be sometimes reformatted in message/rfc822 attachments which will break the OpenPGP signature (also conforming to the PGP/MIME standard) on that part. I'm attaching a simple email with on long header. Forward this as MIME part and sign it sending it through Mailman, the signature will be broken. This is an email security affecting bug, because if people start believing that a *BAD* signature does not mean much, because they get many broken by mailman, they will not react to a seriously manipulated email anymore! ---------------------------------------------------------------------- Comment By: Marc Mutz (mmutz) Date: 2003-10-03 17:54 Message: Logged In: YES user_id=82377 This is not limited to message/rfc822 at all: As a specific example, create a message with an attachment and add the header Content-Disposition: attachment; filename="more-than-70-chars. txt" (all in a single line), then send it through a mailman-managed ml. Result: mailman "fixes" the message to look like Content-Disposition: attachment; \tfilename="more-than-70-chars.txt" It even does that inside a multipart/signed part, and this is where it breaks the signature verification. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-09-30 19:46 Message: Logged In: YES user_id=113859 Here is the email signed by myself and broken after delivery through mailman. Check the "To:" header line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 From noreply at sourceforge.net Sun Jan 4 10:54:17 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 4 10:54:21 2004 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 10:01 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-04 16:54 Message: Logged In: YES user_id=113859 Greg, maybe you should close the bug in addition to send another email to the mailman lists to ask for an 2.0.14 release. An alternative would be to make a patch release, this bug certainly is critical for 2.0.x. On the other hand it most likely does not affect 2.1.x. ---------------------------------------------------------------------- Comment By: Greg Lindahl (greglindahl) Date: 2003-08-06 02:13 Message: Logged In: YES user_id=612574 Thanks -- I see that you fixed all of them in your patch. This should be added to the 2.0.X series. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:41 Message: Logged In: YES user_id=113859 I've submitted a patch for this to the patch tracker 783651 https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Sun Jan 4 17:37:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 4 17:37:39 2004 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 08:01 Message generated for change (Comment added) made by lindahl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- Comment By: Greg Lindahl (lindahl) Date: 2004-01-04 22:37 Message: Logged In: YES user_id=57593 It's not the reporter's place to close a bug report -- thanks for the fix, but the Mailman owners have to close the bug. I'm afraid that the mailman community doesn't spend much time keeping their sourceforge bug list clean. I've given a couple of other people the fix, it's an extremely common situation today. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-04 15:54 Message: Logged In: YES user_id=113859 Greg, maybe you should close the bug in addition to send another email to the mailman lists to ask for an 2.0.14 release. An alternative would be to make a patch release, this bug certainly is critical for 2.0.x. On the other hand it most likely does not affect 2.1.x. ---------------------------------------------------------------------- Comment By: Greg Lindahl (greglindahl) Date: 2003-08-06 00:13 Message: Logged In: YES user_id=612574 Thanks -- I see that you fixed all of them in your patch. This should be added to the 2.0.X series. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 17:41 Message: Logged In: YES user_id=113859 I've submitted a patch for this to the patch tracker 783651 https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 17:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Mon Jan 5 12:03:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 5 12:03:25 2004 Subject: [ mailman-Bugs-871050 ] Uncought runner exception: Empty module name Message-ID: Bugs item #871050, was opened at 2004-01-05 11:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, 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 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 From noreply at sourceforge.net Mon Jan 5 12:09:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 5 12:09:51 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Mon Jan 5 12:18:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 5 12:18:32 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Tue Jan 6 02:20:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 6 02:21:08 2004 Subject: [ mailman-Patches-818601 ] "Announcement-only" (read only) list Message-ID: Patches item #818601, was opened at 2003-10-06 22:07 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103 Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: "Announcement-only" (read only) list Initial Comment: Documents say that Mailman "supports a wide range of mailing list types, such as general discussion lists and announce-only lists". It's exactly true. But some people wish really "announcement-only" feature. By `Announcement-only' feature: o Posting by e-mail is not allowed at all. All messages to posting address are forwarded to owners and no other users won't receive it. o Web interface is provided so that only specified users ("posters") can post messages to list. For example for `mail magazine' publishers, `announcement-only' list is safer (Oooops! I've approved the SPAM!) and let them be free from moderation tasks. Changes on codes: o New CGI script `post'. o New handler `Posttop' which switches messages bound to list to owners (only on annnouncement-only list). o New `announcement_only' configuration directive. o Some modifications of templates. Notice: By now this is buggie (both in Python and English). Comments and Fixes are welcome. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:20 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-29 19:39 Message: Logged In: YES user_id=529503 rel.1.0. o Confusing "announcement-only" has been changed to "read-only". o New admin category. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-09 23:51 Message: Logged In: YES user_id=529503 rel.0.2. * Posttop handler now placed after Hold handler so that spam discarding and auto-response are capable. * Global pipelone processing are ommitted when: -------------------------------------- SpamDetect : [A] and [W] Approve : [W] ReplyBot : [W] Moderate : [A] Hold : - administrivia : [A] - too many recips : [A] - implicit dest. : [A] - suspicious headers : [A] and not [W] - message size : [A] and not [W] - news moderation : [A] and not [W] Posttop : (if [A], may be switched to owner pipeline.) AvoidDuplicates : [A] ------------------------------ [A]: list is announcement-only. [W]: message is posted from Web (by `poster'). * Additional modification to templates. * Some admin option categories are hidden. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103 From noreply at sourceforge.net Tue Jan 6 02:28:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 6 02:28:04 2004 Subject: [ mailman-Patches-630339 ] create list with multiple owners Message-ID: Patches item #630339, was opened at 2002-10-29 18:03 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: create list with multiple owners Initial Comment: Create list with multiple list owners, by 'create' CGI script and 'newlist' command line script. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:28 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 From noreply at sourceforge.net Tue Jan 6 13:32:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 6 13:32:46 2004 Subject: [ mailman-Bugs-871830 ] Small logging error in "subscribe" log Message-ID: Bugs item #871830, was opened at 2004-01-06 18:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871830&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stig Sandbeck Mathisen (shub-internet) Assigned to: Nobody/Anonymous (nobody) Summary: Small logging error in "subscribe" log Initial Comment: Looks like there is a small logging error in the "subscribe" logging. The log lines look like this: Jan 06 18:31:52 2004 (9728) online-driftsmeldinger-ost: pending Stig Sandbeck Mathisen 148.122.46.12 Jan 06 18:32:15 2004 (3682) online-driftsmeldinger-ost: new "ssm@fnord.no" , via email confirmation On the second line, the name and the address should change place, address should be inside <>. and name inside "" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871830&group_id=103 From noreply at sourceforge.net Tue Jan 6 19:46:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 6 19:46:25 2004 Subject: [ mailman-Patches-872068 ] Decorate.py patch Message-ID: Patches item #872068, was opened at 2004-01-07 00:46 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=872068&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Decorate.py patch Initial Comment: Here is a patch which was defered and not included in 2.1.4 for Decorate.py. This fixes most of the footer-in-the-attachment problem by 1. convert header, body and footer into unicode 2. then concatnate them 3. try encode with the list charset 4. if fail, encode with the message charset 5. if both attempts fail, make the footer attachment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=872068&group_id=103 From noreply at sourceforge.net Wed Jan 7 19:14:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 7 19:14:04 2004 Subject: [ mailman-Bugs-872733 ] Changing topics_bodylines_limit value undefines topics Message-ID: Bugs item #872733, was opened at 2004-01-07 18:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=872733&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Peter Smith (peters) Assigned to: Nobody/Anonymous (nobody) Summary: Changing topics_bodylines_limit value undefines topics Initial Comment: If you change the value for "topics_bodylines_limit" at the "Mailing list Configuration Help topics_bodylines_limit Option" screen and then click "Submit", the defined topics will be reset. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=872733&group_id=103 From noreply at sourceforge.net Thu Jan 8 06:38:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 8 06:38:41 2004 Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1 Message-ID: Patches item #839386, was opened at 2003-11-10 18:04 Message generated for change (Comment added) made by kyrian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- >Comment By: Kev Green (kyrian) Date: 2004-01-08 11:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 11:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_id=103 From noreply at sourceforge.net Thu Jan 8 07:32:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 8 07:32:52 2004 Subject: [ mailman-Patches-873035 ] subject handling in -request mail Message-ID: Patches item #873035, was opened at 2004-01-08 12:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=873035&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: subject handling in -request mail Initial Comment: Since spammers get one of our '-request' mail command address as target, we frequently get following error log and many such messages shunted. Jan 08 10:17:02 2004 (11705) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Jan 08 10:17:02 2004 (11705) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range(128) Jan 08 10:17:02 2004 (11705) SHUNTING: 1073506489.162806+2102abfa360c02ffb7bebbce12c1b9f09d8139f9 Apparently, following patch to Queue/CommandRunner.py may solve this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=873035&group_id=103 From noreply at sourceforge.net Sat Jan 10 03:29:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 10 03:29:55 2004 Subject: [ mailman-Feature Requests-874326 ] Per-user reply-to munging Message-ID: Feature Requests item #874326, was opened at 2004-01-10 00:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=874326&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nathan Gray (n8gray) Assigned to: Nobody/Anonymous (nobody) Summary: Per-user reply-to munging Initial Comment: After *yet another* heated debate about reply-to munging it occurred to me that maybe we *can* all just get along. How about letting each user decide whether or not reply-to gets set to the list address? It would be so nice to put this silly issue to rest. Think about it -- this could qualify you for the Nobel Peace Prize! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=874326&group_id=103 From noreply at sourceforge.net Sat Jan 10 03:37:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 10 03:37:17 2004 Subject: [ mailman-Feature Requests-874326 ] Per-user reply-to munging Message-ID: Feature Requests item #874326, was opened at 2004-01-10 00:29 Message generated for change (Comment added) made by n8gray You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=874326&group_id=103 Category: None Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Nathan Gray (n8gray) Assigned to: Nobody/Anonymous (nobody) Summary: Per-user reply-to munging Initial Comment: After *yet another* heated debate about reply-to munging it occurred to me that maybe we *can* all just get along. How about letting each user decide whether or not reply-to gets set to the list address? It would be so nice to put this silly issue to rest. Think about it -- this could qualify you for the Nobel Peace Prize! ---------------------------------------------------------------------- >Comment By: Nathan Gray (n8gray) Date: 2004-01-10 00:37 Message: Logged In: YES user_id=121553 Oops, this is a duplicate of RFEs 828564 and 788314. I guess I should have searched before posting. :-( Still, that does suggest it's a good idea. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=874326&group_id=103 From noreply at sourceforge.net Sat Jan 10 03:45:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 10 03:46:02 2004 Subject: [ mailman-Feature Requests-874329 ] Next/Previous Month links in archives Message-ID: Feature Requests item #874329, was opened at 2004-01-10 00:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=874329&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nathan Gray (n8gray) Assigned to: Nobody/Anonymous (nobody) Summary: Next/Previous Month links in archives Initial Comment: Mailman has really improved my life with its wonderful archive generation, but there's one oversight in the interface. There should be "Next Month" and "Previous Month" links in the thread/date view of the archives. It's pretty annoying to have to manually type the month name in the URL or go back to the list-info, then to the archive list, then to the month in question. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=874329&group_id=103 From noreply at sourceforge.net Sat Jan 10 23:50:36 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 10 23:50:40 2004 Subject: [ mailman-Bugs-874760 ] Expose bug after a user change email address Message-ID: Bugs item #874760, was opened at 2004-01-11 04:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=874760&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Expose bug after a user change email address Initial Comment: If a user changed his email address and confirm by email, then hit a button on the (old email) options page, then he get; Bug in Mailman version 2.1.4 > > We're sorry, we hit a bug! > If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! > > Traceback: > > Traceback (most recent call last): > File "/usr/local/mailman/scripts/driver", line 87, in run_main > main() > File "/usr/local/mailman/Mailman/Cgi/options.py", line 226, in main > password, user): > File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate > ok = self.CheckCookie(ac, user) > File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie > ok = self.__checkone(c, authcontext, user) > File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone > key, secret = self.AuthContextInfo(authcontext, user) > File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo > secret = self.getMemberPassword(user) > File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword > raise Errors.NotAMemberError, member > NotAMemberError: old_user@address I atatch a patch to fix this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=874760&group_id=103 From noreply at sourceforge.net Sun Jan 11 00:02:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 11 00:02:34 2004 Subject: [ mailman-Bugs-874764 ] -admin address is now equiv to -bounce Message-ID: Bugs item #874764, was opened at 2004-01-11 05:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=874764&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: -admin address is now equiv to -bounce Initial Comment: If a new list is created, a notice is sent to the list owner including the questions address mailman-admin@the.site.dom. Since in 2.1.x, -admin adderss is an alias for bounce, if the new list owner sends questions to this address, the message is treated as uninterpretable bounce message. This address should be mailman-owner@the.site.dom. I attach a fix for Cgi/create.py but looks like bin/newlist has the same error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=874764&group_id=103 From noreply at sourceforge.net Tue Jan 13 05:11:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 05:11:34 2004 Subject: [ mailman-Bugs-875971 ] Deprecated option DEFAULT_HOST_NAME is used in Utils.py Message-ID: Bugs item #875971, was opened at 2004-01-13 10:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=875971&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Aleksander Adamowski (the_olo) Assigned to: Nobody/Anonymous (nobody) Summary: Deprecated option DEFAULT_HOST_NAME is used in Utils.py Initial Comment: In Utils.py, in the get_domain() function, a deprecated configuration option is used: DEFAULT_HOST_NAME. It has been superseded by DEFAULT_URL_HOST. DEFAULT_HOST_NAME is now set to None by default. I'm suggesting the following change in Urils.py, near line 640: - hostname = mm_cfg.DEFAULT_HOST_NAME or mm_cfg.DEFAULT_EMAIL_HOST + hostname = mm_cfg.DEFAULT_URL_HOST or mm_cfg.DEFAULT_EMAIL_HOST I'm attaching a patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=875971&group_id=103 From noreply at sourceforge.net Tue Jan 13 05:13:11 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 05:13:14 2004 Subject: [ mailman-Patches-875972 ] Remove deprecated variable from Utils.py Message-ID: Patches item #875972, was opened at 2004-01-13 10:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=875972&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Aleksander Adamowski (the_olo) Assigned to: Nobody/Anonymous (nobody) Summary: Remove deprecated variable from Utils.py Initial Comment: DEFAULT_HOST_NAME has been replaced with DEFAULT_URL_HOST. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=875972&group_id=103 From noreply at sourceforge.net Tue Jan 13 13:00:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 13:00:36 2004 Subject: [ mailman-Feature Requests-876244 ] turn off discard notifications Message-ID: Feature Requests item #876244, was opened at 2004-01-13 13:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=876244&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Abrahams (david_abrahams) Assigned to: Nobody/Anonymous (nobody) Summary: turn off discard notifications Initial Comment: I'd rather not be bothered when spam gets automatically discarded. Can I turn off auto-discard notices? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=876244&group_id=103 From noreply at sourceforge.net Tue Jan 13 13:19:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 13:19:58 2004 Subject: [ mailman-Bugs-876255 ] Unsubscribe fails with buffer exception Message-ID: Bugs item #876255, was opened at 2004-01-13 18:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=876255&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fred Stutzman (chimprawk) Assigned to: Nobody/Anonymous (nobody) Summary: Unsubscribe fails with buffer exception Initial Comment: A user subscribed themselves with a trailing space (%00), and now all efforts to unsubscribe the user fail: >From the web interface, you can select the user and "unsubscribe" them, but they remain on the list (mailman returns no confirmation message) With the remove_members utility, it tells me "No such member", even though find_members "finds" the member. I've munged the address every way possible (using python and shell regexps, adding Unicode, etc) and still can't get the member to unsubscribe. I googled for an answer to this problem, and this seems to be the only solution: http://www.mail-archive.com/mailman-users@python.org/ msg21153.html I'd say since the solution requires editing a binary, this qualifies as a bug. I've also searched the bug archive and couldn't really come up with an answer; I do realize that my searches might not have been correct, so if the answer is in the bug database, I apologize. Thank you very much, Fred Included is the traceback: Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 169, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1376, in change_options newname = Utils.canonstr(newname, mlist.preferred_language) File "/usr/local/mailman/Mailman/Utils.py", line 722, in canonstr parts = re.split(r'&(?P[^;]+);', s) File "/usr/src/build/215241-i386/install/usr/lib/python2.2/ sre.py", line 156, in split return _compile(pattern, 0).split(string, maxsplit) TypeError: expected string or buffer -------------------------------------------------------------------- ------------ Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -------------------------------------------------------------------- ------------ Environment variables: Variable Value PATH_INFO /contemporaries/members HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* CONTENT_TYPE multipart/form-data; boundary=---------------------------7d4ae20610182 HTTP_REFERER http://lists.ibiblio.org/mailman/admin/contemporaries/ members?letter=a&chunk=0 SERVER_SOFTWARE Apache/1.3.29 (Unix) mod_ssl/2.8.16 OpenSSL/0.9.6b PHP/4.3.3 mod_perl/1.29 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin SERVER_ADMIN admin@ibiblio.org SCRIPT_NAME /mailman/admin SCRIPT_URI http://lists.ibiblio.org/mailman/admin/ contemporaries/members SERVER_SIGNATURE Apache/1.3.29 Server at lists.ibiblio.org Port 80 REQUEST_METHOD POST HTTP_HOST lists.ibiblio.org SCRIPT_URL /mailman/admin/contemporaries/members SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/admin/contemporaries/members CONTENT_LENGTH 2873 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; (R1 1.3)) HTTP_CONNECTION Keep-Alive HTTP_COOKIE contemporaries+admin=28020000006934c9fd3f73280000006 234353264653936346633613065306334626530633439356263 6437636238376261613131643430 SERVER_NAME lists.ibiblio.org REMOTE_ADDR 12.107.204.12 REMOTE_PORT 14877 HTTP_ACCEPT_LANGUAGE en-us PATH_TRANSLATED /home/www/contemporaries/members SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR 152.2.210.119 DOCUMENT_ROOT /home/www ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=876255&group_id=103 From noreply at sourceforge.net Tue Jan 13 19:23:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 19:23:26 2004 Subject: [ mailman-Bugs-870028 ] html in listinfo is quoted Message-ID: Bugs item #870028, was opened at 2004-01-03 21:09 Message generated for change (Comment added) made by hertell You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: html in listinfo is quoted Initial Comment: If you enter html into the 'info' text area, the listinfo page sees that html as quoted, not as valid html. This is a result of the XSS hole closure in 2.1.4, but some innocent tags should be allowed back in. ---------------------------------------------------------------------- Comment By: Rene (hertell) Date: 2004-01-14 02:23 Message: Logged In: YES user_id=278485 The same goes if you use Umlauts (???, or ? ? ?) in the welcome-tect text-area. First it converts the Umlaut-character to an decimal reference (ä), and after that it converts the & character into an Character entity. In other words; when the user gets the welcome-email that contains ? characters (?), it is converted twice: This is the code-soup for this character that finally arives: ä instead of the single ? character ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 From noreply at sourceforge.net Tue Jan 13 19:43:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 19:43:52 2004 Subject: [ mailman-Bugs-870028 ] html in listinfo is quoted Message-ID: Bugs item #870028, was opened at 2004-01-03 21:09 Message generated for change (Comment added) made by hertell You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: html in listinfo is quoted Initial Comment: If you enter html into the 'info' text area, the listinfo page sees that html as quoted, not as valid html. This is a result of the XSS hole closure in 2.1.4, but some innocent tags should be allowed back in. ---------------------------------------------------------------------- Comment By: Rene (hertell) Date: 2004-01-14 02:43 Message: Logged In: YES user_id=278485 I tracked down the encoding-problem to the following row in Defaults.py: add_language('en', _('English (USA)'), 'us-ascii') By changing the encoding to iso-8859-1 fixes the problem. add_language('en', _('English (USA)'), 'iso-8859-1') You probably ask why I don't use the admin-pages in my local language? The ansver is that I prefer English before anything else. ---------------------------------------------------------------------- Comment By: Rene (hertell) Date: 2004-01-14 02:23 Message: Logged In: YES user_id=278485 The same goes if you use Umlauts (???, or ? ? ?) in the welcome-tect text-area. First it converts the Umlaut-character to an decimal reference (ä), and after that it converts the & character into an Character entity. In other words; when the user gets the welcome-email that contains ? characters (?), it is converted twice: This is the code-soup for this character that finally arives: ä instead of the single ? character ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 From noreply at sourceforge.net Tue Jan 13 23:51:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 13 23:51:28 2004 Subject: [ mailman-Feature Requests-876244 ] turn off discard notifications Message-ID: Feature Requests item #876244, was opened at 2004-01-13 13:00 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=876244&group_id=103 Category: None Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: David Abrahams (david_abrahams) Assigned to: Nobody/Anonymous (nobody) Summary: turn off discard notifications Initial Comment: I'd rather not be bothered when spam gets automatically discarded. Can I turn off auto-discard notices? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-13 23:51 Message: Logged In: YES user_id=12800 Yes, see Privacy Options -> Sender filters -> forward_auto_discards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=876244&group_id=103 From noreply at sourceforge.net Wed Jan 14 05:56:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 14 05:56:52 2004 Subject: [ mailman-Bugs-871050 ] Uncought runner exception: Empty module name Message-ID: Bugs item #871050, was opened at 2004-01-05 18:03 Message generated for change (Comment added) made by meyerm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, 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 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- Comment By: Marcel Meyer (meyerm) Date: 2004-01-14 11:56 Message: Logged In: YES user_id=66911 Hi, was this somehow resolved?? I just found to have the same problems! What can I do that the messages (the shunt directory is now 1,5 MB big! [not the contents of the dir, but the dir inode itself...!!] ) are written into the archives without loosing anything? unshunt just puts them back into the shunt directory. Is there some patch - anything? Thanks a lot Marcel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 From noreply at sourceforge.net Wed Jan 14 10:05:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 14 10:25:50 2004 Subject: [ mailman-Feature Requests-876244 ] turn off discard notifications Message-ID: Feature Requests item #876244, was opened at 2004-01-13 13:00 Message generated for change (Comment added) made by david_abrahams You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=876244&group_id=103 Category: None Group: None Status: Closed Resolution: None Priority: 5 Submitted By: David Abrahams (david_abrahams) Assigned to: Nobody/Anonymous (nobody) Summary: turn off discard notifications Initial Comment: I'd rather not be bothered when spam gets automatically discarded. Can I turn off auto-discard notices? ---------------------------------------------------------------------- >Comment By: David Abrahams (david_abrahams) Date: 2004-01-14 10:05 Message: Logged In: YES user_id=52572 Thanks! The description: "Should messages from non- members, which are automatically discarded, be forwarded to the list moderator?" doesn't really describe what happens on my list. It's not messages from non-members which we were getting notices about, but messages from addresses explicitly listed in a sender filter. Non-members get a "you have to be a member" message and we get no discard notification no matter how we set that option. I get the feeling that the description of various Mailman settings is really dependent for its correctness on other Mailman settings. It seems the way our list is set up, many of the setting descriptions don't make much sense or do what they say. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-13 23:51 Message: Logged In: YES user_id=12800 Yes, see Privacy Options -> Sender filters -> forward_auto_discards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=876244&group_id=103 From noreply at sourceforge.net Wed Jan 14 21:08:53 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 14 21:09:01 2004 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 22:31 Message generated for change (Comment added) made by joaofraga You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- Comment By: Joao Fraga (joaofraga) Date: 2004-01-15 02:08 Message: Logged In: YES user_id=594460 I am experiencing this bug with Mailman 2.1.4 and Python 2.3.3. Here goes a relevant part of the error log: Jan 15 02:02:58 2004 (25537) Uncaught runner exception: unicode() argument 2 must be string, not None Jan 15 02:02:58 2004 (25537) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/lib/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None Jan 15 02:02:58 2004 (25537) SHUNTING: 1074132178.1086111+ae4e7452c810775c6904c8a4e8c71431dbc4944d ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-27 15:19 Message: Logged In: YES user_id=12800 Please wait until 2.1.3 is released (whenever I can crawl out of SoBig consequences). If the bug persists, please submit a new one then. ---------------------------------------------------------------------- Comment By: jared mauch (jaredmauch) Date: 2003-08-27 06:23 Message: Logged In: YES user_id=131445 I'm seeing what appears to be a similar error related to unicode. i can send you .db and .pck files if it would help. mine is with mailman-2.1.2 Aug 27 01:12:03 2003 (24565) Uncaught runner exception: ASCII encoding error: ordinal not in range(128) Aug 27 01:12:03 2003 (24565) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, 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 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 305, in process t = unicode(t, 'ascii', 'replace').encode('ascii') UnicodeError: ASCII encoding error: ordinal not in range(128) Aug 27 01:12:03 2003 (24565) SHUNTING: 1061961121.185183+0b73a771780f550a6c2e25855f37ea5f250ed212 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-19 05:06 Message: Logged In: YES user_id=12800 This was caused by a bug in the email package. It'll be fixed in email 2.5.4 and in Mailman 2.1.3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-19 02:11 Message: Logged In: YES user_id=12800 A better thing to do is to attach a .pck/.db pair of files for a shunted message. Then I can run it through my system and hopefully reproduce the bug. If the message contains sensitive information or you don't want to upload it for other reasons, please email them as attachments to me: barry@python.org. Make sure you put "Mailman" in the subject. ---------------------------------------------------------------------- Comment By: Colin Allen (ventoux) Date: 2003-08-16 22:43 Message: Logged In: YES user_id=846026 ps - moving the various digest.mboxes freed up the blocked lists - too many messages with attachments in the digests for me to figure out exactly which one was causing the problem, but I'll be happy to forward copy of offending mbox to anyone interested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Fri Jan 16 03:06:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 16 03:06:17 2004 Subject: [ mailman-Bugs-878078 ] Unable to select Slevene language Message-ID: Bugs item #878078, was opened at 2004-01-16 09:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matjaz Kljun (mkljun) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to select Slevene language Initial Comment: When I try to select Slovene language for the mailing list I get this bug report. It's odd that it happens only with Slovene language. If I select Italian or any other language it doesn't complain. Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm self._setValue(mlist, property, val, doc) File "/usr/local/mailman/Mailman/Gui/Language.py", line 120, in _setValue i18n.set_language(val) File "/usr/local/mailman/Mailman/i18n.py", line 35, in set_language language) File "/usr/local/lib/python2.2/gettext.py", line 248, in translation t = _translations.setdefault(key, class_(open(mofile, 'rb'))) File "/usr/local/lib/python2.2/gettext.py", line 106, in __init__ self._parse(fp) File "/usr/local/lib/python2.2/gettext.py", line 180, in _parse k, v = item.split(':', 1) ValueError: unpack list of wrong size Python information: Variable Value sys.version 2.2.2 (#1, Jan 3 2003, 07:54:31) [GCC 3.2.1 [FreeBSD] 20021119 (release)] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd5 Environment variables: Variable Value PATH_INFO /senat/language HTTP_ACCEPT application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://www.upr.si/mailman/admin/senat/language SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.2.3 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin SERVER_ADMIN andy@upr.si SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.27 Server at www.upr.si Port 80 REQUEST_METHOD POST HTTP_HOST www.upr.si HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /usr/local/www/data/senat/language REQUEST_URI /mailman/admin/senat/language CONTENT_LENGTH 118 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 HTTP_CONNECTION keep-alive HTTP_COOKIE senat+admin=280200000069efdd0640732800000061346663386238616161633832333165333334373536393030393639393637303161346334396162 SERVER_NAME www.upr.si REMOTE_ADDR 193.2.97.204 REMOTE_PORT 2967 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 UNIQUE_ID QAbeNMECFgMAAC4QCZ8 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 193.2.22.3 DOCUMENT_ROOT /usr/local/www/data ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_id=103 From noreply at sourceforge.net Fri Jan 16 13:44:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 16 13:44:22 2004 Subject: [ mailman-Feature Requests-878450 ] Add topic list replacement for General List Information Message-ID: Feature Requests item #878450, was opened at 2004-01-16 12:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=878450&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peter Smith (peters) Assigned to: Nobody/Anonymous (nobody) Summary: Add topic list replacement for General List Information Initial Comment: It would be good to have a flag in a list's "General list information page" that would allow you to show and select topics at subscribe-time. Something like "". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=878450&group_id=103 From noreply at sourceforge.net Fri Jan 16 13:45:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 16 13:46:04 2004 Subject: [ mailman-Feature Requests-878450 ] Add topic list replacement for General List Information Message-ID: Feature Requests item #878450, was opened at 2004-01-16 12:44 Message generated for change (Comment added) made by peters You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=878450&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peter Smith (peters) Assigned to: Nobody/Anonymous (nobody) Summary: Add topic list replacement for General List Information Initial Comment: It would be good to have a flag in a list's "General list information page" that would allow you to show and select topics at subscribe-time. Something like "". ---------------------------------------------------------------------- >Comment By: Peter Smith (peters) Date: 2004-01-16 12:45 Message: Logged In: YES user_id=15554 Something like "\". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=878450&group_id=103 From noreply at sourceforge.net Fri Jan 16 13:46:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 16 13:46:52 2004 Subject: [ mailman-Feature Requests-878450 ] Add topic list replacement for General List Information Message-ID: Feature Requests item #878450, was opened at 2004-01-16 12:44 Message generated for change (Comment added) made by peters You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=878450&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peter Smith (peters) Assigned to: Nobody/Anonymous (nobody) Summary: Add topic list replacement for General List Information Initial Comment: It would be good to have a flag in a list's "General list information page" that would allow you to show and select topics at subscribe-time. Something like "". ---------------------------------------------------------------------- >Comment By: Peter Smith (peters) Date: 2004-01-16 12:46 Message: Logged In: YES user_id=15554 (dang SourceForge filtering...) Something like "MM-list-topics". ---------------------------------------------------------------------- Comment By: Peter Smith (peters) Date: 2004-01-16 12:45 Message: Logged In: YES user_id=15554 Something like "\". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=878450&group_id=103 From noreply at sourceforge.net Mon Jan 19 07:43:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 19 07:43:19 2004 Subject: [ mailman-Bugs-878078 ] Unable to select Slevene language Message-ID: Bugs item #878078, was opened at 2004-01-16 09:06 Message generated for change (Comment added) made by mkljun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matjaz Kljun (mkljun) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to select Slevene language Initial Comment: When I try to select Slovene language for the mailing list I get this bug report. It's odd that it happens only with Slovene language. If I select Italian or any other language it doesn't complain. Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm self._setValue(mlist, property, val, doc) File "/usr/local/mailman/Mailman/Gui/Language.py", line 120, in _setValue i18n.set_language(val) File "/usr/local/mailman/Mailman/i18n.py", line 35, in set_language language) File "/usr/local/lib/python2.2/gettext.py", line 248, in translation t = _translations.setdefault(key, class_(open(mofile, 'rb'))) File "/usr/local/lib/python2.2/gettext.py", line 106, in __init__ self._parse(fp) File "/usr/local/lib/python2.2/gettext.py", line 180, in _parse k, v = item.split(':', 1) ValueError: unpack list of wrong size Python information: Variable Value sys.version 2.2.2 (#1, Jan 3 2003, 07:54:31) [GCC 3.2.1 [FreeBSD] 20021119 (release)] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd5 Environment variables: Variable Value PATH_INFO /senat/language HTTP_ACCEPT application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://www.upr.si/mailman/admin/senat/language SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.2.3 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin SERVER_ADMIN andy@upr.si SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.27 Server at www.upr.si Port 80 REQUEST_METHOD POST HTTP_HOST www.upr.si HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /usr/local/www/data/senat/language REQUEST_URI /mailman/admin/senat/language CONTENT_LENGTH 118 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 HTTP_CONNECTION keep-alive HTTP_COOKIE senat+admin=280200000069efdd0640732800000061346663386238616161633832333165333334373536393030393639393637303161346334396162 SERVER_NAME www.upr.si REMOTE_ADDR 193.2.97.204 REMOTE_PORT 2967 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 UNIQUE_ID QAbeNMECFgMAAC4QCZ8 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 193.2.22.3 DOCUMENT_ROOT /usr/local/www/data ---------------------------------------------------------------------- >Comment By: Matjaz Kljun (mkljun) Date: 2004-01-19 13:43 Message: Logged In: YES user_id=952444 The header of mailman.po file of slovene language in version 2.1.4 is currupted. I copied the header of english version and inserted the slovene info and it works fine: # Mailman msgid "" msgstr "" "Project-Id-Version: mailman_new_poprn" "POT-Creation-Date: Sat Dec 13 14:40:28 2003n" "PO-Revision-Date: 2003-09-30 11:18+0200n" "Last-Translator: Urska Colner n" "Language-Team: Sloven??ina n" "MIME-Version: 1.0n" "Content-Type: text/plain; charset=ISO-8859-2n" "Content-Transfer-Encoding: 8bitn" "X-Generator: KBabel 1.0.1n" Thanks for your help ;) M ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_id=103 From noreply at sourceforge.net Mon Jan 19 15:23:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 19 15:23:28 2004 Subject: [ mailman-Bugs-880073 ] list-id might violate RFC2919 and RFC2822 Message-ID: Bugs item #880073, was opened at 2004-01-19 21:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: list-id might violate RFC2919 and RFC2822 Initial Comment: Code in http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/CookHeaders.py?rev=2.33.2.5&view=markup (as shipped with mailman 2.1.4) will use formataddr for the List-Id: listid_h = formataddr((desc, listid)) This will violate the RFC2919, if not(desc), because the angle-brackets might be left out. 3. The List-Id Header Field The List-Id header MAY optionally include a description by including it as a "phrase" [DRUMS] before the angle-bracketed list identifier. The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF Unlike most headers in [RFC822], the List-Id header does not allow free insertion of whitespace and comments around tokens. [Go inside ~mailman/bin] python Python 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. >>> import paths >>> from email.Utils import formataddr >>> formataddr(("A strange mailing list","strange.list.org")) 'A strange mailing list ' >>> formataddr((None,"strange.list.org")) 'strange.list.org' >>> formataddr(("","strange.list.org")) 'strange.list.org' Solution: go back to old code and check http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_id=57904&aid=665732 to limit the line length so you don't violate RFC2822 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 From noreply at sourceforge.net Mon Jan 19 15:25:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 19 15:25:51 2004 Subject: [ mailman-Bugs-880073 ] list-id might violate RFC2919 and RFC2822 Message-ID: Bugs item #880073, was opened at 2004-01-19 21:23 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None >Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: list-id might violate RFC2919 and RFC2822 Initial Comment: Code in http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/CookHeaders.py?rev=2.33.2.5&view=markup (as shipped with mailman 2.1.4) will use formataddr for the List-Id: listid_h = formataddr((desc, listid)) This will violate the RFC2919, if not(desc), because the angle-brackets might be left out. 3. The List-Id Header Field The List-Id header MAY optionally include a description by including it as a "phrase" [DRUMS] before the angle-bracketed list identifier. The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF Unlike most headers in [RFC822], the List-Id header does not allow free insertion of whitespace and comments around tokens. [Go inside ~mailman/bin] python Python 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. >>> import paths >>> from email.Utils import formataddr >>> formataddr(("A strange mailing list","strange.list.org")) 'A strange mailing list ' >>> formataddr((None,"strange.list.org")) 'strange.list.org' >>> formataddr(("","strange.list.org")) 'strange.list.org' Solution: go back to old code and check http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_id=57904&aid=665732 to limit the line length so you don't violate RFC2822 ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-01-19 21:25 Message: Logged In: YES user_id=113859 I'm raising the priority to 6 because many people get annoyed if the List-ID headers change. Mailman 2.1.3 did better in the RFC2919 regard, 2.1.4 breaks it in an attempt to fix other bugs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 From noreply at sourceforge.net Tue Jan 20 07:57:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 20 07:57:52 2004 Subject: [ mailman-Bugs-880543 ] Impossible to recover lost admin-list passwords Message-ID: Bugs item #880543, was opened at 2004-01-20 13:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Ismael Olea (olea) Assigned to: Nobody/Anonymous (nobody) Summary: Impossible to recover lost admin-list passwords Initial Comment: I couldn't find a way to set a new password for a list for which its administrator had lost. Passwords/admins get lots from time to time and it's frustrating to solve it deleting and creating a new list :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_id=103 From noreply at sourceforge.net Tue Jan 20 11:53:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 20 11:53:50 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Tue Jan 20 17:23:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 20 17:23:18 2004 Subject: [ mailman-Bugs-880543 ] Impossible to recover lost admin-list passwords Message-ID: Bugs item #880543, was opened at 2004-01-20 07:57 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_id=103 Category: configuring/installing Group: 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Ismael Olea (olea) Assigned to: Nobody/Anonymous (nobody) Summary: Impossible to recover lost admin-list passwords Initial Comment: I couldn't find a way to set a new password for a list for which its administrator had lost. Passwords/admins get lots from time to time and it's frustrating to solve it deleting and creating a new list :( ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-20 17:23 Message: Logged In: YES user_id=12800 In Mailman 2.1 the only way to reset a list admin password is with the site password. You first have to create the site password from the command line with bin/mmsitepass. Then log into the list with the site password and use it to reset the admin password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880543&group_id=103 From noreply at sourceforge.net Wed Jan 21 08:42:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 21 08:42:31 2004 Subject: [ mailman-Bugs-881369 ] Double HTML encoding of non-ASCII list description Message-ID: Bugs item #881369, was opened at 2004-01-21 13:42 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=881369&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jouni K Sepp?nen (jouni) Assigned to: Nobody/Anonymous (nobody) Summary: Double HTML encoding of non-ASCII list description Initial Comment: I created in Mailman 2.1.4 a list whose description included some non-ASCII characters, e.g. "?". Both on the web page and in the List-ID header these were HTML-encoded twice. That is, the HTML source of the listinfo page replaces the character "?" by ten characters: ampersand, a, m, p, semicolon, hash, 2, 2, 8, semicolon, so that the user sees ampersand, hash, 2, 2, 8, semicolon. Also the List-ID header encodes "?" using these ten characters. It seems that if I change the list's preferred language to Finnish and re-enter the description, it gets encoded correctly: the HTML source simply uses the character directly, and the List-ID header uses RFC 2047 encoding. However, I don't like the Finnish translation of the Mailman pages, so I want to use English as the preferred language. (There seems to be a work-around: I can set the language to Finnish, then set the description, then change the language back to English.) It could be argued that if the language is set to English (USA), Mailman has no way of knowing *a priori* which encoding to use for eight-bit characters. In this case, would it make sense to add a language called "English (ISO Latin 1)", or "English (West-European)", or something similar, for those of us who like the English user interface but communicate in other languages? Or possibly a separate configuration option for the character set? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=881369&group_id=103 From noreply at sourceforge.net Wed Jan 21 13:09:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 21 13:09:39 2004 Subject: [ mailman-Bugs-715581 ] plain text digest bug in appending messages Message-ID: Bugs item #715581, was opened at 2003-04-04 21:50 Message generated for change (Comment added) made by fjpb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: plain text digest bug in appending messages Initial Comment: Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it: (...top of first message...) --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR@aol.com Fri Mar 28 14:04:32 2003 Return-Path: Delivered-To: fans@list.miss-janet.com (...second message continues with all it's headers and content) As you can see, the "From..." of the second message starts directly after the last character of the first message. Here's a second example: (... top of first message...) peace out: -oscarFrom EMAILADDR@aol.com Tue Apr 1 15:04:42 2003 Return-Path: Delivered-To: fans@list.miss-janet.com (..second message continues...) Again, the "From..." from the next message is glued to the previous message. Is this a simple missing end of line issue or is it more complicated? I can't seem to see a good pattern in it... Ricardo. ---------------------------------------------------------------------- Comment By: Fred Bone (fjpb) Date: 2004-01-21 18:09 Message: Logged In: YES user_id=956771 Is the first message originally in quoted-printable, with no concluding blank line? I have seen quite a lot of concatenated messages lately, and in every instance that I've checked the first message is QP, is multipart/alternative with the other part in html (stripped for digest), and has the boundary immediately after the last line of the QP part. The problem affects MIME-digests as well as plaintext ones. I have no clue how it might be fixed, or even where things are going wrong, but maybe someone else can get a handle on it from this info. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 From noreply at sourceforge.net Wed Jan 21 16:06:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 21 16:29:38 2004 Subject: [ mailman-Patches-671057 ] a shell script for lists backup Message-ID: Patches item #671057, was opened at 2003-01-20 09:02 Message generated for change (Comment added) made by chomo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671057&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Fil (filfil) Assigned to: Nobody/Anonymous (nobody) Summary: a shell script for lists backup Initial Comment: #################### mailman_save_lists.sh ##################### # v0.14 2003-01-14 11:30 # # this script saves a copy of mailman lists and config files # call this script regularly from the 'mailman' user # e.g. daily from crontab # 01 08 * * * /path/to/mailman_save_lists.sh # # we do save lists each time in compressed form: either they # are big and we can imagine they change each time, or they # are very small and we don't care # # comments to: # # please configure below: where lists are to be found, # and where states are to be saved (must be 'mailman'-writable) ######## mailman=/home/mailman lists=$mailman/lists/ state=/var/state/mailman/ ######## ---------------------------------------------------------------------- Comment By: alan johnson (chomo) Date: 2004-01-21 21:06 Message: Logged In: YES user_id=943591 yes right ---------------------------------------------------------------------- Comment By: Fil (filfil) Date: 2003-01-20 09:05 Message: Logged In: YES user_id=243444 Can I attach a file? Second try. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671057&group_id=103 From noreply at sourceforge.net Mon Jan 26 15:35:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 26 15:35:34 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 15:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Mon Jan 26 17:13:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 26 17:13:41 2004 Subject: [ mailman-Patches-885098 ] Information leak when issuing a subscribe request Message-ID: Patches item #885098, was opened at 2004-01-26 22:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=885098&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom Coerkamp (tomcoerkamp) Assigned to: Nobody/Anonymous (nobody) Summary: Information leak when issuing a subscribe request Initial Comment: When a request to listname-request is sent with a command "subscribe address=foo@bar.com", the errors are returned to the sender of the command rather than the address it relates to. If the subscriber is already subscribed to the list, an error message is returned to the sender of the request with that error, thus informing the sender of the request the subscription status of the requested email address. Similarly if the subscription request is successful and no confirmation is required, the sender of the request is notified of this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=885098&group_id=103 From noreply at sourceforge.net Tue Jan 27 06:09:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 27 06:09:28 2004 Subject: [ mailman-Bugs-871050 ] Uncought runner exception: Empty module name Message-ID: Bugs item #871050, was opened at 2004-01-05 17:03 Message generated for change (Comment added) made by zebaoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, 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 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-01-27 11:09 Message: Logged In: YES user_id=565663 I use 2.1.3 and have the same problem. Any solution in sight? ---------------------------------------------------------------------- Comment By: Marcel Meyer (meyerm) Date: 2004-01-14 10:56 Message: Logged In: YES user_id=66911 Hi, was this somehow resolved?? I just found to have the same problems! What can I do that the messages (the shunt directory is now 1,5 MB big! [not the contents of the dir, but the dir inode itself...!!] ) are written into the archives without loosing anything? unshunt just puts them back into the shunt directory. Is there some patch - anything? Thanks a lot Marcel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 From noreply at sourceforge.net Tue Jan 27 16:17:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 27 16:17:39 2004 Subject: [ mailman-Bugs-885808 ] unsubscribing without password Message-ID: Bugs item #885808, was opened at 2004-01-27 21:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=885808&group_id=103 Category: (un)subscribing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Darxus (darxus) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribing without password Initial Comment: When a user emails list-request@host with "unsubscribe" in the body, please make it respond with a confirmation request that the user only needs only reply to to confirm unsubscription, similar to the way email only subscription works. Similarly, but less important, please add an email command to have mailman report back the user's password, so that web access is not needed if the user has forgotten their password and wishes to use email commands that require it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=885808&group_id=103 From noreply at sourceforge.net Wed Jan 28 05:56:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 28 05:56:56 2004 Subject: [ mailman-Patches-886124 ] default action for the admin interface Message-ID: Patches item #886124, was opened at 2004-01-28 18:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=886124&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: default action for the admin interface Initial Comment: this patch changes the admindb interface such that each subscribe/held message has an extra action that can be taken: default. You then choose at the bottom what the default action will be (defer, reject, discard etc) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=886124&group_id=103 From noreply at sourceforge.net Wed Jan 28 06:15:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 28 06:15:22 2004 Subject: [ mailman-Patches-755045 ] discard all button for pending posts administration Message-ID: Patches item #755045, was opened at 2003-06-16 06:22 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=755045&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: matze (indygena) Assigned to: Nobody/Anonymous (nobody) Summary: discard all button for pending posts administration Initial Comment: adds a 'discard all' button at the bottom of the pending posts page, usefull for lists with high spam rate. not sure if this feature is of general interest, people in the projects where we applied this patch feel confortable with it. ---------------------------------------------------------------------- Comment By: Pabs (pabs3) Date: 2004-01-28 19:15 Message: Logged In: YES user_id=35028 ppl interested in this may also want the default action patch: http://sourceforge.net/tracker/index.php?func=detail&aid=886124&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=755045&group_id=103 From noreply at sourceforge.net Fri Jan 30 15:03:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 30 15:04:04 2004 Subject: [ mailman-Bugs-887806 ] List preferred_language config. Message-ID: Bugs item #887806, was opened at 2004-01-31 04:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=887806&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Chan Min Wai (dcmwai) Assigned to: Nobody/Anonymous (nobody) Summary: List preferred_language config. Initial Comment: I'm using MM 2.1.1 with Redhat 9.0 (rpm packages). When I see MM can use big5 I'm teting it with fun and it give me an problem that I never think of. In state changing the whole/system wide to big5, I've choose to change the preferred_language in one of my list (dailycquote) to be big5. This cause a big problem I can never get into the admin page anymore. not even bin/config_list -o . This is the error message Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admin.py", line 192, in main show_results(mlist, doc, category, subcat, cgidata) File "/var/mailman/Mailman/Cgi/admin.py", line 515, in show_results form.AddItem(show_variables(mlist, category, subcat, cgidata, doc)) File "/var/mailman/Mailman/Cgi/admin.py", line 564, in show_variables add_options_table_item(mlist, category, subcat, table, item) File "/var/mailman/Mailman/Cgi/admin.py", line 579, in add_options_table_item val = get_item_gui_value(mlist, category, kind, varname, params, extra) File "/var/mailman/Mailman/Cgi/admin.py", line 615, in get_item_gui_value value = gui.getValue(mlist, kind, varname, params) File "/var/mailman/Mailman/Gui/General.py", line 446, in getValue return Utils.uncanonstr(mlist.subject_prefix, mlist.preferred_language) File "/var/mailman/Mailman/Utils.py", line 761, in uncanonstr return s.encode(charset) LookupError: unknown encoding: big5 (when accessing the admin page, after keyin password) This is the error from CLI when using config_list. Traceback (most recent call last): File "../../bin/config_list", line 339, in ? main() File "../../bin/config_list", line 332, in main do_output(listname, outfile) File "../../bin/config_list", line 117, in do_output do_list_categories(mlist, k, None, outfp) File "../../bin/config_list", line 166, in do_list_categories value = gui.getValue(mlist, vtype, varname, data[2]) File "/var/mailman/Mailman/Gui/General.py", line 446, in getValue return Utils.uncanonstr(mlist.subject_prefix, mlist.preferred_language) File "/var/mailman/Mailman/Utils.py", line 761, in uncanonstr return s.encode(charset) LookupError: unknown encoding: big5 As you can see it is all about the unknow big5. something I wounder, why would config_list bouther if it is big5... Please help I've think about a solution that is to edit the Db of the mailling list, however, I've never success. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=887806&group_id=103 From noreply at sourceforge.net Fri Jan 30 21:52:04 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 30 21:52:11 2004 Subject: [ mailman-Bugs-878078 ] Unable to select Slevene language Message-ID: Bugs item #878078, was opened at 2004-01-16 03:06 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Matjaz Kljun (mkljun) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to select Slevene language Initial Comment: When I try to select Slovene language for the mailing list I get this bug report. It's odd that it happens only with Slovene language. If I select Italian or any other language it doesn't complain. Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm self._setValue(mlist, property, val, doc) File "/usr/local/mailman/Mailman/Gui/Language.py", line 120, in _setValue i18n.set_language(val) File "/usr/local/mailman/Mailman/i18n.py", line 35, in set_language language) File "/usr/local/lib/python2.2/gettext.py", line 248, in translation t = _translations.setdefault(key, class_(open(mofile, 'rb'))) File "/usr/local/lib/python2.2/gettext.py", line 106, in __init__ self._parse(fp) File "/usr/local/lib/python2.2/gettext.py", line 180, in _parse k, v = item.split(':', 1) ValueError: unpack list of wrong size Python information: Variable Value sys.version 2.2.2 (#1, Jan 3 2003, 07:54:31) [GCC 3.2.1 [FreeBSD] 20021119 (release)] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd5 Environment variables: Variable Value PATH_INFO /senat/language HTTP_ACCEPT application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://www.upr.si/mailman/admin/senat/language SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.2.3 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin SERVER_ADMIN andy@upr.si SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.27 Server at www.upr.si Port 80 REQUEST_METHOD POST HTTP_HOST www.upr.si HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /usr/local/www/data/senat/language REQUEST_URI /mailman/admin/senat/language CONTENT_LENGTH 118 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 HTTP_CONNECTION keep-alive HTTP_COOKIE senat+admin=280200000069efdd0640732800000061346663386238616161633832333165333334373536393030393639393637303161346334396162 SERVER_NAME www.upr.si REMOTE_ADDR 193.2.97.204 REMOTE_PORT 2967 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 UNIQUE_ID QAbeNMECFgMAAC4QCZ8 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 193.2.22.3 DOCUMENT_ROOT /usr/local/www/data ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-30 21:52 Message: Logged In: YES user_id=12800 I see you took out the line that says "#-#-#-#-# mailman.po (PACKAGE VERSION) #-#-#-#-#\n" Since that line seems bogus, I removed it in CVS. Hopefully that'll do the trick for you. Note that this won't crash for you if you use Python 2.2.3 or Python 2.3, because the gettext.py module was made robust enough to ignore these errors. ---------------------------------------------------------------------- Comment By: Matjaz Kljun (mkljun) Date: 2004-01-19 07:43 Message: Logged In: YES user_id=952444 The header of mailman.po file of slovene language in version 2.1.4 is currupted. I copied the header of english version and inserted the slovene info and it works fine: # Mailman msgid "" msgstr "" "Project-Id-Version: mailman_new_poprn" "POT-Creation-Date: Sat Dec 13 14:40:28 2003n" "PO-Revision-Date: 2003-09-30 11:18+0200n" "Last-Translator: Urska Colner n" "Language-Team: Sloven??ina n" "MIME-Version: 1.0n" "Content-Type: text/plain; charset=ISO-8859-2n" "Content-Transfer-Encoding: 8bitn" "X-Generator: KBabel 1.0.1n" Thanks for your help ;) M ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=878078&group_id=103 From noreply at sourceforge.net Fri Jan 30 22:01:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 30 22:01:26 2004 Subject: [ mailman-Bugs-887806 ] List preferred_language config. Message-ID: Bugs item #887806, was opened at 2004-01-30 15:03 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=887806&group_id=103 Category: configuring/installing Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Chan Min Wai (dcmwai) Assigned to: Nobody/Anonymous (nobody) Summary: List preferred_language config. Initial Comment: I'm using MM 2.1.1 with Redhat 9.0 (rpm packages). When I see MM can use big5 I'm teting it with fun and it give me an problem that I never think of. In state changing the whole/system wide to big5, I've choose to change the preferred_language in one of my list (dailycquote) to be big5. This cause a big problem I can never get into the admin page anymore. not even bin/config_list -o . This is the error message Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admin.py", line 192, in main show_results(mlist, doc, category, subcat, cgidata) File "/var/mailman/Mailman/Cgi/admin.py", line 515, in show_results form.AddItem(show_variables(mlist, category, subcat, cgidata, doc)) File "/var/mailman/Mailman/Cgi/admin.py", line 564, in show_variables add_options_table_item(mlist, category, subcat, table, item) File "/var/mailman/Mailman/Cgi/admin.py", line 579, in add_options_table_item val = get_item_gui_value(mlist, category, kind, varname, params, extra) File "/var/mailman/Mailman/Cgi/admin.py", line 615, in get_item_gui_value value = gui.getValue(mlist, kind, varname, params) File "/var/mailman/Mailman/Gui/General.py", line 446, in getValue return Utils.uncanonstr(mlist.subject_prefix, mlist.preferred_language) File "/var/mailman/Mailman/Utils.py", line 761, in uncanonstr return s.encode(charset) LookupError: unknown encoding: big5 (when accessing the admin page, after keyin password) This is the error from CLI when using config_list. Traceback (most recent call last): File "../../bin/config_list", line 339, in ? main() File "../../bin/config_list", line 332, in main do_output(listname, outfile) File "../../bin/config_list", line 117, in do_output do_list_categories(mlist, k, None, outfp) File "../../bin/config_list", line 166, in do_list_categories value = gui.getValue(mlist, vtype, varname, data[2]) File "/var/mailman/Mailman/Gui/General.py", line 446, in getValue return Utils.uncanonstr(mlist.subject_prefix, mlist.preferred_language) File "/var/mailman/Mailman/Utils.py", line 761, in uncanonstr return s.encode(charset) LookupError: unknown encoding: big5 As you can see it is all about the unknow big5. something I wounder, why would config_list bouther if it is big5... Please help I've think about a solution that is to edit the Db of the mailling list, however, I've never success. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-30 22:01 Message: Logged In: YES user_id=12800 Part of your problem is that Python does not come with Asian encodings out of the box. You will have to add Chinese codecs to get anywhere at all. CJKCodecs are probably your best bet: http://cjkpython.i18n.org However, once you get that installed, you may still have problems. The Chinese translations are very much out of date and need a champion to help work at updating them. If you're interested in helping, please contact mailman-i18n@python.org. In the meantime, I'm going to close this issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=887806&group_id=103 From noreply at sourceforge.net Fri Jan 30 22:06:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 30 22:06:48 2004 Subject: [ mailman-Bugs-885808 ] unsubscribing without password Message-ID: Bugs item #885808, was opened at 2004-01-27 16:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=885808&group_id=103 Category: (un)subscribing Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Darxus (darxus) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribing without password Initial Comment: When a user emails list-request@host with "unsubscribe" in the body, please make it respond with a confirmation request that the user only needs only reply to to confirm unsubscription, similar to the way email only subscription works. Similarly, but less important, please add an email command to have mailman report back the user's password, so that web access is not needed if the user has forgotten their password and wishes to use email commands that require it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-01-30 22:06 Message: Logged In: YES user_id=12800 Both of these features are already in Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=885808&group_id=103