Mailman 3 November 2002 - Mailman-Developers

[ mailman-Bugs-640664 ] autowrap lines over 1000 chars
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #640664, was opened at 2002-11-19 07:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_i… Category: nntp/news Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Chris Dudley (dudleyc) Assigned to: Nobody/Anonymous (nobody) Summary: autowrap lines over 1000 chars Initial Comment: NNTP has a maximum line length of 1000 chars. emails do not have the same restriction. Would it be possible for the script which posts emails to the mailing list to autowrap all the emails at 1000 characters so that they would still be valid nntp posts? Currently i'm getting a fair few error 441 returns from NNTP because some emails exceed the line length limit. It could wrap at the last space or hyphon before the 1000th character, or something similar. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_i…

1 0

[ mailman-Bugs-641436 ] traceback for set nomail for non-member
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #641436, was opened at 2002-11-20 15:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641436&group_i… Category: None Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Marilyn Davis (marilyndavis) Assigned to: Nobody/Anonymous (nobody) Summary: traceback for set nomail for non-member Initial Comment: If a non-member of a list sends a mail message to the request address to "set nomail on passwd", the non-member gets a traceback and the admin gets an "unexpected mailman error" message. Instead, the MailCommandHandler probably wants to catch the exception and suggest to the non-user that she joins the list before she turns off her mail stream. I did this accidentally, first with an unknown password and the second time with the admin's password. Each traceback is a little different. I hope this is helpful. Thank you, Marilyn Davis The MailCommandHandler.py >From t2-request(a)localhost.localdomain Tue Nov 19 14:24:13 2002 Date: Tue, 19 Nov 2002 13:31:01 -0800 From: t2-request(a)localhost.localdomain To: marilyn(a)localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address <t2- request(a)localhost.localdomain>. To obtain instructions on valid Mailman email commands, send email to <t2-request(a)localhost.localdomain> with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to <t2- admin(a)localhost.localdomain>. The following is a detailed description of the problems. >>>>> Subject line ignored: >>>>> Re: Mailman results for T2 ***** set nomail on XXXXXXXX >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at <t2- admin(a)localhost.localdomain>. The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 376, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/home/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError >From t2-request(a)localhost.localdomain Tue Nov 19 14:24:19 2002 Date: Tue, 19 Nov 2002 13:32:01 -0800 From: t2-request(a)localhost.localdomain To: marilyn(a)localhost.localdomain Subject: Mailman results for T2 This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address <t2- request(a)localhost.localdomain>. To obtain instructions on valid Mailman email commands, send email to <t2-request(a)localhost.localdomain> with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to <t2- admin(a)localhost.localdomain>. The following is a detailed description of the problems. ***** set nomail on (the admin password) >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at <t2- admin(a)localhost.localdomain>. The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 235, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 412, in ProcessSetCmd self.SetUserOption(sender, option_info[args[0]], value) File "/home/mailman/Mailman/MailList.py", line 206, in SetUserOption user = self.GetUserCanonicalAddress(user) File "/home/mailman/Mailman/MailList.py", line 174, in GetUserCanonicalAddress cpuser = self.GetUserSubscribedAddress(member) File "/home/mailman/Mailman/MailList.py", line 159, in GetUserSubscribedAddress member = string.lower(member) File "/usr/local/lib/python2.2/string.py", line 54, in lower return s.lower() AttributeError: 'NoneType' object has no attribute 'lower' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=641436&group_i…

1 0

