Mailman-coders September 2004

mailman-coders@python.org

2 participants
67 discussions

[ mailman-Bugs-1031729 ] Messages with empty subject line will not be delivered

by SourceForge.net

Bugs item #1031729, was opened at 2004-09-21 08:13 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=1031729&group_… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Ralf Laue (laue) Assigned to: Nobody/Anonymous (nobody) Summary: Messages with empty subject line will not be delivered Initial Comment: In MailCommandHandler.py, splitsubj = string.split(subject) is called. If, however subject is empty, this leads to an error like: File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 163, in ParseMailCommands splitsubj = string.split(subject) File "/usr/lib/python2.2/string.py", line 117, in split return s.split(sep, maxsplit) AttributeError : 'NoneType' object has no attribute 'split' A possible solution could be to insert if (subject == None): subject = ''" before string.split(subject) is called. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1031729&group_…

16 years, 6 months

[ mailman-Bugs-1030228 ] Mass Subscribe address with control character - can't delete

by SourceForge.net

Bugs item #1030228, was opened at 2004-09-18 05:28 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Mass Subscribe address with control character - can't delete Initial Comment: Mailman 2.1.4 We mass subscribed an automatically generated list of addresses. One of these contained an ascii Vertical-Tab character. The (somewhat munged for privacy) address in the mass subscribe list was lauxxxxxher(a)comcast.net<VT>rixxxxxher where <VT> represents ascii Vertical Tab (hex 0B). The address was subscribed OK and then noticed to be bad. We followed the link from the member list to that member's option page an attempted to unsubscribe it and "encountered a bug". This happened twice in succession and then a third time about an hour later. The error log entry from the first try is attached (with the same address munging). Another list administrator tried the same thing the next morning and that time it worked. We don't know why what we think was the same unsubscribe procedure didn't work 3 times and then worked the next day. the following is in Utils.py # TBD: what other characters should be disallowed? _badchars = re.compile(r'[][()<>|;^,/\200-\377]') A fix might be to add the range \000-\037 to the _badchars re, but this may not be correct. It is not clear whether they should be allowed. RFC 2822 allows "non white space" control characters in domain-literals, but not in local-parts of addresses. However, RFC 2821 (SMTP) says: A domain (or domain name) consists of one or more dot-separated components. These components ("labels" in DNS terminology) are restricted for SMTP purposes to consist of a sequence of letters, digits, and hyphens drawn from the ASCII character set. Thus, it seems that for Mailman purposes it would be safe to not allow any of \000-\037 in addresses. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-21 00:55 Message: Logged In: YES user_id=67709 sorry, I am now updating the patch. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2004-09-20 20:47 Message: Logged In: YES user_id=1123998 I see the patch changes Utils.py as follows: -_badchars = re.compile(r'[][()<>|;^,/\200-\377]') +_badchars = re.compile(r'[][()<>|;^,\000-\037\200-\377]') Per discussion on mailman-developers list, I think \177 should also be disallowed: +_badchars = re.compile(r'[][()<>|;^,\000-\037\177-\377]') ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-20 05:20 Message: Logged In: YES user_id=67709 uploading a patch to fix this and other. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2004-09-18 05:54 Message: Logged In: YES user_id=110886 As a side note, if you have problems with illegal characters in subscribed addresses, here's the relevant FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.013.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_…

16 years, 6 months

[ mailman-Bugs-1030228 ] Mass Subscribe address with control character - can't delete

by SourceForge.net

