From noreply at sourceforge.net Sat Mar 1 01:34:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 1 04:24:19 2003 Subject: [ mailman-Bugs-695526 ] check_perms does not read mm_cfg.py Message-ID: Bugs item #695526, was opened at 2003-03-01 10:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=695526&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Luigi Rosa (lrosa) Assigned to: Nobody/Anonymous (nobody) Summary: check_perms does not read mm_cfg.py Initial Comment: I modified the logs path in mm_cfg.py inserting the line LOG_DIR = '/var/log/mailman' and I verified that Mailman was logging in that directory After that, I run check_perms -v and I noticed that the script still verifies /usr/local/mailman/logs, but doesn't verify /var/log/mailman ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=695526&group_id=103 From noreply at sourceforge.net Tue Mar 4 08:05:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 4 10:55:49 2003 Subject: [ mailman-Bugs-697321 ] minor cosmetic bug in add_members help Message-ID: Bugs item #697321, was opened at 2003-03-04 16:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=697321&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: minor cosmetic bug in add_members help Initial Comment: the commandline options help screen for bin/add_members has a tiny "cosmetic" bug... it says: --digest-members-file=file -d=file But "-d=file" doesn't work.. it should be "-d file" of course. Ricardo. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=697321&group_id=103 From noreply at sourceforge.net Wed Mar 5 05:08:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 5 07:58:05 2003 Subject: [ mailman-Feature Requests-491675 ] logrotate config file Message-ID: Feature Requests item #491675, was opened at 2001-12-11 19:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=491675&group_id=103 Category: None Group: None >Status: Deleted Resolution: None Priority: 5 Submitted By: Luigi Rosa (lrosa) Assigned to: Nobody/Anonymous (nobody) Summary: logrotate config file Initial Comment: During the install procedure you could create the logrotate script in this way: IF exists /etc/logrotate.d IF NOT exists /etc/logrotate.d/mailman Create /etc/logrotate.d/mailman FI FI The /etc/logrotate.d/mailman file could be something like this: # Logrotate file for Mailman 2.0.x $HOME/log/digest { monthly } $HOME/log/error { monthly } $HOME/log/post { weekly } $HOME/log/smtp { weekly } $HOME/log/subscribe { monthly } $HOME/log/vette { monthly } Of course, instead of $HOME you should place the installation path of Mailman ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=491675&group_id=103 From noreply at sourceforge.net Thu Mar 6 02:31:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 6 05:20:47 2003 Subject: [ mailman-Bugs-698609 ] qrunner infinitely queries name server Message-ID: Bugs item #698609, was opened at 2003-03-06 11:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=698609&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Steffen Kaiser (skaus) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner infinitely queries name server Initial Comment: Hi, on a test machine I installed mailman to run locally; sendmail didn't start up however. In result, qrunner caused approx. 300Kbit/s downstream and 150Kbit/s upstream during communication with the name server for at least 10 minutes (seen via sniffer). Eventually I started sendmail and the I/O transfer dropped down to zero almost immediately. Environment: + Linux 2.4.20 + Mailman v2.1.1 + Python 2.2.1 Bye, ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=698609&group_id=103 From noreply at sourceforge.net Thu Mar 6 08:20:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 6 11:09:33 2003 Subject: [ mailman-Bugs-643605 ] RFC2882 and / in subscriber address Message-ID: Bugs item #643605, was opened at 2002-11-25 09:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103 Category: (un)subscribing Group: Postponed Status: Open Resolution: None Priority: 7 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: RFC2882 and / in subscriber address Initial Comment: Reproduced from the mailman-users list. Thanks to Bill for the followup. --chris [][][][][][] Majordomo would tell you the same thing but I agree that it is a legal address (we use similar addresses internally at work) and should be accepted. RFC2822 (http://www.faqs.org/rfcs/rfc2822.html) clearly allows it in the local-part (Section 3.4.1) as a dot-atom. This should be fixed but in the mean time I don't think you are going to get it into mailman. Bill W. At 09:31 AM 11/25/2002 -0600, Christopher Kolar wrote: Hello. I am trying to add a person to a mail list and having some problems. Their organization runs some sort of bestial mail system where the addresses are of the form: schmoe.j/bhs@dns.u99.k12.il.us When I try to drop the address in through the mass subscribe screen I get the following message from Mailman: * Joe Schmoe -- Hostile address (illegal characters) My guess is that the / is getting parsed by Mm as an attempt to reference a file (a la majordomo). Is there a way to force the address onto the subscriber list? It is an actual valid address for delivery. Thanks in advance, --chris ---------------------------------------------------------------------- >Comment By: Christopher Kolar (ckolar) Date: 2003-03-06 10:20 Message: Logged In: YES user_id=40678 Just ran into this again with 2.1.1 and was checking in to see how it is going. I have no idea what these people are doing running some goofy mail system off their dns. I think it is relaying it to a mac-based mail system with servers local in every school. I replaced one of those systems once. Anyway, here's to 3.0. --chris ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 23:01 Message: Logged In: YES user_id=12800 I agree that any RFC 2822 legal address should be allowed by Mailman. This won't get fixed for MM2.1, but I'll keep it open so we can address it in MM3.0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=643605&group_id=103 From noreply at sourceforge.net Thu Mar 6 15:13:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 6 18:02:57 2003 Subject: [ mailman-Bugs-699065 ] Member count substitution for header/footer Message-ID: Bugs item #699065, was opened at 2003-03-06 15:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699065&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Peter Abrahamsen (peidran) Assigned to: Nobody/Anonymous (nobody) Summary: Member count substitution for header/footer Initial Comment: This is a feature request. I would like a substitution string member_count for use in digest and non-digest headers and footers. I hope that this will give my users a better idea of whom they're posting. Thanks, Peter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699065&group_id=103 From noreply at sourceforge.net Thu Mar 6 15:49:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 6 18:38:34 2003 Subject: [ mailman-Bugs-699065 ] Member count substitution for header/footer Message-ID: Bugs item #699065, was opened at 2003-03-06 15:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699065&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 3 Submitted By: Peter Abrahamsen (peidran) Assigned to: Nobody/Anonymous (nobody) Summary: Member count substitution for header/footer Initial Comment: This is a feature request. I would like a substitution string member_count for use in digest and non-digest headers and footers. I hope that this will give my users a better idea of whom they're posting. Thanks, Peter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699065&group_id=103 From noreply at sourceforge.net Thu Mar 6 15:51:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 6 18:40:58 2003 Subject: [ mailman-Patches-699082 ] Fix: 699065 Message-ID: Patches item #699082, was opened at 2003-03-06 15:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699082&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Peter Abrahamsen (peidran) Assigned to: Nobody/Anonymous (nobody) Summary: Fix: 699065 Initial Comment: This patch implements the feature requested in bug 699065, and provides English documentation for it. I figured I might as well do this myself.. :) Peter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699082&group_id=103 From noreply at sourceforge.net Thu Mar 6 20:54:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 6 23:43:14 2003 Subject: [ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning Message-ID: Patches item #699199, was opened at 2003-03-06 23:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 From noreply at sourceforge.net Sat Mar 8 03:04:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 8 05:53:53 2003 Subject: [ mailman-Bugs-699900 ] Postfix 450 errors keep Mailman looping Message-ID: Bugs item #699900, was opened at 2003-03-08 12:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Walter Hop (life4m) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix 450 errors keep Mailman looping Initial Comment: When Postfix is configured to give transient (450) SMTP errors on local error, and Mailman tries to send to an unknown local recipient, Mailman by default keeps trying to deliver the same message every second. 450 is the default on some Postfix installations. This addition to README.POSTFIX might help other people in curing such a problem. I also think retrying every second is a bit blunt, but I haven't investigated that - there's probably a parameter for it :) cheers, walter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 From noreply at sourceforge.net Sat Mar 8 03:06:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 8 05:55:20 2003 Subject: [ mailman-Bugs-699900 ] Postfix 450 errors keep Mailman looping Message-ID: Bugs item #699900, was opened at 2003-03-08 12:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Walter Hop (life4m) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix 450 errors keep Mailman looping Initial Comment: When Postfix is configured to give transient (450) SMTP errors on local error, and Mailman tries to send to an unknown local recipient, Mailman by default keeps trying to deliver the same message every second. 450 is the default on some Postfix installations. This addition to README.POSTFIX might help other people in curing such a problem. I also think retrying every second is a bit blunt, but I haven't investigated that - there's probably a parameter for it :) cheers, walter ---------------------------------------------------------------------- >Comment By: Walter Hop (life4m) Date: 2003-03-08 12:06 Message: Logged In: YES user_id=729148 Attachment didn't go through... Here is it: --- README.POSTFIX Sun Feb 23 23:41:10 2003 +++ README.POSTFIX Sat Mar 8 11:19:16 2003 @@ -25,6 +25,13 @@ well with the default values for VERP_FORMAT and VERP_REGEXP in Defaults.py. + Some Postfix installations may have some error codes set to + 4xx (transient) errors. To prevent Mailman from retrying erroneous + local addresses endlessly, it is advised to set the following in + main.cf: + + unknown_local_recipient_reject_code = 550 + Finally, if you are using Postfix-style virtual domains, read the section on virtual domain support below. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 From noreply at sourceforge.net Sat Mar 8 03:06:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 8 05:55:46 2003 Subject: [ mailman-Bugs-699900 ] Postfix 450 keeps Mailman looping; doc suggestion Message-ID: Bugs item #699900, was opened at 2003-03-08 12:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Walter Hop (life4m) Assigned to: Nobody/Anonymous (nobody) >Summary: Postfix 450 keeps Mailman looping; doc suggestion Initial Comment: When Postfix is configured to give transient (450) SMTP errors on local error, and Mailman tries to send to an unknown local recipient, Mailman by default keeps trying to deliver the same message every second. 450 is the default on some Postfix installations. This addition to README.POSTFIX might help other people in curing such a problem. I also think retrying every second is a bit blunt, but I haven't investigated that - there's probably a parameter for it :) cheers, walter ---------------------------------------------------------------------- Comment By: Walter Hop (life4m) Date: 2003-03-08 12:06 Message: Logged In: YES user_id=729148 Attachment didn't go through... Here is it: --- README.POSTFIX Sun Feb 23 23:41:10 2003 +++ README.POSTFIX Sat Mar 8 11:19:16 2003 @@ -25,6 +25,13 @@ well with the default values for VERP_FORMAT and VERP_REGEXP in Defaults.py. + Some Postfix installations may have some error codes set to + 4xx (transient) errors. To prevent Mailman from retrying erroneous + local addresses endlessly, it is advised to set the following in + main.cf: + + unknown_local_recipient_reject_code = 550 + Finally, if you are using Postfix-style virtual domains, read the section on virtual domain support below. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 From noreply at sourceforge.net Sat Mar 8 15:34:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 8 18:23:39 2003 Subject: [ mailman-Bugs-700140 ] obsolete version number in TODO Message-ID: Bugs item #700140, was opened at 2003-03-08 15:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: obsolete version number in TODO Initial Comment: Got email-2.4.3.tar.gz from the latest cvs. It includes a TODO file, with the following notation: - We should support RFC 2231. Oleg Broytmann has patches to add this support, so we'll look into it for email-1.3. Since this is email-2.4, I presume either its been done or the version number needs to change. This is a low-priority item. I figured I mention it, since I saw it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 From noreply at sourceforge.net Sun Mar 9 14:45:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 9 17:34:18 2003 Subject: [ mailman-Patches-700537 ] Small typo in templates/en/options.html Message-ID: Patches item #700537, was opened at 2003-03-09 17:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700537&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Terri Oda (spot) Assigned to: Nobody/Anonymous (nobody) Summary: Small typo in templates/en/options.html Initial Comment: the word "message" should be pluralized. --- options.html_orig Sun Mar 9 17:31:01 2003 +++ options.html Sun Mar 9 17:31:13 2003 @@ -264,7 +264,7 @@ - Do you want to receive message that do not match any + Do you want to receive messages that do not match any topic filter?

This option only takes effect if you've subscribed to ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700537&group_id=103 From noreply at sourceforge.net Sun Mar 9 14:51:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 9 17:40:23 2003 Subject: [ mailman-Patches-700538 ] Small typo in Mailman/cmd_confirm.py Message-ID: Patches item #700538, was opened at 2003-03-09 17:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700538&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Terri Oda (spot) Assigned to: Nobody/Anonymous (nobody) Summary: Small typo in Mailman/cmd_confirm.py Initial Comment: "with in mailback confirmation notice" should be something like "within a mailback confirmation notice" or "with a mailback confirmation notice" --- cmd_confirm.py_orig Sun Mar 9 17:47:26 2003 +++ cmd_confirm.py Sun Mar 9 17:47:51 2003 @@ -17,7 +17,7 @@ """ confirm Confirm an action. The confirmation-string is required and should be - supplied with in mailback confirmation notice. + supplied within a mailback confirmation notice. """ from Mailman import mm_cfg ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700538&group_id=103 From noreply at sourceforge.net Mon Mar 10 05:23:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 08:12:01 2003 Subject: [ mailman-Patches-700538 ] Small typo in Mailman/cmd_confirm.py Message-ID: Patches item #700538, was opened at 2003-03-09 23:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700538&group_id=103 Category: documentation Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Terri Oda (spot) >Assigned to: Thomas Wouters (twouters) Summary: Small typo in Mailman/cmd_confirm.py Initial Comment: "with in mailback confirmation notice" should be something like "within a mailback confirmation notice" or "with a mailback confirmation notice" --- cmd_confirm.py_orig Sun Mar 9 17:47:26 2003 +++ cmd_confirm.py Sun Mar 9 17:47:51 2003 @@ -17,7 +17,7 @@ """ confirm Confirm an action. The confirmation-string is required and should be - supplied with in mailback confirmation notice. + supplied within a mailback confirmation notice. """ from Mailman import mm_cfg ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:23 Message: Logged In: YES user_id=34209 Thanks, I fixed it. Not that it matters for this case (I didn't use your patch) but please don't paste patches inline in your comment... SourceForge formatting does not do it justice :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700538&group_id=103 From noreply at sourceforge.net Mon Mar 10 05:26:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 08:15:50 2003 Subject: [ mailman-Patches-700537 ] Small typo in templates/en/options.html Message-ID: Patches item #700537, was opened at 2003-03-09 23:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700537&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Terri Oda (spot) Assigned to: Nobody/Anonymous (nobody) Summary: Small typo in templates/en/options.html Initial Comment: the word "message" should be pluralized. --- options.html_orig Sun Mar 9 17:31:01 2003 +++ options.html Sun Mar 9 17:31:13 2003 @@ -264,7 +264,7 @@ - Do you want to receive message that do not match any + Do you want to receive messages that do not match any topic filter?