[ mailman-Bugs-640775 ] Qrunner suddenly doesn't work anymore
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #640775, was opened at 2002-11-19 11:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_i… Category: command line scripts Group: 2.0.x Status: Open Resolution: Works For Me >Priority: 1 Submitted By: David Weisgerber (davidweisgerber) Assigned to: Nobody/Anonymous (nobody) Summary: Qrunner suddenly doesn't work anymore Initial Comment: Since I checked my e-mail-account today I had over 1000 new mails where my cron daemon worries about those errors with your qrunner and listinfo.py: (1) "Traceback (most recent call last): File "/home/mailman/cron/qrunner", line 84, in ? from Mailman import Utils EOFError: EOF read where object expected" (2) "Traceback (most recent call last): File "/home/mailman/cron/gate_news", line 40, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 36, in ? from Mailman import Utils EOFError: EOF read where object expected" Don't know why, I didn't changed something on the machine and there is noone who could change something. Hard disk space is also okay. So I couldn't figure out where the problem was but I hope you can fix it, the web page shows your 'A bug in mailman' page and this is a cat from /logs/error: "Oct 01 10:10:46 2002 (12542) listinfo: no such list "csi172": Oct 01 10:11:05 2002 (12546) Someone tried to access the admin interface for a non-existent list: csi172 Nov 19 18:10:17 2002 admin(9683): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9683): [----- Mailman Version: 2.0.11 -----] admin(9683): [----- Traceback ------] admin(9683): Traceback (most recent call last): admin(9683): File "/home/mailman/scripts/driver", line 90, in run_main admin(9683): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9683): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9683): from Mailman import Utils admin(9683): EOFError: EOF read where object expected admin(9683): [----- Python Information -----] admin(9683): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9683): sys.executable = /usr/bin/python admin(9683): sys.prefix = /usr admin(9683): sys.exec_prefix= /usr admin(9683): sys.path = /usr admin(9683): sys.platform = linux-i386 admin(9683): [----- Environment Variables -----] admin(9683): PATH_INFO: /kutro admin(9683): PYTHONPATH: /home/mailman admin(9683): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9683): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9683): SERVER_ADMIN: root@localhost admin(9683): SCRIPT_NAME: /mailman/listinfo admin(9683): SERVER_SIGNATURE: <ADDRESS>Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80</ADDRESS> admin(9683): REQUEST_METHOD: GET admin(9683): HTTP_HOST: md.2y.net admin(9683): HTTP_KEEP_ALIVE: 300 admin(9683): SERVER_PROTOCOL: HTTP/1.1 admin(9683): QUERY_STRING: admin(9683): REQUEST_URI: /mailman/listinfo/kutro admin(9683): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9683): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9683): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9683): HTTP_CONNECTION: keep-alive admin(9683): SERVER_NAME: md.2y.net admin(9683): REMOTE_ADDR: 192.168.0.2 admin(9683): REMOTE_PORT: 32951 admin(9683): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9683): PATH_TRANSLATED: /home/kutro-homepage admin(9683): SERVER_PORT: 80 admin(9683): GATEWAY_INTERFACE: CGI/1.1 admin(9683): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9683): SERVER_ADDR: 192.168.0.1 admin(9683): DOCUMENT_ROOT: /var/www/html Nov 19 18:10:32 2002 admin(9684): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(9684): [----- Mailman Version: 2.0.11 -----] admin(9684): [----- Traceback ------] admin(9684): Traceback (most recent call last): admin(9684): File "/home/mailman/scripts/driver", line 90, in run_main admin(9684): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(9684): File "/home/mailman/Mailman/Cgi/listinfo.py", line 27, in ? admin(9684): from Mailman import Utils admin(9684): EOFError: EOF read where object expected admin(9684): [----- Python Information -----] admin(9684): sys.version = 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] admin(9684): sys.executable = /usr/bin/python admin(9684): sys.prefix = /usr admin(9684): sys.exec_prefix= /usr admin(9684): sys.path = /usr admin(9684): sys.platform = linux-i386 admin(9684): [----- Environment Variables -----] admin(9684): PYTHONPATH: /home/mailman admin(9684): SERVER_SOFTWARE: Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 admin(9684): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(9684): SERVER_ADMIN: root@localhost admin(9684): SCRIPT_NAME: /mailman/listinfo admin(9684): SERVER_SIGNATURE: <ADDRESS>Apache-AdvancedExtranetServer/1.3.23 Server at md.2y.net Port 80</ADDRESS> admin(9684): REQUEST_METHOD: GET admin(9684): HTTP_HOST: md.2y.net admin(9684): HTTP_KEEP_ALIVE: 300 admin(9684): SERVER_PROTOCOL: HTTP/1.1 admin(9684): QUERY_STRING: admin(9684): REQUEST_URI: /mailman/listinfo admin(9684): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 admin(9684): HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(9684): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 admin(9684): HTTP_CONNECTION: keep-alive admin(9684): SERVER_NAME: md.2y.net admin(9684): REMOTE_ADDR: 192.168.0.2 admin(9684): REMOTE_PORT: 32951 admin(9684): HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(9684): SERVER_PORT: 80 admin(9684): GATEWAY_INTERFACE: CGI/1.1 admin(9684): HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(9684): SERVER_ADDR: 192.168.0.1 admin(9684): DOCUMENT_ROOT: /var/www/html" PS: The logs say that there were no recent activities on any list. ---------------------------------------------------------------------- Comment By: David Weisgerber (davidweisgerber) Date: 2002-11-21 12:39 Message: Logged In: YES user_id=477011 This fixed it for me: Delete /Mailman/Utils.pyc ==> Maybe it's just a python error ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_i…