Bugs item #1030228, was opened at 2004-09-17 22:28 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Mass Subscribe address with control character - can't delete Initial Comment: Mailman 2.1.4 We mass subscribed an automatically generated list of addresses. One of these contained an ascii Vertical-Tab character. The (somewhat munged for privacy) address in the mass subscribe list was lauxxxxxher(a)comcast.net<VT>rixxxxxher where <VT> represents ascii Vertical Tab (hex 0B). The address was subscribed OK and then noticed to be bad. We followed the link from the member list to that member's option page an attempted to unsubscribe it and "encountered a bug". This happened twice in succession and then a third time about an hour later. The error log entry from the first try is attached (with the same address munging). Another list administrator tried the same thing the next morning and that time it worked. We don't know why what we think was the same unsubscribe procedure didn't work 3 times and then worked the next day. the following is in Utils.py # TBD: what other characters should be disallowed? _badchars = re.compile(r'[][()<>|;^,/\200-\377]') A fix might be to add the range \000-\037 to the _badchars re, but this may not be correct. It is not clear whether they should be allowed. RFC 2822 allows "non white space" control characters in domain-literals, but not in local-parts of addresses. However, RFC 2821 (SMTP) says: A domain (or domain name) consists of one or more dot-separated components. These components ("labels" in DNS terminology) are restricted for SMTP purposes to consist of a sequence of letters, digits, and hyphens drawn from the ASCII character set. Thus, it seems that for Mailman purposes it would be safe to not allow any of \000-\037 in addresses. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2004-09-20 13:47 Message: Logged In: YES user_id=1123998 I see the patch changes Utils.py as follows: -_badchars = re.compile(r'[][()<>|;^,/\200-\377]') +_badchars = re.compile(r'[][()<>|;^,\000-\037\200-\377]') Per discussion on mailman-developers list, I think \177 should also be disallowed: +_badchars = re.compile(r'[][()<>|;^,\000-\037\177-\377]') ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-19 22:20 Message: Logged In: YES user_id=67709 uploading a patch to fix this and other. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2004-09-17 22:54 Message: Logged In: YES user_id=110886 As a side note, if you have problems with illegal characters in subscribed addresses, here's the relevant FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.013.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_…

16 years, 6 months

[ mailman-Patches-1003070 ] Decode original subject in post acknowledgement

by SourceForge.net

Patches item #1003070, was opened at 2004-08-04 06:26 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1003070&group_… Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Decode original subject in post acknowledgement Initial Comment: Original subject line in post acknowledgement message will be decoded and be converted. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-20 12:23 Message: Logged In: YES user_id=67709 Fixed in CVS: revision: 2.14.2.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1003070&group_…

16 years, 6 months

[ mailman-Bugs-998609 ] can subscribe with CR+LF in email address

by SourceForge.net

Bugs item #998609, was opened at 2004-07-27 10:13 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=998609&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: can subscribe with CR+LF in email address Initial Comment: With Mailman 2.1.3 (didn't test with newer versions) it is possible to subscribe with an email address which ends with CR+LF. A browser bug made it possible to enter this into the single line entry field, but Mailman should check this. A quick test shows that CR+LF is possible in the middle of an email address, too, but of course this only works when confirmation check is disabled. Unsubscribing or changing the email address wasn't possible, because there are checks against this strange address. Only manually removing all dictionary entries with 'withlist' helped. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-20 05:27 Message: Logged In: YES user_id=67709 A patch is uploaded in: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_… Can you test it ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=998609&group_i…

16 years, 6 months

[ mailman-Bugs-1030228 ] Mass Subscribe address with control character - can't delete

by SourceForge.net

Bugs item #1030228, was opened at 2004-09-18 05:28 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Mass Subscribe address with control character - can't delete Initial Comment: Mailman 2.1.4 We mass subscribed an automatically generated list of addresses. One of these contained an ascii Vertical-Tab character. The (somewhat munged for privacy) address in the mass subscribe list was lauxxxxxher(a)comcast.net<VT>rixxxxxher where <VT> represents ascii Vertical Tab (hex 0B). The address was subscribed OK and then noticed to be bad. We followed the link from the member list to that member's option page an attempted to unsubscribe it and "encountered a bug". This happened twice in succession and then a third time about an hour later. The error log entry from the first try is attached (with the same address munging). Another list administrator tried the same thing the next morning and that time it worked. We don't know why what we think was the same unsubscribe procedure didn't work 3 times and then worked the next day. the following is in Utils.py # TBD: what other characters should be disallowed? _badchars = re.compile(r'[][()<>|;^,/\200-\377]') A fix might be to add the range \000-\037 to the _badchars re, but this may not be correct. It is not clear whether they should be allowed. RFC 2822 allows "non white space" control characters in domain-literals, but not in local-parts of addresses. However, RFC 2821 (SMTP) says: A domain (or domain name) consists of one or more dot-separated components. These components ("labels" in DNS terminology) are restricted for SMTP purposes to consist of a sequence of letters, digits, and hyphens drawn from the ASCII character set. Thus, it seems that for Mailman purposes it would be safe to not allow any of \000-\037 in addresses. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-20 05:20 Message: Logged In: YES user_id=67709 uploading a patch to fix this and other. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2004-09-18 05:54 Message: Logged In: YES user_id=110886 As a side note, if you have problems with illegal characters in subscribed addresses, here's the relevant FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.013.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_…