This option only takes effect if you've subscribed to ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:26 Message: Logged In: YES user_id=34209 Thanks, fixed in CVS. The comment about pasting patches in comments applies again. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=700537&group_id=103 From noreply at sourceforge.net Mon Mar 10 05:35:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 08:24:40 2003 Subject: [ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning Message-ID: Patches item #699199, was opened at 2003-03-07 05:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: The Anarcat (anarcat) >Assigned to: Thomas Wouters (twouters) >Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:35 Message: Logged In: YES user_id=34209 There is no patch attached, and (though my french isn't what it used to be) I don't see how "Annuler la requête d'abonnement" reads as 'confirm my submission request'. Please contact the french translation team directly, if you still think this needs fixing: http://listes.rezo.net/mailman/listinfo/mailman-fr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 From noreply at sourceforge.net Mon Mar 10 05:40:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 08:29:01 2003 Subject: [ mailman-Patches-699082 ] Fix: 699065 Message-ID: Patches item #699082, was opened at 2003-03-07 00:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699082&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Peter Abrahamsen (peidran) Assigned to: Nobody/Anonymous (nobody) Summary: Fix: 699065 Initial Comment: This patch implements the feature requested in bug 699065, and provides English documentation for it. I figured I might as well do this myself.. :) Peter ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:40 Message: Logged In: YES user_id=34209 The patch is missing, sorry. Are you sure you selected the box next to 'Check to Upload and Attach a File:' ? If you don't, hitting 'Browse' and selecting a file doesn't actually do anything. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699082&group_id=103 From noreply at sourceforge.net Mon Mar 10 05:57:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 08:46:47 2003 Subject: [ mailman-Patches-688410 ] better phrasing for listinfo page Message-ID: Patches item #688410, was opened at 2003-02-18 04:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: better phrasing for listinfo page Initial Comment: The default listinfo page says "please send questions or comments to foo-owner@bar.org". The problem with this is that people repeatedly think "oh, I'll send my Samba question to the mail administrator, rather than to the mailing list." This patch attempts to make it more clear that the administrator address is for problems with the lists themselves. It has dropped the number of misdirected mails on our high-traffic site from a couple per week to almost zero. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:57 Message: Logged In: YES user_id=34209 There's no attached patch. Are you sure you clicked the 'Check to Ipload and Attach File' box ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 From noreply at sourceforge.net Mon Mar 10 05:59:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 08:48:40 2003 Subject: [ mailman-Patches-691055 ] Patch to fix a base64 decode error in Scrubber Message-ID: Patches item #691055, was opened at 2003-02-22 07:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Patch to fix a base64 decode error in Scrubber Initial Comment: The base64 decode of attachments isn't always checked to see if an exception was raised. Call were placed around one of the get_payload() calls, so i removed that one and put a try/except in the _bdecode() function. I also removed a redunent if not s: return s in there too. This is a fix for bug http://sourceforge.net/tracker/index.php?func=detail&aid=691039&group_id=103&atid=100103 ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:59 Message: Logged In: YES user_id=34209 This doesn't really belong in Mailman, it's more of an email (the module) problem. I've sent in a bugreport to the appropriate place, leaving this patch and the bug open until it's fixed. (If it is; if it isn't, we need to wrap get_payload in the appropriate try/except, which might be a good idea anyway.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 From noreply at sourceforge.net Mon Mar 10 06:16:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 09:04:42 2003 Subject: [ mailman-Patches-685788 ] fix for Cc: to cc: weirdness Message-ID: Patches item #685788, was opened at 2003-02-13 08:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for Cc: to cc: weirdness Initial Comment: http://mail.python.org/pipermail/mailman-users/2003-February/026353.html describe the problem. It is caused by Mailman/Handlers/AvoidDuplicates.py ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 15:16 Message: Logged In: YES user_id=34209 I wonder if the better solution isn't fixing this in the email package itself, by special-casing the handling of some of the headers. Barry? (I can handle either, I just want to know which I should do :-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 12:17 Message: Logged In: YES user_id=67709 I will be incrementing priority every time I point this patch. ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 From noreply at sourceforge.net Mon Mar 10 06:28:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 09:20:35 2003 Subject: [ mailman-Patches-683906 ] Makefile: add $DESTDIR to install target Message-ID: Patches item #683906, was opened at 2003-02-10 14:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ademar de Souza Reis Jr (ade_br) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile: add $DESTDIR to install target Initial Comment: This patch adds a DESTDIR variable for the install target. It's really useful for people packaging mailman, since they (we) can install it in an empty directory. If DESTDIR is not defined, this patch is harmless (/ is used, as expected). Please apply. :-) - Ademar ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 15:28 Message: Logged In: YES user_id=34209 I agree that this is a good thing (I've done my share of packaging :) but I'm not sure why you're doing this: cd $(DESTDIR)/; \ $(PYTHON) -c 'from compileall import *; compile_dir(".$(prefix)/Mailman")' Especially since it's not in a subshell. Why not just do compile_dir("$(DESTDIR)$(prefix)/Mailman") ? ---------------------------------------------------------------------- Comment By: Ademar de Souza Reis Jr (ade_br) Date: 2003-02-10 14:26 Message: Logged In: YES user_id=184557 uploading patch file (didn't work last time) :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 From noreply at sourceforge.net Mon Mar 10 06:47:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 09:36:42 2003 Subject: [ mailman-Patches-683906 ] Makefile: add $DESTDIR to install target Message-ID: Patches item #683906, was opened at 2003-02-10 11:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ademar de Souza Reis Jr (ade_br) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile: add $DESTDIR to install target Initial Comment: This patch adds a DESTDIR variable for the install target. It's really useful for people packaging mailman, since they (we) can install it in an empty directory. If DESTDIR is not defined, this patch is harmless (/ is used, as expected). Please apply. :-) - Ademar ---------------------------------------------------------------------- >Comment By: Ademar de Souza Reis Jr (ade_br) Date: 2003-03-10 11:47 Message: Logged In: YES user_id=184557 You're probably right. I don't remember why I choosed that approach. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 11:28 Message: Logged In: YES user_id=34209 I agree that this is a good thing (I've done my share of packaging :) but I'm not sure why you're doing this: cd $(DESTDIR)/; \ $(PYTHON) -c 'from compileall import *; compile_dir(".$(prefix)/Mailman")' Especially since it's not in a subshell. Why not just do compile_dir("$(DESTDIR)$(prefix)/Mailman") ? ---------------------------------------------------------------------- Comment By: Ademar de Souza Reis Jr (ade_br) Date: 2003-02-10 11:26 Message: Logged In: YES user_id=184557 uploading patch file (didn't work last time) :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 From noreply at sourceforge.net Mon Mar 10 07:05:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 09:54:06 2003 Subject: [ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning Message-ID: Patches item #699199, was opened at 2003-03-06 23:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Closed Resolution: Works For Me Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Thomas Wouters (twouters) >Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 08:35 Message: Logged In: YES user_id=34209 There is no patch attached, and (though my french isn't what it used to be) I don't see how "Annuler la requête d'abonnement" reads as 'confirm my submission request'. Please contact the french translation team directly, if you still think this needs fixing: http://listes.rezo.net/mailman/listinfo/mailman-fr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 From noreply at sourceforge.net Mon Mar 10 07:07:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 09:56:26 2003 Subject: [ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning Message-ID: Patches item #699199, was opened at 2003-03-06 23:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Closed Resolution: Works For Me Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Thomas Wouters (twouters) >Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- >Comment By: The Anarcat (anarcat) Date: 2003-03-10 10:07 Message: Logged In: YES user_id=246797 Man, what a bad patch report. :( This bug report should have read: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Confirmer la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" If you look closer in the actual .po file, it is indeed written "confirmer" where it should be "annuler". I have attached the patch which should take care of all this. Sorry for the confusion. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 08:35 Message: Logged In: YES user_id=34209 There is no patch attached, and (though my french isn't what it used to be) I don't see how "Annuler la requête d'abonnement" reads as 'confirm my submission request'. Please contact the french translation team directly, if you still think this needs fixing: http://listes.rezo.net/mailman/listinfo/mailman-fr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 From noreply at sourceforge.net Mon Mar 10 07:24:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 10:13:37 2003 Subject: [ mailman-Patches-677940 ] English Only mailman Message-ID: Patches item #677940, was opened at 2003-01-31 04:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=677940&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthew Davis (big-dog) Assigned to: Nobody/Anonymous (nobody) Summary: English Only mailman Initial Comment: Strips out all languages except english. # cd mailman-2.1/messages # rm -fr big5 cs de es et fi fr hu it ja ko lt nl no pt_BR ru sv # cd ../templates # rm -fr big5 cs de es et fi fr hu it ja ko lt nl no pt_BR ru sv gb # cd ../misc # rm -fr JapaneseCodecs-1.4.9.tar.gz KoreanCodecs-2.0.5.tar.gz ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 16:24 Message: Logged In: YES user_id=34209 I don't really see the point of adding this to Mailman, and keeping this patch open in the patch queue. Why is it important to disable all languages except english ? ---------------------------------------------------------------------- Comment By: Matthew Davis (big-dog) Date: 2003-01-31 04:43 Message: Logged In: YES user_id=34240 Trying to attach file again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=677940&group_id=103 From noreply at sourceforge.net Mon Mar 10 07:23:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 10:16:16 2003 Subject: [ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning Message-ID: Patches item #699199, was opened at 2003-03-07 05:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Open Resolution: Works For Me Priority: 5 Submitted By: The Anarcat (anarcat) >Assigned to: Ousmane Wilane (wilane) >Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 16:23 Message: Logged In: YES user_id=34209 Assigning to wilane, who (at least partially) does the French translations. ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2003-03-10 16:07 Message: Logged In: YES user_id=246797 Man, what a bad patch report. :( This bug report should have read: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Confirmer la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" If you look closer in the actual .po file, it is indeed written "confirmer" where it should be "annuler". I have attached the patch which should take care of all this. Sorry for the confusion. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:35 Message: Logged In: YES user_id=34209 There is no patch attached, and (though my french isn't what it used to be) I don't see how "Annuler la requête d'abonnement" reads as 'confirm my submission request'. Please contact the french translation team directly, if you still think this needs fixing: http://listes.rezo.net/mailman/listinfo/mailman-fr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 From noreply at sourceforge.net Mon Mar 10 07:30:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 10:19:29 2003 Subject: [ mailman-Patches-677940 ] English Only mailman Message-ID: Patches item #677940, was opened at 2003-01-30 22:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=677940&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthew Davis (big-dog) Assigned to: Nobody/Anonymous (nobody) Summary: English Only mailman Initial Comment: Strips out all languages except english. # cd mailman-2.1/messages # rm -fr big5 cs de es et fi fr hu it ja ko lt nl no pt_BR ru sv # cd ../templates # rm -fr big5 cs de es et fi fr hu it ja ko lt nl no pt_BR ru sv gb # cd ../misc # rm -fr JapaneseCodecs-1.4.9.tar.gz KoreanCodecs-2.0.5.tar.gz ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-10 10:30 Message: Logged In: YES user_id=12800 Partially it's a size-of-distro issue. Fully i18n Mailman is huge. The other problem is that providing patches for micro releases is a pain because of the binary .mo files. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 10:24 Message: Logged In: YES user_id=34209 I don't really see the point of adding this to Mailman, and keeping this patch open in the patch queue. Why is it important to disable all languages except english ? ---------------------------------------------------------------------- Comment By: Matthew Davis (big-dog) Date: 2003-01-30 22:43 Message: Logged In: YES user_id=34240 Trying to attach file again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=677940&group_id=103 From noreply at sourceforge.net Mon Mar 10 07:49:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 10:39:02 2003 Subject: [ mailman-Patches-673294 ] Add message-id to more log messages Message-ID: Patches item #673294, was opened at 2003-01-23 20:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=673294&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: A.M. Kuchling (akuchling) >Assigned to: Thomas Wouters (twouters) Summary: Add message-id to more log messages Initial Comment: Yesterday I spent some time looking into a user's complaint about not receiving a mems-talk message. Figuring this out required cross-referencing Exim's logs and the Mailman logs, made slightly more annoying because Mailman's post log doesn't mention message-ids. The attached patch includes the message-id in a few more log messages, and should reduce the need to go look at the MTA's logs to find when a message arrived. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 16:49 Message: Logged In: YES user_id=34209 Thanks, applied. I have some pending patches myself that add more logging, for what it's worth, of all kinds. However, I did remove the i18nization of 'n/a', since syslog() messages aren't internationalized anyway. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-01-23 20:48 Message: Logged In: YES user_id=11375 #!@$ SourceForge file upload code... $%^$ ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=673294&group_id=103 From noreply at sourceforge.net Mon Mar 10 08:16:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 11:05:37 2003 Subject: [ mailman-Patches-646989 ] NAH6 Secure List patch: GPG plugin Message-ID: Patches item #646989, was opened at 2002-12-02 17:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 6 Submitted By: Rop Gonggrijp (rop) >Assigned to: Thomas Wouters (twouters) Summary: NAH6 Secure List patch: GPG plugin Initial Comment: "NAH6 Secure List" is a patch for Mailman 2.1b5 that adds GPG functionality. It is built around a key-scheme that allows an admin to create an encrypted list for which even the server operator doesn't have access to the messages. Only the public key for the list is given to the server, so it can perform 'emergency encryption' in case someone forgets, and all users get the public and private key for the list. We think we've done a decent job of describing the new functionality from server-operator, list-admin and list- member points of view. There's also a technical document for those familiar with the Mailman code. Please have a look at: http://www.nah6.com/products/secure-list/ and follow the links from there We feel more people need this, and we'd really like it to be part of the Mailman distribution at some point... Kind Regards, Rop Gonggrijp Joshua Eichen Please forgive mangling the Mailman logo on the site: if y'all don't like it or think it's over the top we'll use something else.... ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 17:16 Message: Logged In: YES user_id=34209 I'm looking at this patch, but I'm a bit confused. Which is the newer patch, v1.0 for Mailman 2.1 (uploaded last) or v1.1 for Mailman 2.1b5 (which is linked to from the NAH6 secure-list page.) Otherwise, the patch looks okay. There are some whitespace issues, and the PGP specific options aren't properly internationalized, but that can all be fixed. The patch edits Defaults.py, but it should be Defaults.py.in (if you want to apply to CVS before installation, anyway.) Oh, and a 'global' statement for DETAILS in the global namespace really isn't necessary... Do you need someone to come over and give a Python tutorial at NAH6 ? :-) Assigning to myself so I don't forget it; if someone else wants it, that's fine by me. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-12 05:01 Message: Logged In: YES user_id=12800 The logo's fine (plus the original is free software). I'm defering this until after MM2.1 because we're about ready for the first release candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103 From noreply at sourceforge.net Mon Mar 10 08:22:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 11:11:19 2003 Subject: [ mailman-Patches-659021 ] Log open requests daily Message-ID: Patches item #659021, was opened at 2002-12-27 15:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=659021&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jost Krieger (jkrieger) Assigned to: Nobody/Anonymous (nobody) Summary: Log open requests daily Initial Comment: For large installations, it helps if the site administrator sees if a list slowly turns bad :-) This patch logs the number of open requests from checkdbs. Jost ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 17:22 Message: Logged In: YES user_id=34209 No patch was attached (sigh, SourceForge.) Are you sure you clicked the 'Check to Upload and Attach a File' box ? I believe you also need to add a 'comment' for a file upload to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=659021&group_id=103 From noreply at sourceforge.net Mon Mar 10 08:26:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 11:15:19 2003 Subject: [ mailman-Patches-691055 ] Patch to fix a base64 decode error in Scrubber Message-ID: Patches item #691055, was opened at 2003-02-22 01:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 Category: None Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Patch to fix a base64 decode error in Scrubber Initial Comment: The base64 decode of attachments isn't always checked to see if an exception was raised. Call were placed around one of the get_payload() calls, so i removed that one and put a try/except in the _bdecode() function. I also removed a redunent if not s: return s in there too. This is a fix for bug http://sourceforge.net/tracker/index.php?func=detail&aid=691039&group_id=103&atid=100103 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-10 11:26 Message: Logged In: YES user_id=12800 I've fixed this in the email.Message class, so I don't think we need to add a try/except to Scrubber. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 08:59 Message: Logged In: YES user_id=34209 This doesn't really belong in Mailman, it's more of an email (the module) problem. I've sent in a bugreport to the appropriate place, leaving this patch and the bug open until it's fixed. (If it is; if it isn't, we need to wrap get_payload in the appropriate try/except, which might be a good idea anyway.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 From noreply at sourceforge.net Mon Mar 10 08:27:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 11:15:43 2003 Subject: [ mailman-Bugs-691039 ] Scrubber broken on bad base64 messages Message-ID: Bugs item #691039, was opened at 2003-02-21 23:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=691039&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber broken on bad base64 messages Initial Comment: This is a stupid virus email that got thru to one of our lists. I'm happy to remove it from the archive, but I'm guessing if this was sent to a list again, it would cause the same error in the delivery and not just in the archiver. Pickling archive state into /usr/local/mailman/archives/private/sage-au/pipermail.pck Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 187, in ? main() File "/usr/local/mailman/bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/local/mailman/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/usr/local/mailman/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 252, in process payload = part.get_payload(decode=1) File "/usr/local/mailman/pythonlib/email/Message.py", line 189, in get_payload return Utils._bdecode(payload) File "/usr/local/mailman/pythonlib/email/Utils.py", line 75, in _bdecode value = base64.decodestring(s) File "/usr/local/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-10 11:27 Message: Logged In: YES user_id=12800 I've fixed this in the email package. ---------------------------------------------------------------------- Comment By: Simon Coggins (scoggins) Date: 2003-02-22 01:21 Message: Logged In: YES user_id=92263 I've added a patch (http://sourceforge.net/tracker/index.php?func=detail&aid=691055&group_id=103&atid=300103) That fixes this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=691039&group_id=103 From noreply at sourceforge.net Mon Mar 10 08:47:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 11:36:16 2003 Subject: [ mailman-Patches-677940 ] English Only mailman Message-ID: Patches item #677940, was opened at 2003-01-31 04:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=677940&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthew Davis (big-dog) Assigned to: Nobody/Anonymous (nobody) Summary: English Only mailman Initial Comment: Strips out all languages except english. # cd mailman-2.1/messages # rm -fr big5 cs de es et fi fr hu it ja ko lt nl no pt_BR ru sv # cd ../templates # rm -fr big5 cs de es et fi fr hu it ja ko lt nl no pt_BR ru sv gb # cd ../misc # rm -fr JapaneseCodecs-1.4.9.tar.gz KoreanCodecs-2.0.5.tar.gz ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 17:47 Message: Logged In: YES user_id=34209 How about something like the attached patch then ? That, with something like 'make english_install' or 'smallinstall' or whatever, could be used to install only the english templates/messages. I would say it adds only minimal overhead to regular Mailman, and it makes installing languages as a separate package a lot easier. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-10 16:30 Message: Logged In: YES user_id=12800 Partially it's a size-of-distro issue. Fully i18n Mailman is huge. The other problem is that providing patches for micro releases is a pain because of the binary .mo files. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 16:24 Message: Logged In: YES user_id=34209 I don't really see the point of adding this to Mailman, and keeping this patch open in the patch queue. Why is it important to disable all languages except english ? ---------------------------------------------------------------------- Comment By: Matthew Davis (big-dog) Date: 2003-01-31 04:43 Message: Logged In: YES user_id=34240 Trying to attach file again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=677940&group_id=103 From noreply at sourceforge.net Mon Mar 10 08:55:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 11:44:25 2003 Subject: [ mailman-Patches-671297 ] set directory permissions, partition install steps Message-ID: Patches item #671297, was opened at 2003-01-20 19:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671297&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: John Dennis (johndennis) Assigned to: Nobody/Anonymous (nobody) Summary: set directory permissions, partition install steps Initial Comment: This patch accomplishes two things: 1) A number of the directories created during make installed had failed to set their permissions correctly, this caused the script check_perms to report errors, this adds the setting of correct permissions to those directories. 2) Most packaging/install tools divide the installation task into 2 distinct phases File Marshaling: This is where the files of the package are built and installed into a temporary root. The the tool collects all the files under the temporary root and adds them to some type of archive file. During installation on the target machine these files are extracted from the archive and placed in matching positions in the target file system with matching ownership and permissions. Target Update: After the files are placed on the target it is often necessary to run commands on the target system to do such things as register the files, register services, etc. The "make install" in the shipped version of mailman did not separate out these two steps. In particular it attempted to compile the python files during the first phase of file marshaling. During this phase the python files are in a temporary root directory, not their final install position on the target. The paths.py file which is included by many of the python files has hard coded in it the the target installation directory (from the configure step). Thus when attempting to compile the files in the marshaling area the compilations would fail because it could not located patch information. Also the make install attempt to run the bin/update, but once again this has to be deferred to target update time, not package build time. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-10 17:55 Message: Logged In: YES user_id=34209 A patch that accomplishes two separate things is usually not a wise idea, but here are my two separate answers :-) 1) The permissions for the new directories are actually wrong; they're set set-groupid (because you use DIRSETGID to set the permissions) but they don't need to be, and I'm sure many sysadmins would not be too happy if they were made DIRSETGID :-) Also, since mkinstalldirs already creates subdirectories of directories it creates, it should be fine to just set umask appropriately, or patch mkinstalldirs so new directories are made with an acceptable mode. 2) Which packaging mechanisms use the original Makefile to do the actual installation/updating on the target system(s) ? I would say SF patch #683906 addresses most of your issues, in that it makes it possible to place files in a separate tree than the one configured. Can you explain why the separate steps are necessary ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671297&group_id=103 From noreply at sourceforge.net Mon Mar 10 16:38:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 19:28:09 2003 Subject: [ mailman-Patches-688410 ] better phrasing for listinfo page Message-ID: Patches item #688410, was opened at 2003-02-18 14:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: better phrasing for listinfo page Initial Comment: The default listinfo page says "please send questions or comments to foo-owner@bar.org". The problem with this is that people repeatedly think "oh, I'll send my Samba question to the mail administrator, rather than to the mailing list." This patch attempts to make it more clear that the administrator address is for problems with the lists themselves. It has dropped the number of misdirected mails on our high-traffic site from a couple per week to almost zero. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-03-11 11:38 Message: Logged In: YES user_id=521 Oops, I'll post it. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 00:57 Message: Logged In: YES user_id=34209 There's no attached patch. Are you sure you clicked the 'Check to Ipload and Attach File' box ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 From noreply at sourceforge.net Mon Mar 10 16:46:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 19:35:29 2003 Subject: [ mailman-Patches-683906 ] Makefile: add $DESTDIR to install target Message-ID: Patches item #683906, was opened at 2003-02-10 14:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 Category: configure/install Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Ademar de Souza Reis Jr (ade_br) >Assigned to: Thomas Wouters (twouters) Summary: Makefile: add $DESTDIR to install target Initial Comment: This patch adds a DESTDIR variable for the install target. It's really useful for people packaging mailman, since they (we) can install it in an empty directory. If DESTDIR is not defined, this patch is harmless (/ is used, as expected). Please apply. :-) - Ademar ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 01:46 Message: Logged In: YES user_id=34209 Thanks... I checked in a slightly altered version (stop bin/update from running, fix some left-out $(DESTDIR)s, fix some whitespace.) If you use this patch yourself, you probably want to grab a diff from CVS instead. ---------------------------------------------------------------------- Comment By: Ademar de Souza Reis Jr (ade_br) Date: 2003-03-10 15:47 Message: Logged In: YES user_id=184557 You're probably right. I don't remember why I choosed that approach. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 15:28 Message: Logged In: YES user_id=34209 I agree that this is a good thing (I've done my share of packaging :) but I'm not sure why you're doing this: cd $(DESTDIR)/; \ $(PYTHON) -c 'from compileall import *; compile_dir(".$(prefix)/Mailman")' Especially since it's not in a subshell. Why not just do compile_dir("$(DESTDIR)$(prefix)/Mailman") ? ---------------------------------------------------------------------- Comment By: Ademar de Souza Reis Jr (ade_br) Date: 2003-02-10 14:26 Message: Logged In: YES user_id=184557 uploading patch file (didn't work last time) :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 From noreply at sourceforge.net Mon Mar 10 17:14:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 20:03:16 2003 Subject: [ mailman-Patches-688410 ] better phrasing for listinfo page Message-ID: Patches item #688410, was opened at 2003-02-18 14:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: better phrasing for listinfo page Initial Comment: The default listinfo page says "please send questions or comments to foo-owner@bar.org". The problem with this is that people repeatedly think "oh, I'll send my Samba question to the mail administrator, rather than to the mailing list." This patch attempts to make it more clear that the administrator address is for problems with the lists themselves. It has dropped the number of misdirected mails on our high-traffic site from a couple per week to almost zero. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-03-11 12:14 Message: Logged In: YES user_id=521 Here's the patch. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-11 11:38 Message: Logged In: YES user_id=521 Oops, I'll post it. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 00:57 Message: Logged In: YES user_id=34209 There's no attached patch. Are you sure you clicked the 'Check to Ipload and Attach File' box ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 From noreply at sourceforge.net Mon Mar 10 17:16:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 10 20:05:17 2003 Subject: [ mailman-Patches-534298 ] forward unhandled bounces to admin Message-ID: Patches item #534298, was opened at 2002-03-25 00:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: forward unhandled bounces to admin Initial Comment: samba.org handles a lot of mail messages, and therefore suffers a lot of bounced messages. Mailman's automatic bounce handling is great, but the problem is that people keep dreaming up new and wierd bounce messages. With Mailman 2.0.8, if I turn on automatic bounce handling then some bouncing addresses are not correctly detected and therefore keep generating large amounts of traffic indefinitely. If I turn it off, we get about 3000 bounces per day. Some of these are just not handled yet by the BouncerAPI and need patches. In some cases there is in fact no deterministic way to work out the bouncing address (at least until we have VERP), and human intervention is required. For example, Novell's brilliant mail software includes no information in the Received lines or bounce message to indicate what the bouncing address is! Anyhow, this patch changes the behaviour of the bounce handler so that bounce messages which do not cause any positive action are forwarded to the list administrator. "Positive action" can mean noticing that the address is already disabled, or marking it as bouncing, or similar things. It doesn't include addresses which don't seem to be on the list, which probably means that we have not interpreted the message properly and more help is required. So in summary bounces which can be automatically handled will be, and others will go to the admin. I'm not sure this is the perfect behaviour, but it certainly seems like an improvement. Perhaps you want to make it more configurable. Please merge this, or something like it. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-03-11 12:16 Message: Logged In: YES user_id=521 This seems to be already fixed in 2.1. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-03 12:18 Message: Logged In: YES user_id=521 Tim, that's not quite so much of a problem as you might think. When excessive bounces are detected Mailman only *disables* addresses rather than removing them. With or without this patch, bouncing addresses which are already disabled are noted in the log file and not further action is taken. Problems can occur if the address is actually removed. This can arise in two ways. One way is that the mail administrator might explicitly remove the user from the list because of manual bounce processing. In that case, any later bounces will also go through to the admin. That's the reason for my patch to add --disable to remove_members. Secondly, users might unsubscribe themselves and then have their address start bouncing. You can imagine Mailman remembering previously-subscribed members so that it could handle these cases, but that's a much bigger project, and probably best done in conjunction with VERP. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 12:03 Message: Logged In: YES user_id=521 This patch modifies the behaviour when handling bounce messages with multiple addresses, such as from Postfix. Now messages in which any of the bouncing addresses cannot be automatically handled are forwarded to the administrator. Eventually it might be nice to put a notice in the message explaining the problem -- e.g. user not found, is not a member, etc. This update also makes "digester lucked out" be considered successful processing. ---------------------------------------------------------------------- Comment By: Tim Potter (tpot) Date: 2002-03-25 10:18 Message: Logged In: YES user_id=9949 The scenario where addresses which don't seem to be on the list can be caused by bounces received after the user has been disabled due to the size of the mail queue. It may cause confusion forwarding them to the admin as there is nothing they can do about it except puzzle over why it was received. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 From noreply at sourceforge.net Tue Mar 11 02:38:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 05:27:28 2003 Subject: [ mailman-Patches-672714 ] cope with garbage Date Message-ID: Patches item #672714, was opened at 2003-01-22 21:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672714&group_id=103 Category: None Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Donn Cave (donnc) >Assigned to: Thomas Wouters (twouters) Summary: cope with garbage Date Initial Comment: rfc822.parsedate(garbage) -> None This patch allows archive generation to survive a garbage Date value. It recognizes the None return and does what it would have done if Date had been missing. *** Mailman/Archiver/pipermail.py.dist Sat Dec 7 18:21:58 2002 --- Mailman/Archiver/pipermail.py Wed Jan 15 15:58:31 2003 *************** *** 223,228 **** --- 223,230 ---- if datestr is missing: return None date = parsedate_tz(datestr) + if date is None: + return None try: return time.mktime(date[:9]) except (ValueError, OverflowError): *** Mailman/Handlers/Scrubber.py.dist Fri Dec 20 11:55:43 2002 --- Mailman/Handlers/Scrubber.py Wed Jan 15 16:00:31 2003 *************** *** 73,78 **** --- 73,80 ---- def safe_strftime(fmt, floatsecs): + if floatsecs is None: + return None try: return time.strftime(fmt, floatsecs) except ValueError: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 11:38 Message: Logged In: YES user_id=34209 This has already been fixed by making the except block following the offending pieces of code also catch 'TypeError'. But thanks for the patch :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672714&group_id=103 From noreply at sourceforge.net Tue Mar 11 03:06:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 05:55:06 2003 Subject: [ mailman-Patches-671294 ] syntax error in tests/fblast.py Message-ID: Patches item #671294, was opened at 2003-01-20 19:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671294&group_id=103 Category: command line scripts Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: John Dennis (johndennis) >Assigned to: Thomas Wouters (twouters) Summary: syntax error in tests/fblast.py Initial Comment: The tests/fblast.py script in version 2.1 had a syntax error due to a missing close paren. diff -r -u mailman-2.1.orig/tests/fblast.py mailman-2.1/tests/fblast.py --- mailman-2.1.orig/tests/fblast.py 2002-03-13 00:59:40.000000000 -0500 +++ mailman-2.1/tests/fblast.py 2003-01-14 16:46:57.000000000 -0500 @@ -54,7 +54,7 @@ """ % {'num' : i, 'FROMADDR': FROMADDR, 'LISTADDR': LISTADDR, - } + }) time.sleep(snooze) finally: conn.quit() ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 12:06 Message: Logged In: YES user_id=34209 Thanks, checked into CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=671294&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:29:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:17:51 2003 Subject: [ mailman-Feature Requests-403310 ] Have a maximum member count limit on lists. Message-ID: Feature Requests item #403310, was opened at 2001-01-18 12:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403310&group_id=103 >Category: None >Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Peter Liljenberg (petli) Assigned to: Nobody/Anonymous (nobody) Summary: Have a maximum member count limit on lists. Initial Comment: This patch to Mailman 2.0.1 makes it possible to control how large lists can be, in terms of members. Different lists can have different limits. Warnings will be sent to the list owner when the list is getting full, at configurable percent levels. When the list becoms full, the owner will be notified and new subscription requests will be queued. When there is room in the list, either because someone else unsubscribes or the limit is increased, queued requests will be subscribed. The limit can only be controlled by a command line script, list owners can't change the limit by themselves unless they have access to the mailman installation. See README.MAXNOMEMBERS for details, which is included in the patch. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:29 Message: Logged In: YES user_id=34209 The patch is no longer available, and likely would need to be entirely rewritten for Mailman 2.1 in any case. I'm moving this patch to Feature Requests, so we can look at it in the future or when someone has a need for it. ---------------------------------------------------------------------- Comment By: Peter Liljenberg (petli) Date: 2001-01-18 12:06 Message: Oh well, the patch was to large to upload here. It can be downloaded from http://www.cendio.se/~petli/mailman/ instead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403310&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:31:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:19:38 2003 Subject: [ mailman-Feature Requests-403066 ] Auto Approval of subscriptions for certain domains Message-ID: Feature Requests item #403066, was opened at 2001-01-01 15:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_id=103 >Category: None >Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Mark Tearle (mtearle) Assigned to: Nobody/Anonymous (nobody) Summary: Auto Approval of subscriptions for certain domains Initial Comment: A patch to enable automatic approval for certain domains, eg people in the example.com are automatically approved all others have to wait for the moderator ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:31 Message: Logged In: YES user_id=34209 Is this still necessary with Mailman 2.1, which has more 'automatic' options (as well as 'memberadaptors') ? In any case, the patch is likely heavily out of date by now, I'm moving this to Feature Requests for now. Feel free to respond if you (still) have a need. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:33:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:21:38 2003 Subject: [ mailman-Feature Requests-410286 ] Change the behavior of Cgi/admin.py Message-ID: Feature Requests item #410286, was opened at 2001-03-21 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=410286&group_id=103 Category: None >Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Chris Ryan (cryan) Assigned to: Nobody/Anonymous (nobody) Summary: Change the behavior of Cgi/admin.py Initial Comment: This patch changes the behavior of Mailman/Cgi/admin.py to use new methods of Mailman/MailList.py (also in this patch) instead of getattr() and setattr(). This will allow for the integration of the datasource driver code that is being developed to work properly without having to overhaul admin.py. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:33 Message: Logged In: YES user_id=34209 Is this still necessary for Mailman 2.1 ? It sounds a lot like the MemberAdaptors that were added. I also don't really see the point of not using getattr/setattr, it clutters the code and it isn't that hard to wrap it. But moving to feature requests, feel free to respond if you still have a need for this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=410286&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:34:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:22:21 2003 Subject: [ mailman-Feature Requests-401383 ] Defines HTML to head and foot all Mailman documents Message-ID: Feature Requests item #401383, was opened at 2000-09-01 03:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=401383&group_id=103 >Category: None >Group: None Status: Open Resolution: Postponed >Priority: 3 Submitted By: dgc (dgc) >Assigned to: Nobody/Anonymous (nobody) Summary: Defines HTML to head and foot all Mailman documents Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:34 Message: Logged In: YES user_id=34209 Moving to feature requests. Is this still actual, though ? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2001-06-07 23:42 Message: Logged In: YES user_id=12800 I'm reopening this one because it might be a good idea, and isn't implemented yet. Apache's mod_layout may be a better long term approach (see Chuq's mailman-developers post on the subject). ---------------------------------------------------------------------- Comment By: dgc (dgc) Date: 2000-12-15 06:10 Message: Revised for 2.0 final. This revision presumes prior application of 101379 and 101372, which are currently postponed. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-19 22:51 Message: This patch is a good idea, however I'm defering this until after 2.0 final. I'm hoping that we'll have a much more uniform way of modifying the look of a Mailman site in the future. ---------------------------------------------------------------------- Comment By: dgc (dgc) Date: 2000-09-01 03:16 Message: This adds GLOBAL_HEADER and GLOBAL_FOOTER variables in Defaults.py, then alters document presentation so that all Mailman documents show whatever they're set to at the head/foot of each page. This is for site look-n-feel stuff. By default it looks identical to what Mailman does already. Patch against 2.0beta5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=401383&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:37:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:25:52 2003 Subject: [ mailman-Patches-401598 ] Add command and args to LockFile's logging Message-ID: Patches item #401598, was opened at 2000-09-21 22:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Dan Mick (dmick) Assigned to: Nobody/Anonymous (nobody) Summary: Add command and args to LockFile's logging Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:37 Message: Logged In: YES user_id=34209 Barry, do you want this ? I'm not sure I see the point, as just sys.argv won't tell you too much in the case of HTTP POSTs, but I guess it doesn't hurt to add this. The patch is still current, and even applies cleanly in spite of being a straight ed diff ! :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:42:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:31:18 2003 Subject: [ mailman-Patches-401672 ] make 'Starting:' and 'Ending:' date localtime instead of GMT Message-ID: Patches item #401672, was opened at 2000-09-27 05:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401672&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: make 'Starting:' and 'Ending:' date localtime instead of GMT Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:42 Message: Logged In: YES user_id=34209 Hmm. I'm not sure which is clearer: Always GMT with no timezone marking, or always localtime (for the server) with no timezone marking :-) Perhaps we should add the timezone instead ? This problem is still current, by the way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401672&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:47:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:36:04 2003 Subject: [ mailman-Patches-401693 ] centers the footer logos Message-ID: Patches item #401693, was opened at 2000-09-28 18:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401693&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Martin Godisch (godisch) Assigned to: Nobody/Anonymous (nobody) Summary: centers the footer logos Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:47 Message: Logged In: YES user_id=34209 This is a style issue, really... I think I prefer the old way, having the logos in three cells spread evenly, but on the left side of those cells. But perhaps Barry likes the centered approach better ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401693&group_id=103 From noreply at sourceforge.net Tue Mar 11 05:50:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:39:40 2003 Subject: [ mailman-Patches-401719 ] insert correct mail signature delimiter Message-ID: Patches item #401719, was opened at 2000-09-30 07:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401719&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Martin Godisch (godisch) Assigned to: Nobody/Anonymous (nobody) Summary: insert correct mail signature delimiter Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:50 Message: Logged In: YES user_id=34209 Hmm. Yes, this is how it should be, except that many people have their own signatures, which already have '-- '. Not that that would hurt, of course. My only objection to this is that this will only take effect for new lists, but then, that may be a feature :-) Barry ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401719&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:04:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:52:42 2003 Subject: [ mailman-Patches-402077 ] get the subscriber's email address insubscribeack.txt Message-ID: Patches item #402077, was opened at 2000-10-23 09:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402077&group_id=103 Category: list administration Group: Mailman 2.0.x >Status: Closed >Resolution: Fixed Priority: 1 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Thomas Wouters (twouters) Summary: get the subscriber's email address insubscribeack.txt Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:04 Message: Logged In: YES user_id=34209 Added to CVS, but as 'user' instead of 'name' (as 'user' is also what, e.g., userpass.txt uses.) Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402077&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:05:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:53:42 2003 Subject: [ mailman-Feature Requests-402100 ] have a nicer admin-address Message-ID: Feature Requests item #402100, was opened at 2000-10-24 11:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=402100&group_id=103 >Category: None >Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Fil (fill) Assigned to: Nobody/Anonymous (nobody) Summary: have a nicer admin-address Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:05 Message: Logged In: YES user_id=34209 This patch somehwat makes sense (other than being broken) but I don't want to make the time to hunt for all the occurances of sending mail as a list right now... Moving to feature requests. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2003-02-25 14:57 Message: Logged In: YES user_id=17693 After apply this patch I have received Bug Page when I try to REMINDER THE PASSWORD. See: admin(25134): [----- Traceback ------] admin(25134): Traceback (most recent call last): admin(25134): File "/usr/lib/mailman/scripts/driver", line 96, in run_main admin(25134): main() admin(25134): File "./usr/lib/mailman/Mailman/Cgi/handle_opts.py", line 97, in main admin(25134): File "./usr/lib/mailman/Mailman/Cgi/handle_opts.py", line 144, in process_form admin(25134): File "/usr/lib/mailman/Mailman/Deliverer.py", line 120, in MailUserPassword admin(25134): msg = Message.UserNotification (recipient, '(%s) %s' % (listname,requestaddr), subject, text) admin(25134): NameError: global name 'listname' is not defined I have no idea how fix it... Can you help me? I know that problem is in the line: msg = Message.UserNotification (recipient, '(%s) %s' % (listname,requestaddr), subject, text)... ---------------------------------------------------------------------- Comment By: Fil (fill) Date: 2000-10-24 11:25 Message: Instead of receiving mail from list-request@.... receive it from (listname) list-request@.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=402100&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:06:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:54:31 2003 Subject: [ mailman-Feature Requests-402455 ] Generate .htaccess files containing username/passwd for list Message-ID: Feature Requests item #402455, was opened at 2000-11-20 19:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=402455&group_id=103 >Category: None >Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Generate .htaccess files containing username/passwd for list Initial Comment: ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:06 Message: Logged In: YES user_id=34209 This patch is out of date, but it shouldn't be hard to write something similar for Mailman 2.1. Moving to feature requests for now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=402455&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:10:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 08:59:22 2003 Subject: [ mailman-Patches-415448 ] Recognize bounces from swbell.net. Message-ID: Patches item #415448, was opened at 2001-04-11 18:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=415448&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) >Assigned to: Thomas Wouters (twouters) Summary: Recognize bounces from swbell.net. Initial Comment: This is a simple patch which causes Mailman/Bouncers/SimpleMatch.py to recognize bounce messages from swbell.net. (Might be "Sun Internet Mail Server".) This is a patch on Mailman-2.0.3. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:10 Message: Logged In: YES user_id=34209 Bounce detection was largely rewritten for Mailman 2.1. Also, swbell.net (at least their incoming mailservers) seem to be using Sendmail now. I'm closing this, if you still see problems with Mailman 2.1, please send us one of the bounces. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=415448&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:15:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:03:48 2003 Subject: [ mailman-Feature Requests-410286 ] Change the behavior of Cgi/admin.py Message-ID: Feature Requests item #410286, was opened at 2001-03-21 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=410286&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Chris Ryan (cryan) Assigned to: Nobody/Anonymous (nobody) Summary: Change the behavior of Cgi/admin.py Initial Comment: This patch changes the behavior of Mailman/Cgi/admin.py to use new methods of Mailman/MailList.py (also in this patch) instead of getattr() and setattr(). This will allow for the integration of the datasource driver code that is being developed to work properly without having to overhaul admin.py. ---------------------------------------------------------------------- >Comment By: Chris Ryan (cryan) Date: 2003-03-11 14:15 Message: Logged In: YES user_id=43820 I haven't kept up with the mailman project for almost 2 years now. I am not sure what developments have been made so the changes set forth in this report are most likely no longer valid. Please close/remove/handle this report as best suits the mailman project. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 13:33 Message: Logged In: YES user_id=34209 Is this still necessary for Mailman 2.1 ? It sounds a lot like the MemberAdaptors that were added. I also don't really see the point of not using getattr/setattr, it clutters the code and it isn't that hard to wrap it. But moving to feature requests, feel free to respond if you still have a need for this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=410286&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:23:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:11:56 2003 Subject: [ mailman-Patches-413752 ] Coerce posts to plain text. Message-ID: Patches item #413752, was opened at 2001-04-04 19:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:23 Message: Logged In: YES user_id=34209 I think we can call Mailman 2.1 sufficiently stable now to close this patch. There should still be a link on the unofficial-patches wiki -- except that I can't find the wiki :-) Barry ? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-10 15:39 Message: Logged In: YES user_id=75166 I encountered some problems with upgrading from MM 2.0.13 to MM 2.1b5 as a consequence of having installed this patch on our existing system. See: http://sourceforge.net/tracker/index.php? func=detail&aid=651406&group_id=103&atid=300103 for details of the symptoms and the solution that worked for me. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 19:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103 I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 19:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 18:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 17:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 06:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-28 05:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-28 02:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 21:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 17:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 17:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 17:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 19:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 22:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 21:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 20:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-20 01:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 21:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 06:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 06:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 06:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-08 05:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 18:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 17:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:25:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:13:52 2003 Subject: [ mailman-Feature Requests-410286 ] Change the behavior of Cgi/admin.py Message-ID: Feature Requests item #410286, was opened at 2001-03-21 16:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=410286&group_id=103 Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Chris Ryan (cryan) >Assigned to: Thomas Wouters (twouters) Summary: Change the behavior of Cgi/admin.py Initial Comment: This patch changes the behavior of Mailman/Cgi/admin.py to use new methods of Mailman/MailList.py (also in this patch) instead of getattr() and setattr(). This will allow for the integration of the datasource driver code that is being developed to work properly without having to overhaul admin.py. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:25 Message: Logged In: YES user_id=34209 Alright, closing then, thanks. As for not keeping up for 2 years -- don't worry, the same thing happened to me, and I came back into the light eventually too. :-) ---------------------------------------------------------------------- Comment By: Chris Ryan (cryan) Date: 2003-03-11 15:15 Message: Logged In: YES user_id=43820 I haven't kept up with the mailman project for almost 2 years now. I am not sure what developments have been made so the changes set forth in this report are most likely no longer valid. Please close/remove/handle this report as best suits the mailman project. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 14:33 Message: Logged In: YES user_id=34209 Is this still necessary for Mailman 2.1 ? It sounds a lot like the MemberAdaptors that were added. I also don't really see the point of not using getattr/setattr, it clutters the code and it isn't that hard to wrap it. But moving to feature requests, feel free to respond if you still have a need for this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=410286&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:26:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:15:02 2003 Subject: [ mailman-Patches-401598 ] Add command and args to LockFile's logging Message-ID: Patches item #401598, was opened at 2000-09-21 16:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 Category: list administration Group: Mailman 2.0.x >Status: Closed >Resolution: Rejected Priority: 1 Submitted By: Dan Mick (dmick) Assigned to: Nobody/Anonymous (nobody) Summary: Add command and args to LockFile's logging Initial Comment: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 09:26 Message: Logged In: YES user_id=12800 No, I think I'll reject this one. I don't want to count on sys.argv for anything. Plus, string module -- yuck :) I'm not exactly sure what information this adds or why Dan needs it so I'm closing this one. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 08:37 Message: Logged In: YES user_id=34209 Barry, do you want this ? I'm not sure I see the point, as just sys.argv won't tell you too much in the case of HTTP POSTs, but I guess it doesn't hurt to add this. The patch is still current, and even applies cleanly in spite of being a straight ed diff ! :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:29:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:17:48 2003 Subject: [ mailman-Patches-432819 ] listinfo and virtual hosts Message-ID: Patches item #432819, was opened at 2001-06-13 18:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=432819&group_id=103 Category: Web UI Group: Mailman 2.0.x >Status: Closed Resolution: None >Priority: 3 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Thomas Wouters (twouters) Summary: listinfo and virtual hosts Initial Comment: If you have virtual hosts the actual hostname from the http-server gets compared with the hostname in the URL of the list from the general configuration page. That comparison is done casesensitive and the output of my listinfo was empty. The patch makes the comparison caseinsensitive. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:29 Message: Logged In: YES user_id=34209 I believe this is already fixed in Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=432819&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:24:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:18:20 2003 Subject: [ mailman-Feature Requests-412398 ] no mailto links within archived text Message-ID: Feature Requests item #412398, was opened at 2001-03-30 08:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=412398&group_id=103 >Category: None >Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: no mailto links within archived text Initial Comment: One of my list subscriber wants this because he get too many personal questions. It would be better if we can obscure all the mail addresses within text though. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:24 Message: Logged In: YES user_id=34209 Moving to feature-requests; the idea is fine, but it should be list- or member-optional, rather than sitewide. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=412398&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:31:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:19:50 2003 Subject: [ mailman-Patches-423983 ] Virtual hosts support fixes Message-ID: Patches item #423983, was opened at 2001-05-14 19:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=423983&group_id=103 Category: Web UI Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 1 Submitted By: pbm (pbm) >Assigned to: Thomas Wouters (twouters) Summary: Virtual hosts support fixes Initial Comment: Even if the VIRTUAL_HOST_OVERVIEW variable is set, all the lists are show in the administrative interface and not just that belongiing to the called virtual host. In addition, the default host name is shown in the text. This is bad, because if you decide to hide the lists belonging to different virtual hosts in the listview interface, users can show them by just clicking on the "admin interface" link. (Of course, they could just change the hostname portion of the URL, but they must knowother vhosts' hostnames). This very simple patch should fix the problem. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:31 Message: Logged In: YES user_id=34209 I believe this is already fixed in Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=423983&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:34:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:23:43 2003 Subject: [ mailman-Patches-413752 ] Coerce posts to plain text. Message-ID: Patches item #413752, was opened at 2001-04-04 19:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 >Category: Unofficial 2.0 patch Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:34 Message: Logged In: YES user_id=34209 I created a seperate 'unofficial 2.0 patch' category, so the patches are more easily found. We could also mark the patch as 'pending' to stop it from showing up under the regular patches overview. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:23 Message: Logged In: YES user_id=34209 I think we can call Mailman 2.1 sufficiently stable now to close this patch. There should still be a link on the unofficial-patches wiki -- except that I can't find the wiki :-) Barry ? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-10 15:39 Message: Logged In: YES user_id=75166 I encountered some problems with upgrading from MM 2.0.13 to MM 2.1b5 as a consequence of having installed this patch on our existing system. See: http://sourceforge.net/tracker/index.php? func=detail&aid=651406&group_id=103&atid=300103 for details of the symptoms and the solution that worked for me. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 19:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103 I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 19:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 18:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 17:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 06:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-28 05:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-28 02:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 21:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 17:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 17:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 17:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 19:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 22:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 21:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 20:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-20 01:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 21:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 06:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 06:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 06:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-08 05:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 18:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 17:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:37:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:27:07 2003 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 20:27 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: 2003-02-10 16: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 19: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 15: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 21: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 21: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 21: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 17: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 12: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 11: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 11: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 12: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 13: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 18: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 16: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 13: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 18: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 18: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 12: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 18: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 13: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 17: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 16: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 11: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 12: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 19: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 17: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 17: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 17: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 18: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 12: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 13: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 12: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 Tue Mar 11 06:38:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:27:19 2003 Subject: [ mailman-Patches-401672 ] make 'Starting:' and 'Ending:' date localtime instead of GMT Message-ID: Patches item #401672, was opened at 2000-09-26 23:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401672&group_id=103 Category: Pipermail Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: make 'Starting:' and 'Ending:' date localtime instead of GMT Initial Comment: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 09:38 Message: Logged In: YES user_id=12800 Really? I think MM2.1 always uses localtime + TZ name. See http://mail.python.org/pipermail/playground/2003-February/date.html ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 08:42 Message: Logged In: YES user_id=34209 Hmm. I'm not sure which is clearer: Always GMT with no timezone marking, or always localtime (for the server) with no timezone marking :-) Perhaps we should add the timezone instead ? This problem is still current, by the way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401672&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:40:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:28:21 2003 Subject: [ mailman-Patches-449681 ] Bug #449677: HyperArch.py charsets Message-ID: Patches item #449681, was opened at 2001-08-10 03:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=449681&group_id=103 Category: Pipermail Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Ben Gertzfield (che_fox) >Assigned to: Thomas Wouters (twouters) Summary: Bug #449677: HyperArch.py charsets Initial Comment: Here's the patch for Bug #449677 (I didn't realize there was a separate Patches section til just now, whoops!). In short, HyperArch.py line 158 assumes charsets are in the form \w+ when in fact they can have characters outside of \w like - : ( ) etc. This patch makes Subject: lines with MIME encodings that use charsets like ISO-2022-JP get decoded properly in the archives. Patch is against Mailman 2.0.6. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:40 Message: Logged In: YES user_id=34209 I believe this is already fixed in Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=449681&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:40:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:29:34 2003 Subject: [ mailman-Patches-401693 ] centers the footer logos Message-ID: Patches item #401693, was opened at 2000-09-28 12:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401693&group_id=103 Category: Web UI Group: Mailman 2.0.x >Status: Closed >Resolution: Rejected Priority: 1 Submitted By: Martin Godisch (godisch) Assigned to: Nobody/Anonymous (nobody) Summary: centers the footer logos Initial Comment: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 09:40 Message: Logged In: YES user_id=12800 The current style looks fine to me. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 08:47 Message: Logged In: YES user_id=34209 This is a style issue, really... I think I prefer the old way, having the logos in three cells spread evenly, but on the left side of those cells. But perhaps Barry likes the centered approach better ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401693&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:42:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:30:49 2003 Subject: [ mailman-Patches-457702 ] SMTP32.py raises exception on None Message-ID: Patches item #457702, was opened at 2001-09-02 10:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457702&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 1 Submitted By: Mark Tearle (mtearle) >Assigned to: Thomas Wouters (twouters) Summary: SMTP32.py raises exception on None Initial Comment: SMTP32.py was dying trying to preforms startswith on None ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:42 Message: Logged In: YES user_id=34209 This is already fixed in Mailman 2.1. ---------------------------------------------------------------------- Comment By: Mark Tearle (mtearle) Date: 2001-09-02 10:55 Message: Logged In: YES user_id=2554 (against Mailman 2.1a3) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=457702&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:42:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:31:23 2003 Subject: [ mailman-Patches-401719 ] insert correct mail signature delimiter Message-ID: Patches item #401719, was opened at 2000-09-30 01:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401719&group_id=103 Category: mail delivery Group: Mailman 2.0.x >Status: Closed >Resolution: Rejected Priority: 1 Submitted By: Martin Godisch (godisch) Assigned to: Nobody/Anonymous (nobody) Summary: insert correct mail signature delimiter Initial Comment: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 09:42 Message: Logged In: YES user_id=12800 Right, I don't want to interfere with existing signature delimiters. Since this is easy to change, I don't want to muck with the default. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 08:50 Message: Logged In: YES user_id=34209 Hmm. Yes, this is how it should be, except that many people have their own signatures, which already have '-- '. Not that that would hurt, of course. My only objection to this is that this will only take effect for new lists, but then, that may be a feature :-) Barry ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401719&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:47:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:36:18 2003 Subject: [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) Assigned to: Nobody/Anonymous (nobody) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:47 Message: Logged In: YES user_id=34209 Ah, this is a good reason not to use '-- ' as the default footer/signature delimiter. The current behaviour (using '----------------' as the delimiter) should work then, as the correct signature delimiter is '-- ', two dashes followed by a space, and nothing else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply at sourceforge.net Tue Mar 11 06:50:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 09:39:24 2003 Subject: [ mailman-Patches-498747 ] Decoration fixes for MIME encodings Message-ID: Patches item #498747, was opened at 2002-01-02 23:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=498747&group_id=103 Category: mail delivery Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 1 Submitted By: Mikhail Zabaluev (mzabaluev) >Assigned to: Thomas Wouters (twouters) Summary: Decoration fixes for MIME encodings Initial Comment: Plugs the case when the sole body of a message is encoded in base64 or quoted-printable. In the former case, the body is left unchanged (I follow the principle of least meddling here); in the latter case, the header and footer are encoded to quoted-printable prior to being appended to the body. Also, some optimizations are made, such as the changed order of conditions. This is rather a short-term fix. For the long-time i18n solutions, I'll post a feature request later. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:50 Message: Logged In: YES user_id=34209 I think Mailman 2.1 fixes all these issues, and there is another unofficial 2.0 patch for flattening MIME messages available. Closing this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=498747&group_id=103 From noreply at sourceforge.net Tue Mar 11 07:15:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 10:05:05 2003 Subject: [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) >Assigned to: Thomas Wouters (twouters) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:15 Message: Logged In: YES user_id=34209 Since we aren't changing the default footer delimiter, marking this closed. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:47 Message: Logged In: YES user_id=34209 Ah, this is a good reason not to use '-- ' as the default footer/signature delimiter. The current behaviour (using '----------------' as the delimiter) should work then, as the correct signature delimiter is '-- ', two dashes followed by a space, and nothing else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply at sourceforge.net Tue Mar 11 07:24:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 10:13:32 2003 Subject: [ mailman-Patches-509269 ] Fix to fallback of thread by subject Message-ID: Patches item #509269, was opened at 2002-01-27 20:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=509269&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Stuart Donaldson (stuartd) Assigned to: Nobody/Anonymous (nobody) Summary: Fix to fallback of thread by subject Initial Comment: The existing code in HyperDatabase.py looks like it was intending to fallback to threading by subject if the In-Reply-To and References headers were missing. However the implementation it is broken, apparently an incomplete port of some other module. This patch fixes the set_location() method, and getOldestArticle methods to allow subject threading to once again work. Note: pipermail.py has an unused database class which also implements broken versions of these methods. This patch does not fix those because they were unused. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:24 Message: Logged In: YES user_id=34209 This patch looks like it still applies, but just looking at this code makes my hea d go *splat*. Can you confirm that this is still an issue for Mailman 2.1, and this is still the correct fix ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=509269&group_id=103 From noreply at sourceforge.net Tue Mar 11 07:36:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 10:37:25 2003 Subject: [ mailman-Patches-510407 ] Mail sizes on Admin request page Message-ID: Patches item #510407, was opened at 2002-01-29 23:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510407&group_id=103 Category: Web UI Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Magnus Stenman (snugge) >Assigned to: Thomas Wouters (twouters) Summary: Mail sizes on Admin request page Initial Comment: I've been having problems with mailman in moderated list mode, where posts over the max allowed size gets thru. This patch adds the size (below subject) to the "Pending Administrative Requests" page, and also adds a warning if that size exceeds the list maximum. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:36 Message: Logged In: YES user_id=34209 This is already fixed in Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510407&group_id=103 From noreply at sourceforge.net Tue Mar 11 08:13:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 11:01:22 2003 Subject: [ mailman-Patches-413752 ] Coerce posts to plain text. Message-ID: Patches item #413752, was opened at 2001-04-04 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 11:13 Message: Logged In: YES user_id=12800 Here's the wiki for MM2.0 unofficial patches. http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/UnofficialMailman20xPatches dairiki's patch is already there so I think we can close this report now. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 09:34 Message: Logged In: YES user_id=34209 I created a seperate 'unofficial 2.0 patch' category, so the patches are more easily found. We could also mark the patch as 'pending' to stop it from showing up under the regular patches overview. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 09:23 Message: Logged In: YES user_id=34209 I think we can call Mailman 2.1 sufficiently stable now to close this patch. There should still be a link on the unofficial-patches wiki -- except that I can't find the wiki :-) Barry ? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-10 09:39 Message: Logged In: YES user_id=75166 I encountered some problems with upgrading from MM 2.0.13 to MM 2.1b5 as a consequence of having installed this patch on our existing system. See: http://sourceforge.net/tracker/index.php? func=detail&aid=651406&group_id=103&atid=300103 for details of the symptoms and the solution that worked for me. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 13:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103 I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 13:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 12:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 11:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 00:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-27 23:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-27 20:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 15:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 11:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 11:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 11:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 13:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 16:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 15:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 14:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-19 19:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 15:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-07 23:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 12:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 11:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 From noreply at sourceforge.net Tue Mar 11 08:23:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 11:12:10 2003 Subject: [ mailman-Patches-413752 ] Coerce posts to plain text. Message-ID: Patches item #413752, was opened at 2001-04-04 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 1 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 11:23 Message: Logged In: YES user_id=12800 +1 on the category. Unfortunately, if you set status to pending, and there are no responses within 14 days it moves to deleted status. Apparently we can't add new stati or resoluti so I'll leave it as Closed/None. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 11:13 Message: Logged In: YES user_id=12800 Here's the wiki for MM2.0 unofficial patches. http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/UnofficialMailman20xPatches dairiki's patch is already there so I think we can close this report now. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 09:34 Message: Logged In: YES user_id=34209 I created a seperate 'unofficial 2.0 patch' category, so the patches are more easily found. We could also mark the patch as 'pending' to stop it from showing up under the regular patches overview. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 09:23 Message: Logged In: YES user_id=34209 I think we can call Mailman 2.1 sufficiently stable now to close this patch. There should still be a link on the unofficial-patches wiki -- except that I can't find the wiki :-) Barry ? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-10 09:39 Message: Logged In: YES user_id=75166 I encountered some problems with upgrading from MM 2.0.13 to MM 2.1b5 as a consequence of having installed this patch on our existing system. See: http://sourceforge.net/tracker/index.php? func=detail&aid=651406&group_id=103&atid=300103 for details of the symptoms and the solution that worked for me. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 13:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103 I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 13:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 12:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 11:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 00:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-27 23:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-27 20:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 15:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 11:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 11:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 11:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 13:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 16:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 15:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 14:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-19 19:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 15:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 00:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-07 23:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 12:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 11:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 From noreply at sourceforge.net Tue Mar 11 11:51:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 14:40:33 2003 Subject: [ mailman-Patches-401598 ] Add command and args to LockFile's logging Message-ID: Patches item #401598, was opened at 2000-09-21 20:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Closed Resolution: Rejected Priority: 1 Submitted By: Dan Mick (dmick) Assigned to: Nobody/Anonymous (nobody) Summary: Add command and args to LockFile's logging Initial Comment: ---------------------------------------------------------------------- >Comment By: Dan Mick (dmick) Date: 2003-03-11 19:51 Message: Logged In: YES user_id=10725 The point was that many different agents can be trying to acquire the same lock file; argv gave me "which agent", and presence in the logs file in a certain order gave me order, so it gave me nearly-free more information about diagnosing lock failures. I guess I don't see how this is a mystery. Fine, throw out string module, but what's wrong with sys.argv? Isn't that exactly the first question to ask, "who's failing to get the lock"? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-11 14:26 Message: Logged In: YES user_id=12800 No, I think I'll reject this one. I don't want to count on sys.argv for anything. Plus, string module -- yuck :) I'm not exactly sure what information this adds or why Dan needs it so I'm closing this one. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 13:37 Message: Logged In: YES user_id=34209 Barry, do you want this ? I'm not sure I see the point, as just sys.argv won't tell you too much in the case of HTTP POSTs, but I guess it doesn't hurt to add this. The patch is still current, and even applies cleanly in spite of being a straight ed diff ! :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=401598&group_id=103 From noreply at sourceforge.net Tue Mar 11 14:13:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 17:02:34 2003 Subject: [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) Assigned to: Thomas Wouters (twouters) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- >Comment By: Kjetil T. Homme (kjetilho) Date: 2003-03-11 23:13 Message: Logged In: YES user_id=147170 closed the bug? why, it's still there. if the user doesn't have a signature delimiter, the mailing list footer will appear as content. that's broken. this patch fixes the problem without breaking anything. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:15 Message: Logged In: YES user_id=34209 Since we aren't changing the default footer delimiter, marking this closed. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:47 Message: Logged In: YES user_id=34209 Ah, this is a good reason not to use '-- ' as the default footer/signature delimiter. The current behaviour (using '----------------' as the delimiter) should work then, as the correct signature delimiter is '-- ', two dashes followed by a space, and nothing else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply at sourceforge.net Tue Mar 11 14:30:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 17:18:20 2003 Subject: [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) Assigned to: Thomas Wouters (twouters) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-11 23:30 Message: Logged In: YES user_id=34209 No, the patch doesn't do it without breaking anything; suddenly, in some cases, the list footer is different. What's more, since the default list footer does not contain the signature separator (by design), the patch would effect to nothing except if people changed the footer to include the signature separator -- and if they do, I have to assume they do it for a reason. In my experience, very few lists change the footer at all, and none so far have added the signature separator. A possible solution would be to enable list administrators to force a signature separator before the footer; that is, if it isn't in the original mail, add it before the footer. I'll add that to my TODO list. ---------------------------------------------------------------------- Comment By: Kjetil T. Homme (kjetilho) Date: 2003-03-11 23:13 Message: Logged In: YES user_id=147170 closed the bug? why, it's still there. if the user doesn't have a signature delimiter, the mailing list footer will appear as content. that's broken. this patch fixes the problem without breaking anything. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:15 Message: Logged In: YES user_id=34209 Since we aren't changing the default footer delimiter, marking this closed. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:47 Message: Logged In: YES user_id=34209 Ah, this is a good reason not to use '-- ' as the default footer/signature delimiter. The current behaviour (using '----------------' as the delimiter) should work then, as the correct signature delimiter is '-- ', two dashes followed by a space, and nothing else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:17:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:05:13 2003 Subject: [ mailman-Patches-522080 ] Respond sensibly to blank -request email Message-ID: Patches item #522080, was opened at 2002-02-24 16:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=522080&group_id=103 Category: list administration Group: Mailman 2.0.x >Status: Closed >Resolution: Fixed Priority: 1 Submitted By: Seb Wills (sebwills) >Assigned to: Thomas Wouters (twouters) Summary: Respond sensibly to blank -request email Initial Comment: In Mailman 2.0.8, if you send an emtpy message containing no commands to the -request address, the reply is also entirely blank. This extremely simple patch to MailCommandHandler.py changes this behaviour so that a blank message to a - request address returns an error telling the user that their message contained no commands, and reminding them how to get the help message. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:17 Message: Logged In: YES user_id=34209 I've added something similar to CVS, with different code (since the entire command handler was rewritten for Mailman 2.1) but with more or less the same message. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=522080&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:19:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:08:36 2003 Subject: [ mailman-Patches-534298 ] forward unhandled bounces to admin Message-ID: Patches item #534298, was opened at 2002-03-24 14:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 Category: list administration Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: forward unhandled bounces to admin Initial Comment: samba.org handles a lot of mail messages, and therefore suffers a lot of bounced messages. Mailman's automatic bounce handling is great, but the problem is that people keep dreaming up new and wierd bounce messages. With Mailman 2.0.8, if I turn on automatic bounce handling then some bouncing addresses are not correctly detected and therefore keep generating large amounts of traffic indefinitely. If I turn it off, we get about 3000 bounces per day. Some of these are just not handled yet by the BouncerAPI and need patches. In some cases there is in fact no deterministic way to work out the bouncing address (at least until we have VERP), and human intervention is required. For example, Novell's brilliant mail software includes no information in the Received lines or bounce message to indicate what the bouncing address is! Anyhow, this patch changes the behaviour of the bounce handler so that bounce messages which do not cause any positive action are forwarded to the list administrator. "Positive action" can mean noticing that the address is already disabled, or marking it as bouncing, or similar things. It doesn't include addresses which don't seem to be on the list, which probably means that we have not interpreted the message properly and more help is required. So in summary bounces which can be automatically handled will be, and others will go to the admin. I'm not sure this is the perfect behaviour, but it certainly seems like an improvement. Perhaps you want to make it more configurable. Please merge this, or something like it. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:19 Message: Logged In: YES user_id=34209 Yeah, Mailman 2.1's bounce detection and handling was largely rewritten. It also uses VERP now, so it should solve most of your bounce problems, if not all. I'm going to close this patch, as well as your other pending bounce-detection patches, but if you see any new unhandled bounces (or find that previously-reported ones still fail to detect) please do open a new bug- or patch-report. (Preferably with an example message for us to test on.) I promise we wont let it rest as long as this one has. :-) ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-11 02:16 Message: Logged In: YES user_id=521 This seems to be already fixed in 2.1. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-03 04:18 Message: Logged In: YES user_id=521 Tim, that's not quite so much of a problem as you might think. When excessive bounces are detected Mailman only *disables* addresses rather than removing them. With or without this patch, bouncing addresses which are already disabled are noted in the log file and not further action is taken. Problems can occur if the address is actually removed. This can arise in two ways. One way is that the mail administrator might explicitly remove the user from the list because of manual bounce processing. In that case, any later bounces will also go through to the admin. That's the reason for my patch to add --disable to remove_members. Secondly, users might unsubscribe themselves and then have their address start bouncing. You can imagine Mailman remembering previously-subscribed members so that it could handle these cases, but that's a much bigger project, and probably best done in conjunction with VERP. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 02:03 Message: Logged In: YES user_id=521 This patch modifies the behaviour when handling bounce messages with multiple addresses, such as from Postfix. Now messages in which any of the bouncing addresses cannot be automatically handled are forwarded to the administrator. Eventually it might be nice to put a notice in the message explaining the problem -- e.g. user not found, is not a member, etc. This update also makes "digester lucked out" be considered successful processing. ---------------------------------------------------------------------- Comment By: Tim Potter (tpot) Date: 2002-03-25 00:18 Message: Logged In: YES user_id=9949 The scenario where addresses which don't seem to be on the list can be caused by bounces received after the user has been disabled due to the size of the mail queue. It may cause confusion forwarding them to the admin as there is nothing they can do about it except puzzle over why it was received. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:20:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:09:06 2003 Subject: [ mailman-Patches-520621 ] patch to handle new Yahoo! bounce format Message-ID: Patches item #520621, was opened at 2002-02-20 21:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: patch to handle new Yahoo! bounce format Initial Comment: Yahoo seem to have changed the format of their bounce messages. This patch makes 2.0.8 detect them again. >From looking at CVSweb it seems like it would work fine with 2.2 as well. Python Rocks! ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:20 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-02-21 19:42 Message: Logged In: YES user_id=521 (Silly sourceforge attachments!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:21:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:09:53 2003 Subject: [ mailman-Patches-521110 ] patch to handle new MAIL32 bounce format Message-ID: Patches item #521110, was opened at 2002-02-21 19:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521110&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: patch to handle new MAIL32 bounce format Initial Comment: We've observed many bounce messages apparently from the MAIL32 mailer, but with slightly different text. This patch lets Mailman detect them automatically. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521110&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:21:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:10:03 2003 Subject: [ mailman-Patches-521124 ] Bouncer for SMTP_Gateway Message-ID: Patches item #521124, was opened at 2002-02-21 20:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521124&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for SMTP_Gateway Initial Comment: Another whacko mail bounce format. We see a few of these. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521124&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:21:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:10:24 2003 Subject: [ mailman-Patches-521129 ] Bouncer for ATTMail Message-ID: Patches item #521129, was opened at 2002-02-21 20:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for ATTMail Initial Comment: Seems to use UUCP-style addresses; metadata is in the headers. You also need to insert this into the list of bouncers in BouncerAPI.py ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:22:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:10:49 2003 Subject: [ mailman-Patches-534297 ] demon.co.uk and another bounce handler Message-ID: Patches item #534297, was opened at 2002-03-24 14:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: demon.co.uk and another bounce handler Initial Comment: This patch handles the format currently observed for demo.co.uk addresses as of 2002-02-24. Please merge it. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:22 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 02:10 Message: Logged In: YES user_id=521 The machine in the second format says "PP 5.0" in its SMTP banner. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 01:51 Message: Logged In: YES user_id=521 Here's an updated patch which handles another format. I can't see any identification of what software it is. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 14:08 Message: Logged In: YES user_id=521 oops, here it is ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:22:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:11:14 2003 Subject: [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) Assigned to: Thomas Wouters (twouters) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:22 Message: Logged In: YES user_id=34209 No, the patch doesn't do it without breaking anything; suddenly, in some cases, the list footer is different. What's more, since the default list footer does not contain the signature separator (by design), the patch would effect to nothing except if people changed the footer to include the signature separator -- and if they do, I have to assume they do it for a reason. In my experience, very few lists change the footer at all, and none so far have added the signature separator. A possible solution would be to enable list administrators to force a signature separator before the footer; that is, if it isn't in the original mail, add it before the footer. I'll add that to my TODO list. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 23:30 Message: Logged In: YES user_id=34209 No, the patch doesn't do it without breaking anything; suddenly, in some cases, the list footer is different. What's more, since the default list footer does not contain the signature separator (by design), the patch would effect to nothing except if people changed the footer to include the signature separator -- and if they do, I have to assume they do it for a reason. In my experience, very few lists change the footer at all, and none so far have added the signature separator. A possible solution would be to enable list administrators to force a signature separator before the footer; that is, if it isn't in the original mail, add it before the footer. I'll add that to my TODO list. ---------------------------------------------------------------------- Comment By: Kjetil T. Homme (kjetilho) Date: 2003-03-11 23:13 Message: Logged In: YES user_id=147170 closed the bug? why, it's still there. if the user doesn't have a signature delimiter, the mailing list footer will appear as content. that's broken. this patch fixes the problem without breaking anything. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:15 Message: Logged In: YES user_id=34209 Since we aren't changing the default footer delimiter, marking this closed. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:47 Message: Logged In: YES user_id=34209 Ah, this is a good reason not to use '-- ' as the default footer/signature delimiter. The current behaviour (using '----------------' as the delimiter) should work then, as the correct signature delimiter is '-- ', two dashes followed by a space, and nothing else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:25:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:13:49 2003 Subject: [ mailman-Patches-562061 ] Poor grammar: templates/subscribeack.txt Message-ID: Patches item #562061, was opened at 2002-05-29 22:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=562061&group_id=103 Category: None Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Dominic Hargreaves (therealdom) Assigned to: Nobody/Anonymous (nobody) Summary: Poor grammar: templates/subscribeack.txt Initial Comment: This file contains the phrase: "You may also have your password mailed to you automatically off of the Web page noted above." This is incorrect, and should read: "You may also have your password mailed to you automatically from the Web page noted above." The attached trivial patch fixes this. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:25 Message: Logged In: YES user_id=34209 No longer applies to Mailman 2.1, as subscribeack.txt was rewritten, but thanks for the report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=562061&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:30:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:18:58 2003 Subject: [ mailman-Patches-594831 ] Incomplete DSN bounce tracking Message-ID: Patches item #594831, was opened at 2002-08-14 02:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=594831&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Jesús Cea Avión (jcea) Assigned to: Nobody/Anonymous (nobody) Summary: Incomplete DSN bounce tracking Initial Comment: Mailman 2.0.13 here. I didn´t check Mailman 2.1.*. I'm very surprised nobody found & correct the problem before. Problem: Some valid DSN bounce notifications are not correctly parsed. A DSN message with several "packets", last packet is ignored. Reproduce: not neccesary. Code inspection should show this patch as trivially correct. Patch: In file Mailman/Bouncers/DSN.py, simply add two lines: --- DSN.py Tue Aug 13 13:22:39 2002 +++ DSN2.py Wed Aug 14 01:57:09 2002 @@ -105,6 +105,10 @@ headers[string.lower(hdr)] = string.strip(val) # now go through all the blocks, finding the recip address that is being # reported. + + if len(headers) : + blocks.append(headers) + addrs = [] for headers in blocks: if string.lower(headers.get('action', '')) <> 'failed': ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:30 Message: Logged In: YES user_id=34209 I don't think this applies to Mailman 2.1, as it uses full VERP (optionally, but enabled by default, and strongly encouraged) and bounce detection by DSN parsing was rewritten as well, and seems to do the right thing. But thanks for the report, if you notice it is still current, please file another patch or bugreport :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=594831&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:31:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:19:55 2003 Subject: [ mailman-Patches-623783 ] Option to discard non-member postings Message-ID: Patches item #623783, was opened at 2002-10-15 23:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=623783&group_id=103 Category: list administration Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Alan Batie (abatie) Assigned to: Nobody/Anonymous (nobody) Summary: Option to discard non-member postings Initial Comment: Spam has become such an epidemic that any even semi-public list must restrict postings to members only, but then it's up to the administrator to go in and manually delete it all, which is a real pain through the web interface in mailman. This patch adds an option to just throw all non-member postings away. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:31 Message: Logged In: YES user_id=34209 This is already in Mailman 2.1 by now, so closing this patch. But thanks for the report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=623783&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:32:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:20:49 2003 Subject: [ mailman-Patches-624112 ] mail password reminder bug Message-ID: Patches item #624112, was opened at 2002-10-16 16:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=624112&group_id=103 Category: mail delivery Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Marcin Deranek (marcin_deranek) Assigned to: Nobody/Anonymous (nobody) Summary: mail password reminder bug Initial Comment: cron/mailpasswds script sends improper headers (Sender, Errors-To, X-BeenThere, Return-Path). It uses headers of first publicly available mailing list. My patch uses MAILMAN_OWNER variable from config file as sender of password reminder. Patch was created for version 2.0.13. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:32 Message: Logged In: YES user_id=34209 This is fixed in Mailman 2.1; it requires a site-wide-installation list, and uses that for such messages. But thanks for the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=624112&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:36:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:25:05 2003 Subject: [ mailman-Feature Requests-636504 ] Configurable absolute URLs for scripts Message-ID: Feature Requests item #636504, was opened at 2002-11-11 09:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636504&group_id=103 >Category: None >Group: None Status: Open >Resolution: Out of Date Priority: 1 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable absolute URLs for scripts Initial Comment: In my Mailman setup I want to use http for some URLs (most of them, including the archives) for less CPU usage on the server, and https on some URLs (login with password, list administration) for better (if not good, since the passwords go in cleartext over mail anyway) security. One way of accomplishing this is to make script URLs absolute, and set DEFAULT_URL to a https hostname. This patch makes it possible to configure if GetScriptURL should by default return an absolute URL using a variable in Default.py/mm_cfg.py. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:36 Message: Logged In: YES user_id=34209 I see the point of using https in list administration, but not member options (member passwords aren't really secure to start with.) But the patch is way out of date by now, sorry about that... Moving this to feature requests, to look at it in the future. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=636504&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:38:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:27:40 2003 Subject: [ mailman-Patches-637686 ] Simple members-in-LDAP support. Message-ID: Patches item #637686, was opened at 2002-11-13 11:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=637686&group_id=103 Category: mail delivery Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 1 Submitted By: Erik Forsberg (forsberg) Assigned to: Nobody/Anonymous (nobody) Summary: Simple members-in-LDAP support. Initial Comment: In an organization where all users are in a LDAP directory, fetching data about members of a mailing list from the directory is sometimes a good idea. For example, in my directory, I can find out all members of a certain organizational unit using a LDAP search. I still want all the other features of Mailman - archives, restrict posting to members, etc.. This patch makes it possible to define a LDAP search URI (RFC2255) in the configuration. When posting to the list, the search is executed and the resulting mail addresses are added to the normal list members. It's configurable on a per-installation-level if the ldap search configuration should be displayed. The python-ldap module is needed in order for this to work. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:38 Message: Logged In: YES user_id=34209 This doesn't apply to Mailman 2.1 anymore, though the MemberAdaptor interface allows you to fairly easily create something similar but better. I'm marking this patch closed, but if you consider it still useful for Mailman 2.0 users (and they do too) we could add it to the unofficial 2.0 patch list... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=637686&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:43:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:31:33 2003 Subject: [ mailman-Patches-534298 ] forward unhandled bounces to admin Message-ID: Patches item #534298, was opened at 2002-03-25 00:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Closed Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: forward unhandled bounces to admin Initial Comment: samba.org handles a lot of mail messages, and therefore suffers a lot of bounced messages. Mailman's automatic bounce handling is great, but the problem is that people keep dreaming up new and wierd bounce messages. With Mailman 2.0.8, if I turn on automatic bounce handling then some bouncing addresses are not correctly detected and therefore keep generating large amounts of traffic indefinitely. If I turn it off, we get about 3000 bounces per day. Some of these are just not handled yet by the BouncerAPI and need patches. In some cases there is in fact no deterministic way to work out the bouncing address (at least until we have VERP), and human intervention is required. For example, Novell's brilliant mail software includes no information in the Received lines or bounce message to indicate what the bouncing address is! Anyhow, this patch changes the behaviour of the bounce handler so that bounce messages which do not cause any positive action are forwarded to the list administrator. "Positive action" can mean noticing that the address is already disabled, or marking it as bouncing, or similar things. It doesn't include addresses which don't seem to be on the list, which probably means that we have not interpreted the message properly and more help is required. So in summary bounces which can be automatically handled will be, and others will go to the admin. I'm not sure this is the perfect behaviour, but it certainly seems like an improvement. Perhaps you want to make it more configurable. Please merge this, or something like it. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-03-12 11:43 Message: Logged In: YES user_id=521 > Yeah, Mailman 2.1's bounce detection and handling was > largely rewritten. It also uses VERP now, so it should solve > most of your bounce problems, if not all. Yes, we're using VERP now and it's beautiful. In particular we have a lot of Exchange subscribers, and their bounce messages are nearly unintelligible. > I'm going to close this patch, as well as your other pending > bounce-detection patches, but if you see any new unhandled bounces > (or find that previously-reported ones still fail to detect) please > do open a new bug- or patch-report. I am OK about closing this one, but please reopen the others. Since Mailman still has the option of using a bounce parser rather than VERP it seems to make sense to have the parser be as smart as possible. Some people might not want to use VERP. Unless the patches no longer merge, I would encourage you to put them in. > (Preferably with an example message for us to test on.) I will do that in future. I think that was not mentioned when I sent them, though I do think the patches have partial examples in their comments. > I promise we wont let it rest as long as this one has. :-) Thanks. I know it can be hard to get around to these things. -- Martin ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 11:19 Message: Logged In: YES user_id=34209 Yeah, Mailman 2.1's bounce detection and handling was largely rewritten. It also uses VERP now, so it should solve most of your bounce problems, if not all. I'm going to close this patch, as well as your other pending bounce-detection patches, but if you see any new unhandled bounces (or find that previously-reported ones still fail to detect) please do open a new bug- or patch-report. (Preferably with an example message for us to test on.) I promise we wont let it rest as long as this one has. :-) ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-11 12:16 Message: Logged In: YES user_id=521 This seems to be already fixed in 2.1. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-03 12:18 Message: Logged In: YES user_id=521 Tim, that's not quite so much of a problem as you might think. When excessive bounces are detected Mailman only *disables* addresses rather than removing them. With or without this patch, bouncing addresses which are already disabled are noted in the log file and not further action is taken. Problems can occur if the address is actually removed. This can arise in two ways. One way is that the mail administrator might explicitly remove the user from the list because of manual bounce processing. In that case, any later bounces will also go through to the admin. That's the reason for my patch to add --disable to remove_members. Secondly, users might unsubscribe themselves and then have their address start bouncing. You can imagine Mailman remembering previously-subscribed members so that it could handle these cases, but that's a much bigger project, and probably best done in conjunction with VERP. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 12:03 Message: Logged In: YES user_id=521 This patch modifies the behaviour when handling bounce messages with multiple addresses, such as from Postfix. Now messages in which any of the bouncing addresses cannot be automatically handled are forwarded to the administrator. Eventually it might be nice to put a notice in the message explaining the problem -- e.g. user not found, is not a member, etc. This update also makes "digester lucked out" be considered successful processing. ---------------------------------------------------------------------- Comment By: Tim Potter (tpot) Date: 2002-03-25 10:18 Message: Logged In: YES user_id=9949 The scenario where addresses which don't seem to be on the list can be caused by bounces received after the user has been disabled due to the size of the mail queue. It may cause confusion forwarding them to the admin as there is nothing they can do about it except puzzle over why it was received. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:48:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:37:01 2003 Subject: [ mailman-Patches-534298 ] forward unhandled bounces to admin Message-ID: Patches item #534298, was opened at 2002-03-24 14:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Closed Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: forward unhandled bounces to admin Initial Comment: samba.org handles a lot of mail messages, and therefore suffers a lot of bounced messages. Mailman's automatic bounce handling is great, but the problem is that people keep dreaming up new and wierd bounce messages. With Mailman 2.0.8, if I turn on automatic bounce handling then some bouncing addresses are not correctly detected and therefore keep generating large amounts of traffic indefinitely. If I turn it off, we get about 3000 bounces per day. Some of these are just not handled yet by the BouncerAPI and need patches. In some cases there is in fact no deterministic way to work out the bouncing address (at least until we have VERP), and human intervention is required. For example, Novell's brilliant mail software includes no information in the Received lines or bounce message to indicate what the bouncing address is! Anyhow, this patch changes the behaviour of the bounce handler so that bounce messages which do not cause any positive action are forwarded to the list administrator. "Positive action" can mean noticing that the address is already disabled, or marking it as bouncing, or similar things. It doesn't include addresses which don't seem to be on the list, which probably means that we have not interpreted the message properly and more help is required. So in summary bounces which can be automatically handled will be, and others will go to the admin. I'm not sure this is the perfect behaviour, but it certainly seems like an improvement. Perhaps you want to make it more configurable. Please merge this, or something like it. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:48 Message: Logged In: YES user_id=34209 As mentioned in email, I'll re-check the other bounce-detection patches, but the ones I checked didn't apply to 2.1 for other reasons as well (like their original module being completely rewritten.) ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-12 01:43 Message: Logged In: YES user_id=521 > Yeah, Mailman 2.1's bounce detection and handling was > largely rewritten. It also uses VERP now, so it should solve > most of your bounce problems, if not all. Yes, we're using VERP now and it's beautiful. In particular we have a lot of Exchange subscribers, and their bounce messages are nearly unintelligible. > I'm going to close this patch, as well as your other pending > bounce-detection patches, but if you see any new unhandled bounces > (or find that previously-reported ones still fail to detect) please > do open a new bug- or patch-report. I am OK about closing this one, but please reopen the others. Since Mailman still has the option of using a bounce parser rather than VERP it seems to make sense to have the parser be as smart as possible. Some people might not want to use VERP. Unless the patches no longer merge, I would encourage you to put them in. > (Preferably with an example message for us to test on.) I will do that in future. I think that was not mentioned when I sent them, though I do think the patches have partial examples in their comments. > I promise we wont let it rest as long as this one has. :-) Thanks. I know it can be hard to get around to these things. -- Martin ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:19 Message: Logged In: YES user_id=34209 Yeah, Mailman 2.1's bounce detection and handling was largely rewritten. It also uses VERP now, so it should solve most of your bounce problems, if not all. I'm going to close this patch, as well as your other pending bounce-detection patches, but if you see any new unhandled bounces (or find that previously-reported ones still fail to detect) please do open a new bug- or patch-report. (Preferably with an example message for us to test on.) I promise we wont let it rest as long as this one has. :-) ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-11 02:16 Message: Logged In: YES user_id=521 This seems to be already fixed in 2.1. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-04-03 04:18 Message: Logged In: YES user_id=521 Tim, that's not quite so much of a problem as you might think. When excessive bounces are detected Mailman only *disables* addresses rather than removing them. With or without this patch, bouncing addresses which are already disabled are noted in the log file and not further action is taken. Problems can occur if the address is actually removed. This can arise in two ways. One way is that the mail administrator might explicitly remove the user from the list because of manual bounce processing. In that case, any later bounces will also go through to the admin. That's the reason for my patch to add --disable to remove_members. Secondly, users might unsubscribe themselves and then have their address start bouncing. You can imagine Mailman remembering previously-subscribed members so that it could handle these cases, but that's a much bigger project, and probably best done in conjunction with VERP. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 02:03 Message: Logged In: YES user_id=521 This patch modifies the behaviour when handling bounce messages with multiple addresses, such as from Postfix. Now messages in which any of the bouncing addresses cannot be automatically handled are forwarded to the administrator. Eventually it might be nice to put a notice in the message explaining the problem -- e.g. user not found, is not a member, etc. This update also makes "digester lucked out" be considered successful processing. ---------------------------------------------------------------------- Comment By: Tim Potter (tpot) Date: 2002-03-25 00:18 Message: Logged In: YES user_id=9949 The scenario where addresses which don't seem to be on the list can be caused by bounces received after the user has been disabled due to the size of the mail queue. It may cause confusion forwarding them to the admin as there is nothing they can do about it except puzzle over why it was received. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534298&group_id=103 From noreply at sourceforge.net Tue Mar 11 16:52:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 11 19:40:51 2003 Subject: [ mailman-Patches-493622 ] Edit signature delimiter in footer Message-ID: Patches item #493622, was opened at 2001-12-15 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 1 Submitted By: Kjetil T. Homme (kjetilho) Assigned to: Thomas Wouters (twouters) Summary: Edit signature delimiter in footer Initial Comment: According to the standards, a MUA should search for the signature delimiter from the bottom. If the footer contains a standard signature delimiter, it will be chopped off by the MUA, but the real signature is left intact. This patch changes the footer delimiter to "__ " when the original message has a signature already. ---------------------------------------------------------------------- >Comment By: Kjetil T. Homme (kjetilho) Date: 2003-03-12 01:52 Message: Logged In: YES user_id=147170 yes, some lists change the footer delimiter to "-- ", but of course, most administrators accept defaults blindly. as a user of many Mailman lists, it is very annoying to have footers appear as text, when my email client could ignore it easily if a proper footer delimiter was used. however, fixing the code which appends the footer is better than having the signature delimiter be part of the footer. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:22 Message: Logged In: YES user_id=34209 No, the patch doesn't do it without breaking anything; suddenly, in some cases, the list footer is different. What's more, since the default list footer does not contain the signature separator (by design), the patch would effect to nothing except if people changed the footer to include the signature separator -- and if they do, I have to assume they do it for a reason. In my experience, very few lists change the footer at all, and none so far have added the signature separator. A possible solution would be to enable list administrators to force a signature separator before the footer; that is, if it isn't in the original mail, add it before the footer. I'll add that to my TODO list. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 23:30 Message: Logged In: YES user_id=34209 No, the patch doesn't do it without breaking anything; suddenly, in some cases, the list footer is different. What's more, since the default list footer does not contain the signature separator (by design), the patch would effect to nothing except if people changed the footer to include the signature separator -- and if they do, I have to assume they do it for a reason. In my experience, very few lists change the footer at all, and none so far have added the signature separator. A possible solution would be to enable list administrators to force a signature separator before the footer; that is, if it isn't in the original mail, add it before the footer. I'll add that to my TODO list. ---------------------------------------------------------------------- Comment By: Kjetil T. Homme (kjetilho) Date: 2003-03-11 23:13 Message: Logged In: YES user_id=147170 closed the bug? why, it's still there. if the user doesn't have a signature delimiter, the mailing list footer will appear as content. that's broken. this patch fixes the problem without breaking anything. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 16:15 Message: Logged In: YES user_id=34209 Since we aren't changing the default footer delimiter, marking this closed. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 15:47 Message: Logged In: YES user_id=34209 Ah, this is a good reason not to use '-- ' as the default footer/signature delimiter. The current behaviour (using '----------------' as the delimiter) should work then, as the correct signature delimiter is '-- ', two dashes followed by a space, and nothing else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=493622&group_id=103 From noreply at sourceforge.net Wed Mar 12 09:46:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 12:35:33 2003 Subject: [ mailman-Patches-520621 ] patch to handle new Yahoo! bounce format Message-ID: Patches item #520621, was opened at 2002-02-20 21:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Open Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) >Assigned to: Thomas Wouters (twouters) Summary: patch to handle new Yahoo! bounce format Initial Comment: Yahoo seem to have changed the format of their bounce messages. This patch makes 2.0.8 detect them again. >From looking at CVSweb it seems like it would work fine with 2.2 as well. Python Rocks! ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 18:46 Message: Logged In: YES user_id=34209 Re-opening, because this one would apply to current CVS, and might be necessary for non-VERP bounce detection. I'm worried that the new format doesn't handle the old format :-) I'm not sure how these Yahoo bounces work in any case; there is only one type of Yahoo mailserver active at the moment ? ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:20 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-02-21 19:42 Message: Logged In: YES user_id=521 (Silly sourceforge attachments!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 From noreply at sourceforge.net Wed Mar 12 09:46:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 12:35:41 2003 Subject: [ mailman-Patches-521110 ] patch to handle new MAIL32 bounce format Message-ID: Patches item #521110, was opened at 2002-02-21 19:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521110&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Open Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: patch to handle new MAIL32 bounce format Initial Comment: We've observed many bounce messages apparently from the MAIL32 mailer, but with slightly different text. This patch lets Mailman detect them automatically. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 18:46 Message: Logged In: YES user_id=34209 The SMTP32 bounce detector was already expanded, in 2.1, to cover some more phrasings. ('delivery failed' and 'undeliverable to') Do you happen to know if that covers what this patch would cover ? ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521110&group_id=103 From noreply at sourceforge.net Wed Mar 12 09:50:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 12:38:05 2003 Subject: [ mailman-Patches-521124 ] Bouncer for SMTP_Gateway Message-ID: Patches item #521124, was opened at 2002-02-21 20:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521124&group_id=103 Category: bounce processing Group: Mailman 2.0.x Status: Closed Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for SMTP_Gateway Initial Comment: Another whacko mail bounce format. We see a few of these. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 18:50 Message: Logged In: YES user_id=34209 >From reading the code, I believe this is already covered by the Postfix bounce detector in Mailman 2.1. I've added it explicitly now. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521124&group_id=103 From noreply at sourceforge.net Wed Mar 12 09:50:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 12:38:39 2003 Subject: [ mailman-Patches-521129 ] Bouncer for ATTMail Message-ID: Patches item #521129, was opened at 2002-02-21 20:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Open Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for ATTMail Initial Comment: Seems to use UUCP-style addresses; metadata is in the headers. You also need to insert this into the list of bouncers in BouncerAPI.py ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 18:50 Message: Logged In: YES user_id=34209 I'm worried about this generating a lot of false-positives, as it *only* looks at those two headers, and nothing else. Barry ? ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 From noreply at sourceforge.net Wed Mar 12 09:50:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 12:38:50 2003 Subject: [ mailman-Patches-520621 ] patch to handle new Yahoo! bounce format Message-ID: Patches item #520621, was opened at 2002-02-20 15:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 Category: bounce processing Group: Mailman 2.0.x Status: Open Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Thomas Wouters (twouters) Summary: patch to handle new Yahoo! bounce format Initial Comment: Yahoo seem to have changed the format of their bounce messages. This patch makes 2.0.8 detect them again. >From looking at CVSweb it seems like it would work fine with 2.2 as well. Python Rocks! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-12 12:50 Message: Logged In: YES user_id=12800 Try running the test suite and see! :) ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 12:46 Message: Logged In: YES user_id=34209 Re-opening, because this one would apply to current CVS, and might be necessary for non-VERP bounce detection. I'm worried that the new format doesn't handle the old format :-) I'm not sure how these Yahoo bounces work in any case; there is only one type of Yahoo mailserver active at the moment ? ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 19:20 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-02-21 13:42 Message: Logged In: YES user_id=521 (Silly sourceforge attachments!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=520621&group_id=103 From noreply at sourceforge.net Wed Mar 12 09:52:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 12:40:30 2003 Subject: [ mailman-Patches-534297 ] demon.co.uk and another bounce handler Message-ID: Patches item #534297, was opened at 2002-03-24 14:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 Category: bounce processing Group: Mailman 2.0.x >Status: Open Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: demon.co.uk and another bounce handler Initial Comment: This patch handles the format currently observed for demo.co.uk addresses as of 2002-02-24. Please merge it. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-12 18:52 Message: Logged In: YES user_id=34209 Added the first one to SimpleMatch.py in CVS. The second one looks fishy; the text implies it's a delay-warning, not an actual bounce. I'm not sure whether to add it, partly because the machine in the comment is now running Postfix. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 01:22 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 02:10 Message: Logged In: YES user_id=521 The machine in the second format says "PP 5.0" in its SMTP banner. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-25 01:51 Message: Logged In: YES user_id=521 Here's an updated patch which handles another format. I can't see any identification of what software it is. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2002-03-24 14:08 Message: Logged In: YES user_id=521 oops, here it is ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534297&group_id=103 From noreply at sourceforge.net Wed Mar 12 10:24:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 12 13:13:04 2003 Subject: [ mailman-Patches-521129 ] Bouncer for ATTMail Message-ID: Patches item #521129, was opened at 2002-02-21 14:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 Category: bounce processing Group: Mailman 2.0.x Status: Open Resolution: Out of Date Priority: 1 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer for ATTMail Initial Comment: Seems to use UUCP-style addresses; metadata is in the headers. You also need to insert this into the list of bouncers in BouncerAPI.py ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-12 13:24 Message: Logged In: YES user_id=12800 I wouldn't want to add this without a sample bounce message that we can add to the test suite. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-12 12:50 Message: Logged In: YES user_id=34209 I'm worried about this generating a lot of false-positives, as it *only* looks at those two headers, and nothing else. Barry ? ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 19:21 Message: Logged In: YES user_id=34209 Most likely solved by Mailman 2.1 using VERP. Closing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=521129&group_id=103 From noreply at sourceforge.net Wed Mar 12 21:21:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 00:10:27 2003 Subject: [ mailman-Bugs-700140 ] obsolete version number in TODO Message-ID: Bugs item #700140, was opened at 2003-03-08 18:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 Category: documentation Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: obsolete version number in TODO Initial Comment: Got email-2.4.3.tar.gz from the latest cvs. It includes a TODO file, with the following notation: - We should support RFC 2231. Oleg Broytmann has patches to add this support, so we'll look into it for email-1.3. Since this is email-2.4, I presume either its been done or the version number needs to change. This is a low-priority item. I figured I mention it, since I saw it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-13 00:21 Message: Logged In: YES user_id=12800 Bugs and patches on the email package probably belong better on the Python or mimelib projects. But in any event, I've updated the TODO list. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 From noreply at sourceforge.net Wed Mar 12 21:58:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 00:47:10 2003 Subject: [ mailman-Bugs-699900 ] Postfix 450 keeps Mailman looping; doc suggestion Message-ID: Bugs item #699900, was opened at 2003-03-08 06:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Walter Hop (life4m) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix 450 keeps Mailman looping; doc suggestion Initial Comment: When Postfix is configured to give transient (450) SMTP errors on local error, and Mailman tries to send to an unknown local recipient, Mailman by default keeps trying to deliver the same message every second. 450 is the default on some Postfix installations. This addition to README.POSTFIX might help other people in curing such a problem. I also think retrying every second is a bit blunt, but I haven't investigated that - there's probably a parameter for it :) cheers, walter ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-13 00:58 Message: Logged In: YES user_id=12800 Thanks. Not only did I add a blurb to README.POSTFIX, but I fixed the retry-every-second problem. ---------------------------------------------------------------------- Comment By: Walter Hop (life4m) Date: 2003-03-08 06:06 Message: Logged In: YES user_id=729148 Attachment didn't go through... Here is it: --- README.POSTFIX Sun Feb 23 23:41:10 2003 +++ README.POSTFIX Sat Mar 8 11:19:16 2003 @@ -25,6 +25,13 @@ well with the default values for VERP_FORMAT and VERP_REGEXP in Defaults.py. + Some Postfix installations may have some error codes set to + 4xx (transient) errors. To prevent Mailman from retrying erroneous + local addresses endlessly, it is advised to set the following in + main.cf: + + unknown_local_recipient_reject_code = 550 + Finally, if you are using Postfix-style virtual domains, read the section on virtual domain support below. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=699900&group_id=103 From noreply at sourceforge.net Thu Mar 13 08:52:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 11:40:46 2003 Subject: [ mailman-Patches-703076 ] Updated patch that allows posting authorization for members Message-ID: Patches item #703076, was opened at 2003-03-13 10:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=703076&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nathan Neulinger (nneul) Assigned to: Nobody/Anonymous (nobody) Summary: Updated patch that allows posting authorization for members Initial Comment: This patch allows you to specify +listname in the accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, and discard_these_nonmembers boxes in the list configuration, and will dynamically include the members of those lists. This is very useful when you have lists that forward to other lists. For example: mygroup-leaders mygroup-helpers mygroup-workers with mygroup-all forwarding to each of the above. You could put +mygroup-helpers +mygroup-workers +mygroup-leaders in the accept box for each of those lists, and it will allow any of the members of any of the lists to post to the mygroup-all list. Or similar affect for other configurations. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=703076&group_id=103 From noreply at sourceforge.net Thu Mar 13 08:53:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 11:41:40 2003 Subject: [ mailman-Patches-703078 ] patch to add a DEFAULT_UCFIRST_REAL_NAME option Message-ID: Patches item #703078, was opened at 2003-03-13 10:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=703078&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nathan Neulinger (nneul) Assigned to: Nobody/Anonymous (nobody) Summary: patch to add a DEFAULT_UCFIRST_REAL_NAME option Initial Comment: This patch adds a DEFAULT_UCFIRST_REAL_NAME option, defaulting to 1, which allows site admin to request that new lists all be created with the list name being all lowercase by default, instead of the mixed case name. -- Nathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=703078&group_id=103 From noreply at sourceforge.net Thu Mar 13 08:54:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 11:43:36 2003 Subject: [ mailman-Patches-670522 ] Sublists for posting authorization Message-ID: Patches item #670522, was opened at 2003-01-18 19:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670522&group_id=103 Category: list administration Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Nathan Neulinger (nneul) Assigned to: Nobody/Anonymous (nobody) Summary: Sublists for posting authorization Initial Comment: This allows functionality like the "send" option for Listserv. Patch is based on the list_exploder patch submitted for 2.0. Putting: +list@thisdomain in the *_these_nonmembers boxes, and it will expand that to the contents of that list when checking for authorization to post/etc. Patch is not very invasive, although someone more familiar with the mailman sources will likely want to rename the subroutines to something more in scheme. ---------------------------------------------------------------------- >Comment By: Nathan Neulinger (nneul) Date: 2003-03-13 10:54 Message: Logged In: YES user_id=22767 closing my own post, I submitted a newer version in another patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670522&group_id=103 From noreply at sourceforge.net Thu Mar 13 11:52:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 14:40:49 2003 Subject: [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-10 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-13 14:52 Message: Logged In: YES user_id=12800 Upping the priority ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 18:29 Message: Logged In: YES user_id=12800 This would be cool to add to cron/checkdbs. Here are some ideas - either have a MAX_REQUEST_AGE value in Defaults.py or a max_request_age attribute on lists if you want this to be different per-list (which might be a good idea since this is dependent on how often the list admins clear their pendings) - in the checkdbs message, keep a record of how many old ones you expire and mention it in the user notification. e.g. 17 old requests automatically expired. I'll mark this as for MM2.1 group, but it's really going to be pushed back until the following release. ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-10 20:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply at sourceforge.net Thu Mar 13 13:04:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 15:53:02 2003 Subject: [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 06:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- Comment By: Fil (filfil) Date: 2003-03-13 22:04 Message: Logged In: YES user_id=243444 Is it possible to modify that code so that it calls the classic spamassassin if the spamd daemon is not running? (Or is it already functioning this way?) ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2003-02-07 08:23 Message: Logged In: YES user_id=81797 I can't get this code to work with Mailman 2.1. A message that triggers the hold for moderator starts bouncing messages from the list owner and just sits in a mail loop until I remove SpamAssassin from the filter chain, delivering a message for every loop to the admin interface. I spent a couple of hours looking at it, but I can't see why it is doing this. It's defeinitely in the Hold.hold_for_whatever, but I don't know why that's failing. Just thought I'd mention it. I guess we'll stay with 2.0 where it's working fine with the other patch-set. Sean ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-02-03 03:39 Message: Logged In: YES user_id=485579 Yes, use the version with the "footsie" code. I don't appear to have permission to delete the older version from this patch tracker. It doesn't make any special exceptions with regard to the list owner, but I'll have a look at making that part of the logic smarter. ---------------------------------------------------------------------- Comment By: Shamanic Acid (shamanicacid) Date: 2003-01-28 08:18 Message: Logged In: YES user_id=698712 I am a bit confused in which SpamAssassin.py file to use. There does not seem to be an embedded version number in the download links. The diff I see is as follows: $ diff SpamAssassin.1.py SpamAssassin.py 62,65d61 < # First, play footsie with _ so that the following are marked as translated, < # but aren't actually translated until we need the text later on. < def _(s): < return s 71,73d66 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < 78,80d70 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < Question # 1. Do I want to use the SpamAssassin.py file with the "footsie" code? Question # 2. Does the SpamAssassin.py code allow for exceptions when the e-mail is from the $list-owner ( bounces to moderator ) ? I ask because I ran into a problem with a mailer-loop occuring when SpamAssassin errantly tagged the $list-owner moderator bounces as spam. ( spamassasin marks pending e-mails from $list-owner with score 7.6 ) I have not read through all the code, I am curious if mlist.isMember(sender) includes the owner alias? Many Thanks in Advance ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-12 17:01 Message: Logged In: YES user_id=485579 I've updated the SpamAssassin handler to report a more detailed reason when a DiscardMessage and HoldMessage exception is raised. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-01 01:33 Message: Logged In: YES user_id=485579 The attached patch adds the SpamAssassin handler to Mailman's mail processing pipelines. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 17:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 From noreply at sourceforge.net Thu Mar 13 15:03:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 17:51:55 2003 Subject: [ mailman-Bugs-703287 ] INSTALL is too terse about site-wide list Message-ID: Bugs item #703287, was opened at 2003-03-13 17:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703287&group_id=103 Category: documentation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark McEahern (mceahm) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL is too terse about site-wide list Initial Comment: The INSTALL file is too terse about the purpose of the site-wide mailing list. See: http://mail.python.org/pipermail/mailman-users/2003- March/027179.html I recommend adding something like this to the end of the bullet that starts 'Create a "site-wide" mailing list.': """Errors and warnings generated by Mailman itself will be sent to the site-wide mailing list, so the first thing you probably want to do is make this list private. Your site administrators should probably be the only ones subscribed to this list.""" Of course, I'm new to Mailman, so I don't know whether the above is true or useful. But I as is, the INSTALL file provides very little context for the purpose of the site- wide list. Thanks, // mark ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703287&group_id=103 From noreply at sourceforge.net Thu Mar 13 15:04:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 17:53:04 2003 Subject: [ mailman-Bugs-703287 ] INSTALL is too terse about site-wide list Message-ID: Bugs item #703287, was opened at 2003-03-13 17:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703287&group_id=103 Category: documentation >Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Submitted By: Mark McEahern (mceahm) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL is too terse about site-wide list Initial Comment: The INSTALL file is too terse about the purpose of the site-wide mailing list. See: http://mail.python.org/pipermail/mailman-users/2003- March/027179.html I recommend adding something like this to the end of the bullet that starts 'Create a "site-wide" mailing list.': """Errors and warnings generated by Mailman itself will be sent to the site-wide mailing list, so the first thing you probably want to do is make this list private. Your site administrators should probably be the only ones subscribed to this list.""" Of course, I'm new to Mailman, so I don't know whether the above is true or useful. But I as is, the INSTALL file provides very little context for the purpose of the site- wide list. Thanks, // mark ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703287&group_id=103 From noreply at sourceforge.net Thu Mar 13 15:05:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 17:53:17 2003 Subject: [ mailman-Bugs-703287 ] INSTALL is too terse about site-wide list Message-ID: Bugs item #703287, was opened at 2003-03-13 17:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703287&group_id=103 Category: documentation >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark McEahern (mceahm) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL is too terse about site-wide list Initial Comment: The INSTALL file is too terse about the purpose of the site-wide mailing list. See: http://mail.python.org/pipermail/mailman-users/2003- March/027179.html I recommend adding something like this to the end of the bullet that starts 'Create a "site-wide" mailing list.': """Errors and warnings generated by Mailman itself will be sent to the site-wide mailing list, so the first thing you probably want to do is make this list private. Your site administrators should probably be the only ones subscribed to this list.""" Of course, I'm new to Mailman, so I don't know whether the above is true or useful. But I as is, the INSTALL file provides very little context for the purpose of the site- wide list. Thanks, // mark ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703287&group_id=103 From noreply at sourceforge.net Thu Mar 13 20:49:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 13 23:38:30 2003 Subject: [ mailman-Bugs-697321 ] minor cosmetic bug in add_members help Message-ID: Bugs item #697321, was opened at 2003-03-04 11:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=697321&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: minor cosmetic bug in add_members help Initial Comment: the commandline options help screen for bin/add_members has a tiny "cosmetic" bug... it says: --digest-members-file=file -d=file But "-d=file" doesn't work.. it should be "-d file" of course. Ricardo. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-13 23:49 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=697321&group_id=103 From noreply at sourceforge.net Thu Mar 13 21:31:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 14 00:19:21 2003 Subject: [ mailman-Bugs-695526 ] check_perms does not read mm_cfg.py Message-ID: Bugs item #695526, was opened at 2003-03-01 04:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=695526&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Luigi Rosa (lrosa) Assigned to: Nobody/Anonymous (nobody) Summary: check_perms does not read mm_cfg.py Initial Comment: I modified the logs path in mm_cfg.py inserting the line LOG_DIR = '/var/log/mailman' and I verified that Mailman was logging in that directory After that, I run check_perms -v and I noticed that the script still verifies /usr/local/mailman/logs, but doesn't verify /var/log/mailman ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-14 00:31 Message: Logged In: YES user_id=12800 Fixed specifically to follow mm_cfg.LOG_DIR ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=695526&group_id=103 From noreply at sourceforge.net Fri Mar 14 17:03:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 14 19:52:07 2003 Subject: [ mailman-Bugs-703941 ] Invited user can subscribe to any list (inc private lists) Message-ID: Bugs item #703941, was opened at 2003-03-15 12:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703941&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stuart Bishop (zenzen) Assigned to: Nobody/Anonymous (nobody) Summary: Invited user can subscribe to any list (inc private lists) Initial Comment: Currently, the Pending queue maintains no reference to what mailing list a subscription request is for. This is encoded in the URL, and isn't a security problem for subscriptions. However, Invitations are a special sort of subscription that bypasses the subscription approval step if the user accepts the invitation. So if a user munges the URL they are sent from http://wherever/invited_list/123cookie to http://whereever/private_list/123cookie, and goes to that link, they are subscribed to the private list with no notification to anyone. Simple solution may be to set userdesc.invited to the listname rather than just '1', and then when checking for the invited flag make sure that someone is hacking the system. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703941&group_id=103 From noreply at sourceforge.net Sat Mar 15 06:56:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 15 09:44:01 2003 Subject: [ mailman-Bugs-703941 ] Invited user can subscribe to any list (inc private lists) Message-ID: Bugs item #703941, was opened at 2003-03-14 20:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703941&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None >Priority: 8 Submitted By: Stuart Bishop (zenzen) Assigned to: Nobody/Anonymous (nobody) Summary: Invited user can subscribe to any list (inc private lists) Initial Comment: Currently, the Pending queue maintains no reference to what mailing list a subscription request is for. This is encoded in the URL, and isn't a security problem for subscriptions. However, Invitations are a special sort of subscription that bypasses the subscription approval step if the user accepts the invitation. So if a user munges the URL they are sent from http://wherever/invited_list/123cookie to http://whereever/private_list/123cookie, and goes to that link, they are subscribed to the private list with no notification to anyone. Simple solution may be to set userdesc.invited to the listname rather than just '1', and then when checking for the invited flag make sure that someone is hacking the system. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-15 09:56 Message: Logged In: YES user_id=12800 Raising the priority so this must be fixed for 2.1.2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703941&group_id=103 From noreply at sourceforge.net Sat Mar 15 14:06:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 15 16:54:07 2003 Subject: [ mailman-Patches-670167 ] fix i18n attachment description in archive Message-ID: Patches item #670167, was opened at 2003-01-18 05:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: Accepted >Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix i18n attachment description in archive Initial Comment: Bug-ID 669081 (Major attachment handling bug!) is caused inaccurate handling of charset in Scrubber.py. This is caused by misuse of email functions (or by bug in email package). In Scrubber.py, attempt is made to get message charset by part.get_charset() but it returns only None, as far as I experimented. In this patch, message charset is extracted from regular expression pattern in content-type header. This also set the charset of internally crafted message part. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-24 04:34 Message: Logged In: YES user_id=67709 Uploading revised patch to fix more error. Sorry for the people downloaded earlier. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-24 01:39 Message: Logged In: YES user_id=67709 update my patch to fix error reported by sumeet File "/list/Mailman/Handlers/Scrubber.py", line 320, in process if not t.endswith('\n'): AttributeError: 'NoneType' object has no attribute 'endswith' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-22 07:05 Message: Logged In: YES user_id=67709 This patch for Scrubber.py now include Bug-ID #691039. save_attachment() now returns (url, size), because in previous code, get_paylaod() is called before calling save_attachment() only to get the size. save_attachment() calls get_payload() inside. We might be able to discard the attachment if get_payload(decode=1) fail. (TBD: return discard message and size 0 ?) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:31 Message: Logged In: YES user_id=67709 Increment priority because this is now a bug fix. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 06:08 Message: Logged In: YES user_id=67709 I made a new patch to fix embedded multipart messages are stripped bug. this patch is for CVS. see http://mail.python.org/pipermail/mailman-users/2003-February/026071.html ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-20 05:13 Message: Logged In: YES user_id=12800 Reopening so this issue doesn't get lost. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-20 04:03 Message: Logged In: YES user_id=67709 We, Japanese, need additional process of stringify and regenerate message instance.. Internal message is in 'euc-jp' but return value of get_content_charset() becomes 'iso-2022-jp' even though the get_payload() returns euc-jp text. The message and part body is converted to iso-2022-jp when it is output to SMTP (or whatever accepts in string format). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-20 02:18 Message: Logged In: YES user_id=12800 Accepted, with changes. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-19 00:52 Message: Logged In: YES user_id=67709 Update of patch. Please backout the first one if you have already applied. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 From noreply at sourceforge.net Sat Mar 15 18:57:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 15 21:45:39 2003 Subject: [ mailman-Patches-665569 ] make Postfix bounce detection work with newer postfix Message-ID: Patches item #665569, was opened at 2003-01-10 17:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: make Postfix bounce detection work with newer postfix Initial Comment: Mailman does not recognise bounce messages from newer versions of Postfix. The content-type header on bounce messages looks like this: Content-Type: multipart/report; report-type=delivery-status; boundary="2892E4C0CF.1042189077/quoll.daa.com.au" Mailman only looks for bounce messages with type multipart/mixed, so skips them. The simple solution is to check for both content types (which should allow mailman to continue to work with old postfixes. The attached patch is against 2.0.x (haven't upgraded to MM2.1 yet), but the code is almost identical for 2.1 so the patch should be easy to apply. ---------------------------------------------------------------------- >Comment By: James Henstridge (jhenstridge) Date: 2003-03-16 10:57 Message: Logged In: YES user_id=146903 Not sure if this code is applicable to MM2.1. I guess the generic DSN bounce detection handles it. If there is another MM2.0.x bug fix release, it may be nice to apply. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2003-01-10 17:36 Message: Logged In: YES user_id=146903 Hmm. It seems to have lost the attachment ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 From noreply at sourceforge.net Sat Mar 15 23:09:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 16 01:57:36 2003 Subject: [ mailman-Bugs-703941 ] Invited user can subscribe to any list (inc private lists) Message-ID: Bugs item #703941, was opened at 2003-03-14 20:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703941&group_id=103 Category: security/privacy Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 8 Submitted By: Stuart Bishop (zenzen) Assigned to: Nobody/Anonymous (nobody) Summary: Invited user can subscribe to any list (inc private lists) Initial Comment: Currently, the Pending queue maintains no reference to what mailing list a subscription request is for. This is encoded in the URL, and isn't a security problem for subscriptions. However, Invitations are a special sort of subscription that bypasses the subscription approval step if the user accepts the invitation. So if a user munges the URL they are sent from http://wherever/invited_list/123cookie to http://whereever/private_list/123cookie, and goes to that link, they are subscribed to the private list with no notification to anyone. Simple solution may be to set userdesc.invited to the listname rather than just '1', and then when checking for the invited flag make sure that someone is hacking the system. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-16 02:09 Message: Logged In: YES user_id=12800 Fixed! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-15 09:56 Message: Logged In: YES user_id=12800 Raising the priority so this must be fixed for 2.1.2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=703941&group_id=103 From noreply at sourceforge.net Sun Mar 16 01:43:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 16 04:31:44 2003 Subject: [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 13:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2003-03-16 17:43 Message: Logged In: YES user_id=146903 If you haven't assigned copyright for your work to the FSF, don't say that your code is copyrighted by the FSF. Doing so could cause problems in the event of a lawsuit. Accurate copyright notices are essential. In answer to filfil's question, the code requires that spamd is running. However, if it can't contact spamd for some reason, the message will pass this filter, so that mail doesn't get lost. ---------------------------------------------------------------------- Comment By: Fil (filfil) Date: 2003-03-14 05:04 Message: Logged In: YES user_id=243444 Is it possible to modify that code so that it calls the classic spamassassin if the spamd daemon is not running? (Or is it already functioning this way?) ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2003-02-07 15:23 Message: Logged In: YES user_id=81797 I can't get this code to work with Mailman 2.1. A message that triggers the hold for moderator starts bouncing messages from the list owner and just sits in a mail loop until I remove SpamAssassin from the filter chain, delivering a message for every loop to the admin interface. I spent a couple of hours looking at it, but I can't see why it is doing this. It's defeinitely in the Hold.hold_for_whatever, but I don't know why that's failing. Just thought I'd mention it. I guess we'll stay with 2.0 where it's working fine with the other patch-set. Sean ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-02-03 10:39 Message: Logged In: YES user_id=485579 Yes, use the version with the "footsie" code. I don't appear to have permission to delete the older version from this patch tracker. It doesn't make any special exceptions with regard to the list owner, but I'll have a look at making that part of the logic smarter. ---------------------------------------------------------------------- Comment By: Shamanic Acid (shamanicacid) Date: 2003-01-28 15:18 Message: Logged In: YES user_id=698712 I am a bit confused in which SpamAssassin.py file to use. There does not seem to be an embedded version number in the download links. The diff I see is as follows: $ diff SpamAssassin.1.py SpamAssassin.py 62,65d61 < # First, play footsie with _ so that the following are marked as translated, < # but aren't actually translated until we need the text later on. < def _(s): < return s 71,73d66 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < 78,80d70 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < Question # 1. Do I want to use the SpamAssassin.py file with the "footsie" code? Question # 2. Does the SpamAssassin.py code allow for exceptions when the e-mail is from the $list-owner ( bounces to moderator ) ? I ask because I ran into a problem with a mailer-loop occuring when SpamAssassin errantly tagged the $list-owner moderator bounces as spam. ( spamassasin marks pending e-mails from $list-owner with score 7.6 ) I have not read through all the code, I am curious if mlist.isMember(sender) includes the owner alias? Many Thanks in Advance ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-13 00:01 Message: Logged In: YES user_id=485579 I've updated the SpamAssassin handler to report a more detailed reason when a DiscardMessage and HoldMessage exception is raised. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-01 08:33 Message: Logged In: YES user_id=485579 The attached patch adds the SpamAssassin handler to Mailman's mail processing pipelines. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-28 00:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 From noreply at sourceforge.net Sun Mar 16 11:15:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 16 14:03:44 2003 Subject: [ mailman-Bugs-658261 ] transcheck error for double % Message-ID: Bugs item #658261, was opened at 2002-12-24 18:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Simone Piunno (pioppo) Summary: transcheck error for double % Initial Comment: As reported by Daniel Buchmann, transcheck doesn't detect correctly when a literal % is expressed as a double %, e.g. %%(<variabelnavn>)s is detected a variable reference to interpolate insted of a simple text. The fix would require a much more complex parser, which is not worth it now but could be in 2.2. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-03-16 20:15 Message: Logged In: YES user_id=227443 here is a small solution to the problem.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103 From noreply at sourceforge.net Sun Mar 16 13:35:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 16 16:22:58 2003 Subject: [ mailman-Bugs-704661 ] extra html opening and closing tags Message-ID: Bugs item #704661, was opened at 2003-03-16 16:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704661&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Carl C. Longnecker (longneck) Assigned to: Nobody/Anonymous (nobody) Summary: extra html opening and closing tags Initial Comment: mailman 2.0.13 i customized all of the public HTML pages using the mailman administration interface. they all look OK, except for the "Changing user options results page". check out this page: http://www.tampabaytot.org/mailman/listinfo/theology-on- tap_tampabaytot.org try and unsubscribe squeak@no.way with any password. when you get to the results page, it's white (should be yellow). if you look at the source, you'll notice there are two sets of html, body, head, etc. tags. They are not in the configuration page, so mailman must be adding them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704661&group_id=103 From noreply at sourceforge.net Sun Mar 16 20:41:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 16 23:28:54 2003 Subject: [ mailman-Bugs-658261 ] transcheck error for double % Message-ID: Bugs item #658261, was opened at 2002-12-24 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Simone Piunno (pioppo) Summary: transcheck error for double % Initial Comment: As reported by Daniel Buchmann, transcheck doesn't detect correctly when a literal % is expressed as a double %, e.g. %%(<variabelnavn>)s is detected a variable reference to interpolate insted of a simple text. The fix would require a much more complex parser, which is not worth it now but could be in 2.2. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-16 23:41 Message: Logged In: YES user_id=12800 Applied, thanks ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-03-16 14:15 Message: Logged In: YES user_id=227443 here is a small solution to the problem.... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103 From noreply at sourceforge.net Sun Mar 16 21:46:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 17 00:35:09 2003 Subject: [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 16:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- >Comment By: James Henstridge (jhenstridge) Date: 2003-03-17 13:46 Message: Logged In: YES user_id=146903 Attached is an updated version of the filter for adding SpamAssassin support to mailman. This version is targetted at Mailman 2.1.x. The code for talking to spamd has been split out into a separate file, so that it can be updated independently of the Mailman specific code. It has also been updated to work with SpamAssassin 2.50 (and should be a lot more robust to future additions to the spamd protocol). The filter has also been changed to use the list name as the username passed to spamd, which means that separate auto-whitelists and bayes databases can be maintained for each list. Installation is trivial. Simply copy spamd.py and SpamAssassin.py to the Mailman/Handlers directory and add the following line to Mailman/mm_cfg.py: GLOBAL_PIPELINE.insert(1, 'SpamAssassin') ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:32 Message: Logged In: YES user_id=81797 That last one had a missing quote. Try this patch: *** SpamAssassin.py.orig Fri Aug 23 00:28:59 2002 --- SpamAssassin.py Fri Aug 23 00:31:00 2002 *************** *** 30,45 **** from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_PORT = 0 ! try: ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! i = string.find(SPAMD_HOST, ':') ! if i >= 0: ! SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] ! try: SPAMD_PORT = int(SPAMD_PORT) ! except: SPAMD_PORT = None ! except: ! SPAMD_HOST = 'localhost' if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE --- 30,44 ---- from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_HOST = 'localhost' ! SPAMD_PORT = None ! if hasattr(mm_cfg, 'SPAMASSASSIN_HOST'): ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! try: ! SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) ! SPAMD_PORT = int(SPAMD_PORT) ! except ValueError: ! SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:19 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:18 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: dann frazier (dannf) Date: 2002-08-18 02:11 Message: Logged In: YES user_id=146718 hey James, found a typo. also wanted to point out: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139942&repeatmerged=yes --- SpamAssassin.py.orig Sat Aug 17 12:05:41 2002 +++ SpamAssassin.py Sat Aug 17 12:06:13 2002 @@ -35,7 +35,7 @@ SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST i = string.find(SPAMD_HOST, ':') if i >= 0: - SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] + SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], SPAMD_HOST[i+1:] try: SPAMD_PORT = int(SPAMD_PORT) except: SPAMD_PORT = None except: ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 17:00 Message: Logged In: YES user_id=146903 remembering to check the "upload file" checkbox this time ... ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 16:59 Message: Logged In: YES user_id=146903 Yet another new version that fixes a small typo. With previous messages, you couldn't approve messages that had been identified as spam once (they would get identified again when the queue got processed, instead of passing the message through). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-10 08:19 Message: Logged In: YES user_id=146903 The Mailman installation on mail.gnome.org also uses this filter. I don't think there are any stability problems with the filter. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-07-10 05:16 Message: Logged In: YES user_id=81797 FYI, I ran the previous version since installation and it seemed to work fine. I didn't run into any problems, with probably 500 messages handled. I've updated to the new version and it seems ok so far, but I've only sent about 10 messages through. Sean ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-03 12:02 Message: Logged In: YES user_id=146903 Yet another version. There were some bugs in handling of certain error conditions when talking to spamd. These would result in exceptions and the messages staying in the delivery queue :( With the new version, the message will be passed through unchecked under these conditions, and a message will be added to the error log. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-13 05:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 14:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 14:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-26 09:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From noreply at sourceforge.net Sun Mar 16 23:54:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 17 02:42:04 2003 Subject: [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 16:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration >Group: Mailman 2.1 Status: Open Resolution: None Priority: 1 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2003-03-17 13:46 Message: Logged In: YES user_id=146903 Attached is an updated version of the filter for adding SpamAssassin support to mailman. This version is targetted at Mailman 2.1.x. The code for talking to spamd has been split out into a separate file, so that it can be updated independently of the Mailman specific code. It has also been updated to work with SpamAssassin 2.50 (and should be a lot more robust to future additions to the spamd protocol). The filter has also been changed to use the list name as the username passed to spamd, which means that separate auto-whitelists and bayes databases can be maintained for each list. Installation is trivial. Simply copy spamd.py and SpamAssassin.py to the Mailman/Handlers directory and add the following line to Mailman/mm_cfg.py: GLOBAL_PIPELINE.insert(1, 'SpamAssassin') ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:32 Message: Logged In: YES user_id=81797 That last one had a missing quote. Try this patch: *** SpamAssassin.py.orig Fri Aug 23 00:28:59 2002 --- SpamAssassin.py Fri Aug 23 00:31:00 2002 *************** *** 30,45 **** from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_PORT = 0 ! try: ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! i = string.find(SPAMD_HOST, ':') ! if i >= 0: ! SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] ! try: SPAMD_PORT = int(SPAMD_PORT) ! except: SPAMD_PORT = None ! except: ! SPAMD_HOST = 'localhost' if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE --- 30,44 ---- from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_HOST = 'localhost' ! SPAMD_PORT = None ! if hasattr(mm_cfg, 'SPAMASSASSIN_HOST'): ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! try: ! SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) ! SPAMD_PORT = int(SPAMD_PORT) ! except ValueError: ! SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:19 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:18 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: dann frazier (dannf) Date: 2002-08-18 02:11 Message: Logged In: YES user_id=146718 hey James, found a typo. also wanted to point out: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139942&repeatmerged=yes --- SpamAssassin.py.orig Sat Aug 17 12:05:41 2002 +++ SpamAssassin.py Sat Aug 17 12:06:13 2002 @@ -35,7 +35,7 @@ SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST i = string.find(SPAMD_HOST, ':') if i >= 0: - SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] + SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], SPAMD_HOST[i+1:] try: SPAMD_PORT = int(SPAMD_PORT) except: SPAMD_PORT = None except: ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 17:00 Message: Logged In: YES user_id=146903 remembering to check the "upload file" checkbox this time ... ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 16:59 Message: Logged In: YES user_id=146903 Yet another new version that fixes a small typo. With previous messages, you couldn't approve messages that had been identified as spam once (they would get identified again when the queue got processed, instead of passing the message through). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-10 08:19 Message: Logged In: YES user_id=146903 The Mailman installation on mail.gnome.org also uses this filter. I don't think there are any stability problems with the filter. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-07-10 05:16 Message: Logged In: YES user_id=81797 FYI, I ran the previous version since installation and it seemed to work fine. I didn't run into any problems, with probably 500 messages handled. I've updated to the new version and it seems ok so far, but I've only sent about 10 messages through. Sean ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-03 12:02 Message: Logged In: YES user_id=146903 Yet another version. There were some bugs in handling of certain error conditions when talking to spamd. These would result in exceptions and the messages staying in the delivery queue :( With the new version, the message will be passed through unchecked under these conditions, and a message will be added to the error log. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-13 05:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 14:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 14:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-26 09:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From noreply at sourceforge.net Mon Mar 17 02:51:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 17 05:39:03 2003 Subject: [ mailman-Bugs-704912 ] Invitation bug Message-ID: Bugs item #704912, was opened at 2003-03-17 11:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704912&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Invitation bug Initial Comment: There seems to be a bug in parsing the confirmation of an invitation to join a mailing list. I suspect this has something to do with MIME decoding of the Subject: header. When sending a reply to the autogenerated invitation (in my case, using pine), with this header: Subject: Re: =?iso-8859-1?q?confirm_55ed0163ec2f0a56ac257f708b 470b6a892935f2?= nothing happened. But when sending a reply with this header (which was the case if I used Netscape Mail or Evolution): Subject: Re: confirm 9924a8cb2e31d2f1605ca6228ff210901ff17aba I was subscribed. Maybe Mailman doesn't decode the Subject: before parsing it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704912&group_id=103 From noreply at sourceforge.net Mon Mar 17 09:44:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 17 12:33:49 2003 Subject: [ mailman-Bugs-670535 ] qrunner stops for no apparent reason Message-ID: Bugs item #670535, was opened at 2003-01-18 21:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner stops for no apparent reason Initial Comment: About once every day or so, qrunner will stop for no apparent reason. The qrunner log file has the following ... Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner exiting. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner exiting. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner exiting. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner exiting. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner exiting. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner exiting. Jan 18 14:29:10 2003 (3444) NewsRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:12 2003 (3444) NewsRunner qrunner exiting. No other log has any indication of what might be happening. Is there a way to increase the logging somewhere so the cause can be identified? ---------------------------------------------------------------------- >Comment By: David Gibbs (midrangeman) Date: 2003-03-17 11:44 Message: Logged In: YES user_id=86339 Additional environment details: Redhat Linux 8.0, uname = "Linux xxx.midrange.com 2.4.18- 26.8.0 #1 Mon Feb 24 10:21:42 EST 2003 i686 i686 i386 GNU/Linux" Python: 2.2.1 CPU: P4 2.4ghz, 512mb RAM Dunno if this makes a difference, but I have the following directories ... /usr/lib/python1.5 /usr/lib/python2.1 /usr/lib/python2.2 Any chance there is a conflict? ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-24 12:31 Message: Logged In: YES user_id=86339 I added some debug code to mailmanctl and found out that the sigalarm handler is firing just before the qrunners are terminating. ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-22 15:31 Message: Logged In: YES user_id=86339 After some further research, QRUNNER seems to stop after exactly 24 hours of operation. That is, 24 hours after qrunner starts, it ends as if someone killed it with SIGTERM. I know for a fact that nobody is actually doing this ... and no process on my system should be aware of the fact that qrunner is actually running. I will not discount the possiblity that this is an environmental factor, but it seems to me that a daemon process should not be affected by environmental factors. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-19 16:46 Message: Logged In: YES user_id=12800 I'm not sure what kind of logging would help. Some process somewhere is SIGTERMing the mailmanctl controller process. There's no way to know where a signal is coming from, so I'm not sure what more you could do in mailmanctl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103 From noreply at sourceforge.net Mon Mar 17 14:17:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 17 17:05:31 2003 Subject: [ mailman-Patches-645297 ] Add PGP support Message-ID: Patches item #645297, was opened at 2002-11-28 15:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Ben Laurie (benl) >Assigned to: Thomas Wouters (twouters) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-17 23:17 Message: Logged In: YES user_id=34209 I'll look at incorporating this when I look at the SecureList patch by NAH6 (SF patch #646989, currently.) ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-02-06 06:16 Message: Logged In: YES user_id=106549 My vote goes to a PGP whitelist and blacklist feature. Messages signed with a key present in the whitelist could go skip moderation, messages in the blacklist would be either ignored or rejected, and all other messages could go through moderation. That way, PGP signatures are not required, but those using them would see their messages delivered quickly. Mailman would have two keyrings, and would manage them by specifying --keyring to gpg. PGP keys would be retreived from a PGP key server. When moderating a message that was signed with a key missing from the whitelist, there would be an option named "Add key to whitelist", and an other one for the blacklist. Keys could be added to the white/blacklist through the web interface by specifying at least a key ID, and mailman would ask gpg to fetch the key from mailman's default key server. Initially proposed in French on: http://www.linux-quebec.org/archives/general/msg03787.html Nicolas Marchildon ---------------------------------------------------------------------- Comment By: David Shaw (dmshaw) Date: 2003-01-04 20:59 Message: Logged In: YES user_id=606006 Another vote of support. I actually submitted an enhancement request earlier today for exactly this. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 20:37 Message: Logged In: YES user_id=147905 Adding a vote of support for this patch. Please add it as soon as it's appropriate! I've been waiting a long time for this functionality and I'd hate to see the patch bitrot. :-) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-12 04:56 Message: Logged In: YES user_id=12800 I have to defer this patch until after MM2.1 since we're about ready for the first release candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 From noreply at sourceforge.net Mon Mar 17 17:09:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 17 19:57:08 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Tue Mar 18 11:35:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 18 14:23:38 2003 Subject: [ mailman-Bugs-705794 ] TimeOutError / NotLockedError Message-ID: Bugs item #705794, was opened at 2003-03-18 20:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=705794&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: TimeOutError / NotLockedError Initial Comment: With the newest CVS I have several notes about TimeOutError/NotLockedError in my error-log and mails are shunted. Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 169, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1260, in change_options mlist.InviteNewMember(userdesc, invitation) File "/usr/lib/mailman/Mailman/MailList.py", line 693, in InviteNewMember cookie = Pending.new(Pending.SUBSCRIPTION, userdesc) File "/usr/lib/mailman/Mailman/Pending.py", line 61, in new lock.lock(timeout=30) File "/usr/lib/mailman/Mailman/LockFile.py", line 293, in lock raise TimeOutError TimeOutError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=705794&group_id=103 From noreply at sourceforge.net Tue Mar 18 16:31:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 18 19:18:54 2003 Subject: [ mailman-Bugs-705982 ] cvs-version: header-errors with long listnames Message-ID: Bugs item #705982, was opened at 2003-03-19 01:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=705982&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: cvs-version: header-errors with long listnames Initial Comment: since updating to the cvs-version, a blank line is inserted into the headers of lists with long listnames. the effect is that the header-lines after the empty line are shown in the mailclient. It seems to correspondate with the length of the listname and indirect with the line-length in the header. the lists worked correctly before updating. any ideas? Example: (you see 2 blank lines after the long lines and comma) From: "Jan Kellermann" To: Date: Tue, 18 Mar 2003 20:07:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailman-Approved-At: Tue, 18 Mar 2003 19:52:42 +0100 Subject: [Ein-ganz-langer-listen-name-zum-testen] test X-BeenThere: ein-ganz-langer-listen-name-zum- testen@werk21server.de X-Mailman-Version: 2.1.1+ Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ein-ganz-langer-listen-name-zum-testen- bounces+kelly=werk21.de@werk21server.de Errors-To: ein-ganz-langer-listen-name-zum-testen- bounces+kelly=werk21.de@werk21server.de ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=705982&group_id=103 From noreply at sourceforge.net Thu Mar 20 06:10:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 20 08:58:28 2003 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 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: 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 Fri Mar 21 08:37:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 11:24:44 2003 Subject: [ mailman-Bugs-707604 ] remove_members doesn't use default setting Message-ID: Bugs item #707604, was opened at 2003-03-21 16:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707604&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: remove_members doesn't use default setting Initial Comment: bin/remove_members turns on "userack" by default... even though it's supposed to use the list config setting whether or not it should send a message to the unsubscribers (line 111 in remove_members says "userack = 1"). is this a bug or has this been done intentionally? the danger is that even if you have "nouserack" set in your system, using "remove_members -a" will always mail all unsubscribers unless you specifically tell it not to through the command line... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707604&group_id=103 From noreply at sourceforge.net Fri Mar 21 08:50:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 11:37:31 2003 Subject: [ mailman-Bugs-707608 ] cvs-version: error in qrunner Message-ID: Bugs item #707608, was opened at 2003-03-21 17:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707608&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: cvs-version: error in qrunner Initial Comment: mailman writes the errormessages *directly to console* and in the error-log. Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e Mar 21 16:15:49 2003 qrunner(12304): Traceback (most recent call last): Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? Mar 21 16:15:49 2003 qrunner(12304): main() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main Mar 21 16:15:49 2003 qrunner(12304): qrunner.run() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 59, in run Mar 21 16:15:49 2003 qrunner(12304): filecnt = self._oneloop() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 88, in _oneloop Mar 21 16:15:49 2003 qrunner(12304): msg, msgdata = self._switchboard.dequeue(filebase) Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue Mar 21 16:15:49 2003 qrunner(12304): if data.has_key ('rejection-notice'): Mar 21 16:15:49 2003 qrunner(12304): AttributeError : 'NoneType' object has no attribute 'has_key' Mar 21 16:54:24 2003 qrunner(12191): Traceback (most recent call last): Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? Mar 21 16:54:24 2003 qrunner(12191): main() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main Mar 21 16:54:24 2003 qrunner(12191): qrunner.run() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 59, in run Mar 21 16:54:24 2003 qrunner(12191): filecnt = self._oneloop() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 88, in _oneloop Mar 21 16:54:24 2003 qrunner(12191): msg, msgdata = self._switchboard.dequeue(filebase) Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue Mar 21 16:54:24 2003 qrunner(12191): if data.has_key ('rejection-notice'): Mar 21 16:54:24 2003 qrunner(12191): AttributeError : 'NoneType' object has no attribute 'has_key' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707608&group_id=103 From noreply at sourceforge.net Fri Mar 21 08:55:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 11:41:49 2003 Subject: [ mailman-Bugs-707610 ] Uncaught runner exception: Empty module name Message-ID: Bugs item #707610, was opened at 2003-03-21 17:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: Empty module name Initial Comment: mailman is shunting a lot of mails with this message in error-log, my language-version is german. i work with the current cvs-version Mar 21 16:11:21 2003 (12591) Uncaught runner exception: Empty module name Mar 21 16:11:21 2003 (12591) Traceback (most recent call last): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_id=103 From noreply at sourceforge.net Fri Mar 21 08:56:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 11:43:17 2003 Subject: [ mailman-Bugs-707612 ] traceback in senddigests Message-ID: Bugs item #707612, was opened at 2003-03-21 17:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707612&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: traceback in senddigests Initial Comment: my senddigests (cron) aborts with this message. my language-version is german, i am working with the cvs- version. Traceback (most recent call last): File "/usr/local/mailman-2.1//cron/senddigests", line 94, in ? main() File "/usr/local/mailman-2.1//cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman-2.1//Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707612&group_id=103 From noreply at sourceforge.net Fri Mar 21 09:03:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 11:51:02 2003 Subject: [ mailman-Bugs-707608 ] cvs-version: error in qrunner Message-ID: Bugs item #707608, was opened at 2003-03-21 11:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707608&group_id=103 Category: None >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: cvs-version: error in qrunner Initial Comment: mailman writes the errormessages *directly to console* and in the error-log. Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e Mar 21 16:15:49 2003 qrunner(12304): Traceback (most recent call last): Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? Mar 21 16:15:49 2003 qrunner(12304): main() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main Mar 21 16:15:49 2003 qrunner(12304): qrunner.run() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 59, in run Mar 21 16:15:49 2003 qrunner(12304): filecnt = self._oneloop() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 88, in _oneloop Mar 21 16:15:49 2003 qrunner(12304): msg, msgdata = self._switchboard.dequeue(filebase) Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue Mar 21 16:15:49 2003 qrunner(12304): if data.has_key ('rejection-notice'): Mar 21 16:15:49 2003 qrunner(12304): AttributeError : 'NoneType' object has no attribute 'has_key' Mar 21 16:54:24 2003 qrunner(12191): Traceback (most recent call last): Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? Mar 21 16:54:24 2003 qrunner(12191): main() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main Mar 21 16:54:24 2003 qrunner(12191): qrunner.run() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 59, in run Mar 21 16:54:24 2003 qrunner(12191): filecnt = self._oneloop() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 88, in _oneloop Mar 21 16:54:24 2003 qrunner(12191): msg, msgdata = self._switchboard.dequeue(filebase) Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue Mar 21 16:54:24 2003 qrunner(12191): if data.has_key ('rejection-notice'): Mar 21 16:54:24 2003 qrunner(12191): AttributeError : 'NoneType' object has no attribute 'has_key' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707608&group_id=103 From noreply at sourceforge.net Fri Mar 21 09:05:26 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 11:52:30 2003 Subject: [ mailman-Bugs-707612 ] traceback in senddigests Message-ID: Bugs item #707612, was opened at 2003-03-21 11:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707612&group_id=103 Category: None >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: traceback in senddigests Initial Comment: my senddigests (cron) aborts with this message. my language-version is german, i am working with the cvs- version. Traceback (most recent call last): File "/usr/local/mailman-2.1//cron/senddigests", line 94, in ? main() File "/usr/local/mailman-2.1//cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman-2.1//Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707612&group_id=103 From noreply at sourceforge.net Fri Mar 21 09:26:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 12:13:35 2003 Subject: [ mailman-Patches-707624 ] SMTPDirect doesn't use persistent SMTP connections Message-ID: Patches item #707624, was opened at 2003-03-21 18:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=707624&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jesús Cea Avión (jcea) Assigned to: Nobody/Anonymous (nobody) Summary: SMTPDirect doesn't use persistent SMTP connections Initial Comment: Mailman 2.1.1 here. "/Mailman/Handlers/SMTPDirect.py" is suppose to reuse SMTP connections up to "mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION" different messages. Nevertheless, it's NOT the case: "SMTPDirect" drop the connection when send each message. This is an important CPU hog when mailman has a long queue spool. Here is the patch (sorry, I can't send it as an attach, shame on me). It's fairly trivial : >>>>> Index: SMTPDirect.py =================================================================== RCS file: /opt/src/cvsroot/mailman/Mailman/Handlers/SMTPDirect.py,v retrieving revision 1.1.1.5 retrieving revision 1.1.1.5.2.1 diff -u -u -r1.1.1.5 -r1.1.1.5.2.1 --- SMTPDirect.py 2003/03/20 10:14:58 1.1.1.5 +++ SMTPDirect.py 2003/03/21 16:48:31 1.1.1.5.2.1 @@ -48,7 +48,7 @@ # Manage a connection to the SMTP server -class Connection: +class ConnectionClass: def __init__(self): self.__connect() @@ -79,7 +79,15 @@ def quit(self): self.__conn.quit() + def rset(self) : + self.__conn.rset() + def __del__(self) : + self.quit() + + +Connection=ConnectionClass() + def process(mlist, msg, msgdata): recips = msgdata.get('recips') @@ -130,7 +138,7 @@ # This means at worst, the last chunk for which delivery was attempted # could get duplicates but not every one, and no recips should miss the # message. - conn = Connection() + conn = Connection try: msgdata['undelivered'] = chunks while chunks: @@ -147,7 +155,8 @@ raise del msgdata['undelivered'] finally: - conn.quit() + conn.rset() + # conn.quit() msgdata['recips'] = origrecips # Log the successful post t1 = time.time() <<<<< ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=707624&group_id=103 From noreply at sourceforge.net Fri Mar 21 09:54:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 12:43:13 2003 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 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: 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 Fri Mar 21 10:29:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 13:17:50 2003 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 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: 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 Fri Mar 21 16:36:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 19:23:43 2003 Subject: [ mailman-Bugs-678626 ] "error: incorrect padding" Message-ID: Bugs item #678626, was opened at 2003-02-01 12:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) >Summary: "error: incorrect padding" Initial Comment: Just ran the cvs update, and have started getting messages that otherwise look normal kicking this message out and shunting. Attached the errorlog. ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-22 01:36 Message: Logged In: YES user_id=34209 This has been fixed in a recent CVS checkin, and will be backported to Mailman 2.1.2. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-01 13:24 Message: Logged In: YES user_id=67709 Are you not using an external demime/stripmime? This kind of message is generated when an attatchment is base64 encoded but somehow corruped. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_id=103 From noreply at sourceforge.net Fri Mar 21 16:45:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 19:32:45 2003 Subject: [ mailman-Bugs-671984 ] move_list script - Syntax Errors Message-ID: Bugs item #671984, was opened at 2003-01-21 20:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671984&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Mark (backquack) Assigned to: Nobody/Anonymous (nobody) Summary: move_list script - Syntax Errors Initial Comment: Initial execution of the move_list script resulted in serveral regarding korean encodings... Traceback (innermost last): File "./move_list", line 42, in ? import paths File "./paths.py", line 60, in ? import korean.aliases File "/home/mailman/pythonlib/korean/aliases.py", line 23, in ? import encodings.aliases After editing paths.py and commenting out korean.aliases and executing move_list -h I get the following..... ./move_list -h Traceback (innermost last): File "./move_list", line 44, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 686 text += Utils.maketext( ^ SyntaxError: invalid syntax ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-22 01:45 Message: Logged In: YES user_id=34209 'move_list' was removed in Mailman 2.1 (somewhere before Mailman 2.1a2 in fact), so you shouldn't have it, let alone use it. The error you're getting suggests you are using an ancient version of Python: it chokes on the use of augmented assignment, which was added in Python 2.0. Mailman 2.1 requires Python 2.1 or higher. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671984&group_id=103 From noreply at sourceforge.net Fri Mar 21 16:54:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 21 19:41:02 2003 Subject: [ mailman-Bugs-670535 ] qrunner stops for no apparent reason Message-ID: Bugs item #670535, was opened at 2003-01-19 04:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner stops for no apparent reason Initial Comment: About once every day or so, qrunner will stop for no apparent reason. The qrunner log file has the following ... Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner exiting. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner exiting. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner exiting. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner exiting. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner exiting. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner exiting. Jan 18 14:29:10 2003 (3444) NewsRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:12 2003 (3444) NewsRunner qrunner exiting. No other log has any indication of what might be happening. Is there a way to increase the logging somewhere so the cause can be identified? ---------------------------------------------------------------------- >Comment By: Thomas Wouters (twouters) Date: 2003-03-22 01:54 Message: Logged In: YES user_id=34209 No, having multiple versions of Python should not be causing this. Nor should the SIGALRM handler being triggered cause it, unless something is seriously broken in your setup -- but we've already been there. The only way to see if a SIGTERM is actually being delivered is running the processes under strace or gdb, but this seriously disrupts regular operation. There is no way that i know of to find out where a signal is coming from, once you find out that it really is a signal. If it *isn't* a real signal, I would start looking at libc bugs and other platform bugs. You can try upgrading Python to 2.2.2 (the latest bugfix release) but I would be very suprised if it fixed your problem. RedHat does not have a great reputation for stability, so be sure to check for any RedHat updates. ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-03-17 18:44 Message: Logged In: YES user_id=86339 Additional environment details: Redhat Linux 8.0, uname = "Linux xxx.midrange.com 2.4.18- 26.8.0 #1 Mon Feb 24 10:21:42 EST 2003 i686 i686 i386 GNU/Linux" Python: 2.2.1 CPU: P4 2.4ghz, 512mb RAM Dunno if this makes a difference, but I have the following directories ... /usr/lib/python1.5 /usr/lib/python2.1 /usr/lib/python2.2 Any chance there is a conflict? ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-24 19:31 Message: Logged In: YES user_id=86339 I added some debug code to mailmanctl and found out that the sigalarm handler is firing just before the qrunners are terminating. ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-22 22:31 Message: Logged In: YES user_id=86339 After some further research, QRUNNER seems to stop after exactly 24 hours of operation. That is, 24 hours after qrunner starts, it ends as if someone killed it with SIGTERM. I know for a fact that nobody is actually doing this ... and no process on my system should be aware of the fact that qrunner is actually running. I will not discount the possiblity that this is an environmental factor, but it seems to me that a daemon process should not be affected by environmental factors. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-19 23:46 Message: Logged In: YES user_id=12800 I'm not sure what kind of logging would help. Some process somewhere is SIGTERMing the mailmanctl controller process. There's no way to know where a signal is coming from, so I'm not sure what more you could do in mailmanctl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103 From noreply at sourceforge.net Fri Mar 21 21:59:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 22 00:47:25 2003 Subject: [ mailman-Bugs-700140 ] obsolete version number in TODO Message-ID: Bugs item #700140, was opened at 2003-03-08 15:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 Category: documentation Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: obsolete version number in TODO Initial Comment: Got email-2.4.3.tar.gz from the latest cvs. It includes a TODO file, with the following notation: - We should support RFC 2231. Oleg Broytmann has patches to add this support, so we'll look into it for email-1.3. Since this is email-2.4, I presume either its been done or the version number needs to change. This is a low-priority item. I figured I mention it, since I saw it. ---------------------------------------------------------------------- >Comment By: Ross Boylan (rboylan) Date: 2003-03-21 21:59 Message: Logged In: YES user_id=300987 I just did a cvs update and looked at email-2.5b1 in there. The TODO still refers to email-1.3. (21-Mar-2003). Out of curiosity, where do python and mimelilb bugs go? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-12 21:21 Message: Logged In: YES user_id=12800 Bugs and patches on the email package probably belong better on the Python or mimelib projects. But in any event, I've updated the TODO list. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 From noreply at sourceforge.net Fri Mar 21 22:08:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 22 00:55:55 2003 Subject: [ mailman-Bugs-700140 ] obsolete version number in TODO Message-ID: Bugs item #700140, was opened at 2003-03-08 18:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 Category: documentation Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: obsolete version number in TODO Initial Comment: Got email-2.4.3.tar.gz from the latest cvs. It includes a TODO file, with the following notation: - We should support RFC 2231. Oleg Broytmann has patches to add this support, so we'll look into it for email-1.3. Since this is email-2.4, I presume either its been done or the version number needs to change. This is a low-priority item. I figured I mention it, since I saw it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-22 01:08 Message: Logged In: YES user_id=12800 I'll bet you're looking at the maintenance branch. I still have to backport the trunk changes to the maint branch. Python bugs should go in the Python project trackers. mimelib bugs should probably go there too, or in the standalone mimelib project. If you submit email package bug reports in the Python project, be sure to assign them to me. ---------------------------------------------------------------------- Comment By: Ross Boylan (rboylan) Date: 2003-03-22 00:59 Message: Logged In: YES user_id=300987 I just did a cvs update and looked at email-2.5b1 in there. The TODO still refers to email-1.3. (21-Mar-2003). Out of curiosity, where do python and mimelilb bugs go? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-13 00:21 Message: Logged In: YES user_id=12800 Bugs and patches on the email package probably belong better on the Python or mimelib projects. But in any event, I've updated the TODO list. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=700140&group_id=103 From noreply at sourceforge.net Sat Mar 22 08:02:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Mar 22 10:49:21 2003 Subject: [ mailman-Bugs-707604 ] remove_members doesn't use default setting Message-ID: Bugs item #707604, was opened at 2003-03-21 11:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707604&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: remove_members doesn't use default setting Initial Comment: bin/remove_members turns on "userack" by default... even though it's supposed to use the list config setting whether or not it should send a message to the unsubscribers (line 111 in remove_members says "userack = 1"). is this a bug or has this been done intentionally? the danger is that even if you have "nouserack" set in your system, using "remove_members -a" will always mail all unsubscribers unless you specifically tell it not to through the command line... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707604&group_id=103 From noreply at sourceforge.net Sun Mar 23 23:33:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 24 02:20:22 2003 Subject: [ mailman-Patches-707624 ] SMTPDirect doesn't use persistent SMTP connections Message-ID: Patches item #707624, was opened at 2003-03-21 18:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=707624&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jesús Cea Avión (jcea) Assigned to: Nobody/Anonymous (nobody) Summary: SMTPDirect doesn't use persistent SMTP connections Initial Comment: Mailman 2.1.1 here. "/Mailman/Handlers/SMTPDirect.py" is suppose to reuse SMTP connections up to "mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION" different messages. Nevertheless, it's NOT the case: "SMTPDirect" drop the connection when send each message. This is an important CPU hog when mailman has a long queue spool. Here is the patch (sorry, I can't send it as an attach, shame on me). It's fairly trivial : >>>>> Index: SMTPDirect.py =================================================================== RCS file: /opt/src/cvsroot/mailman/Mailman/Handlers/SMTPDirect.py,v retrieving revision 1.1.1.5 retrieving revision 1.1.1.5.2.1 diff -u -u -r1.1.1.5 -r1.1.1.5.2.1 --- SMTPDirect.py 2003/03/20 10:14:58 1.1.1.5 +++ SMTPDirect.py 2003/03/21 16:48:31 1.1.1.5.2.1 @@ -48,7 +48,7 @@ # Manage a connection to the SMTP server -class Connection: +class ConnectionClass: def __init__(self): self.__connect() @@ -79,7 +79,15 @@ def quit(self): self.__conn.quit() + def rset(self) : + self.__conn.rset() + def __del__(self) : + self.quit() + + +Connection=ConnectionClass() + def process(mlist, msg, msgdata): recips = msgdata.get('recips') @@ -130,7 +138,7 @@ # This means at worst, the last chunk for which delivery was attempted # could get duplicates but not every one, and no recips should miss the # message. - conn = Connection() + conn = Connection try: msgdata['undelivered'] = chunks while chunks: @@ -147,7 +155,8 @@ raise del msgdata['undelivered'] finally: - conn.quit() + conn.rset() + # conn.quit() msgdata['recips'] = origrecips # Log the successful post t1 = time.time() <<<<< ---------------------------------------------------------------------- >Comment By: Jesús Cea Avión (jcea) Date: 2003-03-24 08:33 Message: Logged In: YES user_id=97460 The proposed patch causes exceptions if space between messages is greater than SMTP timeout. Corrected patch (I still can't attach a file): >>>>> Index: SMTPDirect.py =================================================================== RCS file: /opt/src/cvsroot/mailman/Mailman/Handlers/SMTPDirect.py,v retrieving revision 1.1.1.5 retrieving revision 1.1.1.5.2.3 diff -u -r1.1.1.5 -r1.1.1.5.2.3 --- SMTPDirect.py 2003/03/20 10:14:58 1.1.1.5 +++ SMTPDirect.py 2003/03/24 07:11:32 1.1.1.5.2.3 @@ -48,7 +48,7 @@ # Manage a connection to the SMTP server -class Connection: +class ConnectionClass: def __init__(self): self.__connect() @@ -58,6 +58,15 @@ self.__numsessions = mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION def sendmail(self, envsender, recips, msgtext): + try : + self.__conn.rset() + except : + try : + self.__conn.quit() + except : + pass + self.__connect() + try: results = self.__conn.sendmail(envsender, recips, msgtext) except smtplib.SMTPException: @@ -79,6 +88,11 @@ def quit(self): self.__conn.quit() + def __del__(self) : + self.quit() + + +Connection=ConnectionClass() def process(mlist, msg, msgdata): @@ -130,7 +144,7 @@ # This means at worst, the last chunk for which delivery was attempted # could get duplicates but not every one, and no recips should miss the # message. - conn = Connection() + conn = Connection try: msgdata['undelivered'] = chunks while chunks: @@ -147,7 +161,7 @@ raise del msgdata['undelivered'] finally: - conn.quit() + # conn.quit() msgdata['recips'] = origrecips # Log the successful post t1 = time.time() <<<<< ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=707624&group_id=103 From noreply at sourceforge.net Wed Mar 26 13:49:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 26 16:36:16 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 21:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Thu Mar 27 04:05:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 27 06:51:41 2003 Subject: [ mailman-Bugs-710678 ] find_member fails using -w option Message-ID: Bugs item #710678, was opened at 2003-03-27 12:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=710678&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: find_member fails using -w option Initial Comment: When run with the -w option $prefix/bin/find_member Traceback (most recent call last): File "../../bin/find_member", line 185, in ? main() File "../../bin/find_member", line 168, in main matches = scanlists(options) File "../../bin/find_member", line 115, in scanlists entries = matches.get(addr, {}) UnboundLocalError: local variable 'addr' referenced before assignment The findm-2.1.1-0.1.patch corrects the problem. It should be applied with the follwoing command from with the MM build directory as the current working directory: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=710678&group_id=103 From noreply at sourceforge.net Thu Mar 27 04:23:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 27 07:11:23 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 14:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Fri Mar 28 11:59:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 28 14:44:30 2003 Subject: [ mailman-Feature Requests-402455 ] Generate .htaccess files containing username/passwd for list Message-ID: Feature Requests item #402455, was opened at 2000-11-20 10:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=402455&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Generate .htaccess files containing username/passwd for list Initial Comment: ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-03-28 11:59 Message: Logged In: NO Try http://sourceforge.net/tracker/index.php? func=detail&aid=670142&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 06:06 Message: Logged In: YES user_id=34209 This patch is out of date, but it shouldn't be hard to write something similar for Mailman 2.1. Moving to feature requests for now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=402455&group_id=103 From noreply at sourceforge.net Fri Mar 28 12:56:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 28 15:42:19 2003 Subject: [ mailman-Bugs-711564 ] make install fails, something with bin/update Message-ID: Bugs item #711564, was opened at 2003-03-28 13:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=711564&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: ryan pratt (rhpratt) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails, something with bin/update Initial Comment: I am running mailman 2.1.1, python 2.2.2, gcc 2.95.3 on Solaris 9. I've also tried it on Solaris 8. python seems to be working. import random returns fine. ... ... Compiling /opt/mailman/Mailman/Utils.py ... Compiling /opt/mailman/Mailman/Version.py ... Compiling /opt/mailman/Mailman/__init__.py ... Compiling /opt/mailman/Mailman/htmlformat.py ... Compiling /opt/mailman/Mailman/i18n.py ... Compiling /opt/mailman/Mailman/versions.py ... bin/update: downgrade is detected), nothing will be done.^J^J -h/--help^J Print this text and exit.^J^JUse this script to help you update to the latest release of Mailman from^Jsome previous version. It knows about versions back to 1.0b4 (?).^J""": not found bin/update: Perform all necessary upgrades.^J^JUsage: %(PROGRAM)s [options]^J^JOptions:^J -f/--force^J Force running the upgrade procedures. Normally, if the version number^J of the installed Mailman matches the current version number (or a^J : not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: FRESH: not found bin/update: NOTFRESH: not found bin/update: syntax error at line 58: `(' unexpected *** Error code 2 make: Fatal error: Command failed for target `update' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=711564&group_id=103