1 0

[ mailman-Patches-634303 ] Recode pipermail templates
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Patches item #634303, was opened at 2002-11-06 03:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_i… Category: Pipermail Group: Mailman 2.1 >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Recode pipermail templates Initial Comment: This patch transparently recodes the pipermail templates and messages if the article and index files have a different encoding than the template language If necessary, HTML character references are generate. If recoding fails, it will proceed without exception, but produce garbage. For messages, this uses a method self._, which first invokes _, then does the recoding. This makes it necessary for _ to go back more than one frame, so the number of frames is now an optional parameter (defaulting to 1). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:16 Message: Logged In: YES user_id=12800 That's a good point (not having the codec). I'm happy with producing an error if the message comes in a charset for which there's no installed codec. I'll make sure that happens. ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-11-18 18:25 Message: Logged In: YES user_id=21627 My concern with this approach is that we might not have a codec for the encoding of the message. That means we cannot decode the message to unicode, which means we cannot htmlify unsupported characters. OTOH, we do have codecs for the preferred encodings of all supported languages. [Sorry I didn't think of this issue when we were talking about it recently] If we consider this case unlikely to occur in real life, and are prepared to produce some error message in the page if it does happen, then the approach is fine. As for PEP293: Yes, this is precisely the intention: it simplifies generating html-escaped strings, and it is more efficient than any other strategy (since the codec will call the error handling only when an encoding error occurs). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 15:46 Message: Logged In: YES user_id=12800 Feel free to shoot holes in this, but I think it might not be simpler to just get rid of the multiple _charsets stuff in HyperArch.HyperArchive. Say we always encode the indices pages with the character set of the list's preferred language, except that we also html-ify any bogus characters outside that charset. Seems to me we can chop a bunch of code and still get the results we want, even if at the expense of potentially bigger pages (which I don't care about). I'm going to commit some changes and test them out on the playground list. This seem to work well here for my test lists. Semi-related: would PEP 293 allow us to get rid of unicode_quote? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=634303&group_i…

1 0

[ mailman-Patches-640518 ] SpamAssassin handler
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Patches item #640518, was opened at 2002-11-19 00:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_i… Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_i…

1 0

[ mailman-Patches-644797 ] Revised mailer exit status
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Patches item #644797, was opened at 2002-11-27 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i… Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i…

1 0

[ mailman-Patches-644797 ] Revised mailer exit status
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Patches item #644797, was opened at 2002-11-27 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i… Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_i…

1 0

[ mailman-Bugs-644774 ] "description" doesn't get encoded
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #644774, was opened at 2002-11-27 16:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_i… Category: None Group: 2.1 beta >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) >Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_i…

1 0

[ mailman-Bugs-644774 ] "description" doesn't get encoded
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #644774, was opened at 2002-11-27 16:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_i… Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644774&group_i…

1 0

[ mailman-Bugs-644773 ] "description" doesn't get encoded
by noreply＠sourceforge.net Nov. 27, 2002

Nov. 27, 2002

Bugs item #644773, was opened at 2002-11-27 16:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_i… Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Sven Anderson (tuttle) Assigned to: Nobody/Anonymous (nobody) Summary: "description" doesn't get encoded Initial Comment: Mailman 2.1b5 The "description" option is being used for both the web- pages and the Reply-To: header. If there are non-ASCII characters in it, it won't be encoded, so that there are unencoded non-ASCII characters in the mail header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644773&group_i…

1 0