16 years, 6 months

[ mailman-Bugs-1028975 ] checkdbs remainders for not existing requests

by SourceForge.net

Bugs item #1028975, was opened at 2004-09-16 04:40 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1028975&group_… Category: command line scripts Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Alberto Marconi (albertomarconi) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs remainders for not existing requests Initial Comment: checkdbs sends remainders to list owners concerning pending requests which do not exist. It happens on new lists which are missing the request.pck file. The count of the pending requests is -1. The NumRequestsPending() function returns -1 if the request.pck file is missing. The following patch correct this problem: --- checkdbs.orig 2004-09-13 18:36:31.000000000 +0200 +++ checkdbs 2004-09-16 05:33:27.000000000 +0200 @@ -96,7 +96,7 @@ del mlist.hold_and_cmd_autoresponses [sender] # Only here have we changed the list's database mlist.Save() - if count: + if count > 0: i18n.set_language(mlist.preferred_language) realname = mlist.real_name text = Utils.maketext( ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-19 09:27 Message: Logged In: YES user_id=67709 see http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.038.htp this is fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1028975&group_…

16 years, 6 months

[ mailman-Bugs-1004091 ] "-1 Mailman moderator request(s) waiting"

by SourceForge.net

Bugs item #1004091, was opened at 2004-08-05 17:54 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1004091&group_… Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Lucian Smith (luciansmith) Assigned to: Nobody/Anonymous (nobody) Summary: "-1 Mailman moderator request(s) waiting" Initial Comment: Mailman mailed this to me today. I have no idea why. I'm running 2.1.5: --------- From: mailman-bounces(a)evolution.genetics.washington.edu To: mailman-owner(a)evolution.genetics.washington.edu Subject: -1 Mailman moderator request(s) waiting Date: Thu, 05 Aug 2004 08:00:01 -0700 Sender: mailman-bounces(a)gs.washington.edu Message-ID: <mailman.0.1091718001.15981.mailman(a)evolution.genetics.washington.edu> The Mailman(a)evolution.genetics.washington.edu mailing list has -1 request(s) waiting for your consideration at: http://evolution.genetics.washington.edu/mailman/admindb/mailman Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. --------- First of all, the URL given doesn't work (it takes me to the general http://evolution.gs.washington.edu/mailman/listinfo page), secondly, I don't think 'mailman' is an actual mailing list that we have, and thirdly, 'negative one'? That's just wacky. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-19 09:26 Message: Logged In: YES user_id=67709 See http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.038.htp This bug is fixed in CVS. ---------------------------------------------------------------------- Comment By: neth (neth) Date: 2004-09-19 06:54 Message: Logged In: YES user_id=1124447 Same problem here. I even got an empty subscription request. Has somebody any idea, what is causing this problem? We're using Mailman 2.1.5 on debian. One of the mails i got: >From mailman-bounces(a)www.XXX.de Sun Sep 19 08:00:08 2004 Return-path: <mailman-bounces(a)XXX.de> Envelope-to: XXX(a)XXX.de Received: from localhost ([127.0.0.1] helo=project.UTUM.local ident=mailman) by project.UTUM.local with esmtp (Exim 3.35 #1 (Debian)) id 1C8uk4-00062l-00 for <XXX(a)XXX.de>; Sun, 19 Sep 2004 08:00:08 +0200 Received: from localhost ([127.0.0.1] helo=project.UTUM.local ident=mailman) by project.UTUM.local with esmtp (Exim 3.35 #1 (Debian)) id 1C8uk2-00061X-00 for <ws2005-owner(a)XXX.de>; Sun, 19 Sep 2004 08:00:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: -1 Ws2005 moderator request(s) waiting From: ws2005-bounces(a)XXX.de To: ws2005-owner(a)XXX.de Message-ID: <mailman.12.1095573602.23049.ws2005(a)XXX.de> Date: Sun, 19 Sep 2004 08:00:02 +0200 Precedence: bulk X-BeenThere: ws2005(a)XXX.de X-Mailman-Version: 2.1.5 List-Id: ws2005.XXX.de X-List-Administrivia: yes Sender: mailman-bounces(a)XXX.de Errors-To: mailman-bounces(a)XXX.de X-UID: 79 X-Length: 1469 The Ws2005(a)XXX.de mailing list has -1 request(s) waiting for your consideration at: https://www.XXX.de/mailman/admindb/ws2005 Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1004091&group_…

