From noreply at sourceforge.net Fri Jul 4 07:20:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jul 4 09:20:55 2003 Subject: [ mailman-Bugs-765935 ] qrunner eat my disk inodes and kills my machine! Message-ID: Bugs item #765935, was opened at 2003-07-04 13:20 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=765935&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jon Haynes (senyahnoj) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner eat my disk inodes and kills my machine! Initial Comment: One of the mailman crontab scripts (I think qrunner) has been writing a new log file every minute since I installed mailman 4 months ago. 400,000 separate logfiles later, my /var partition fills up with the inodes of these empty files effectively disabling most of my favourite services. Nasty. Currently taking over 5 hours to clean up /var. I have disabled the mailman crontab. I'm using version 2.0.9-1 (RedHat RPM). Is this fixed in subsequent versions? Something like appending to an existing logfile would be nice. Anyone else using mailman, I'd advise giving your system a periodic 'df -i' just in case this miserable fate befalls you too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=765935&group_id=103 From noreply at sourceforge.net Fri Jul 4 08:04:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jul 4 10:05:07 2003 Subject: [ mailman-Bugs-765935 ] qrunner eat my disk inodes and kills my machine! Message-ID: Bugs item #765935, was opened at 2003-07-04 09:20 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=765935&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jon Haynes (senyahnoj) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner eat my disk inodes and kills my machine! Initial Comment: One of the mailman crontab scripts (I think qrunner) has been writing a new log file every minute since I installed mailman 4 months ago. 400,000 separate logfiles later, my /var partition fills up with the inodes of these empty files effectively disabling most of my favourite services. Nasty. Currently taking over 5 hours to clean up /var. I have disabled the mailman crontab. I'm using version 2.0.9-1 (RedHat RPM). Is this fixed in subsequent versions? Something like appending to an existing logfile would be nice. Anyone else using mailman, I'd advise giving your system a periodic 'df -i' just in case this miserable fate befalls you too. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-07-04 10:04 Message: Logged In: YES user_id=12800 You don't say what OS version you're using, although I'll assume it's some older RedHat variant. First, you should upgrade from 2.0.9 anyway, either to 2.0.13 or to 2.1.2 (my recommendation). I run both 2.0.x and 2.1 systems for years on RedHat 7.3 and 9 and have never seen this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=765935&group_id=103 From noreply at sourceforge.net Fri Jul 4 08:57:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jul 4 10:57:37 2003 Subject: [ mailman-Bugs-765935 ] qrunner eat my disk inodes and kills my machine! Message-ID: Bugs item #765935, was opened at 2003-07-04 13:20 Message generated for change (Comment added) made by senyahnoj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=765935&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jon Haynes (senyahnoj) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner eat my disk inodes and kills my machine! Initial Comment: One of the mailman crontab scripts (I think qrunner) has been writing a new log file every minute since I installed mailman 4 months ago. 400,000 separate logfiles later, my /var partition fills up with the inodes of these empty files effectively disabling most of my favourite services. Nasty. Currently taking over 5 hours to clean up /var. I have disabled the mailman crontab. I'm using version 2.0.9-1 (RedHat RPM). Is this fixed in subsequent versions? Something like appending to an existing logfile would be nice. Anyone else using mailman, I'd advise giving your system a periodic 'df -i' just in case this miserable fate befalls you too. ---------------------------------------------------------------------- >Comment By: Jon Haynes (senyahnoj) Date: 2003-07-04 14:57 Message: Logged In: YES user_id=815874 I'm using RedHat 7.3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-07-04 14:04 Message: Logged In: YES user_id=12800 You don't say what OS version you're using, although I'll assume it's some older RedHat variant. First, you should upgrade from 2.0.9 anyway, either to 2.0.13 or to 2.1.2 (my recommendation). I run both 2.0.x and 2.1 systems for years on RedHat 7.3 and 9 and have never seen this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=765935&group_id=103 From noreply at sourceforge.net Sun Jul 6 06:28:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jul 6 08:28:41 2003 Subject: [ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name} Message-ID: Bugs item #766667, was opened at 2003-07-06 15:28 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=766667&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 From noreply at sourceforge.net Mon Jul 7 21:32:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jul 7 23:32:28 2003 Subject: [ mailman-Feature Requests-604841 ] simulate bounce Message-ID: Feature Requests item #604841, was opened at 2002-09-04 19:26 Message generated for change (Comment added) made by tuma You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=604841&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Justin (returnthis) Assigned to: Nobody/Anonymous (nobody) Summary: simulate bounce Initial Comment: It would be great to add a "simulate invalid address" to the authorization page. e.g. along with the Defer/Accept/Reject/Discard options. This would simply send an invalid address message back to the sender. Usually used for spam emails with members only posting. Would greatly reduce spam as the invalid address would be removed by most automated spamming systems. ---------------------------------------------------------------------- Comment By: David Tuma (tuma) Date: 2003-07-07 21:32 Message: Logged In: YES user_id=64192 I agree - this would be a wonderful feature!! I recently had to change my "wide-open" list to a moderated list because the spam reached unprecedented / unacceptable levels. Many of my list members were dropping off the list because they couldn't afford to receive porn advertisements at their work email addresses any longer. Now that it's a moderated list, I have to login at least once daily to reject all the spam that is in the inbox. If I had a "Bounce" option in addition to the "Defer/Accept/Reject/Discard" options, this might help reduce the flow of spam in the future. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=604841&group_id=103 From noreply at sourceforge.net Mon Jul 7 23:31:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 01:31:11 2003 Subject: [ mailman-Patches-767565 ] Another alternative to SMART_ADDRESS_MATCH Message-ID: Patches item #767565, was opened at 2003-07-08 14:31 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=767565&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Another alternative to SMART_ADDRESS_MATCH Initial Comment: SMART_ADDRESS_MATCH and COLLAPSIBLE_DOMAINS (patch [526483]) treat subdomains of e-mail address as equivalent. ALIAS_DOMAINS directive of this patch is a map with keys for aliased domain and values for official (canonicalized) domain. Members' e-mail addresses are always cannonicalized internally. Aliased domain(s) of member address are treated equivalent to official domain when member try to login, to get or change options etc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=767565&group_id=103 From noreply at sourceforge.net Tue Jul 8 01:55:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 8 03:55:44 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 15:55 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=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) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_id=103 From noreply at sourceforge.net Thu Jul 10 06:49:26 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 10 08:49:29 2003 Subject: [ mailman-Bugs-769100 ] Ordinal not in range (128) Message-ID: Bugs item #769100, was opened at 2003-07-10 14:49 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=769100&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bram Dispa (bdispa) Assigned to: Nobody/Anonymous (nobody) Summary: Ordinal not in range (128) Initial Comment: Hi, One of my Mailman users reported this error.... --- 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 "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/admin.py", line 193, in main print doc.Format() File "/home/mailman/Mailman/htmlformat.py", line 331, in Format output.append(Container.Format(self, indent)) File "/home/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/home/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/home/mailman/Mailman/htmlformat.py", line 417, in Format output = output + Container.Format(self, indent+2) File "/home/mailman/Mailman/htmlformat.py", line 265, in Format return EMPTYSTRING.join(output) UnicodeError: ASCII decoding error: ordinal not in range (128) ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.2.1 (#1, Aug 30 2002, 12:15:30) [GCC 3.2 20020822 (Red Hat Linux Rawhide 3.2-4)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value HTTP_COOKIE cirao+admin=280200000069be5f0d3f73280000006138376 46337393163336638323531333231383336666537383163 62303535363161393364656666 SERVER_SOFTWARE Apache/1.3.23 (Unix) (Red- Hat/Linux) mod_ssl/2.8.7 OpenSSL/0.9.6b PHP/4.1.2 mod_perl/1.26 PYTHONPATH /home/mailman SCRIPT_FILENAME /home/mailman/cgi-bin/admin SERVER_ADMIN ***HIDDEN*** SCRIPT_NAME /admin SERVER_SIGNATURE REQUEST_METHOD GET HTTP_HOST ***HIDDEN*** PATH_INFO /cirao/members SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /admin/cirao/members HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) HTTP_REFERER http://***HIDDEN***/admin/cirao SERVER_NAME ***HIDDEN*** REMOTE_ADDR 213.224.83.46 HTTP_X_FORWARDED_FOR 213.118.173.252 REMOTE_PORT 52240 HTTP_ACCEPT_LANGUAGE en-us,en- gb;q=0.8,en;q=0.6,nl-be;q=0.4,nl;q=0.2 HTTP_VIA 1.1 ncasse02 (NetCache NetApp/5.3.1R3) PATH_TRANSLATED /home/mailman/cgi- bin/cirao/members SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 REMOTE_HOST ***HIDDEN*** HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR 80.84.234.55 DOCUMENT_ROOT /home/mailman ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=769100&group_id=103 From noreply at sourceforge.net Thu Jul 10 18:52:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 10 20:52:48 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by akuchling You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Thu Jul 10 19:00:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 10 21:00:24 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by akuchling You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 21:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Thu Jul 10 22:44:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jul 11 00:44:57 2003 Subject: [ mailman-Bugs-769484 ] Creating mailman failure Message-ID: Bugs item #769484, was opened at 2003-07-11 00:44 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=769484&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Barry Fawthrop (brif8) Assigned to: Nobody/Anonymous (nobody) Summary: Creating mailman failure Initial Comment: 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 1, Operation not permitted) Python information: ------------------------------- What is going on?? MTA = postfix ./configure --with-mail-gid=postfix --with-cgi-gid=nobody install went fine, followed all docs upto create list, and this failure?? Thanks Barry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=769484&group_id=103 From noreply at sourceforge.net Sun Jul 13 06:25:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jul 13 08:26:01 2003 Subject: [ mailman-Bugs-770506 ] bounce mail not included in bounce action notification Message-ID: Bugs item #770506, was opened at 2003-07-13 14:25 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=770506&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: bounce mail not included in bounce action notification Initial Comment: Hi! Instead of the usual bounce message which tells the reason for the bounce (e.g. 'user over quota') on which a list moderator can decide whether to remove a user or not, this bounce action notification only includes the original list mail that was sent to the user. Since I have received proper bounce action notifications later this problem may occur only in a german setup or my mailman upgrade happened after this incident. I tried to provoke a bounce action notification with my test list but apperantly there must be bounces for some while before that happens. I only sent a number of mails within some 20 minutes. Return-path: Envelope-to: bernhard@rainbow.bksys.at Delivery-date: Wed, 09 Jul 2003 12:01:10 +0200 Received: from mx0.gmx.de ([213.165.64.100] helo=mx0.gmx.net) by rainbow.bksys.at with smtp (Exim 3.36 #1 (Debian)) id 19aBl7-00063W-00 for ; Wed, 09 Jul 2003 12:01:09 +0200 Received: (qmail 22835 invoked by alias); 9 Jul 2003 10:00:39 -0000 Delivered-To: GMX delivery to darsie@gmx.at Received: (qmail 22648 invoked by uid 65534); 9 Jul 2003 10:00:38 -0000 Received: from rainbow.bksys.at (EHLO rainbow.bksys.at) (212.41.248.75) by mx0.gmx.net (mx004) with SMTP; 09 Jul 2003 12:00:38 +0200 Received: from s ([127.0.0.1] helo=rainbow.bksys.at ident=ident-is-useless) by rainbow.bksys.at with esmtp (Exim 3.36 #1 (Debian)) id 19aBk9-00063N-00 for ; Wed, 09 Jul 2003 12:00:09 +0200 Received: from s ([127.0.0.1] helo=rainbow.bksys.at ident=ident-is-useless) by rainbow.bksys.at with esmtp (Exim 3.36 #1 (Debian)) id 19aBk7-00063F-00 for ; Wed, 09 Jul 2003 12:00:07 +0200 Subject: =?iso-8859-1?q?Bounce_action_notification?= From: mailman@rainbow.bksys.at To: ac-owner@rainbow.bksys.at MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============76570886680946471==" Message-ID: Date: Wed, 09 Jul 2003 12:00:06 +0200 Precedence: bulk X-BeenThere: ac@rainbow.bksys.at X-Mailman-Version: 2.1.1 List-Id: =?iso-8859-1?q?Austria_Circle_-_=D6sterreic?= =?iso-8859-1?q?hische_Rainbow_mailing_list?= X-List-Administrivia: yes Sender: mailman-bounces@rainbow.hn.org Errors-To: mailman-bounces@rainbow.hn.org X-GMX-Antispam: 0 (Mail was not recognized as spam) X-Resent-By: Forwarder X-Resent-For: darsie@gmx.at X-Resent-To: bernhard@rainbow.bksys.at X-Spam-Status: No, hits=0.8 required=5.0 tests=MAILTO_WITH_SUBJ,NO_REAL_NAME version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) --===============76570886680946471== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Dies ist eine Mailman-Verst=E4ndigung betreffend die Unzustellbarkeit von Emails an eine bestimmte Adresse ("bounce"). Liste: AC Abonnent: c.vonwiller@utanet.at Vorgang: Abonnement disabled. Grund: Zu viele oder fatale Bounces = Die ausl=F6sende Nachricht ist weiter unten angeh=E4ngt. Fragen? Kontaktieren Sie den Mailman Systemverwalter unter mailman@rainbow.bksys.at. --===============76570886680946471== Content-Type: message/rfc822 MIME-Version: 1.0 From: ac-request@rainbow.bksys.at Subject: =?iso-8859-1?q?AC_Nachrichtensammlung=2C_Band_2=2C_Eintrag_5?= To: ac@rainbow.bksys.at Reply-To: ac@rainbow.bksys.at MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-BeenThere: ac@rainbow.bksys.at X-Mailman-Version: 2.1.1 Precedence: list List-Id: =?iso-8859-1?q?Austria_Circle_-_=D6sterreic?= =?iso-8859-1?q?hische_Rainbow_mailing_list?= List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ac-bounces@rainbow.bksys.at Errors-To: ac-bounces@rainbow.bksys.at Um Emails an die Liste AC zu schicken, schicken Sie diese an die Adresse ac@rainbow.bksys.at Um sich via Web von der Liste zu entfernen oder draufzusetzen: http://rainbow.bksys.at/mailman/listinfo/ac oder, via Email, schicken Sie eine Email mit dem Wort 'help' in Subject/Betreff oder im Text an ac-request@rainbow.bksys.at Sie koennen den Listenverwalter dieser Lister unter der Adresse ac-owner@rainbow.bksys.at erreichen Wenn Sie antworten, bitte editieren Sie die Subject/Betreff auf einen sinnvollen Inhalt der spezifischer ist als "Re: Contents of AC digest..." Meldungen des Tages: 1. Re: AC Nachrichtensammlung, Band 2, Eintrag 4 (Hela Sattler) ---------------------------------------------------------------------- Message: 1 Date: Tue, 8 Jul 2003 12:07:20 +0200 From: "Hela Sattler" Subject: [AC] Re: AC Nachrichtensammlung, Band 2, Eintrag 4 To: Message-ID: <001d01c34538$b8672b40$c3adb23e@Hela> Content-Type: text/plain; charset=3D"iso-8859-1" Lieber Bernie! Es wird immer geheimnisvoller. Diese Mail habe ich heute erhalten: >----- Original Message ----- >From: >To: >Sent: Tuesday, July 08, 2003 12:00 PM >Subject: AC Nachrichtensammlung, Band 2, Eintrag 4 ---------------------------------------------------------------------------- ---- >Meldungen des Tages: >1. August (Raphael Wegmann) >2. Re: AC Nachrichtensammlung, Band 2, Eintrag 3 (earth1) ---------------------------------------------------------------------------- ---- ...Welchen Eintrag habe ich da gemacht??? Gr=FC=DFe an Sherlock Holmes Hela ------------------------------ -- = Die oesterreichische Rainbow Mailingliste: ac@rainbow.bksys.at http://rainbow.hn.org/mailman/listinfo/ac Ende AC Nachrichtensammlung, Band 2, Eintrag 5 ********************************************** --===============76570886680946471==-- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=770506&group_id=103 From noreply at sourceforge.net Sun Jul 13 16:27:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jul 13 18:27:27 2003 Subject: [ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name} Message-ID: Bugs item #766667, was opened at 2003-07-06 14:28 Message generated for change (Comment added) made by darsie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 00:27 Message: Logged In: YES user_id=559942 appearently the same bug exists for unsubscribing or requesting a password reminder. e.g. at http://bksys.at/mailman/listinfo/test I'll see if there is already an update for debian/testing that fixes the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 From noreply at sourceforge.net Sun Jul 13 16:43:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jul 13 18:43:32 2003 Subject: [ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name} Message-ID: Bugs item #766667, was opened at 2003-07-06 14:28 Message generated for change (Comment added) made by darsie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 00:43 Message: Logged In: YES user_id=559942 The debian/unstable package 2.1.2-6 fixes both bugs. ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 00:27 Message: Logged In: YES user_id=559942 appearently the same bug exists for unsubscribing or requesting a password reminder. e.g. at http://bksys.at/mailman/listinfo/test I'll see if there is already an update for debian/testing that fixes the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 From noreply at sourceforge.net Tue Jul 15 09:03:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 11:03:37 2003 Subject: [ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name} Message-ID: Bugs item #766667, was opened at 2003-07-06 15:28 Message generated for change (Comment added) made by iku You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- >Comment By: Ivan Kurmanov (iku) Date: 2003-07-15 18:03 Message: Logged In: YES user_id=320488 Looks like this problem is *unstable* python problem. In my case fixed by installing a stable python version. ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 01:43 Message: Logged In: YES user_id=559942 The debian/unstable package 2.1.2-6 fixes both bugs. ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 01:27 Message: Logged In: YES user_id=559942 appearently the same bug exists for unsubscribing or requesting a password reminder. e.g. at http://bksys.at/mailman/listinfo/test I'll see if there is already an update for debian/testing that fixes the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_id=103 From noreply at sourceforge.net Tue Jul 15 12:55:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jul 15 14:55:32 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by akuchling You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 14:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 21:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Thu Jul 17 07:06:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 17 09:06:07 2003 Subject: [ mailman-Bugs-759842 ] Formatting archives that don't have newlines Message-ID: Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Formatting archives that don't have newlines Initial Comment: I have a problem (mostly with M$ Outlook users) that when a user sends a message without newlines in it (because their email client auto-displays it "properly" for them), the message gets stored just like this in the archives as expected. The problem is that when the message gets pulled up in the webpages, they will appear as one long line instead of being formatted to the size of the browser width. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 15:06 Message: Logged In: YES user_id=201573 Yep, I have this too. Did you get any possible resolution to this? I guess it should not be too difficult to add this functionality (maybe within the mail2html part of the conversion) to add a limit on width (I think there may be a HTML possibility to enforce this). I don't know python, unfortunately, to go trapsing through the mailman code. I'll take a look though... Anthony Carter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103 From noreply at sourceforge.net Thu Jul 17 07:19:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 17 09:19:50 2003 Subject: [ mailman-Bugs-759842 ] Formatting archives that don't have newlines Message-ID: Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Formatting archives that don't have newlines Initial Comment: I have a problem (mostly with M$ Outlook users) that when a user sends a message without newlines in it (because their email client auto-displays it "properly" for them), the message gets stored just like this in the archives as expected. The problem is that when the message gets pulled up in the webpages, they will appear as one long line instead of being formatted to the size of the browser width. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 15:19 Message: Logged In: YES user_id=201573 I notice that the archiver uses a 
 and
