From noreply at sourceforge.net Sat Feb 1 03:41:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 1 06:36:29 2003 Subject: [ mailman-Bugs-678626 ] "error: incorrect padding" Message-ID: Bugs item #678626, was opened at 2003-02-01 11: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: Open Resolution: None 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_id=103 From noreply at sourceforge.net Sat Feb 1 03:53:26 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 1 06:48:09 2003 Subject: [ mailman-Bugs-678626 ] "error: incorrect padding" Message-ID: Bugs item #678626, was opened at 2003-02-01 11: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: Open Resolution: None 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678626&group_id=103 From noreply at sourceforge.net Sat Feb 1 04:24:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 1 07:19:25 2003 Subject: [ mailman-Bugs-678626 ] "error: incorrect padding" Message-ID: Bugs item #678626, was opened at 2003-02-01 11: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: Open Resolution: None 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: Tokio Kikuchi (tkikuchi) Date: 2003-02-01 12: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 Sat Feb 1 06:13:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 1 09:07:57 2003 Subject: [ mailman-Bugs-678672 ] no list identification in cron error mail Message-ID: Bugs item #678672, was opened at 2003-02-01 14:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678672&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: no list identification in cron error mail Initial Comment: in the message below from the checkdbs cron job, there is no identification of the list with the erroneous `tuple'. it sure would be nice if there was. i ended up adding a print statement to checkdbs to find out what it was -- perhaps this could become a -v option to checkdbs. Finally, it sure would be nice if mailman just dealt with this problem instead of aborting. Thanks to help from mailman-users, I can get past it now by removing any relevant heldmsg's and removing request.db. Seems like this does not take a human to do. The error has happened with every mailman migration I've been involved in. Thanks, karl *** checkdbs Fri Jan 31 14:30:50 2003 --- checkdbs.v Fri Jan 31 14:45:50 2003 *************** *** 54,55 **** --- 54,56 ---- # the list must be locked in order to open the requests database + sys.stdout.write (name + '\n') mlist = MailList.MailList(name) Here's the mail. >From mailman@tug.org Sat Feb 1 02:00:04 2003 Return-Path: Received: from tug.org (tug.org [130.225.2.178]) by f7.net (8.11.6/8.11.6) with ESMTP id h11703p21212 for ; Sat, 1 Feb 2003 02:00:04 -0500 Received: (from mailman@localhost) by tug.org (8.11.6/8.11.6) id h11702s25380 for mailman; Sat, 1 Feb 2003 08:00:02 +0100 Message-Id: <200302010700.h11702s25380@tug.org> X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: Date: Sat, 1 Feb 2003 08:00:02 +0100 From: root@tug.org (Cron Daemon) To: mailman@tug.org Subject: Cron /usr/local/bin/python -S /usr/local/mailman/cron/checkdbs Traceback (most recent call last): File "/usr/local/mailman/cron/checkdbs", line 136, in ? main() File "/usr/local/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/usr/local/mailman/cron/checkdbs", line 102, in pending_requests when, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) ValueError: unpack tuple of wrong size ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=678672&group_id=103 From noreply at sourceforge.net Sun Feb 2 14:47:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 2 17:42:03 2003 Subject: [ mailman-Feature Requests-679234 ] Nested Lists(Segments) enhanced support Message-ID: Feature Requests item #679234, was opened at 2003-02-03 00:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679234&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rosstyk Ivantsiv (lumik) Assigned to: Nobody/Anonymous (nobody) Summary: Nested Lists(Segments) enhanced support Initial Comment: Imagine a simple situation: I run the tourism-related mailing list, which I use to send various proposals to other companies providing touristic services and located in different cities. I want to group all subscribers into groups(segments) depending, for example, on their geographic location. I consider some postings not to be interesting (even abusing) for some groups of subscribers, so I set the WHOLE group not to receive mail with a single operation and than send my posting to the list. Sure, this can be realized in current version of mailman by creating nested lists but it looks not to be the best choice. I advise you to realize some little segment support in mailman (probably based on a subscriber description). Here is the quote from Lyris documentation: "Let's say you'd like to send a special message to only those list members who - joined your list a week ago - live in France - are celebrating their birthday today - have made a major purchase in the last year - have an email address at a particular domain (e.g., aol.com or hotmail.com) ListManager allows you to send to a segment, or subset, of your list who meet the criteria you define. Instead of sending to your entire list, you can use segments to filter exactly who should get a message based on whatever criteria you choose. " Lyris(www.lyris.com) ListManager is a list manager with lots of features but it really sucks: -stupid unconvenient web-interface(pages reload many times to perform a simple operation) -it's not absolutely free(for example, to support segments I have to pay) -no internationalization!!! That's why I've chosen Mailman :) If you include some segment support in your next release, mailman will be 100%convenience system for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679234&group_id=103 From noreply at sourceforge.net Sun Feb 2 18:39:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 2 21:34:24 2003 Subject: [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 00: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: Jon Parise (jparise) Date: 2003-02-02 21: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 02: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 11: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: 2002-12-31 19: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 11: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 Mon Feb 3 11:39:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 14:33:40 2003 Subject: [ mailman-Feature Requests-679743 ] mail-to and reply-to links for archive view Message-ID: Feature Requests item #679743, was opened at 2003-02-03 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) Summary: mail-to and reply-to links for archive view Initial Comment: I believe it would be very, very desirable to have mail-to and reply-to links in the mailing list archives section. I do not subscribe (to Zope mailing lists which are reported run on mailman) but do browse and, on occasion, am inspired enough to post. It would be a great convenience to have a mail-to (new thread) and reply-to (reply to currently displayed post) links to ease the process. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_id=103 From noreply at sourceforge.net Mon Feb 3 11:49:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 14:43:26 2003 Subject: [ mailman-Feature Requests-679751 ] Stationary "Next message:" link/buttons Message-ID: Feature Requests item #679751, was opened at 2003-02-03 19:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679751&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) Summary: Stationary "Next message:" link/buttons Initial Comment: It would be desirable for browsing if the "Next message:" link was stationary (so that the mouse could stay stationary instead of having to track it from message to message). It already does stay stationary under most circumstances (so that's good). It would be nice for it to be perfect. The two situations which cause problems are: 1. beginning of messages (when there is no previous message), so next message migrates up a line. This could be avoided by leaving a blank line or inactive link for "Previous message:" for that circumstance. 2. The message title grows to more than one line (or shrinks from more than one line). In these cases, all the buttons bounce down (or up) as the case may be. This issue could be alleviated by putting the button-links above the title. I'm not sure about aesthetics, but I'd certainly find it more functional (and would take function over form, if choosing). On second thought, putting navigation above the title also has a cost of making it scroll offview when slightly scrolling down the page (to continue reading) which would be a downgrade. Instead, how about leaving the basic format as is, but preceding the navigation link/buttons (e.g., "Next message:") with additional almost-redundant stationary buttons which do *not* get pushed down by wrapped titles? If the buttons had mnemonic graphics (e.g., forward arrow, back arrow, etc.), they'd be self-explanatory and most of the time adjacent to their textual counterparts. Other times, they'd be stationary for a convenient stationary browsing interface. Under wrap conditions, the wrapped portion of the title would continue to the right of the stationary buttons, so the buttons always appear in the same locations for every message. Other than these minor tweaks, I'd say the interface is very pleasant to use. The mail-to/reply-to would be a godsend (increased participation and all that), and the navigation tweaks a significant upgrade. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679751&group_id=103 From noreply at sourceforge.net Mon Feb 3 11:54:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 14:48:52 2003 Subject: [ mailman-Feature Requests-679743 ] mail-to and reply-to links for archive view Message-ID: Feature Requests item #679743, was opened at 2003-02-03 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_id=103 Category: None Group: None >Status: Deleted Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) Summary: mail-to and reply-to links for archive view Initial Comment: I believe it would be very, very desirable to have mail-to and reply-to links in the mailing list archives section. I do not subscribe (to Zope mailing lists which are reported run on mailman) but do browse and, on occasion, am inspired enough to post. It would be a great convenience to have a mail-to (new thread) and reply-to (reply to currently displayed post) links to ease the process. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_id=103 From noreply at sourceforge.net Mon Feb 3 11:54:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 14:49:18 2003 Subject: [ mailman-Feature Requests-679751 ] Stationary "Next message:" link/buttons Message-ID: Feature Requests item #679751, was opened at 2003-02-03 19:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679751&group_id=103 Category: None Group: None >Status: Deleted Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) >Summary: Stationary "Next message:" link/buttons Initial Comment: It would be desirable for browsing if the "Next message:" link was stationary (so that the mouse could stay stationary instead of having to track it from message to message). It already does stay stationary under most circumstances (so that's good). It would be nice for it to be perfect. The two situations which cause problems are: 1. beginning of messages (when there is no previous message), so next message migrates up a line. This could be avoided by leaving a blank line or inactive link for "Previous message:" for that circumstance. 2. The message title grows to more than one line (or shrinks from more than one line). In these cases, all the buttons bounce down (or up) as the case may be. This issue could be alleviated by putting the button-links above the title. I'm not sure about aesthetics, but I'd certainly find it more functional (and would take function over form, if choosing). On second thought, putting navigation above the title also has a cost of making it scroll offview when slightly scrolling down the page (to continue reading) which would be a downgrade. Instead, how about leaving the basic format as is, but preceding the navigation link/buttons (e.g., "Next message:") with additional almost-redundant stationary buttons which do *not* get pushed down by wrapped titles? If the buttons had mnemonic graphics (e.g., forward arrow, back arrow, etc.), they'd be self-explanatory and most of the time adjacent to their textual counterparts. Other times, they'd be stationary for a convenient stationary browsing interface. Under wrap conditions, the wrapped portion of the title would continue to the right of the stationary buttons, so the buttons always appear in the same locations for every message. Other than these minor tweaks, I'd say the interface is very pleasant to use. The mail-to/reply-to would be a godsend (increased participation and all that), and the navigation tweaks a significant upgrade. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679751&group_id=103 From noreply at sourceforge.net Mon Feb 3 12:00:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 14:55:21 2003 Subject: [ mailman-Feature Requests-679743 ] mail-to and reply-to links for archive view Message-ID: Feature Requests item #679743, was opened at 2003-02-03 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_id=103 Category: None Group: None >Status: Open Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) Summary: mail-to and reply-to links for archive view Initial Comment: I believe it would be very, very desirable to have mail-to and reply-to links in the mailing list archives section. I do not subscribe (to Zope mailing lists which are reported run on mailman) but do browse and, on occasion, am inspired enough to post. It would be a great convenience to have a mail-to (new thread) and reply-to (reply to currently displayed post) links to ease the process. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679743&group_id=103 From noreply at sourceforge.net Mon Feb 3 12:01:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 14:55:39 2003 Subject: [ mailman-Feature Requests-679751 ] Stationary "Next message:" link/buttons Message-ID: Feature Requests item #679751, was opened at 2003-02-03 19:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679751&group_id=103 Category: None Group: None >Status: Open Resolution: None Priority: 5 Submitted By: Joe Grace (occam) Assigned to: Nobody/Anonymous (nobody) >Summary: Stationary "Next message:" link/buttons Initial Comment: It would be desirable for browsing if the "Next message:" link was stationary (so that the mouse could stay stationary instead of having to track it from message to message). It already does stay stationary under most circumstances (so that's good). It would be nice for it to be perfect. The two situations which cause problems are: 1. beginning of messages (when there is no previous message), so next message migrates up a line. This could be avoided by leaving a blank line or inactive link for "Previous message:" for that circumstance. 2. The message title grows to more than one line (or shrinks from more than one line). In these cases, all the buttons bounce down (or up) as the case may be. This issue could be alleviated by putting the button-links above the title. I'm not sure about aesthetics, but I'd certainly find it more functional (and would take function over form, if choosing). On second thought, putting navigation above the title also has a cost of making it scroll offview when slightly scrolling down the page (to continue reading) which would be a downgrade. Instead, how about leaving the basic format as is, but preceding the navigation link/buttons (e.g., "Next message:") with additional almost-redundant stationary buttons which do *not* get pushed down by wrapped titles? If the buttons had mnemonic graphics (e.g., forward arrow, back arrow, etc.), they'd be self-explanatory and most of the time adjacent to their textual counterparts. Other times, they'd be stationary for a convenient stationary browsing interface. Under wrap conditions, the wrapped portion of the title would continue to the right of the stationary buttons, so the buttons always appear in the same locations for every message. Other than these minor tweaks, I'd say the interface is very pleasant to use. The mail-to/reply-to would be a godsend (increased participation and all that), and the navigation tweaks a significant upgrade. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679751&group_id=103 From noreply at sourceforge.net Mon Feb 3 14:43:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 17:37:32 2003 Subject: [ mailman-Bugs-679869 ] No admin interface for pipermail archives Message-ID: Bugs item #679869, was opened at 2003-02-04 09:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=679869&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tim Potter (tpot) Assigned to: Nobody/Anonymous (nobody) Summary: No admin interface for pipermail archives Initial Comment: It would be very handy to have an administrative interface to the pipermail archives. This would be useful mainly for weeding out spam without having to edit the mbox file and regenerate the archives. I've also been asked to remove sensitive information from archived messages which would be something else useful to be able to do via the web. Removing individual messages would have to be careful to maintain the old URLs to avoid breaking external links to individual messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=679869&group_id=103 From noreply at sourceforge.net Mon Feb 3 14:54:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 17:48:44 2003 Subject: [ mailman-Feature Requests-679869 ] No admin interface for pipermail archives Message-ID: Feature Requests item #679869, was opened at 2003-02-03 17:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679869&group_id=103 >Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tim Potter (tpot) Assigned to: Nobody/Anonymous (nobody) Summary: No admin interface for pipermail archives Initial Comment: It would be very handy to have an administrative interface to the pipermail archives. This would be useful mainly for weeding out spam without having to edit the mbox file and regenerate the archives. I've also been asked to remove sensitive information from archived messages which would be something else useful to be able to do via the web. Removing individual messages would have to be careful to maintain the old URLs to avoid breaking external links to individual messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=679869&group_id=103 From noreply at sourceforge.net Mon Feb 3 19:44:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 22:39:20 2003 Subject: [ mailman-Patches-680000 ] Fix for cron/mailpasswds and SuppressPasswordReminder Message-ID: Patches item #680000, was opened at 2003-02-03 22:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=680000&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for cron/mailpasswds and SuppressPasswordReminder Initial Comment: It looks like the "massive rewrite" that occured between revisions 2.5 and 2.5 of cron/mailpasswds removed the SuppressPasswordReminder check. The attached patch corrects cron/mailpasswds to honor the SuppressPasswordReminder option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=680000&group_id=103 From noreply at sourceforge.net Mon Feb 3 19:46:55 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 22:41:32 2003 Subject: [ mailman-Patches-680000 ] Fix for cron/mailpasswds and SuppressPasswordReminder Message-ID: Patches item #680000, was opened at 2003-02-03 22:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=680000&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for cron/mailpasswds and SuppressPasswordReminder Initial Comment: It looks like the "massive rewrite" that occured between revisions 2.5 and 2.5 of cron/mailpasswds removed the SuppressPasswordReminder check. The attached patch corrects cron/mailpasswds to honor the SuppressPasswordReminder option. ---------------------------------------------------------------------- >Comment By: Jon Parise (jparise) Date: 2003-02-03 22:46 Message: Logged In: YES user_id=485579 It looks like SourceForge lost the patch. Trying again ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=680000&group_id=103 From noreply at sourceforge.net Mon Feb 3 20:23:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 3 23:18:01 2003 Subject: [ mailman-Patches-680000 ] Fix for cron/mailpasswds and SuppressPasswordReminder Message-ID: Patches item #680000, was opened at 2003-02-03 22:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=680000&group_id=103 Category: command line scripts Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for cron/mailpasswds and SuppressPasswordReminder Initial Comment: It looks like the "massive rewrite" that occured between revisions 2.5 and 2.5 of cron/mailpasswds removed the SuppressPasswordReminder check. The attached patch corrects cron/mailpasswds to honor the SuppressPasswordReminder option. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-03 23:23 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-02-03 22:46 Message: Logged In: YES user_id=485579 It looks like SourceForge lost the patch. Trying again ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=680000&group_id=103 From noreply at sourceforge.net Mon Feb 3 22:08:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 4 01:03:17 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: 5 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-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 Mon Feb 3 22:20:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 4 01:14:20 2003 Subject: [ mailman-Patches-674553 ] patch for options.py cross site scripting bug Message-ID: Patches item #674553, was opened at 2003-01-25 12:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674553&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: patch for options.py cross site scripting bug Initial Comment: fix this issue Example: ----------------- This is a simple example for version 2.1: 1) With mailman options the email variable is vulnerable to cross-site scripting. You can recognise the vulnerabilities with this type of URL: https://www.yourserver.com:443/mailman/options/yourlist? language=en&email=<SCRIPT>alert('Can%20Cross%20Site%20Attack')</SCRIPT> and that prove that any (malicious) script code is possible on web interface part of Mailman. 2) The default error page mailman generates does not adequately filter its input making it susceptible to cross-site scripting. https://www.yourserver.com:443//mailman/options/yourlist? language=<SCRIPT>alert('Can%20Cross%20Site%20Attack')</SCRIPT> ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 06:20 Message: Logged In: YES user_id=67709 I think this can be closed now. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-26 21:33 Message: Logged In: YES user_id=12800 Very good. Here's the patch I intend to commit and advertise as a fix for the cross-site scripting bug. This additionally fixes a crash when the language cgi variable is deliberately given a bogus value. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-26 04:17 Message: Logged In: YES user_id=67709 Please review my second patch. It use Utils.ValidateEmail() and return immediately if the input string is insecure. Also, websafe(user) again to secure the final output. Note that the Exapmle is circulated in bugtraq ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-25 15:24 Message: Logged In: YES user_id=12800 Please try this more comprehensive fix. If it looks good, I will issue a security patch later today. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674553&group_id=103 From noreply at sourceforge.net Mon Feb 3 22:45:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 4 01:40:18 2003 Subject: [ mailman-Patches-667026 ] HyperArch.py unicode substitution Message-ID: Patches item #667026, was opened at 2003-01-13 07:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py unicode substitution Initial Comment: bin/arch and HyperArch.py produced error when i18n characters are present in the message body. I suspect that the text is in unicode string. This patch tests if text is unicode and then make the substitute string unicode. File "/usr/home/mailman/mailman-21/Mailman/Archiver/pipermail.py", line 592, i n add_article temp = self.format_article(article) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1192, in format_article self.__processbody_URLquote(lines) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1131, in __processbody_URLquote text = re.sub('@', _(' at '), text) File "/usr/local/lib/python2.1/sre.py", line 63, in sub return _compile(pattern, 0).sub(repl, string, count) File "/usr/local/lib/python2.1/sre.py", line 164, in _sub return _subn(pattern, template, string, count)[0] File "/usr/local/lib/python2.1/sre.py", line 185, in _subn append(filter(m)) File "/usr/local/lib/python2.1/sre.py", line 173, in filter return sre_parse.expand_template(template, match) File "/usr/local/lib/python2.1/sre_parse.py", line 732, in expand_template return string.join(literals, sep) File "/usr/local/lib/python2.1/string.py", line 128, in join return sep.join(words) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 06:45 Message: Logged In: YES user_id=67709 Update this patch for small bug. Charset defaults to 'us-ascii'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 From noreply at sourceforge.net Mon Feb 3 23:15:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 4 02:09:29 2003 Subject: [ mailman-Patches-674401 ] ToDigest.py i18n subject Message-ID: Patches item #674401, was opened at 2003-01-25 01:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 07:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 07:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 05:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 05:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-25 01:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 From roland.dworschak at cod3rs.com Wed Feb 5 08:50:01 2003 From: roland.dworschak at cod3rs.com (Roland Dworschak) Date: Wed Feb 5 02:50:16 2003 Subject: no longer moderated if changing email Message-ID: <3E40C229.6020304@cod3rs.com> hi there, we're using Mailman v2.1. Our list has set "default_member_moderation" to "Yes" and all new members have the "mod"-value set correctly, but if any of this members changes his email address via the webinterface (/mailman/options//) his "mod"-value is no longer set and he's able to post to the list without any moderation. I haven't found anything in the archive, maybe someone has a solution to this. regards -- Roland Dworschak http://cod3rs.com/ fingerprint : 0ED3 5AF2 CE34 26C5 10CA A63B 1F99 C37F 4748 90F3 pgp/gpg key : http://cod3rs.com/pgp-gpg/roland.dworschak.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 250 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-coders/attachments/20030205/9df71300/attachment.bin From noreply at sourceforge.net Wed Feb 5 10:12:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 5 13:19:04 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: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: 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-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 Wed Feb 5 21:16:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 6 00:10:51 2003 Subject: [ mailman-Patches-645297 ] Add PGP support Message-ID: Patches item #645297, was opened at 2002-11-28 09: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: Nobody/Anonymous (nobody) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-02-06 00: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 14: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 14: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-11 22: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 Wed Feb 5 22:50:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 6 01:44:40 2003 Subject: [ mailman-Bugs-681505 ] no moderation after changing email Message-ID: Bugs item #681505, was opened at 2003-02-06 06:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=681505&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Roland Dworschak (cod3rs) Assigned to: Nobody/Anonymous (nobody) Summary: no moderation after changing email Initial Comment: we're using Mailman v2.1. Our list has set "default_member_moderation" to "Yes" and all new members have the "mod"-value set correctly, but if any of this members changes his email address via the webinterface (/mailman/options//) his "mod"-value is no longer set and he's able to post to the list without any moderation. I haven't found anything in the archive, maybe someone has a solution to this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=681505&group_id=103 From noreply at sourceforge.net Thu Feb 6 16:37:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 6 19:31:16 2003 Subject: [ mailman-Patches-674401 ] ToDigest.py i18n subject Message-ID: Patches item #674401, was opened at 2003-01-25 01:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-07 00:37 Message: Logged In: YES user_id=67709 updating patch for fixing new unicode-related error reported by Dan Mick. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 07:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 07:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 05:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 05:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-25 01:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 From noreply at sourceforge.net Thu Feb 6 19:28:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 6 22:22:48 2003 Subject: [ mailman-Patches-674401 ] ToDigest.py i18n subject Message-ID: Patches item #674401, was opened at 2003-01-25 01:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-07 03:28 Message: Logged In: YES user_id=67709 Sorry, I have uploaded intermediate version. This is final, I hope. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-07 00:37 Message: Logged In: YES user_id=67709 updating patch for fixing new unicode-related error reported by Dan Mick. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 07:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 07:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 05:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 05:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-25 01:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 From noreply at sourceforge.net Thu Feb 6 20:24:55 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 6 23:18:46 2003 Subject: [ mailman-Patches-674401 ] ToDigest.py i18n subject Message-ID: Patches item #674401, was opened at 2003-01-24 20:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-06 23:24 Message: Logged In: YES user_id=12800 I'm accepting and applying this patch -- with two differences. One the line that says "return oneline.encode()" I want to pass the argument "replace" so that there's more chance that much of the header decoding can actually happen. Without this, iso-8859-1 encoded Subject: headers posted to an English list leave the RFC 2047 encodings in the header, which looks ugly. The second change is to replace the bare except (bad! :) in oneline() with a qualified except. I believe only UnicodeError and LookupError can occur here, although with the first change above, maybe not even UnicodeError. Now I want to see if this fixes the problem I've been having with the spambayes list. Thanks! :) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 22:28 Message: Logged In: YES user_id=67709 Sorry, I have uploaded intermediate version. This is final, I hope. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 19:37 Message: Logged In: YES user_id=67709 updating patch for fixing new unicode-related error reported by Dan Mick. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 02:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 02:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 00:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 00:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-24 20:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 From noreply at sourceforge.net Thu Feb 6 21:14:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 00:08:32 2003 Subject: [ mailman-Patches-674401 ] ToDigest.py i18n subject Message-ID: Patches item #674401, was opened at 2003-01-24 20:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 00:14 Message: Logged In: YES user_id=12800 Looks like this is working for python.org at least, so I'm closing the issue. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-06 23:24 Message: Logged In: YES user_id=12800 I'm accepting and applying this patch -- with two differences. One the line that says "return oneline.encode()" I want to pass the argument "replace" so that there's more chance that much of the header decoding can actually happen. Without this, iso-8859-1 encoded Subject: headers posted to an English list leave the RFC 2047 encodings in the header, which looks ugly. The second change is to replace the bare except (bad! :) in oneline() with a qualified except. I believe only UnicodeError and LookupError can occur here, although with the first change above, maybe not even UnicodeError. Now I want to see if this fixes the problem I've been having with the spambayes list. Thanks! :) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 22:28 Message: Logged In: YES user_id=67709 Sorry, I have uploaded intermediate version. This is final, I hope. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 19:37 Message: Logged In: YES user_id=67709 updating patch for fixing new unicode-related error reported by Dan Mick. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 02:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 02:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 00:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 00:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-24 20:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_id=103 From noreply at sourceforge.net Thu Feb 6 22:30:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 01:24:00 2003 Subject: [ mailman-Bugs-668664 ] ValueError processing held messages Message-ID: Bugs item #668664, was opened at 2003-01-15 14:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=668664&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: ValueError processing held messages Initial Comment: I've seen this problem both with cron/checkdbs and now with the admindb CGI. I'm submitting this one because it has lots of detail. I've had some luck playing with try/except in checkdbs, but that just skips the entry that's having problems, doesn't actually deal with it. Jan 14 18:21:47 2003 admin(54023): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(54023): [----- Mailman Version: 2.1 -----] admin(54023): [----- Traceback ------] admin(54023): Traceback (most recent call last): admin(54023): File "/home/mailman-2.1/scripts/driver", line 87, in run_main admin(54023): main() admin(54023): File "/home/mailman-2.1/Mailman/Cgi/admindb.py", line 226, in main admin(54023): num = show_pending_subs(mlist, form) admin(54023): File "/home/mailman-2.1/Mailman/Cgi/admindb.py", line 287, in show_pending_subs admin(54023): time, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) admin(54023): ValueError: unpack tuple of wrong size admin(54023): [----- Python Information -----] admin(54023): sys.version = 2.2.2 (#1, Dec 1 2002, 11:44:59) [GCC 2.95.3 20010315 (release) [FreeBSD]] admin(54023): sys.executable = /usr/local/bin/python admin(54023): sys.prefix = /usr/local admin(54023): sys.exec_prefix = /usr/local admin(54023): sys.path = /usr/local admin(54023): sys.platform = freebsd4 admin(54023): [----- Environment Variables -----] admin(54023): PATH_INFO: /wnet admin(54023): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */* admin(54023): CONTENT_TYPE: application/x-www-form-urlencoded admin(54023): HTTP_REFERER: http://lists.samurai.com/mailman/admindb/wnet admin(54023): SERVER_SOFTWARE: Apache/1.3.27 (Unix) admin(54023): PYTHONPATH: /home/mailman-2.1 admin(54023): SCRIPT_FILENAME: /home/mailman-2.1/cgi-bin/admindb admin(54023): SERVER_ADMIN: webmaster@samurai.com admin(54023): SCRIPT_NAME: /mailman/admindb admin(54023): SCRIPT_URI: http://lists.samurai.com/mailman/admindb/wnet admin(54023): SERVER_SIGNATURE:
Apache/1.3.27 Server at lists.samurai.com Port 80
admin(54023): admin(54023): REQUEST_METHOD: POST admin(54023): HTTP_HOST: lists.samurai.com admin(54023): SCRIPT_URL: /mailman/admindb/wnet admin(54023): SERVER_PROTOCOL: HTTP/1.1 admin(54023): QUERY_STRING: admin(54023): HTTP_CACHE_CONTROL: no-cache admin(54023): REQUEST_URI: /mailman/admindb/wnet admin(54023): CONTENT_LENGTH: 18 admin(54023): PATH_TRANSLATED: /usr/local/www/data/wnet admin(54023): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461) admin(54023): HTTP_CONNECTION: Keep-Alive admin(54023): SERVER_NAME: lists.samurai.com admin(54023): REMOTE_ADDR: 65.93.181.251 admin(54023): REMOTE_PORT: 4749 admin(54023): HTTP_ACCEPT_LANGUAGE: en-ca admin(54023): UNIQUE_ID: PiSbis3PHE8AAKK7eCk admin(54023): SERVER_PORT: 80 admin(54023): GATEWAY_INTERFACE: CGI/1.1 admin(54023): REMOTE_HOST: sherbrooke-hse-ppp3609836.sympatico.ca admin(54023): HTTP_ACCEPT_ENCODING: gzip, deflate admin(54023): SERVER_ADDR: 205.207.28.81 admin(54023): DOCUMENT_ROOT: /usr/local/www/data Bryan ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 01:30 Message: Logged In: YES user_id=12800 I believe I've finally fixed this in MM2.1+ (cvs) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=668664&group_id=103 From noreply at sourceforge.net Thu Feb 6 23:23:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 02:17:06 2003 Subject: [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 05: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: Sean Reifschneider (jafo) Date: 2003-02-07 07: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 02: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 07: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 16: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 00: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 16: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 Fri Feb 7 13:37:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 16:31:15 2003 Subject: [ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix Message-ID: Patches item #682573, was opened at 2003-02-07 22:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 From noreply at sourceforge.net Fri Feb 7 13:39:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 16:33:21 2003 Subject: [ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix Message-ID: Patches item #682573, was opened at 2003-02-07 22:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2003-02-07 22:39 Message: Logged In: YES user_id=60479 Ok. Trying to attach patch a second time... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 From noreply at sourceforge.net Fri Feb 7 13:44:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 16:37:28 2003 Subject: [ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix Message-ID: Patches item #682573, was opened at 2003-02-07 22:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2003-02-07 22:44 Message: Logged In: YES user_id=60479 Sorry for the spam, I got the diff wrong... stupid me. ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2003-02-07 22:39 Message: Logged In: YES user_id=60479 Ok. Trying to attach patch a second time... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 From noreply at sourceforge.net Fri Feb 7 08:28:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 20:24:53 2003 Subject: [ mailman-Bugs-671147 ] ValueError on admin of upgraded list Message-ID: Bugs item #671147, was opened at 2003-01-20 08:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671147&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: seb bacon (sebbacon) Assigned to: Nobody/Anonymous (nobody) Summary: ValueError on admin of upgraded list Initial Comment: This is a dupe of bug 668664, but I'm darned if I can see how you can upload a file as a comment to an already existing bug. I looked at this bug for a friend and there appear to be a couple of obvious bugs that cause this ValueError to happen. I don't use mailman, so I didn't bother checking that this fix works, but hopefully it's helpful ;-) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 11:28 Message: Logged In: YES user_id=12800 There was no attachment, probably because you didn't check the upload box (yes, this is SF's suckage). No matter, I believe this will be fixed for 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671147&group_id=103 From noreply at sourceforge.net Fri Feb 7 20:38:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 7 23:32:44 2003 Subject: [ mailman-Patches-664611 ] Updated README.QMAIL doc patch Message-ID: Patches item #664611, was opened at 2003-01-08 14:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 23:38 Message: Logged In: YES user_id=12800 Applied the v2 doc ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-09 02:24 Message: Logged In: YES user_id=675094 Directory paths have changed to reflect new installations vs upgrading from prior installs ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 22:50 Message: Logged In: YES user_id=675094 Didn't look like SF got my patch the first time. It's attached now ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 From noreply at sourceforge.net Fri Feb 7 21:11:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 8 00:05:32 2003 Subject: [ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix Message-ID: Patches item #682573, was opened at 2003-02-07 16:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2003-02-07 16:44 Message: Logged In: YES user_id=60479 Sorry for the spam, I got the diff wrong... stupid me. ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2003-02-07 16:39 Message: Logged In: YES user_id=60479 Ok. Trying to attach patch a second time... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_id=103 From noreply at sourceforge.net Sun Feb 9 22:22:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 01:17:31 2003 Subject: [ mailman-Patches-683774 ] Selective No-Archive Message-ID: Patches item #683774, was opened at 2003-02-10 06:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683774&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jon E (babzog) Assigned to: Nobody/Anonymous (nobody) Summary: Selective No-Archive Initial Comment: What this does is allow you to approve a message that has been held for moderation (msg exceeds size limit for example) so it can be delivered, but preventing it from being archived if the noarchive checkbox is checked, thus saving disk space. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683774&group_id=103 From noreply at sourceforge.net Mon Feb 10 01:48:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 04:42:00 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 11:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Mon Feb 10 02:01:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 04:54:39 2003 Subject: [ mailman-Bugs-593728 ] Traceback rebuilding archive Message-ID: Bugs item #593728, was opened at 2002-08-11 20:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 Category: Pipermail Group: 2.1 beta >Status: Open Resolution: Fixed Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback rebuilding archive Initial Comment: Witn Mailman 2.1b3, rebuilding a pipermail archive using $ bin/arch listname runs fine for 2 lists, but on the third one gives the following traceback: [...] Updating HTML for article 52 Updating HTML for article 53 Schreibe Archivzustand in Datei /home/mailman/archives/private/humor/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/home/mailman/Mailman/Archiver/pipermail.py", line 545, 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 "/home/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/home/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 159, in process part.set_payload(_("""\ File "/home/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-09 06:26 Message: Logged In: YES user_id=12800 Thanks Stefan, I got your mbox file, which appeared to contain one message. That message has an unknown charset in its RFC 2047 Subject header. Mailman cvs seems to handle this file just fine, so I'm closing this as fixed in 2.1b5+ ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 20:11 Message: Logged In: YES user_id=483131 Just tried to rebuild the other archives: 4 of 21 mbox-files can't be rebuilt. There are two kinds of tracebacks: * "ASCII decoding error" (see above) * "Lookup error: unknown encoding" I'll send the archive causing the second kind of traceback to Barry, hence it contains somewhat internal information. ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 18:58 Message: Logged In: YES user_id=483131 Sorry for the long delay. I fiddled around with the 19MB mbox file, and cut out the part which causes this error (refer to the attached file). The traceback also appeared using 2.1b5. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:47 Message: Logged In: YES user_id=12800 I'm moving the bug report to pending since I haven't seen an update. I suspect this is fixed in current cvs. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-16 23:55 Message: Logged In: YES user_id=12800 Can you upload the .mbox file for the list you're regenerating? If not (perhaps because it's proprietary information), can you make it available for me to look at privately? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 From noreply at sourceforge.net Mon Feb 10 02:02:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 04:55:17 2003 Subject: [ mailman-Bugs-593728 ] Traceback rebuilding archive Message-ID: Bugs item #593728, was opened at 2002-08-11 20:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 Category: Pipermail >Group: 2.1 (stable) Status: Open Resolution: Fixed Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback rebuilding archive Initial Comment: Witn Mailman 2.1b3, rebuilding a pipermail archive using $ bin/arch listname runs fine for 2 lists, but on the third one gives the following traceback: [...] Updating HTML for article 52 Updating HTML for article 53 Schreibe Archivzustand in Datei /home/mailman/archives/private/humor/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/home/mailman/Mailman/Archiver/pipermail.py", line 545, 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 "/home/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/home/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 159, in process part.set_payload(_("""\ File "/home/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-09 06:26 Message: Logged In: YES user_id=12800 Thanks Stefan, I got your mbox file, which appeared to contain one message. That message has an unknown charset in its RFC 2047 Subject header. Mailman cvs seems to handle this file just fine, so I'm closing this as fixed in 2.1b5+ ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 20:11 Message: Logged In: YES user_id=483131 Just tried to rebuild the other archives: 4 of 21 mbox-files can't be rebuilt. There are two kinds of tracebacks: * "ASCII decoding error" (see above) * "Lookup error: unknown encoding" I'll send the archive causing the second kind of traceback to Barry, hence it contains somewhat internal information. ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 18:58 Message: Logged In: YES user_id=483131 Sorry for the long delay. I fiddled around with the 19MB mbox file, and cut out the part which causes this error (refer to the attached file). The traceback also appeared using 2.1b5. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:47 Message: Logged In: YES user_id=12800 I'm moving the bug report to pending since I haven't seen an update. I suspect this is fixed in current cvs. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-16 23:55 Message: Logged In: YES user_id=12800 Can you upload the .mbox file for the list you're regenerating? If not (perhaps because it's proprietary information), can you make it available for me to look at privately? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 From noreply at sourceforge.net Mon Feb 10 02:07:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 05:00:32 2003 Subject: [ mailman-Bugs-593728 ] Traceback rebuilding archive Message-ID: Bugs item #593728, was opened at 2002-08-11 20:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: Fixed Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback rebuilding archive Initial Comment: Witn Mailman 2.1b3, rebuilding a pipermail archive using $ bin/arch listname runs fine for 2 lists, but on the third one gives the following traceback: [...] Updating HTML for article 52 Updating HTML for article 53 Schreibe Archivzustand in Datei /home/mailman/archives/private/humor/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/home/mailman/Mailman/Archiver/pipermail.py", line 545, 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 "/home/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/home/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 159, in process part.set_payload(_("""\ File "/home/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Stefan Divjak (stdivjak) Date: 2003-02-10 12:07 Message: Logged In: YES user_id=483131 Barry told me, that it is fixed in the current CVS version in September 2002, but this bug still appears in mailman 2.1.1 (using bin/arch on the attached mbox-file), so I switched the status to open again. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-09 06:26 Message: Logged In: YES user_id=12800 Thanks Stefan, I got your mbox file, which appeared to contain one message. That message has an unknown charset in its RFC 2047 Subject header. Mailman cvs seems to handle this file just fine, so I'm closing this as fixed in 2.1b5+ ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 20:11 Message: Logged In: YES user_id=483131 Just tried to rebuild the other archives: 4 of 21 mbox-files can't be rebuilt. There are two kinds of tracebacks: * "ASCII decoding error" (see above) * "Lookup error: unknown encoding" I'll send the archive causing the second kind of traceback to Barry, hence it contains somewhat internal information. ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 18:58 Message: Logged In: YES user_id=483131 Sorry for the long delay. I fiddled around with the 19MB mbox file, and cut out the part which causes this error (refer to the attached file). The traceback also appeared using 2.1b5. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:47 Message: Logged In: YES user_id=12800 I'm moving the bug report to pending since I haven't seen an update. I suspect this is fixed in current cvs. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-16 23:55 Message: Logged In: YES user_id=12800 Can you upload the .mbox file for the list you're regenerating? If not (perhaps because it's proprietary information), can you make it available for me to look at privately? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 From noreply at sourceforge.net Mon Feb 10 03:18:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 06:15:25 2003 Subject: [ mailman-Patches-668685 ] sys.exit handling by script/driver Message-ID: Patches item #668685, was opened at 2003-01-15 19:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668685&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: sys.exit handling by script/driver Initial Comment: The code in the $prefix/scripts/driver script concedes that it is valid for a script it is supervising to exit using sys.exit rather than just returning from the main function. However, if the script being supervised does use sys.exit, the driver script fails to pass on the output generated by the supervised script. In the case of cgi scripts this means that an internal server error is reported by the http server because no output has been returned. And finding the reason for this is tedious! The attached patch file (driver-2.1-0.1.patch) can applied with the following command with pwd being the MM build directory: patch -p1 < ../ ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:18 Message: Logged In: YES user_id=75166 driver-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668685&group_id=103 From noreply at sourceforge.net Mon Feb 10 03:42:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 06:36:17 2003 Subject: [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply at sourceforge.net Mon Feb 10 03:50:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 06:43:31 2003 Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-03 18:19 Message: Logged In: YES user_id=75166 the mm_mailer script in mailer-2.1-0.2.patch now handles VERP'ed return addresses in bounced mail which I missed in the original implementation ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:34 Message: Logged In: YES user_id=75166 mailer-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 12:16 Message: Logged In: YES user_id=75166 mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds the case of listname and servername for compaiblity with MMs naive belief that listnames are case all lower case. case "(Email addresses are not case sensitive, but they are sensitive to almost everything else :-)" ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:37 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:36 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply at sourceforge.net Mon Feb 10 04:02:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 06:58:32 2003 Subject: [ mailman-Patches-661138 ] corrects defects in some HTML templates Message-ID: Patches item #661138, was opened at 2003-01-02 15:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=661138&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: corrects defects in some HTML templates Initial Comment: This patch corrects some defects in HTML templates in the MM 2.1 release. Apply the patch from within the MM 2.1 build directory using the command: patch -p1 < path-to-patch-file The following are changed by the patch Various languages (de, en, es, et, fi, hu, it, ja, lt, nl, pt_BR) ----------------- admindetails.html - removed extraneous P tags from inside UL Swedish templates ----------------- admindetails.html - removed spurious body tags adminpreamble.html - removed spurious body tags article.html - moved stuff from inside BODY tag back to inside HEAD tag headfoot.html - removed spurious body tags French templates ---------------- archidxfoot.html - removed spurious HTML and BODY open tags archidxhead.html - removed spurious HTML and BODY close tags and moved stuff from inside BODY tag back to inside HEAD tag Dutch templates --------------- article.html - added \n to end of file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-02-10 12:02 Message: Logged In: YES user_id=75166 templates-2.1-0.1.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=661138&group_id=103 From noreply at sourceforge.net Mon Feb 10 05:21:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 08:14: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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=683906&group_id=103 From noreply at sourceforge.net Mon Feb 10 05:26:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 08:20:13 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-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 Feb 10 07:49:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 10:42:25 2003 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:53 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:52 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Mon Feb 10 07:50:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 10 10:55:35 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: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: 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 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 Tue Feb 11 01:46:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 11 04:39:53 2003 Subject: [ mailman-Feature Requests-684475 ] Co-Admin for user management Message-ID: Feature Requests item #684475, was opened at 2003-02-11 10:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 6 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Co-Admin for user management Initial Comment: It would be very helpful, to have the possibility to have a co-admin, who`s only able to manage subscribe/unsubscribe-management (finding out in which lists a user is subscribe, unsubscribing then from any lists). For the moment it`s necessary to give a co-admin a full shell-Account on the server and he`s capable to do a lot of important changes. We have so many users in our lists, that I can`t handle all of the stupid "unsubscribe me"-Users by myself and and I need help from somebody who can do that and who ONLY can do that. It`s just like the possibility to have a seperate password for list-moderators who can`t change the list configuration. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 From noreply at sourceforge.net Tue Feb 11 01:52:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 11 04:46:24 2003 Subject: [ mailman-Bugs-681505 ] no moderation after changing email Message-ID: Bugs item #681505, was opened at 2003-02-06 06:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=681505&group_id=103 Category: security/privacy Group: 2.1 (stable) >Status: Deleted Resolution: None Priority: 5 Submitted By: Roland Dworschak (cod3rs) Assigned to: Nobody/Anonymous (nobody) Summary: no moderation after changing email Initial Comment: we're using Mailman v2.1. Our list has set "default_member_moderation" to "Yes" and all new members have the "mod"-value set correctly, but if any of this members changes his email address via the webinterface (/mailman/options//) his "mod"-value is no longer set and he's able to post to the list without any moderation. I haven't found anything in the archive, maybe someone has a solution to this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=681505&group_id=103 From noreply at sourceforge.net Tue Feb 11 05:32:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 11 08:25:50 2003 Subject: [ mailman-Feature Requests-684475 ] Co-Admin for user management Message-ID: Feature Requests item #684475, was opened at 2003-02-11 04:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 6 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Co-Admin for user management Initial Comment: It would be very helpful, to have the possibility to have a co-admin, who`s only able to manage subscribe/unsubscribe-management (finding out in which lists a user is subscribe, unsubscribing then from any lists). For the moment it`s necessary to give a co-admin a full shell-Account on the server and he`s capable to do a lot of important changes. We have so many users in our lists, that I can`t handle all of the stupid "unsubscribe me"-Users by myself and and I need help from somebody who can do that and who ONLY can do that. It`s just like the possibility to have a seperate password for list-moderators who can`t change the list configuration. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-11 08:32 Message: Logged In: YES user_id=12800 This is already in MM2.1. Please see the separate moderator task (go to the passwords category). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 From noreply at sourceforge.net Tue Feb 11 05:42:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 11 08:35:53 2003 Subject: [ mailman-Feature Requests-684475 ] Co-Admin for user management Message-ID: Feature Requests item #684475, was opened at 2003-02-11 10:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 Category: None Group: None >Status: Pending Resolution: Out of Date Priority: 6 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Co-Admin for user management Initial Comment: It would be very helpful, to have the possibility to have a co-admin, who`s only able to manage subscribe/unsubscribe-management (finding out in which lists a user is subscribe, unsubscribing then from any lists). For the moment it`s necessary to give a co-admin a full shell-Account on the server and he`s capable to do a lot of important changes. We have so many users in our lists, that I can`t handle all of the stupid "unsubscribe me"-Users by myself and and I need help from somebody who can do that and who ONLY can do that. It`s just like the possibility to have a seperate password for list-moderators who can`t change the list configuration. ---------------------------------------------------------------------- >Comment By: Peer Heinlein (pheinlein) Date: 2003-02-11 14:42 Message: Logged In: YES user_id=581680 It is not in MM 2.1, because I don`t need a seperate moderator for *one* list! I need a superuser-moderator who has user-management-access to *all* lists systemwide no matter who`s the onwer, and what`s the list`s owner and moderator password. Mailman has a Mailman-Owner-Superuser-Password that is accepted in nearly every password-field. The superuser has access to every list-configuration. I need the same kind for a systemwide superuser-usermanager who has access just to the user-management. It`s necessary to handle conflicts with users who don`t know in which lists they are and how to unsubscribe and who I have to unsubscribe globally from every list. *I* can do that with some shell-commands. But *I* can`t do everything on the system... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-11 14:32 Message: Logged In: YES user_id=12800 This is already in MM2.1. Please see the separate moderator task (go to the passwords category). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 From noreply at sourceforge.net Tue Feb 11 06:23:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 11 09:16:35 2003 Subject: [ mailman-Feature Requests-684475 ] Co-Admin for user management Message-ID: Feature Requests item #684475, was opened at 2003-02-11 04:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 Category: None Group: None >Status: Open Resolution: Out of Date Priority: 6 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Co-Admin for user management Initial Comment: It would be very helpful, to have the possibility to have a co-admin, who`s only able to manage subscribe/unsubscribe-management (finding out in which lists a user is subscribe, unsubscribing then from any lists). For the moment it`s necessary to give a co-admin a full shell-Account on the server and he`s capable to do a lot of important changes. We have so many users in our lists, that I can`t handle all of the stupid "unsubscribe me"-Users by myself and and I need help from somebody who can do that and who ONLY can do that. It`s just like the possibility to have a seperate password for list-moderators who can`t change the list configuration. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-02-11 08:42 Message: Logged In: YES user_id=581680 It is not in MM 2.1, because I don`t need a seperate moderator for *one* list! I need a superuser-moderator who has user-management-access to *all* lists systemwide no matter who`s the onwer, and what`s the list`s owner and moderator password. Mailman has a Mailman-Owner-Superuser-Password that is accepted in nearly every password-field. The superuser has access to every list-configuration. I need the same kind for a systemwide superuser-usermanager who has access just to the user-management. It`s necessary to handle conflicts with users who don`t know in which lists they are and how to unsubscribe and who I have to unsubscribe globally from every list. *I* can do that with some shell-commands. But *I* can`t do everything on the system... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-11 08:32 Message: Logged In: YES user_id=12800 This is already in MM2.1. Please see the separate moderator task (go to the passwords category). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=684475&group_id=103 From noreply at sourceforge.net Tue Feb 11 17:10:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 11 20:10:18 2003 Subject: [ mailman-Bugs-685040 ] mailmanctl reopen does not reopen all log files Message-ID: Bugs item #685040, was opened at 2003-02-12 12:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=685040&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl reopen does not reopen all log files Initial Comment: In Mailman 2.1: The help for mailmanctl reopen says that it causes all log files to be closed, and reopened the next time they are used. However, it does not seem to cover the qrunner and error logs. After running this command, lsof shows: [root@dp logs]# lsof -p 9207 .... mailmanct 9207 root 0u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 1u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 2u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 3u REG 8,1 116944 2130090 /var/mailman/logs/error.1 mailmanct 9207 root 4u REG 8,1 649 2130251 /var/mailman/logs/qrunner After running it again: [root@dp logs]# lsof -p 9214 .... python 9214 mailman 0u CHR 136,7 9 /dev/pts/7 python 9214 mailman 1u CHR 136,7 9 /dev/pts/7 python 9214 mailman 2u CHR 136,7 9 /dev/pts/7 python 9214 mailman 3u REG 8,1 116944 2130090 /var/mailman/logs/error.1 python 9214 mailman 4u REG 8,1 116944 2130090 /var/mailman/logs/error.1 python 9214 mailman 5u REG 8,1 649 2130251 /var/mailman/logs/qrunner The same is true for the qrunner child processes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=685040&group_id=103 From noreply at sourceforge.net Wed Feb 12 20:05:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 12 22:58:43 2003 Subject: [ mailman-Bugs-672649 ] canonstr -> unicode usernames Message-ID: Bugs item #672649, was opened at 2003-01-22 14:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: canonstr -> unicode usernames Initial Comment: Cgi.subscribe.process_form gets a unicode value for fullname, from Utils.canonstr() (return unicode(newstr, charset, 'replace') This came to my attention because it broke OwnerNotification when the email Message couldn't "flatten" itself with the unicode payload. Suspect that's only the beginning of the trouble that will be caused, so I'm hoping we really don't want unicode usernames values as a rule. I fixed it in subscribe.py with fullname = fullname.encode('iso8859-1'), but note that canonstr is used elsewhere like this. ---------------------------------------------------------------------- Comment By: Pat Carr (pcarr) Date: 2003-02-12 23:05 Message: Logged In: YES user_id=710070 I stumbled over the same bug, but in my case it was bailing only in the confirm.py script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_id=103 From noreply at sourceforge.net Wed Feb 12 23:47:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 13 02:40:35 2003 Subject: [ mailman-Patches-685788 ] fix for Cc: to cc: weirdness Message-ID: Patches item #685788, was opened at 2003-02-13 07:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 From noreply at sourceforge.net Wed Feb 12 23:52:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 13 02:45:22 2003 Subject: [ mailman-Patches-685788 ] fix for Cc: to cc: weirdness Message-ID: Patches item #685788, was opened at 2003-02-13 07: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: 5 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 From noreply at sourceforge.net Thu Feb 13 02:25:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 13 05:18:52 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 10:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Fri Feb 14 02:02:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 14 04:55:42 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Fri Feb 14 03:33:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 14 06:26:35 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Sat Feb 15 03:17:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 15 06:10:21 2003 Subject: [ mailman-Patches-685788 ] fix for Cc: to cc: weirdness Message-ID: Patches item #685788, was opened at 2003-02-13 07: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: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11: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 Sat Feb 15 03:21:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 15 06:13:55 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None >Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 10:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Sat Feb 15 03:37:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 15 06:29:41 2003 Subject: [ mailman-Bugs-672649 ] canonstr -> unicode usernames Message-ID: Bugs item #672649, was opened at 2003-01-22 19:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: canonstr -> unicode usernames Initial Comment: Cgi.subscribe.process_form gets a unicode value for fullname, from Utils.canonstr() (return unicode(newstr, charset, 'replace') This came to my attention because it broke OwnerNotification when the email Message couldn't "flatten" itself with the unicode payload. Suspect that's only the beginning of the trouble that will be caused, so I'm hoping we really don't want unicode usernames values as a rule. I fixed it in subscribe.py with fullname = fullname.encode('iso8859-1'), but note that canonstr is used elsewhere like this. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:37 Message: Logged In: YES user_id=67709 If your users choose to input latin-1 charcters in fullname, it will be better to set iso-8859-1as english charset. in mm_cfg.py, def _(s): return s LC_DESCRIPTIONS['en'] = (_('English (USA)'), 'iso-8859-1') del _ ---------------------------------------------------------------------- Comment By: Pat Carr (pcarr) Date: 2003-02-13 04:05 Message: Logged In: YES user_id=710070 I stumbled over the same bug, but in my case it was bailing only in the confirm.py script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_id=103 From noreply at sourceforge.net Sun Feb 16 17:05:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 16 19:58:13 2003 Subject: [ mailman-Patches-687704 ] use external style sheet config option Message-ID: Patches item #687704, was opened at 2003-02-17 02:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: use external style sheet config option Initial Comment: Adds an optional stylesheet config option to Defaults.py, and adds the place holders for it into the english templates and the cgis. The style sheet is in a separate file, making per site customization less messy when the templates get modified by Mailman developers. Sample style sheet using verdana/arial in 9pt is included. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_id=103 From noreply at sourceforge.net Sun Feb 16 17:07:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 16 20:03:57 2003 Subject: [ mailman-Patches-687704 ] use external style sheet config option Message-ID: Patches item #687704, was opened at 2003-02-17 02:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None >Priority: 3 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: use external style sheet config option Initial Comment: Adds an optional stylesheet config option to Defaults.py, and adds the place holders for it into the english templates and the cgis. The style sheet is in a separate file, making per site customization less messy when the templates get modified by Mailman developers. Sample style sheet using verdana/arial in 9pt is included. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_id=103 From noreply at sourceforge.net Sun Feb 16 21:48:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 17 00:40:52 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 11:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 07:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 13:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 12:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Mon Feb 17 03:45:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 17 06:38:05 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-17 11:45 Message: Logged In: YES user_id=67709 stdivjak> [mailman@styx cron]# ./checkdbs you should type python -S /path/to/checkdbs ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 05:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 10:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Mon Feb 17 19:11:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 17 22:03:17 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 From noreply at sourceforge.net Mon Feb 17 20:37:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 17 23:29:56 2003 Subject: [ mailman-Bugs-662504 ] Mailman Admin Notification Racing Message-ID: Bugs item #662504, was opened at 2003-01-05 02:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Deleted Resolution: None Priority: 7 Submitted By: Ian Wilson (tacgeek) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman Admin Notification Racing Initial Comment: Hi folks; When a non-list member sends a message to a list, I start to receive emails in a race format...up to about 20 a minute in some instances. Here's how to replicate problem (for those who need to know, and please understand I'm not being a smartbutt, but someone who is just confused with this behavior). 1.) Create new list 2.) Add your email in list administrator's area 3.) Save 4.) Send an email to list from a non-subscribed list 5.) Watch the fireworks on your Admin Email I'm having to go in, stop qrunner, then delete the request.db file before starting qrunner before the race condition stops. Any help would be appreciated! Ian ian@dysfunctional-household.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 From noreply at sourceforge.net Tue Feb 18 00:11:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 18 03:04:04 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 11:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 10:11 Message: Logged In: YES user_id=483131 Unfortunately, there's no difference :-( ... [mailman@styx mailman]$ python - S /home/mailman/cron/checkdbs Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 138, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-17 13:45 Message: Logged In: YES user_id=67709 stdivjak> [mailman@styx cron]# ./checkdbs you should type python -S /path/to/checkdbs ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 07:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 13:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 12:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Tue Feb 18 03:12:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 18 06:05:23 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-18 11:12 Message: Logged In: YES user_id=67709 OK, somehow ^L has disappeared during genrating diff from cvs. I am uploading new patch using non-cvs diff. (You might be able to report error in patch command execution) ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 08:11 Message: Logged In: YES user_id=483131 Unfortunately, there's no difference :-( ... [mailman@styx mailman]$ python - S /home/mailman/cron/checkdbs Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 138, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-17 11:45 Message: Logged In: YES user_id=67709 stdivjak> [mailman@styx cron]# ./checkdbs you should type python -S /path/to/checkdbs ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 05:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 10:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Tue Feb 18 03:53:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 18 06:45:46 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 11:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 13:53 Message: Logged In: YES user_id=483131 Patching worked without any errors, and so does the checkdbs script now. Well done! :-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-18 13:12 Message: Logged In: YES user_id=67709 OK, somehow ^L has disappeared during genrating diff from cvs. I am uploading new patch using non-cvs diff. (You might be able to report error in patch command execution) ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 10:11 Message: Logged In: YES user_id=483131 Unfortunately, there's no difference :-( ... [mailman@styx mailman]$ python - S /home/mailman/cron/checkdbs Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 138, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-17 13:45 Message: Logged In: YES user_id=67709 stdivjak> [mailman@styx cron]# ./checkdbs you should type python -S /path/to/checkdbs ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 07:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 13:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 12:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Tue Feb 18 08:55:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 18 11:47:45 2003 Subject: [ mailman-Bugs-688751 ] Scrubber/attachment bug on NetBSD Message-ID: Bugs item #688751, was opened at 2003-02-18 11:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber/attachment bug on NetBSD Initial Comment: I'm using Mailman 2.1.1, and have encountered issues with mail delivery of messages with attachments (having to do, I think, with the recent change to use the scrubber on such messages for digests). I actually have ARCHIVE_SCRUBBER set to 0 on my system, since I use MHonArc for archiving. Still, the scrubber is called from ToDigest. As a result of this bug, ANY message with an attachment is currently getting shunted!! :( Here's an example stacktrace from the error log: Feb 18 11:20:55 2003 (7122) Uncaught runner exception: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' Feb 18 11:20:55 2003 (7122) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 219, in process url = save_attachment(mlist, part, dir, filter_html=0) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 341, in save_attachment makedirs(fsdir) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 333, in makedirs os.path.walk(dir, twiddle, None) File "/usr/pkg/lib/python2.2/posixpath.py", line 279, in walk func(arg, top, names) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 332, in twiddle os.chmod(dirname, 02775) OSError: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' To work aorund this issue, I've currently commented out lines 331-333 on my system. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 From noreply at sourceforge.net Wed Feb 19 06:35:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 19 09:27:13 2003 Subject: [ mailman-Feature Requests-689291 ] capability to hold by externally specified rule Message-ID: Feature Requests item #689291, was opened at 2003-02-19 09:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=689291&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: George M. Sipe (gsipe) Assigned to: Nobody/Anonymous (nobody) Summary: capability to hold by externally specified rule Initial Comment: I use a procmail script to front-end mailman posts in order to add custom filtering and holds. In order to hold messages, I set a "X-Hold:" header and add that to mailman's DEFAULT_BOUNCE_MATCHING_HEADERS list. Mailman sets the reason for hold to "Your message was deemed inappropriate by the moderator." I would like to have a mechanism where I can pass the reason in a header. This simple enhancement would provide a powerful moderation extension. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=689291&group_id=103 From noreply at sourceforge.net Wed Feb 19 16:26:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 19 19:18:46 2003 Subject: [ mailman-Patches-667026 ] HyperArch.py unicode substitution Message-ID: Patches item #667026, was opened at 2003-01-13 07:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None >Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py unicode substitution Initial Comment: bin/arch and HyperArch.py produced error when i18n characters are present in the message body. I suspect that the text is in unicode string. This patch tests if text is unicode and then make the substitute string unicode. File "/usr/home/mailman/mailman-21/Mailman/Archiver/pipermail.py", line 592, i n add_article temp = self.format_article(article) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1192, in format_article self.__processbody_URLquote(lines) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1131, in __processbody_URLquote text = re.sub('@', _(' at '), text) File "/usr/local/lib/python2.1/sre.py", line 63, in sub return _compile(pattern, 0).sub(repl, string, count) File "/usr/local/lib/python2.1/sre.py", line 164, in _sub return _subn(pattern, template, string, count)[0] File "/usr/local/lib/python2.1/sre.py", line 185, in _subn append(filter(m)) File "/usr/local/lib/python2.1/sre.py", line 173, in filter return sre_parse.expand_template(template, match) File "/usr/local/lib/python2.1/sre_parse.py", line 732, in expand_template return string.join(literals, sep) File "/usr/local/lib/python2.1/string.py", line 128, in join return sep.join(words) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 00:26 Message: Logged In: YES user_id=67709 I think this deserves to be included in next release (2.1.2). So, increment priority and clean up old patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 06:45 Message: Logged In: YES user_id=67709 Update this patch for small bug. Charset defaults to 'us-ascii'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 From noreply at sourceforge.net Wed Feb 19 17:24:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 19 20:17:07 2003 Subject: [ mailman-Patches-664209 ] best effort to keep text/plain Message-ID: Patches item #664209, was opened at 2003-01-08 06:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:24 Message: Logged In: YES user_id=67709 Refine the code and increment priority. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-08 07:34 Message: Logged In: YES user_id=67709 Expand this patch to base64 encoded plain text. apply the second patch Decorate.py.diff2 to the original Decorate.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Wed Feb 19 17:26:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 19 20:18:35 2003 Subject: [ mailman-Patches-664209 ] best effort to keep text/plain Message-ID: Patches item #664209, was opened at 2003-01-08 06:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None >Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:24 Message: Logged In: YES user_id=67709 Refine the code and increment priority. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-08 07:34 Message: Logged In: YES user_id=67709 Expand this patch to base64 encoded plain text. apply the second patch Decorate.py.diff2 to the original Decorate.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Wed Feb 19 17:31:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 19 20:23:06 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: 6 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-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 Thu Feb 20 03:42:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 20 06:34:10 2003 Subject: [ mailman-Patches-664209 ] best effort to keep text/plain Message-ID: Patches item #664209, was opened at 2003-01-08 06:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 11:42 Message: Logged In: YES user_id=67709 Sorry, there was a error in the previous patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:24 Message: Logged In: YES user_id=67709 Refine the code and increment priority. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-08 07:34 Message: Logged In: YES user_id=67709 Expand this patch to base64 encoded plain text. apply the second patch Decorate.py.diff2 to the original Decorate.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Thu Feb 20 18:38:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 20 21:30:28 2003 Subject: [ mailman-Patches-690448 ] MailList.py patch to fix a few bugs Message-ID: Patches item #690448, was opened at 2003-02-21 02:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=690448&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: MailList.py patch to fix a few bugs Initial Comment: There are bugs in MailList.py handling subscribe/unsbuscribe code. 1. Bug #677668 Subscription confirmation fails when a user chose different language in English list 2. When a user enter a latin/CJK name in full-name in Englush list. 3. Admin unsubscription notify is not sent. This patch fix these. (as far as my test goes) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=690448&group_id=103 From noreply at sourceforge.net Fri Feb 21 20:57:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 21 23:48:58 2003 Subject: [ mailman-Bugs-691039 ] Scrubber broken on bad base64 messages Message-ID: Bugs item #691039, was opened at 2003-02-22 15: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: Open Resolution: None 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=691039&group_id=103 From noreply at sourceforge.net Fri Feb 21 22:19:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 22 01:10:48 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 17:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 Category: None Group: None 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 From noreply at sourceforge.net Fri Feb 21 22:21:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 22 01:13:34 2003 Subject: [ mailman-Bugs-691039 ] Scrubber broken on bad base64 messages Message-ID: Bugs item #691039, was opened at 2003-02-22 15: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: Open Resolution: None 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: Simon Coggins (scoggins) Date: 2003-02-22 17: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 Fri Feb 21 23:05:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 22 01:56:57 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: 6 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-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 Feb 22 08:05:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 22 10:56:59 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: 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=691055&group_id=103 From noreply at sourceforge.net Sun Feb 23 04:15:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 23 07:06:38 2003 Subject: [ mailman-Bugs-593728 ] Traceback rebuilding archive Message-ID: Bugs item #593728, was opened at 2002-08-11 20:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open >Resolution: Works For Me Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback rebuilding archive Initial Comment: Witn Mailman 2.1b3, rebuilding a pipermail archive using $ bin/arch listname runs fine for 2 lists, but on the third one gives the following traceback: [...] Updating HTML for article 52 Updating HTML for article 53 Schreibe Archivzustand in Datei /home/mailman/archives/private/humor/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/home/mailman/Mailman/Archiver/pipermail.py", line 545, 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 "/home/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/home/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 159, in process part.set_payload(_("""\ File "/home/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Stefan Divjak (stdivjak) Date: 2003-02-23 14:15 Message: Logged In: YES user_id=483131 Workaround: - open the mbox-File in any Editor - search for "*=" - replace iso-encoded MIME-fields 'name*' and 'filename*' by plain text, removing the asterisk: name*="iso8859-15''Autobahngeb%FChrjpg%2Ejpg" -> name="Autobahngebuehr.jpg" ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-10 12:07 Message: Logged In: YES user_id=483131 Barry told me, that it is fixed in the current CVS version in September 2002, but this bug still appears in mailman 2.1.1 (using bin/arch on the attached mbox-file), so I switched the status to open again. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-09 06:26 Message: Logged In: YES user_id=12800 Thanks Stefan, I got your mbox file, which appeared to contain one message. That message has an unknown charset in its RFC 2047 Subject header. Mailman cvs seems to handle this file just fine, so I'm closing this as fixed in 2.1b5+ ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 20:11 Message: Logged In: YES user_id=483131 Just tried to rebuild the other archives: 4 of 21 mbox-files can't be rebuilt. There are two kinds of tracebacks: * "ASCII decoding error" (see above) * "Lookup error: unknown encoding" I'll send the archive causing the second kind of traceback to Barry, hence it contains somewhat internal information. ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2002-12-08 18:58 Message: Logged In: YES user_id=483131 Sorry for the long delay. I fiddled around with the 19MB mbox file, and cut out the part which causes this error (refer to the attached file). The traceback also appeared using 2.1b5. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:47 Message: Logged In: YES user_id=12800 I'm moving the bug report to pending since I haven't seen an update. I suspect this is fixed in current cvs. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-16 23:55 Message: Logged In: YES user_id=12800 Can you upload the .mbox file for the list you're regenerating? If not (perhaps because it's proprietary information), can you make it available for me to look at privately? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 From noreply at sourceforge.net Sun Feb 23 17:39:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 23 20:30:22 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: 6 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 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 Sun Feb 23 19:22:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 23 22:13:37 2003 Subject: [ mailman-Bugs-677668 ] Subscription confirmation fails Message-ID: Bugs item #677668, was opened at 2003-01-30 14:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=677668&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Subscription confirmation fails Initial Comment: If the list language is english, but a subscribing user chooses a different language (e.g. norwegian), the following error occurs when confirming the subscription: admin(5296): Traceback (most recent call last): admin(5296): File "/home/mailman/scripts/driver", line 87, in run_main admin(5296): main() admin(5296): File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main admin(5296): subscription_confirm(mlist, doc, cookie, cgidata) admin(5296): File "/home/mailman/Mailman/Cgi/confirm.py", line 331, in subscription_confirm admin(5296): op, addr, pw, digest, lang = mlist.ProcessConfirmation( admin(5296): File "/home/mailman/Mailman/MailList.py", line 1071, in ProcessConfirmation admin(5296): self.ApprovedAddMember(userdesc) admin(5296): File "/home/mailman/Mailman/MailList.py", line 900, in ApprovedAddMember admin(5296): msg = Message.OwnerNotification(self, subject, text) admin(5296): File "/home/mailman/Mailman/Message.py", line 257, in __init__ admin(5296): UserNotification.__init__(self, recips, sender, subject, text, lang) admin(5296): File "/home/mailman/Mailman/Message.py", line 203, in __init__ admin(5296): self['Subject'] = Header(subject, charset, header_name='Subject') admin(5296): File "/home/mailman/pythonlib/email/Header.py", line 164, in __init__ admin(5296): self.append(s, charset) admin(5296): File "/home/mailman/pythonlib/email/Header.py", line 230, in append admin(5296): ustr = unicode(s, incodec) admin(5296): UnicodeError: ASCII decoding error: ordinal not in range(128) The user then recieves the welcome-to-this-mailing-list email, but is not subscribed to the list. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-23 22:22 Message: Logged In: YES user_id=12800 Fixed in cvs via TK's patch # 690448 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=677668&group_id=103 From noreply at sourceforge.net Sun Feb 23 19:22:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 23 22:14:00 2003 Subject: [ mailman-Patches-690448 ] MailList.py patch to fix a few bugs Message-ID: Patches item #690448, was opened at 2003-02-20 21:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=690448&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: MailList.py patch to fix a few bugs Initial Comment: There are bugs in MailList.py handling subscribe/unsbuscribe code. 1. Bug #677668 Subscription confirmation fails when a user chose different language in English list 2. When a user enter a latin/CJK name in full-name in Englush list. 3. Admin unsubscription notify is not sent. This patch fix these. (as far as my test goes) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-23 22:22 Message: Logged In: YES user_id=12800 Applied, thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=690448&group_id=103 From noreply at sourceforge.net Sun Feb 23 20:34:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 23 23:26:09 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: 6 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 Tue Feb 25 05:57:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 25 08:48:57 2003 Subject: [ mailman-Patches-402100 ] have a nicer admin-address Message-ID: Patches item #402100, was opened at 2000-10-24 07:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=402100&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Fil (fill) Assigned to: Nobody/Anonymous (nobody) Summary: have a nicer admin-address Initial Comment: ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2003-02-25 10: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 07: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=300103&aid=402100&group_id=103 From noreply at sourceforge.net Tue Feb 25 17:25:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 25 20:16:41 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 01:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Wed Feb 26 21:33:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 27 01:24:21 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-27 05:33 Message: Logged In: YES user_id=67709 sorry for daily update but there was an error in i18n handling of '(no subject)' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 01:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Wed Feb 26 23:20:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 27 02:11:00 2003 Subject: [ mailman-Bugs-694216 ] Max KB of body not filtered when approving nonsubscriber msg Message-ID: Bugs item #694216, was opened at 2003-02-27 01:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=694216&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Bryan Thome (bxt) Assigned to: Nobody/Anonymous (nobody) Summary: Max KB of body not filtered when approving nonsubscriber msg Initial Comment: When tending to admin requests to allow a post by a non-subscriber there is no indication of the size of the message or if it violates the "Maximum length in Kb of a message body" setting. If the message is allowed there is no additional check to verify the message body size and the message is sent to the list regardless of byte size. version: 2.0.13 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=694216&group_id=103 From noreply at sourceforge.net Fri Feb 28 00:02:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 28 02:52:31 2003 Subject: [ mailman-Patches-694902 ] Fix MIME digest attachment Message-ID: Patches item #694902, was opened at 2003-02-28 08:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Fix MIME digest attachment Initial Comment: ToDigest.py in Mailman 2.1.1 was improved in handling plain text digest but there was a side effect in MIME digest. We should now use copy of Message instance because the original is scrubbed afterwards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103