16 years, 6 months

[ mailman-Bugs-1004091 ] "-1 Mailman moderator request(s) waiting"

by SourceForge.net

Bugs item #1004091, was opened at 2004-08-05 19:54 Message generated for change (Comment added) made by neth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1004091&group_… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Lucian Smith (luciansmith) Assigned to: Nobody/Anonymous (nobody) Summary: "-1 Mailman moderator request(s) waiting" Initial Comment: Mailman mailed this to me today. I have no idea why. I'm running 2.1.5: --------- From: mailman-bounces(a)evolution.genetics.washington.edu To: mailman-owner(a)evolution.genetics.washington.edu Subject: -1 Mailman moderator request(s) waiting Date: Thu, 05 Aug 2004 08:00:01 -0700 Sender: mailman-bounces(a)gs.washington.edu Message-ID: <mailman.0.1091718001.15981.mailman(a)evolution.genetics.washington.edu> The Mailman(a)evolution.genetics.washington.edu mailing list has -1 request(s) waiting for your consideration at: http://evolution.genetics.washington.edu/mailman/admindb/mailman Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. --------- First of all, the URL given doesn't work (it takes me to the general http://evolution.gs.washington.edu/mailman/listinfo page), secondly, I don't think 'mailman' is an actual mailing list that we have, and thirdly, 'negative one'? That's just wacky. ---------------------------------------------------------------------- Comment By: neth (neth) Date: 2004-09-19 08:54 Message: Logged In: YES user_id=1124447 Same problem here. I even got an empty subscription request. Has somebody any idea, what is causing this problem? We're using Mailman 2.1.5 on debian. One of the mails i got: >From mailman-bounces(a)www.XXX.de Sun Sep 19 08:00:08 2004 Return-path: <mailman-bounces(a)XXX.de> Envelope-to: XXX(a)XXX.de Received: from localhost ([127.0.0.1] helo=project.UTUM.local ident=mailman) by project.UTUM.local with esmtp (Exim 3.35 #1 (Debian)) id 1C8uk4-00062l-00 for <XXX(a)XXX.de>; Sun, 19 Sep 2004 08:00:08 +0200 Received: from localhost ([127.0.0.1] helo=project.UTUM.local ident=mailman) by project.UTUM.local with esmtp (Exim 3.35 #1 (Debian)) id 1C8uk2-00061X-00 for <ws2005-owner(a)XXX.de>; Sun, 19 Sep 2004 08:00:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: -1 Ws2005 moderator request(s) waiting From: ws2005-bounces(a)XXX.de To: ws2005-owner(a)XXX.de Message-ID: <mailman.12.1095573602.23049.ws2005(a)XXX.de> Date: Sun, 19 Sep 2004 08:00:02 +0200 Precedence: bulk X-BeenThere: ws2005(a)XXX.de X-Mailman-Version: 2.1.5 List-Id: ws2005.XXX.de X-List-Administrivia: yes Sender: mailman-bounces(a)XXX.de Errors-To: mailman-bounces(a)XXX.de X-UID: 79 X-Length: 1469 The Ws2005(a)XXX.de mailing list has -1 request(s) waiting for your consideration at: https://www.XXX.de/mailman/admindb/ws2005 Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1004091&group_…

16 years, 6 months

[ mailman-Patches-872068 ] Decorate.py patch

by SourceForge.net

Patches item #872068, was opened at 2004-01-07 00:46 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=872068&group_i… Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Decorate.py patch Initial Comment: Here is a patch which was defered and not included in 2.1.4 for Decorate.py. This fixes most of the footer-in-the-attachment problem by 1. convert header, body and footer into unicode 2. then concatnate them 3. try encode with the list charset 4. if fail, encode with the message charset 5. if both attempts fail, make the footer attachment. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-18 08:41 Message: Logged In: YES user_id=67709 committed (new revision: 2.21.2.4) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=872068&group_i…

16 years, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders September 2004