around the article (from mailmanhome/templates/en/article.html. The PRE tag says that no formatting should occur as it is preformatted...I wonder what would happen if that PRE disappeared somehow... the text comes from whatever defines %(body)s in the Python code somewhere. This mus also defines the PRE tag as it is not in the template. Anthony ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 15:06 Message: Logged In: YES user_id=201573 Yep, I have this too. Did you get any possible resolution to this? I guess it should not be too difficult to add this functionality (maybe within the mail2html part of the conversion) to add a limit on width (I think there may be a HTML possibility to enforce this). I don't know python, unfortunately, to go trapsing through the mailman code. I'll take a look though... Anthony Carter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103 From noreply at sourceforge.net Thu Jul 17 07:28:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jul 17 09:28:36 2003 Subject: [ mailman-Bugs-759842 ] Formatting archives that don't have newlines Message-ID: Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Formatting archives that don't have newlines Initial Comment: I have a problem (mostly with M$ Outlook users) that when a user sends a message without newlines in it (because their email client auto-displays it "properly" for them), the message gets stored just like this in the archives as expected. The problem is that when the message gets pulled up in the webpages, they will appear as one long line instead of being formatted to the size of the browser width. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 15:28 Message: Logged In: YES user_id=201573 Right, well removing the 
 tags in the file

$mailman/Mailman/Archiver/HyperArch.py

does not fix the problem. In fact, it makes it worse.
However, I have yet to see if it is possible to substitute
it with a tag that will dictate the width of the text.

Will keep you posted.

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 15:19

Message:
Logged In: YES 
user_id=201573

I notice that the archiver uses a 
 and 
 around
the article (from mailmanhome/templates/en/article.html. The
PRE tag says that no formatting should occur as it is
preformatted...I wonder what would happen if that PRE
disappeared somehow...

the text comes from whatever defines %(body)s in the Python
code somewhere. This mus also defines the PRE tag as it is
not in the template.

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 15:06

Message:
Logged In: YES 
user_id=201573

Yep, I have this too. Did you get any possible resolution to
this?

I guess it should not be too difficult to add this
functionality (maybe within the mail2html part of the
conversion) to add a limit on width (I think there may be a
HTML possibility to enforce this). I don't know python,
unfortunately, to go trapsing through the mailman code.

I'll take a look though...

Anthony Carter

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103

From noreply at sourceforge.net  Thu Jul 17 07:37:50 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Jul 17 09:37:55 2003
Subject: [ mailman-Bugs-759842 ] Formatting archives that don't have newlines
Message-ID: 

Bugs item #759842, was opened at 2003-06-24 16:23
Message generated for change (Comment added) made by karem_lore
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103

Category: Pipermail
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Pug Bainter (phelim_gervase)
Assigned to: Nobody/Anonymous (nobody)
Summary: Formatting archives that don't have newlines

Initial Comment:
I have a problem (mostly with M$ Outlook users) that
when a user sends a message without newlines in it
(because their email client auto-displays it "properly"
for them), the message gets stored just like this in
the archives as expected. The problem is that when the
message gets pulled up in the webpages, they will
appear as one long line instead of being formatted to
the size of the browser width.


----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 15:37

Message:
Logged In: YES 
user_id=201573

Found the solution!

In the file HyperArch.py in $mailmanhome/Mailman/Archiver

search for 
 and replace it with 
 (change
80 to whatever you want).

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 15:28

Message:
Logged In: YES 
user_id=201573

Right, well removing the 
 tags in the file

$mailman/Mailman/Archiver/HyperArch.py

does not fix the problem. In fact, it makes it worse.
However, I have yet to see if it is possible to substitute
it with a tag that will dictate the width of the text.

Will keep you posted.

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 15:19

Message:
Logged In: YES 
user_id=201573

I notice that the archiver uses a 
 and 
 around
the article (from mailmanhome/templates/en/article.html. The
PRE tag says that no formatting should occur as it is
preformatted...I wonder what would happen if that PRE
disappeared somehow...

the text comes from whatever defines %(body)s in the Python
code somewhere. This mus also defines the PRE tag as it is
not in the template.

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 15:06

Message:
Logged In: YES 
user_id=201573

Yep, I have this too. Did you get any possible resolution to
this?

I guess it should not be too difficult to add this
functionality (maybe within the mail2html part of the
conversion) to add a limit on width (I think there may be a
HTML possibility to enforce this). I don't know python,
unfortunately, to go trapsing through the mailman code.

I'll take a look though...

Anthony Carter

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103

From noreply at sourceforge.net  Sun Jul 20 12:29:16 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun Jul 20 14:29:20 2003
Subject: [ mailman-Bugs-774644 ] Pipermail ignores URL_HOST in attachment
	paths
Message-ID: 

Bugs item #774644, was opened at 2003-07-20 11:29
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=774644&group_id=103

Category: Pipermail
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Joel Peshkin (peshkin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Pipermail ignores URL_HOST in attachment paths

Initial Comment:


In a new mailman 2.1.2 installation, the URL_HOST is
set to one of the virtual domains hosted by the
webserver.  All of the email and web interfaces handle
that properly including most fuctions of pipermail
EXCEPT that URLs to attachments stored get
HOSTNAME/pipermail.... instead of URL_HOST/pipermail....



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=774644&group_id=103

From noreply at sourceforge.net  Mon Jul 21 09:59:25 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 21 11:59:29 2003
Subject: [ mailman-Bugs-744466 ] error message
Message-ID: 

Bugs item #744466, was opened at 2003-05-27 19:41
Message generated for change (Comment added) made by nizz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=744466&group_id=103

Category: nntp/news
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Robert Hinson (oppie)
Assigned to: Nobody/Anonymous (nobody)
Summary: error message

Initial Comment:
I get this error message.

From: Cron Daemon 
To: mailman@oppie.oppie.net
Subject: Cron  /usr/bin/python -
S /var/mailman/cron/gate_news

Traceback (innermost last):
  File "/var/mailman/cron/gate_news", line 222, in ?
    main()
  File "/var/mailman/cron/gate_news", line 203, in main
    process_lists(lock)
  File "/var/mailman/cron/gate_news", line 148, in 
process_lists
    conn, first, last = open_newsgroup(mlist)
  File "/var/mailman/cron/gate_news", line 75, in 
open_newsgroup
    password=mm_cfg.NNTP_PASSWORD)
  File "/var/mailman/Mailman/pythonlib/nntplib.py", line 
114, in __init__
    self.welcome = self.getresp()
  File "/var/mailman/Mailman/pythonlib/nntplib.py", line 
184, in getresp
    raise NNTPTemporaryError(resp)
Mailman.pythonlib.nntplib.NNTPTemporaryError: 400 
File exists writing SMstore
file -- throttling

I am running INN Version inn-2.3.2-5

Python version python-1.5.2-43.72

mailman version mailman-2.0.13-1

RedHat 7.2 
Linux oppie 2.4.18-27.7.x #1 Fri Mar 14 05:51:48 
EST 2003 i586 unknown

Can someone please help me figure this out?

Thanks.


----------------------------------------------------------------------

Comment By: Nis J?rgensen (nizz)
Date: 2003-07-21 15:59

Message:
Logged In: YES 
user_id=60889

This looks like your news server is malfunctioning. Can you
connect to it with a normal nntp client?

Apparently this is "normal" INN behavior when not shut down
properly. 

Anyway, this is probably not a mailman issue - I suggest
closing the bug.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=744466&group_id=103

From noreply at sourceforge.net  Mon Jul 21 10:17:04 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 21 12:17:07 2003
Subject: [ mailman-Bugs-775100 ] gate_news: Handling missing groups
Message-ID: 

Bugs item #775100, was opened at 2003-07-21 16:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=775100&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nis J?rgensen (nizz)
Assigned to: Nobody/Anonymous (nobody)
Summary: gate_news: Handling missing groups

Initial Comment:
At the moment, if a non-existing newsgroup is chosen
for mirroring, we break out of the loop:

    for listname in Utils.list_names():
[...]
        try:
            conn, first, last = open_newsgroup(mlist)
        except (socket.error, nntplib.NNTPError):
            break
[...]

I believe that, at least for some NNTPErrors, we should
do a "continue" instead.

My naive patch would be this: 

        try:
            conn, first, last = open_newsgroup(mlist)
        except nntplib.NNTPError:
            continue 
        except socket.error:
            break

But if people have good reason to break on
othernNTPErrors, we might want to do a more finegrained
check.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=775100&group_id=103

From noreply at sourceforge.net  Mon Jul 21 10:18:27 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 21 12:18:33 2003
Subject: [ mailman-Bugs-775100 ] gate_news: Handling missing groups
Message-ID: 

Bugs item #775100, was opened at 2003-07-21 16:17
Message generated for change (Settings changed) made by nizz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=775100&group_id=103

>Category: nntp/news
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nis J?rgensen (nizz)
Assigned to: Nobody/Anonymous (nobody)
Summary: gate_news: Handling missing groups

Initial Comment:
At the moment, if a non-existing newsgroup is chosen
for mirroring, we break out of the loop:

    for listname in Utils.list_names():
[...]
        try:
            conn, first, last = open_newsgroup(mlist)
        except (socket.error, nntplib.NNTPError):
            break
[...]

I believe that, at least for some NNTPErrors, we should
do a "continue" instead.

My naive patch would be this: 

        try:
            conn, first, last = open_newsgroup(mlist)
        except nntplib.NNTPError:
            continue 
        except socket.error:
            break

But if people have good reason to break on
othernNTPErrors, we might want to do a more finegrained
check.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=775100&group_id=103

From noreply at sourceforge.net  Mon Jul 21 17:45:12 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 21 19:45:20 2003
Subject: [ mailman-Bugs-596215 ] html bugs in 2.0.13
Message-ID: 

Bugs item #596215, was opened at 2002-08-16 18:57
Message generated for change (Comment added) made by netik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596215&group_id=103

Category: Web/CGI
Group: 2.0.x
Status: Open
Resolution: None
Priority: 1
Submitted By: Chuq Von Rospach (chuqui)
Assigned to: Nobody/Anonymous (nobody)
Summary: html bugs in 2.0.13

Initial Comment:
Ran into some HTML bugs in 2.0.13. For instance, going to 
the listinfo/mailman-subscribers page and subscribing, it 
returns the "confirmation is required" warning.

It looks good, but view source it. An unterminated " is in the 
body, not in the head.

While it seems to format okay in browsers, it's seriously 
broken HTML, and it's driving mod_layout nuts, since it 
depends on the body tags to do header/footer insertions 
right. I think there's one other generated page with similar 
problems, too, but I'm not sure which it is yet.



----------------------------------------------------------------------

Comment By: John Adams (netik)
Date: 2003-07-21 23:45

Message:
Logged In: YES 
user_id=61093

This also breaks things in an interesting way when you're 
attempting to change the background color of the subscribe 
results page (or any page, for that matter.)

The doc object is created in main is built in htmlformat.py:


        if self.title:
            output.append('%s%s' % (tab, 
self.title))
        output.append('%s' % tab)
        output.append('%s

The worst part is that this bug occurs on EVERY SINGLE PAGE 
that mailman generates!

You can fix this serious bug by commenting out the line:

        output.append('%s
in htmlformat.py, line #281 (at least in my version, which is
2.0.9.

Also, there is a secondary issue associated with page 
generation; lots of calls to doc.Format immediately set the 
bgcolor to #ffffff; There needs to be a way to set the global 
(or per-list) background color and not hardcode it in this way.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596215&group_id=103

From noreply at sourceforge.net  Thu Jul 24 04:09:05 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Jul 24 06:09:09 2003
Subject: [ mailman-Bugs-776850 ] German version: confusing interface
Message-ID: 

Bugs item #776850, was opened at 2003-07-24 12:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103

Category: Web/CGI
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jan Kellermann (werk21)
Assigned to: Nobody/Anonymous (nobody)
Summary: German version: confusing interface

Initial Comment:
In the membership area are two submit buttons:
"Submit your Changes" and "set". The 2nd on is to set 
everyone's moderation bit.
In the german version they are "?nderungen vornehmen" 
and "?nderung ?bernehmen" which is too similar, leading 
users to wrongly submit.

Please change this in the language-module.

thx Jan Kellermann

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103

From noreply at sourceforge.net  Thu Jul 24 04:13:33 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Jul 24 06:13:38 2003
Subject: [ mailman-Bugs-776850 ] German version: confusing interface
Message-ID: 

Bugs item #776850, was opened at 2003-07-24 12:09
Message generated for change (Comment added) made by werk21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103

Category: Web/CGI
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jan Kellermann (werk21)
Assigned to: Nobody/Anonymous (nobody)
Summary: German version: confusing interface

Initial Comment:
In the membership area are two submit buttons:
"Submit your Changes" and "set". The 2nd on is to set 
everyone's moderation bit.
In the german version they are "?nderungen vornehmen" 
and "?nderung ?bernehmen" which is too similar, leading 
users to wrongly submit.

Please change this in the language-module.

thx Jan Kellermann

----------------------------------------------------------------------

>Comment By: Jan Kellermann (werk21)
Date: 2003-07-24 12:13

Message:
Logged In: YES 
user_id=737219

BTW you can please change 
"Membership Management" in "Mitgliederverwaltung" 
and "Privacy Options" in "Sicherheitseinstellungen"
as used in older versions. :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103

From noreply at sourceforge.net  Thu Jul 24 06:53:09 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu Jul 24 08:53:22 2003
Subject: [ mailman-Bugs-776850 ] German version: confusing interface
Message-ID: 

Bugs item #776850, was opened at 2003-07-24 06:09
Message generated for change (Settings changed) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103

Category: Web/CGI
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jan Kellermann (werk21)
>Assigned to: Peer Heinlein (pheinlein)
Summary: German version: confusing interface

Initial Comment:
In the membership area are two submit buttons:
"Submit your Changes" and "set". The 2nd on is to set 
everyone's moderation bit.
In the german version they are "?nderungen vornehmen" 
and "?nderung ?bernehmen" which is too similar, leading 
users to wrongly submit.

Please change this in the language-module.

thx Jan Kellermann

----------------------------------------------------------------------

Comment By: Jan Kellermann (werk21)
Date: 2003-07-24 06:13

Message:
Logged In: YES 
user_id=737219

BTW you can please change 
"Membership Management" in "Mitgliederverwaltung" 
and "Privacy Options" in "Sicherheitseinstellungen"
as used in older versions. :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103

From noreply at sourceforge.net  Fri Jul 25 04:02:38 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Jul 25 06:02:44 2003
Subject: [ mailman-Bugs-777444 ] mailmanctl doesn't setgroups when run as
	root
Message-ID: 

Bugs item #777444, was opened at 2003-07-25 10:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=777444&group_id=103

Category: security/privacy
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Barrett (ppsys)
Assigned to: Nobody/Anonymous (nobody)
Summary: mailmanctl doesn't setgroups when run as root

Initial Comment:
When mailmanctl is executed as root the checkprivs
function performs setgid and setuid to reduce the
process privileges.

But mailmanctl fails to set the supplemental groups of
the process to those of the setuid'ed user, effectively
leaving the
processes with the same group privileges as root and,
potentially, without the group privileges of the
setuid'ed user.

This patch uses os.setgroups() to fix that.

Problem definition and solution by Jonas Meurer.

I'm just filing the bug fix for him.

Apply the patch from within the Mailman build directory
with:

patch -p1 < path-to-patch-file

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=777444&group_id=103

From noreply at sourceforge.net  Sat Jul 26 15:58:37 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat Jul 26 17:58:41 2003
Subject: [ mailman-Bugs-778237 ] Invitations/Confirmations need expire info
Message-ID: 

Bugs item #778237, was opened at 2003-07-26 17:58
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=778237&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: Invitations/Confirmations need expire info

Initial Comment:
Both subscription invitations and subscription
confirmation messages fail to indicate when they will
expire.  Folks get confused when stale confirmations
don't work.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778237&group_id=103

From noreply at sourceforge.net  Sun Jul 27 22:00:33 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 00:00:37 2003
Subject: [ mailman-Bugs-778728 ] mm-handler: addresses are case-sensitive
Message-ID: 

Bugs item #778728, was opened at 2003-07-28 13:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: mm-handler: addresses are case-sensitive

Initial Comment:
A message to List-request@listhost (capitalized) causes
error message "Returned mail: List unknown":

> Your mail for List-request@listhost could not be sent:
> 	no list named "List" is known by listhost
<>


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_id=103

From noreply at sourceforge.net  Mon Jul 28 03:18:23 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 05:18:26 2003
Subject: [ mailman-Feature Requests-778815 ] Hide "other subscriptions" of
	members from owner
Message-ID: 

Feature Requests item #778815, was opened at 2003-07-28 18:18
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=778815&group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Hide "other subscriptions" of members from owner

Initial Comment:
On Mailman-2.1.2, list owner(s) can view "List of other
subscriptions" of list members accessing members'
option pages.

This seems not to be allowed.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=778815&group_id=103

From noreply at sourceforge.net  Mon Jul 28 07:44:29 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 09:44:32 2003
Subject: [ mailman-Patches-778929 ] templates/cs/listinfo.html: Small
	grammar fix
Message-ID: 

Patches item #778929, was opened at 2003-07-28 13:44
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=778929&group_id=103

Category: internationalization
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Rudolf Cejka (cejkar)
Assigned to: Nobody/Anonymous (nobody)
Summary: templates/cs/listinfo.html: Small grammar fix

Initial Comment:
Changed prohl?dnou to prohl?dnout.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=778929&group_id=103

From noreply at sourceforge.net  Mon Jul 28 11:10:59 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 13:11:04 2003
Subject: [ mailman-Bugs-778728 ] mm-handler: addresses are case-sensitive
Message-ID: 

Bugs item #778728, was opened at 2003-07-28 04:00
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: mm-handler: addresses are case-sensitive

Initial Comment:
A message to List-request@listhost (capitalized) causes
error message "Returned mail: List unknown":

> Your mail for List-request@listhost could not be sent:
> 	no list named "List" is known by listhost
<>


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-07-28 17:10

Message:
Logged In: YES 
user_id=75166

Changing line 200 of the mm-handler Perl script from:

    $list = $addr;

to read:

   $list = lc $addr;

will fix this problem.

mm-handler is an unsupported contribution and has other
potential
problems which can lead to mail loss.

There is an alernative Python implementation of this
approach which is more tightly integrated with MM and does
not have the same defects: see MM patch #64481

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_id=103

From noreply at sourceforge.net  Mon Jul 28 11:14:36 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 13:14:41 2003
Subject: [ mailman-Bugs-778728 ] mm-handler: addresses are case-sensitive
Message-ID: 

Bugs item #778728, was opened at 2003-07-28 04:00
Message generated for change (Comment added) made by ppsys
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: mm-handler: addresses are case-sensitive

Initial Comment:
A message to List-request@listhost (capitalized) causes
error message "Returned mail: List unknown":

> Your mail for List-request@listhost could not be sent:
> 	no list named "List" is known by listhost
<>


----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-07-28 17:14

Message:
Logged In: YES 
user_id=75166

The Python version is see MM patch #644810 (not see MM patch
#64481); sorry for the typo

----------------------------------------------------------------------

Comment By: Richard Barrett (ppsys)
Date: 2003-07-28 17:10

Message:
Logged In: YES 
user_id=75166

Changing line 200 of the mm-handler Perl script from:

    $list = $addr;

to read:

   $list = lc $addr;

will fix this problem.

mm-handler is an unsupported contribution and has other
potential
problems which can lead to mail loss.

There is an alernative Python implementation of this
approach which is more tightly integrated with MM and does
not have the same defects: see MM patch #64481

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_id=103

From noreply at sourceforge.net  Mon Jul 28 17:39:34 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 19:39:37 2003
Subject: [ mailman-Bugs-779230 ] SBC/SWBell bounces not being caught
Message-ID: 

Bugs item #779230, was opened at 2003-07-28 18:39
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=779230&group_id=103

Category: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Pug Bainter (phelim_gervase)
Assigned to: Nobody/Anonymous (nobody)
Summary: SBC/SWBell bounces not being caught

Initial Comment:
This was reported in 2.0.x and closed. It is still a 
problem in 2.1.x.

The two styles I've seen that aren't caught are:

==========================================
Message from sbcglobal.net.
Unable to deliver message to the following address(es).
     
:
Sorry, your message to morganavandya@sbcglobal.net 
cannot be delivered.  This account is over quota.

==========================================
and:
==========================================
Message from swbell.net.
Unable to deliver message to the following address(es).
     
:
This user doesn't have a swbell.net account 
(khemail@swbell.net) [-9]



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=779230&group_id=103

From noreply at sourceforge.net  Mon Jul 28 17:59:59 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon Jul 28 20:00:05 2003
Subject: [ mailman-Bugs-759842 ] Formatting archives that don't have newlines
Message-ID: 

Bugs item #759842, was opened at 2003-06-24 09:23
Message generated for change (Comment added) made by phelim_gervase
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103

Category: Pipermail
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Pug Bainter (phelim_gervase)
Assigned to: Nobody/Anonymous (nobody)
Summary: Formatting archives that don't have newlines

Initial Comment:
I have a problem (mostly with M$ Outlook users) that
when a user sends a message without newlines in it
(because their email client auto-displays it "properly"
for them), the message gets stored just like this in
the archives as expected. The problem is that when the
message gets pulled up in the webpages, they will
appear as one long line instead of being formatted to
the size of the browser width.


----------------------------------------------------------------------

>Comment By: Pug Bainter (phelim_gervase)
Date: 2003-07-28 18:59

Message:
Logged In: YES 
user_id=484284

Please note that the 
 doesn't seem to work 
for many Internet Explorer users. I think it is supported in IE 
6.x and later.

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 08:37

Message:
Logged In: YES 
user_id=201573

Found the solution!

In the file HyperArch.py in $mailmanhome/Mailman/Archiver

search for 
 and replace it with 
 (change
80 to whatever you want).

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 08:28

Message:
Logged In: YES 
user_id=201573

Right, well removing the 
 tags in the file

$mailman/Mailman/Archiver/HyperArch.py

does not fix the problem. In fact, it makes it worse.
However, I have yet to see if it is possible to substitute
it with a tag that will dictate the width of the text.

Will keep you posted.

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 08:19

Message:
Logged In: YES 
user_id=201573

I notice that the archiver uses a 
 and 
 around
the article (from mailmanhome/templates/en/article.html. The
PRE tag says that no formatting should occur as it is
preformatted...I wonder what would happen if that PRE
disappeared somehow...

the text comes from whatever defines %(body)s in the Python
code somewhere. This mus also defines the PRE tag as it is
not in the template.

Anthony

----------------------------------------------------------------------

Comment By: Anthony Carter (karem_lore)
Date: 2003-07-17 08:06

Message:
Logged In: YES 
user_id=201573

Yep, I have this too. Did you get any possible resolution to
this?

I guess it should not be too difficult to add this
functionality (maybe within the mail2html part of the
conversion) to add a limit on width (I think there may be a
HTML possibility to enforce this). I don't know python,
unfortunately, to go trapsing through the mailman code.

I'll take a look though...

Anthony Carter

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103

From noreply at sourceforge.net  Wed Jul 30 01:25:57 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Jul 30 03:26:01 2003
Subject: [ mailman-Bugs-780051 ] senddigests crashes when a whole message is
	discarded
Message-ID: 

Bugs item #780051, was opened at 2003-07-30 16:25
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=780051&group_id=103

Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Hatuka*nezumi (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: senddigests crashes when a whole message is discarded

Initial Comment:
Traceback (most recent call last):
  File "/usr/local/mailman/cron/senddigests", line 94, in ?
    main()
  File "/usr/local/mailman/cron/senddigests", line 86,
in main
    mlist.send_digest_now()
  File "/usr/local/mailman/Mailman/Digester.py", line
60, in send_digest_now
    ToDigest.send_digests(self, 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
179, in process
    raise DiscardMessage
Mailman.Errors.DiscardMessage


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780051&group_id=103

From noreply at sourceforge.net  Wed Jul 30 06:09:17 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed Jul 30 08:09:20 2003
Subject: [ mailman-Bugs-780171 ] "unknown encoding" in senddigests
Message-ID: 

Bugs item #780171, was opened at 2003-07-30 14:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780171&group_id=103

Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Ervin N?meth (nemethe)
Assigned to: Nobody/Anonymous (nobody)
Summary: "unknown encoding" in senddigests

Initial Comment:
Traceback (most recent call last):
  File "/usr/local/mailman/cron/senddigests", line 94, in ?
    main()
  File "/usr/local/mailman/cron/senddigests", line 86,
in main
    mlist.send_digest_now()
  File "/usr/local/mailman/Mailman/Digester.py", line
60, in send_digest_now
    ToDigest.send_digests(self, mboxfp)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
123, in send_digests
    send_i18n_digests(mlist, mboxfp)
  File
"/usr/local/mailman/Mailman/Handlers/ToDigest.py", line
295, 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 689, in get_filename
    return unicode(newvalue[2], newvalue[0])
LookupError: unknown encoding


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780171&group_id=103

From noreply at sourceforge.net  Thu Jul 31 23:51:28 2003
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri Aug  1 01:51:32 2003
Subject: [ mailman-Bugs-740453 ] encoding problems (1/3)
Message-ID: 

Bugs item #740453, was opened at 2003-05-20 22:32
Message generated for change (Comment added) made by hatukanezumi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=740453&group_id=103

Category: mail delivery
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Fil (filfil)
Assigned to: Nobody/Anonymous (nobody)
Summary: encoding problems (1/3)

Initial Comment:
May 20 11:47:10 2003 (8944) Uncaught runner exception: ASCII 
decoding error: or
May 20 11:47:10 2003 (8944) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in 
_oneloop
    self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in 
_onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 
218, in _dispo
    res = Results(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 
75, in __init_
    subj = make_header(decode_header(subj)).__unicode__()
  File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in 
make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in 
append
    ustr = unicode(s, incodec, errors)
UnicodeError: ASCII decoding error: ordinal not in range(128)

May 20 11:47:10 2003 (8944) SHUNTING: 
1052919608.508467+145b45eb26201772a1a52c3



----------------------------------------------------------------------

Comment By: Hatuka*nezumi (hatukanezumi)
Date: 2003-08-01 14:51

Message:
Logged In: YES 
user_id=529503

This is regenerated on 2.1.2 by a message with raw-8bit subject.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=740453&group_id=103