From noreply at sourceforge.net Sat Aug 2 08:46:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Aug 2 10:46:21 2003 Subject: [ mailman-Bugs-781977 ] Attempt to invoke directory as as script Message-ID: Bugs item #781977, was opened at 2003-08-02 10:46 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=781977&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Attempt to invoke directory as as script Initial Comment: Package: mailman Version: 2.1.2-7 Log entries like the following appear with some regularity. ,----[ Excerpt from: /var/log/apache-ssl ] [Fri Aug 1 15:54:12 2003] [error] [client 128.242.232.130] attempt to invoke directory as script: /usr/lib/cgi-bin/mailman `---- -- System Information Debian Release: 3.0 Kernel Version: Linux lists 2.4.20-bf2.4 #1 Wed Dec 25 13:17:08 UTC 2002 i686 GNU/Linux Versions of the packages mailman depends on: ii cron 3.0pl1-72 management of regular background processing ii debconf 1.0.32 Debian configuration management system ii libc6 2.3.1-17 GNU C Library: Shared libraries and Timezone ii logrotate 3.5.9-8 Log rotation utility ii pwgen 2.03-1 Automatic Password generation ii python 2.2.3-3 An interactive high-level object-oriented la ii ucf 0.18 Update Configuration File: preserves user ch exim Not installed or no info ii postfix 2.0.13-2003070 A high-performance mail transport agent ^^^ (Provides virtual package mail-transport-agent) apache Not installed or no info ii apache-ssl 1.3.27.0-2 Versatile, high-performance HTTP server with ^^^ (Provides virtual package httpd) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=781977&group_id=103 From noreply at sourceforge.net Sat Aug 2 11:24:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Aug 2 13:24:57 2003 Subject: [ mailman-Bugs-782024 ] Private archives link error Message-ID: Bugs item #782024, was opened at 2003-08-02 17:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nicola Soranzo (soranzo) Assigned to: Nobody/Anonymous (nobody) Summary: Private archives link error Initial Comment: If I visit http://domain/mailman/private/listname/ all the links to the Thread, Subject, ... monthly archives are correct, but if the URL is http://domain/mailman/private/listname (without the trailing slash), the links are incorrect, eg.: http://domain/mailman/private/2003-July/thread.html (without the listname between private and the month). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_id=103 From noreply at sourceforge.net Sun Aug 3 13:11:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 3 15:11:41 2003 Subject: [ mailman-Feature Requests-782426 ] sign-up page enhancement Message-ID: Feature Requests item #782426, was opened at 2003-08-03 12:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782426&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: sign-up page enhancement Initial Comment: The signup webpage should include enough information so that people can know how to whitelist and/or filter mailing list email before they receive mail from the list server or list that they are subscribing to. This is particularly important for users who are using a challenge/response system to help keep spam out of their inbox, as they might not receive the confirmation request or any list email if they don't properly whitelist these emails before subscribing! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782426&group_id=103 From noreply at sourceforge.net Sun Aug 3 13:19:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 3 15:19:52 2003 Subject: [ mailman-Feature Requests-782427 ] subscription options at subscribe time Message-ID: Feature Requests item #782427, was opened at 2003-08-03 12:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782427&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: subscription options at subscribe time Initial Comment: Enable the subscriber to select subscription options when signing up for a list. For instance, if someone is already subscribed to a list from one email address (which might be an alias that goes to a team), but wants to add a second address that would be allowed to post to this list (e.g. the address of a team member), they want to subscribe the second address with the "no delivery" option enabled from the start. Presently they need to subscribe, then confirm, then go back and set "no delivery". This should be able to be done at subscription time via both the website signup page and via the email interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782427&group_id=103 From noreply at sourceforge.net Sun Aug 3 13:22:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 3 15:22:35 2003 Subject: [ mailman-Feature Requests-782429 ] admin moderation page view option cookie Message-ID: Feature Requests item #782429, was opened at 2003-08-03 12:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782429&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: admin moderation page view option cookie Initial Comment: Enable for a list moderator to select if they want to "view the details" of messages held for moderation, then remember that moderator's preference (via a cookie) so that when they next go to approve held postings, the page comes up as desired. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782429&group_id=103 From noreply at sourceforge.net Sun Aug 3 13:29:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 3 15:29:09 2003 Subject: [ mailman-Feature Requests-782434 ] moderation page upgrade Message-ID: Feature Requests item #782434, was opened at 2003-08-03 12:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782434&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: moderation page upgrade Initial Comment: When viewing in the "view all details" mode, the radio buttons for the action are at the top of the message, but the actual message (where you generally determine if the message should be sent to your list or not) is at the bottom. In many cases these are far enough apart that you have to scroll down to see the message, then scroll up to select the option. Scrolling up and down many times to approve/reject/discard many messages gets old. :-) Suggestions: 1) Enable the list owner to select if the radio buttons should appear at the top or the bottom of each message to be approved. Note: If the buttons are moved down, the text box for reject message should also be moved down. 2) Enable the list owner to select to have messages shown as text on the page, rather than in text scroll boxes (to eliminate even more mousing and scrolling...). 3) Enable these change per moderator rather than per list owner. (I'm guessing that this is a lot harder and that it won't be possible right now, but I wanted to suggest it here so that you think about how it might be possible.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782434&group_id=103 From noreply at sourceforge.net Sun Aug 3 13:32:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 3 15:32:17 2003 Subject: [ mailman-Feature Requests-782436 ] members per page on admin page Message-ID: Feature Requests item #782436, was opened at 2003-08-03 12:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782436&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: members per page on admin page Initial Comment: Put a radio button option on the membership page to allow list owners to change the number of members returned on each page. I suggest that the options include: 25 per page 50 per page 100 per page 200 per page 500 per page all subscribers on one page (use with caution if you have a big list!) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782436&group_id=103 From noreply at sourceforge.net Tue Aug 5 11:05:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 5 13:05:43 2003 Subject: [ mailman-Bugs-665732 ] List-Id should be one line. Message-ID: Bugs item #665732, was opened at 2003-01-10 15:05 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id should be one line. Initial Comment: If the List-Id: header gets splitted into several lines, which I could observe on lists I'm on which switched to mailman 2.1 now, it is getting harder to filter the list based on the fixed part of the list id. Filtering would need to look at more than one line. So a procmail pattern (procmail uses egrep an basically work on one line) like :0: *^List-Id:.* $ kmail-incoming would not work anymore reliably when the description of the mailinglist is getting longer. Before mailman 2.1 the above pattern was save against the changes in the description. I know that headers longer than one line are allowed, still I consider is a design bug at mailman does not necessrily need to make filtering harder at this point. ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:05 Message: Logged In: YES user_id=113859 I'm attaching a patch which fixes this bug against 2.1.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 From noreply at sourceforge.net Tue Aug 5 11:32:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 5 13:33:05 2003 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 10:01 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Tue Aug 5 11:40:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 5 13:40:25 2003 Subject: [ mailman-Patches-783651 ] Fix #726736 Message-ID: Patches item #783651, was opened at 2003-08-05 19:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=783651&group_id=103 Category: bounce processing Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Fix #726736 Initial Comment: Se the beginning of the patch itself and the bug description at http://sourceforge.net/tracker/index.php?func=detail&aid=726736&group_id=103&atid=100103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=783651&group_id=103 From noreply at sourceforge.net Tue Aug 5 11:41:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 5 13:41:44 2003 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 10:01 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:41 Message: Logged In: YES user_id=113859 I've submitted a patch for this to the patch tracker 783651 https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Tue Aug 5 18:13:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 5 20:13:21 2003 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 08:01 Message generated for change (Comment added) made by greglindahl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- >Comment By: Greg Lindahl (greglindahl) Date: 2003-08-06 00:13 Message: Logged In: YES user_id=612574 Thanks -- I see that you fixed all of them in your patch. This should be added to the 2.0.X series. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 17:41 Message: Logged In: YES user_id=113859 I've submitted a patch for this to the patch tracker 783651 https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 17:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Thu Aug 7 05:15:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 7 07:15:22 2003 Subject: [ mailman-Bugs-784700 ] 'make install' after 'make' modifies source tree Message-ID: Bugs item #784700, was opened at 2003-08-07 13:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784700&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: 'make install' after 'make' modifies source tree Initial Comment: With mailman 2.1.2 './configure' and 'make' run fine, but then I switched to the mailman user account to do 'make install'. It tried to unpack misc/email-2.5.1.tar.gz, misc/JapaneseCodecs-1.4.9.tar.gz and misc/KoreanCodecs-2.0.5.tar.gz, but this failed because the mailman user doesn't have write permission in the source tree. I think 'make install' shouldn't need to write to the source tree after 'make' was done. Either this has to be done during 'make' or to the /tmp directory. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784700&group_id=103 From noreply at sourceforge.net Thu Aug 7 05:33:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 7 07:33:32 2003 Subject: [ mailman-Bugs-784706 ] Clarify need for genaliases in UPGRADING Message-ID: Bugs item #784706, was opened at 2003-08-07 13:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: Clarify need for genaliases in UPGRADING Initial Comment: mailman-2.1.2/UPGRADING says: NOTE: When upgrading to Mailman 2.1beta1, you will need to regenerate your aliases files. There have been many changes to the alias names, the programs they map to, and the name of the wrapper script. See README. for details of making Mailman work with your mail server. I've upgraded from 2.0.13 to 2.1.2, this is not 2.1beta1, so I don't need to regenerate my aliases files. And the next paragraph says: To regenerate your aliases, use the bin/genaliases script. I've just learned that I don't need to update my aliases files, therefore this is only an information just in case I want to do it, but I don't want it now. To make this clear, you could write: NOTE: You will need to regenerate your aliases files. because this file is distributed with a Mailman version which needs the genaliases step. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_id=103 From noreply at sourceforge.net Thu Aug 7 05:33:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 7 07:33:52 2003 Subject: [ mailman-Bugs-784706 ] Clarify need for genaliases in UPGRADING Message-ID: Bugs item #784706, was opened at 2003-08-07 13:33 Message generated for change (Settings changed) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 4 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: Clarify need for genaliases in UPGRADING Initial Comment: mailman-2.1.2/UPGRADING says: NOTE: When upgrading to Mailman 2.1beta1, you will need to regenerate your aliases files. There have been many changes to the alias names, the programs they map to, and the name of the wrapper script. See README. for details of making Mailman work with your mail server. I've upgraded from 2.0.13 to 2.1.2, this is not 2.1beta1, so I don't need to regenerate my aliases files. And the next paragraph says: To regenerate your aliases, use the bin/genaliases script. I've just learned that I don't need to update my aliases files, therefore this is only an information just in case I want to do it, but I don't want it now. To make this clear, you could write: NOTE: You will need to regenerate your aliases files. because this file is distributed with a Mailman version which needs the genaliases step. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_id=103 From noreply at sourceforge.net Thu Aug 7 11:03:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 7 13:03:32 2003 Subject: [ mailman-Bugs-784888 ] Wrong domain in public archives Message-ID: Bugs item #784888, was opened at 2003-08-07 10:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_id=103 From noreply at sourceforge.net Thu Aug 7 22:14:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 8 00:14:59 2003 Subject: [ mailman-Bugs-785174 ] uncaught bounce notification (Symantec_AntiVirus_for_SMTP_GG Message-ID: Bugs item #785174, was opened at 2003-08-08 12:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785174&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: uncaught bounce notification (Symantec_AntiVirus_for_SMTP_GG Initial Comment: mm 2.1 doesn't detect the following bounce message Perhaps in this case it should ignore it as its only a temporary failure. Date: Fri, 08 Aug 2003 08:49:31 +0800 From: Symantec_AntiVirus_for_SMTP_Gateways@murdoch.edu.au To: imc-perth-bounces@lists.indymedia.org Subject: Delivery failure notification Your message with Subject: [imc-perth] a good feature story could not be delivered to the following recipients: m.sargeant@student.murdoch.edu.au 30051866@student.murdoch.edu.au Please do not resend your original message. Delivery attempts will continue to be made for 5 day(s). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785174&group_id=103 From noreply at sourceforge.net Fri Aug 8 09:37:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 8 11:37:38 2003 Subject: [ mailman-Bugs-785450 ] scripts/driver bug Message-ID: Bugs item #785450, was opened at 2003-08-08 10:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785450&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kevin N Carpenter (kevinc_63366) Assigned to: Nobody/Anonymous (nobody) Summary: scripts/driver bug Initial Comment: One of my primary list is broke. The other lists appear to be fine. Any help would be greatly appreciated! Note that this occurred in 2.1.0 - I upgraded to 2.1.2 but the problem still exist. Bug in Mailman version 2.1.2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 85, in main mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 124, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 583, in Load dict, e = self.__load(file) File "/usr/local/mailman/Mailman/MailList.py", line 556, in __load dict = loadfunc(fp) UnpicklingError: invalid load key, 'n'. ------------------------------------------------------------- ------------------- Python information: Variable Value sys.version 2.2.3 (#1, Aug 7 2003, 19:30:01) [GCC 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------------- ------------------- Environment variables: Variable Value PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) (Gentoo/Linux) PHP/4.3.1 SCRIPT_FILENAME /home/mailman/cgi-bin/admindb SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/admindb SERVER_SIGNATURE Apache/1.3.27 Server at mail.seaplace.org Port 80 REQUEST_METHOD GET HTTP_HOST www.seaplace.org PATH_INFO /reefkeepers SERVER_PROTOCOL HTTP/1.0 QUERY_STRING REQUEST_URI /mailman/admindb/reefkeepers HTTP_ACCEPT */* PATH_TRANSLATED /home/httpd/htdocs/reefkeepers HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Mon_AutoConfig_v1.02_STL; .NET CLR 1.0.3705; .NET CLR 1.1.4322) HTTP_CONNECTION keep-alive SERVER_NAME mail.seaplace.org REMOTE_ADDR 199.89.234.122 HTTP_X_FORWARDED_FOR 10.133.116.235 REMOTE_PORT 21100 HTTP_ACCEPT_LANGUAGE en-us HTTP_VIA 1.1 ics_server.monsanto.com (ICS 2.2.76) SERVER_ADDR 66.128.118.35 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate UNIQUE_ID PzPApEKAdiMAAF4RtrM DOCUMENT_ROOT /home/httpd/htdocs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785450&group_id=103 From noreply at sourceforge.net Sun Aug 10 10:47:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 10 12:47:27 2003 Subject: [ mailman-Feature Requests-786326 ] Rotation through moderators Message-ID: Feature Requests item #786326, was opened at 2003-08-10 16:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=786326&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Milos Popovic (milos_popovic) Assigned to: Nobody/Anonymous (nobody) Summary: Rotation through moderators Initial Comment: A useful moderation feature in LISTSERV, when multiple moderators are listed, is that it can deliver moderation requests to moderators in *rotation* (only one moderator at a time), thus reducing the individual workload. I've found this a useful feature to share the workload of verifying mostly filtered spam that's held for moderation on lists that need to accept outside posts and need to have a quick moderator approval turnaround time on posts. The quick turn-around time means moderation requests are sent immediately for each post, rather than just being bundled at the end of each day. It would be very useful to have such a feature (option to rotate through moderators, for the individual post moderation requests only) in MailMan. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=786326&group_id=103 From noreply at sourceforge.net Mon Aug 11 06:15:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 11 08:15:18 2003 Subject: [ mailman-Bugs-784888 ] Wrong domain in public archives Message-ID: Bugs item #784888, was opened at 2003-08-07 17:03 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-08-11 12:15 Message: Logged In: YES user_id=67709 Have you defined your (url_host, mail_host) pair in your mm_cfg.py ? You should state like: add_virtualhost('www.virtual.dom', 'mail.virtual.dom') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_id=103 From noreply at sourceforge.net Mon Aug 11 11:19:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 11 13:19:41 2003 Subject: [ mailman-Bugs-669201 ] feature: unified membership allow post list. Message-ID: Bugs item #669201, was opened at 2003-01-16 10:22 Message generated for change (Comment added) made by banerian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: feature: unified membership allow post list. Initial Comment: i host a variety of lists that obtain posts from members and non-members alike. they also have times where the email address they send from changes. i'd like the ability to create a global list of people that are allowed to post to lists and have it be enabled/disabled on a per-list basis. eg: list1 - use list members, extra people and GLOBAL_allow_list list2 - use list members, extra people only. ---------------------------------------------------------------------- Comment By: stefani banerian (banerian) Date: 2003-08-11 10:19 Message: Logged In: YES user_id=798204 in privacy options, it would be also good if regexp or globs worked in the configuration option "Addresses of members accepted for posting to this list without implicit approval requirement" without this ability to use regexp or globs, such as .*@my.domain.org allowing posts from certain domains is somewhat painful. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_id=103 From noreply at sourceforge.net Mon Aug 11 14:46:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 11 16:46:48 2003 Subject: [ mailman-Bugs-784888 ] Wrong domain in public archives Message-ID: Bugs item #784888, was opened at 2003-08-07 10:03 Message generated for change (Comment added) made by robbrandt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- >Comment By: Rob Brandt (robbrandt) Date: 2003-08-11 13:46 Message: Logged In: YES user_id=332197 The problem is resolved, with great help from Richard Barrett. For the sake of posterity, let the bug archives show: * Be sure you have proper virtual host mapping (add_virtualhost()) in mm_cfg.py; * Be sure that the list setting for "Host name this list prefers for email" is in fact your mail exchange address, not a base URL for browsing (which was my problem); * Run fix_url.py ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-08-11 05:15 Message: Logged In: YES user_id=67709 Have you defined your (url_host, mail_host) pair in your mm_cfg.py ? You should state like: add_virtualhost('www.virtual.dom', 'mail.virtual.dom') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_id=103 From noreply at sourceforge.net Mon Aug 11 15:25:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 11 17:25:35 2003 Subject: [ mailman-Patches-762130 ] web interface for editing archives Message-ID: Patches item #762130, was opened at 2003-06-27 18:05 Message generated for change (Comment added) made by aaboyd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=762130&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Adriane Boyd (aaboyd) Assigned to: Nobody/Anonymous (nobody) Summary: web interface for editing archives Initial Comment: This patch makes it possible for list administrators to edit their list archives through a web interface linked into the admin interface. A new cgi script called editarch allows administrators to browse by month and delete messages from the archives. The messages are immediately deleted from the mbox file, but because of the overhead in reprocessing archives, the archives aren't redone on-the-fly. Instead, a file is kept with a running list of recently edited archives and a nightly cron job does the reprocessing. The file location is configurable in mm_cfg. (Note: since it has to read through the mbox file message by message, pages will load slowly for lists with large archives.) In the mailman 2.1.2 source directory: patch -p1 < editarch-2.1.2-0.1.patch ---------------------------------------------------------------------- >Comment By: Adriane Boyd (aaboyd) Date: 2003-08-11 17:25 Message: Logged In: YES user_id=696276 Updated so that the permissions on the mbox file are set properly after editing. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=762130&group_id=103 From noreply at sourceforge.net Wed Aug 13 12:57:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 13 14:57:59 2003 Subject: [ mailman-Feature Requests-233766 ] wish: keep .htpasswd file from subscriber passwords Message-ID: Feature Requests item #233766, was opened at 2001-02-23 16:06 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=233766&group_id=103 Category: None Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: wish: keep .htpasswd file from subscriber passwords Initial Comment: Wish: It would be nice if you could have more webpages under the same access priviledges then a private mailman archive. Mailinglists are often used for collaboration of a group and mailman already implements a simple access control system. To additionally have theses passwords used for different authentification could be very useful not only for webpages. ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2003-08-13 20:57 Message: Logged In: YES user_id=113859 [ 402455 ] Generate .htaccess files containing username/passwd for list seems to be the same wish, to I'm closing this one as a dublicate. https://sourceforge.net/tracker/index.php?func=detail&aid=402455&group_id=103&atid=350103 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2001-03-02 07:30 Message: Logged In: YES user_id=12800 Sending over to Feature Requests. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=233766&group_id=103 From noreply at sourceforge.net Wed Aug 13 13:02:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 13 15:15:32 2003 Subject: [ mailman-Feature Requests-441317 ] allow for different reply-to address Message-ID: Feature Requests item #441317, was opened at 2001-07-14 20:19 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=441317&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: allow for different reply-to address Initial Comment: we have just started using Mailman and the one feature that we are used to with MajorDomo that we need is the ability to change the reply-to address in outgoing mail. this allows us to do the following: create a announcements list and then a second list for discussion of those announcements. the first then has its reply-to field set to the discussion list so that no one tries to reply to the announcement list. people who only want the annoucements and not the discussion sign up for only the one list. can this be done? ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-13 21:02 Message: Logged In: YES user_id=113859 If I understand your request correct, this can be done with Mailman 2.0.x and 2.1.x. Check the administration interface [General Options] -> reply_to_address ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-07-14 20:21 Message: Logged In: NO i submitted the above request and i dont see my email address in the report so here it is: ron@tao.ca ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=441317&group_id=103 From noreply at sourceforge.net Wed Aug 13 14:22:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 13 16:22:53 2003 Subject: [ mailman-Feature Requests-788314 ] personal option for explicit reply-to header Message-ID: Feature Requests item #788314, was opened at 2003-08-13 22:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=788314&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: personal option for explicit reply-to header Initial Comment: Some list members have a broken email reader that will not give them a list reply option. Outlook for instance. People using some email readers just don't use it, because the functionality is hidden (like many KMail users). They beg the adminstrator to mangle the reply-to header. Other users of course find that harmful. A per user (and per list?) option to set an explicit reply-to header to the list seems to be a good solution. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=788314&group_id=103 From noreply at sourceforge.net Thu Aug 14 18:52:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 14 20:52:46 2003 Subject: [ mailman-Patches-789015 ] Archiver.py patch for pipermail URL generation Message-ID: Patches item #789015, was opened at 2003-08-15 00:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=789015&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Archiver.py patch for pipermail URL generation Initial Comment: In Archiver.py, there is a function GetBaseArchiveURL() which is called whenever needed the archiver page url. While it is all right if (urlhost, mailhost) pair is one to one, if there are many to one urlhost->mailhost pairs, this function may return wrong host name. This patch trys to extract urlhost from private archive url and therefore does not suffer from multiple hostname for sigle email host. See more detailed discussion in the posting by Richard Barret in Mailman-Developers; http://mail.python.org/pipermail/mailman-developers/2003-August/015498.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=789015&group_id=103 From noreply at sourceforge.net Fri Aug 15 14:52:26 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 15 16:52:30 2003 Subject: [ mailman-Bugs-789501 ] README.MACOSX Message-ID: Bugs item #789501, was opened at 2003-08-15 13:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789501&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Robert Daeley (daeley) Assigned to: Nobody/Anonymous (nobody) Summary: README.MACOSX Initial Comment: The README.MACOSX file that came with the 2.1.2 download refers to this URL re "Kathleen Webb posted her experiences in getting Mailman running on Jaguar using Sendmail." -- http://mail.python.org/pipermail/mailman-users/2002-October/022947.html The URL should be: http://mail.python.org/pipermail/mailman-users/2002-October/022944.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789501&group_id=103 From noreply at sourceforge.net Fri Aug 15 21:49:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 15 23:49:53 2003 Subject: [ mailman-Feature Requests-789617 ] Administrative Interface > Privacy Options > Sender Filters Message-ID: Feature Requests item #789617, was opened at 2003-08-15 20:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=789617&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: Administrative Interface > Privacy Options > Sender Filters Initial Comment: > Will I have to unmoderate new members for the life > of this list, or can I hack the default behavior somehow? The answer is: Administrative Interface > Privacy options > Sender filters > By default, should new list member postings be moderated? Given the number of times this question has been posted to the mailman-users list, it does not seem to be intuitive that list moderation settings are found under: Privacy options > Sender filters I suggest that in the next release, directly in the Administrative Interface there be two sub-categories of: List Accessibility Options and Privacy Options The first one would contain the options that can restrict Access to the list as a whole (who can post, who can view the archives, who can see if this list even exists). The second one restricts access to Private subscriber information (obscure poster addresses in the archives or when remailing posts to the list subscribers, restricting who can get a list of subscribers, etc.) I feel that this would make it a lot easier for list managers to figure out where these options are within the list management interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=789617&group_id=103 From noreply at sourceforge.net Fri Aug 15 21:52:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 15 23:52:21 2003 Subject: [ mailman-Feature Requests-789618 ] Broadband viewing of list administration options Message-ID: Feature Requests item #789618, was opened at 2003-08-15 20:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=789618&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: Broadband viewing of list administration options Initial Comment: Provide a button to allow a list administrator to see all the list administrative options on one page, or to see the whole tree of options on one large page (and then you would click on the destination option to reach a page where you can change the setting). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=789618&group_id=103 From noreply at sourceforge.net Sat Aug 16 15:31:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Aug 16 17:31:22 2003 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 16:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Sat Aug 16 15:43:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Aug 16 17:43:16 2003 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 16:31 Message generated for change (Comment added) made by ventoux You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- >Comment By: Colin Allen (ventoux) Date: 2003-08-16 16:43 Message: Logged In: YES user_id=846026 ps - moving the various digest.mboxes freed up the blocked lists - too many messages with attachments in the digests for me to figure out exactly which one was causing the problem, but I'll be happy to forward copy of offending mbox to anyone interested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Mon Aug 18 06:20:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 18 08:20:55 2003 Subject: [ mailman-Patches-790494 ] built-in automatic discard Message-ID: Patches item #790494, was opened at 2003-08-18 12:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=790494&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: built-in automatic discard Initial Comment: This patch is a revision of #636412 (discard old pending post) script. While the script was to be run by cron, this patch gives full feature of 1. site wide default of MAX_DAYS_TO_HOLD in Defaults.py (mm_cfg.py). 2. list admin can set list specific max_days_to_hold through Web GUI 3. integreate in cron/checkdbs and reports the number of discarded messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=790494&group_id=103 From noreply at sourceforge.net Mon Aug 18 19:11:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 18 21:12:07 2003 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 17:31 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-18 21:11 Message: Logged In: YES user_id=12800 A better thing to do is to attach a .pck/.db pair of files for a shunted message. Then I can run it through my system and hopefully reproduce the bug. If the message contains sensitive information or you don't want to upload it for other reasons, please email them as attachments to me: barry@python.org. Make sure you put "Mailman" in the subject. ---------------------------------------------------------------------- Comment By: Colin Allen (ventoux) Date: 2003-08-16 17:43 Message: Logged In: YES user_id=846026 ps - moving the various digest.mboxes freed up the blocked lists - too many messages with attachments in the digests for me to figure out exactly which one was causing the problem, but I'll be happy to forward copy of offending mbox to anyone interested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Mon Aug 18 22:06:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 19 00:06:11 2003 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 17:31 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-19 00:06 Message: Logged In: YES user_id=12800 This was caused by a bug in the email package. It'll be fixed in email 2.5.4 and in Mailman 2.1.3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-18 21:11 Message: Logged In: YES user_id=12800 A better thing to do is to attach a .pck/.db pair of files for a shunted message. Then I can run it through my system and hopefully reproduce the bug. If the message contains sensitive information or you don't want to upload it for other reasons, please email them as attachments to me: barry@python.org. Make sure you put "Mailman" in the subject. ---------------------------------------------------------------------- Comment By: Colin Allen (ventoux) Date: 2003-08-16 17:43 Message: Logged In: YES user_id=846026 ps - moving the various digest.mboxes freed up the blocked lists - too many messages with attachments in the digests for me to figure out exactly which one was causing the problem, but I'll be happy to forward copy of offending mbox to anyone interested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Tue Aug 19 00:09:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 19 02:09:16 2003 Subject: [ mailman-Bugs-791012 ] Cosmetic: Held Posting section has no heading Message-ID: Bugs item #791012, was opened at 2003-08-19 15:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=791012&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Cosmetic: Held Posting section has no heading Initial Comment: Held posting section on cgi-bin/admindb has no heading. Attached patch will add heading "Posting Held for Approval" (or equivalent in list language). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=791012&group_id=103 From noreply at sourceforge.net Wed Aug 20 08:10:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 22 11:50:34 2003 Subject: [ mailman-Feature Requests-791928 ] digest filter options Message-ID: Feature Requests item #791928, was opened at 2003-08-20 07:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791928&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: digest filter options Initial Comment: Add an option on the *digest* settings page to automatically discard, bounce to the sender (with an explanatory message), or hold for moderator approval all messages with a subject that matches the list-created subject used on the outgoing digest. That way when you setup your digest options, you can easily select from several common methods of how listmanagers often want their list to handle replies from digest subscribers. Link to this setting from the page that has the other incoming message filtering options, so that when you are looking at your incoming message filtering options you notice/remember that you also have special filters relating to digests. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791928&group_id=103 From noreply at sourceforge.net Wed Aug 20 08:05:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 22 11:50:35 2003 Subject: [ mailman-Feature Requests-791923 ] filtering options for non-spam Message-ID: Feature Requests item #791923, was opened at 2003-08-20 07:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791923&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: filtering options for non-spam Initial Comment: Presently, the only content filtering option is for "spam filters", found at: mailman/admin//?VARHELP=privacy/spam/bounce_matching_headers If your listname gets a lot of spam requests (including spam requests sent "from" a subscriber, an increasingly common spam tactic triggered by a virus), the listowner may elect to discard messages that fail this filter, rather than forward them to the moderators to be manually deleted one by one. However, this then prevents the listowner from being able to add content filters such as: Subject: *-DIGEST* To keep digest subscribers from posting to the list without first changing the subject of their message. It would be nice to have 2 sets of filters, one set that can be used to trigger a discard (for spam), and another set that will be held and forwarded to the moderators. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=791923&group_id=103 From noreply at sourceforge.net Sat Aug 23 09:37:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Aug 24 21:25:59 2003 Subject: [ mailman-Feature Requests-793792 ] Options for the message approval page(s) Message-ID: Feature Requests item #793792, was opened at 2003-08-23 08:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=793792&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: Options for the message approval page(s) Initial Comment: On the generic message approval page (example http://mail.python.org/mailman/admindb/mailman-users ) you have the following options: ++++++++++++++++ Action to take on all these held messages: Defer Accept Reject Discard Preserve messages for the site administrator Forward messages (individually) to: Add to a sender filter Accepts Holds Rejects Discards Ban from ever subscribing to this mailing list ++++++++++++++++ When you elect to see all details of the message (example http://mail.python.org/mailman/admindb/mailman-users?details=all ) you only have the following subset of options: ++++++++++++++++ Defer Approve Reject Discard Preserve message for site administrator Additionally, forward this message to: ++++++++++++++++ Please include the options to add to the sender filter and to ban the sender on the "details=all" page. Also note that "accept" changed to "approve", and should be standardized on one or the other. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=793792&group_id=103 From noreply at sourceforge.net Mon Aug 25 01:40:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 25 03:41:22 2003 Subject: [ mailman-Patches-794537 ] Improve text/plain attachment handling Message-ID: Patches item #794537, was opened at 2003-08-25 16:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=794537&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Improve text/plain attachment handling Initial Comment: o Treating VERY large text attachment as inline can crash Mailman (and users' browsers, maybe). o In text/plain attachment lacks of Charset parameter, senders' process codes (EBCDIC, Shift_JIS etc.) are often used. Charsets same as first text part can not be assumed always. My patch handles text/plain parts as: 1. A text/plain part with 'attachment' Content-Disposition type is not inline. 2. A text/plain part without Charset parameter is not inline, except in non-multipart message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=794537&group_id=103 From noreply at sourceforge.net Mon Aug 25 09:22:07 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 25 11:22:26 2003 Subject: [ mailman-Feature Requests-464913 ] allow posters from another list Message-ID: Feature Requests item #464913, was opened at 2001-09-25 21:01 Message generated for change (Comment added) made by wstomv You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=464913&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: allow posters from another list Initial Comment: I have several related lists, each member of which should be able to post to the other lists. I'd like to see an enhancement to the 'posters' option so that a poster which starts with an @ would be assumed to be the description of a list, and if the poster is a member of that list, he will be allowed to submit the post without being held for approval. For example, the faculty list would allow posting by members of the faculty list and @staff, and the staff list by its members plus @faculty . John ---------------------------------------------------------------------- Comment By: Tom Verhoeff (wstomv) Date: 2003-08-25 17:22 Message: Logged In: YES user_id=126282 I support this request. Here is another example for using this feature. I am involved in some (not-for-profit) organizations. Typically such an organization has a board and some committees. It has a mailing list for all (and only) the members, and also additional lists for the board and each of the committees. You want the privacy setting on the board/committee lists to allow posting by all respective board/committee members without moderation. Furthermore, I want to allow unmoderated posting to the board/committee lists by all members, i.e. subscribers to the main members list. Only the respective board/committee members have access to the archive of their board/committee. Other members have no such access. Is there a simple way to realize this in the current Mailman version? ---------------------------------------------------------------------- Comment By: Greg Lindahl (lindahl) Date: 2001-11-07 20:56 Message: Logged In: YES user_id=57593 In majordomo this could be configured by specifying a list of files that were extra people who could post. It was useful in that fashion, and also for posters who used multiple accounts. Right now in mailman I think I'd have to add a fake user with email turned off to cover multiple accounts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=464913&group_id=103 From noreply at sourceforge.net Mon Aug 25 17:45:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 25 19:45:26 2003 Subject: [ mailman-Bugs-767596 ] mailman list archive links not working with virtual hosts Message-ID: Bugs item #767596, was opened at 2003-07-08 03:55 Message generated for change (Comment added) made by leftlink You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nick Hemsley (blackisha) Assigned to: Nobody/Anonymous (nobody) Summary: mailman list archive links not working with virtual hosts Initial Comment: any mailman page with a link to the archives page for a mailing-list on a virtual-host, points to the primary hostname, instead of pointing to the virtual-domain. try this page for an example of the problem http://itomic.com/mailman/listinfo/asaconsultants_itomic.com the Asaconsultants archives link points to http://earth.itomic.com/pipermail/asaconsultants_itomic.com/ which is the primary hostname of the server on which itomic.com resides. it should point to http://itomic.com/pipermail/asaconsultants_itomic.com p.s. this list was recently upgraded to 2.1.2 by make install-ing into a previously existing mailman (2.0.13) directory (it said things in make install about upgrading, so I assumed it was handling ok) ---------------------------------------------------------------------- Comment By: rich cowan (leftlink) Date: 2003-08-25 19:45 Message: Logged In: YES user_id=538509 This bug should renamed: "LIST Archive Links Broken After 2.1 Upgrade." That's because it is one of several problems with updating: it appears that on one machine where the list info is at: domain.org/cgi-bin/mailman/listinfo/nosi-steering the archives link for this list points to: domain.org/pipermail/ i.e. the list name vanishes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_id=103 From noreply at sourceforge.net Mon Aug 25 17:55:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 25 19:56:36 2003 Subject: [ mailman-Patches-795012 ] show_qfiles script to dump qfiles/*/*.pck Message-ID: Patches item #795012, was opened at 2003-08-25 19:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: show_qfiles script to dump qfiles/*/*.pck Initial Comment: The attached script takes a list of filenames from the qfiles tree on the command line, and dumps each one. Handy when queued messages are pickles rather than plain text, and it presents the same UI in both cases. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 From noreply at sourceforge.net Mon Aug 25 17:57:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 25 19:57:12 2003 Subject: [ mailman-Patches-795012 ] show_qfiles script to dump qfiles/*/*.pck Message-ID: Patches item #795012, was opened at 2003-08-25 19:55 Message generated for change (Comment added) made by gward You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: show_qfiles script to dump qfiles/*/*.pck Initial Comment: The attached script takes a list of filenames from the qfiles tree on the command line, and dumps each one. Handy when queued messages are pickles rather than plain text, and it presents the same UI in both cases. ---------------------------------------------------------------------- >Comment By: Greg Ward (gward) Date: 2003-08-25 19:57 Message: Logged In: YES user_id=14422 oops, this time I'll actually check the stupid "upload" checkbox... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 From noreply at sourceforge.net Mon Aug 25 19:40:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 25 21:41:37 2003 Subject: [ mailman-Patches-795012 ] show_qfiles script to dump qfiles/*/*.pck Message-ID: Patches item #795012, was opened at 2003-08-25 19:55 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Greg Ward (gward) Assigned to: Nobody/Anonymous (nobody) Summary: show_qfiles script to dump qfiles/*/*.pck Initial Comment: The attached script takes a list of filenames from the qfiles tree on the command line, and dumps each one. Handy when queued messages are pickles rather than plain text, and it presents the same UI in both cases. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-25 21:40 Message: Logged In: YES user_id=12800 Nice! Now, do you want to copyright assign to the FSF so I can add it to the distro? :) ---------------------------------------------------------------------- Comment By: Greg Ward (gward) Date: 2003-08-25 19:57 Message: Logged In: YES user_id=14422 oops, this time I'll actually check the stupid "upload" checkbox... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795012&group_id=103 From noreply at sourceforge.net Tue Aug 26 07:54:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 26 09:54:37 2003 Subject: [ mailman-Patches-795369 ] fix for contrib/check_perms_grsecurity.py Message-ID: Patches item #795369, was opened at 2003-08-26 10:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795369&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Arran Fraser (juliuspc) Assigned to: Nobody/Anonymous (nobody) Summary: fix for contrib/check_perms_grsecurity.py Initial Comment: contrib/check_perms_grsecurity.py saved the day for me while trying to get Mailman to work on my high-security Mandrake 9.1 server. However, I had to make a small change in order to make this script work, so I thought I should pass this on to save everyone else the trouble. On lines 67-69, an array binfilestopatch is declared. AFAIK this array is only used on line 146. However, these files are not in the current path, as the code assumes they are. There are more than one ways to fix this, the easiest of which was to change line 147 FROM filefd = open(script, "r") TO filefd = open("bin/" + script, "r") Hope this helps! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=795369&group_id=103 From noreply at sourceforge.net Tue Aug 26 23:23:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 27 01:23:18 2003 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 17:31 Message generated for change (Comment added) made by jaredmauch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- Comment By: jared mauch (jaredmauch) Date: 2003-08-27 01:23 Message: Logged In: YES user_id=131445 I'm seeing what appears to be a similar error related to unicode. i can send you .db and .pck files if it would help. mine is with mailman-2.1.2 Aug 27 01:12:03 2003 (24565) Uncaught runner exception: ASCII encoding error: ordinal not in range(128) Aug 27 01:12:03 2003 (24565) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 305, in process t = unicode(t, 'ascii', 'replace').encode('ascii') UnicodeError: ASCII encoding error: ordinal not in range(128) Aug 27 01:12:03 2003 (24565) SHUNTING: 1061961121.185183+0b73a771780f550a6c2e25855f37ea5f250ed212 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-19 00:06 Message: Logged In: YES user_id=12800 This was caused by a bug in the email package. It'll be fixed in email 2.5.4 and in Mailman 2.1.3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-18 21:11 Message: Logged In: YES user_id=12800 A better thing to do is to attach a .pck/.db pair of files for a shunted message. Then I can run it through my system and hopefully reproduce the bug. If the message contains sensitive information or you don't want to upload it for other reasons, please email them as attachments to me: barry@python.org. Make sure you put "Mailman" in the subject. ---------------------------------------------------------------------- Comment By: Colin Allen (ventoux) Date: 2003-08-16 17:43 Message: Logged In: YES user_id=846026 ps - moving the various digest.mboxes freed up the blocked lists - too many messages with attachments in the digests for me to figure out exactly which one was causing the problem, but I'll be happy to forward copy of offending mbox to anyone interested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Wed Aug 27 08:19:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 27 10:20:05 2003 Subject: [ mailman-Bugs-789897 ] Shunt clogged up - RFC2231 unicode problem? Message-ID: Bugs item #789897, was opened at 2003-08-16 17:31 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Colin Allen (ventoux) Assigned to: Nobody/Anonymous (nobody) Summary: Shunt clogged up - RFC2231 unicode problem? Initial Comment: Dozens of messages are backed up in my shunt directory with the message "TypeError: unicode() argument 2 must be string, not None" (full traceback example below). This seems very similar to a problem fixed by ber with 2.0.x earlier this year but I'm running 2.1.2 (on FreeBSD). I tried my best to apply a similar solution to Message.py but apparently I don't know enough about python to make it work. Here's a typical Traceback -- Aug 16 16:08:25 2003 (46338) Uncaught runner exception: unicode() argument 2 must be string, not None Aug 16 16:08:25 2003 (46338) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/ IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-27 10:19 Message: Logged In: YES user_id=12800 Please wait until 2.1.3 is released (whenever I can crawl out of SoBig consequences). If the bug persists, please submit a new one then. ---------------------------------------------------------------------- Comment By: jared mauch (jaredmauch) Date: 2003-08-27 01:23 Message: Logged In: YES user_id=131445 I'm seeing what appears to be a similar error related to unicode. i can send you .db and .pck files if it would help. mine is with mailman-2.1.2 Aug 27 01:12:03 2003 (24565) Uncaught runner exception: ASCII encoding error: ordinal not in range(128) Aug 27 01:12:03 2003 (24565) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 305, in process t = unicode(t, 'ascii', 'replace').encode('ascii') UnicodeError: ASCII encoding error: ordinal not in range(128) Aug 27 01:12:03 2003 (24565) SHUNTING: 1061961121.185183+0b73a771780f550a6c2e25855f37ea5f250ed212 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-19 00:06 Message: Logged In: YES user_id=12800 This was caused by a bug in the email package. It'll be fixed in email 2.5.4 and in Mailman 2.1.3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-08-18 21:11 Message: Logged In: YES user_id=12800 A better thing to do is to attach a .pck/.db pair of files for a shunted message. Then I can run it through my system and hopefully reproduce the bug. If the message contains sensitive information or you don't want to upload it for other reasons, please email them as attachments to me: barry@python.org. Make sure you put "Mailman" in the subject. ---------------------------------------------------------------------- Comment By: Colin Allen (ventoux) Date: 2003-08-16 17:43 Message: Logged In: YES user_id=846026 ps - moving the various digest.mboxes freed up the blocked lists - too many messages with attachments in the digests for me to figure out exactly which one was causing the problem, but I'll be happy to forward copy of offending mbox to anyone interested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789897&group_id=103 From noreply at sourceforge.net Thu Aug 28 14:45:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 28 16:47:06 2003 Subject: [ mailman-Patches-796950 ] Mails get shunt for no apparent reason Message-ID: Patches item #796950, was opened at 2003-08-28 13:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=796950&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Nadim Shaikli (shaikli) Assigned to: Nobody/Anonymous (nobody) Summary: Mails get shunt for no apparent reason Initial Comment: Here's the patch that was noted on this thread, http://mail.python.org/pipermail/mailman-developers/2003-August/015547.html I hope it makes it ASAP as it has solved a major problem for us and could be of use to others (there is a bug report with symptoms very similar to what we saw, bug #707610 among others). --- Scrubber.py.orig 2003-08-13 23:19:19.000000000 -0700 +++ Scrubber.py 2003-08-14 00:23:47.000000000 -0700 @@ -305,6 +305,8 @@ t = unicode(t, 'ascii', 'replace').encode('ascii') try: # Should use HTML-Escape, or try generalizing to UTF-8 + if len(charset) == 0: + charset = 'us-ascii' t = t.encode(charset, 'replace') except (UnicodeError, LookupError): t = t.encode(lcset, 'replace') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=796950&group_id=103 From noreply at sourceforge.net Fri Aug 29 00:45:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 29 02:45:14 2003 Subject: [ mailman-Bugs-797123 ] encode_ascii_prefixes was already deprecated Message-ID: Bugs item #797123, was opened at 2003-08-29 06:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=797123&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: encode_ascii_prefixes was already deprecated Initial Comment: During the course of improvement of i18n subject prefix, `encode_ascii_prefixes' was deprecated. It still apears on admin//languages screen. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=797123&group_id=103 From noreply at sourceforge.net Fri Aug 29 05:53:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 29 07:53:08 2003 Subject: [ mailman-Bugs-797232 ] senddigests can crash Message-ID: Bugs item #797232, was opened at 2003-08-29 13:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=797232&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests can crash Initial Comment: In certain circumstances the senddigests cron job can crash. Here is the traceback: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/ufs/sjoerd/src/Python/dist/src/Lib/encodings/__init__.py", line 69, in search_function globals(), locals(), _import_tail) ValueError: Empty module name The reason of the crash is that charset in the call to t.encode is the empty string. Why it is that, I don't know, and I don't have the email message that triggered it. But apparently it's possible, so should be protected against. This is with Python 2.3 and current CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=797232&group_id=103 From noreply at sourceforge.net Fri Aug 29 11:58:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 29 13:59:22 2003 Subject: [ mailman-Feature Requests-797436 ] subscription confirmation log access Message-ID: Feature Requests item #797436, was opened at 2003-08-29 10:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: subscription confirmation log access Initial Comment: Please create a system for mailing list owners to access the logs that prove that subscriptions were confirmed (opt-in confirmation). Ideally, this would be available both via the web administration page and via email, like all other list management tasks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_id=103