From noreply at sourceforge.net Mon Feb 2 19:16:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 2 19:16:18 2004 Subject: [ mailman-Bugs-449677 ] HyperArch.py assumes charsets are in \w+ Message-ID: Bugs item #449677, was opened at 2001-08-10 03:25 Message generated for change (Comment added) made by cfaerber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=449677&group_id=103 Category: Pipermail Group: 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Ben Gertzfield (che_fox) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py assumes charsets are in \w+ Initial Comment: Using Mailman 2.0.6, I noticed that Japanese messages in charset iso-2022-jp are not archived correctly; their subject lines stay in MIME-encoded format, like Subject: =?ISO-2022-JP?B?WxskQiQqTD5BMBsoQi5jb21dLmNvbS8uag==?= etc. I tracked this down to the following line in HyperArch.py:158 # content-type charset rx_charset = re.compile('charset="(\w+)"') This is incorrect. According to the de-facto list of charsets at http://www.iana.org/assignments/character-sets charsets can have all sorts of characters outside of [a-zA-Z0-9_] , such as - ( ) : . etc. So, we must accept anything between the quotes with a fuzzy .+? match, instead of forcing \w+. Patch attached, against Mailman 2.0.6. ---------------------------------------------------------------------- Comment By: Claus F?rber (cfaerber) Date: 2004-02-03 01:16 Message: Logged In: YES user_id=126984 This is still incorrect: The quotes are not required. There can be whitespace and folding around the "=" sign. A string matching 'charset="(\w+)"' can occur within other parameters. ---------------------------------------------------------------------- Comment By: Ben Gertzfield (che_fox) Date: 2001-08-10 04:53 Message: Logged In: YES user_id=89313 Note: this is the solution to the problem in Bug #431511. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=449677&group_id=103 From noreply at sourceforge.net Tue Feb 3 23:03:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 3 23:03:36 2004 Subject: [ mailman-Bugs-744466 ] error message Message-ID: Bugs item #744466, was opened at 2003-05-27 14:41 Message generated for change (Settings changed) made by oppie 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: Deleted 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 10: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 Wed Feb 4 15:45:04 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 4 15:45:13 2004 Subject: [ mailman-Bugs-890732 ] poor date parsing trips archiving Message-ID: Bugs item #890732, was opened at 2004-02-04 21:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Denys Duchier (duchier) Assigned to: Nobody/Anonymous (nobody) Summary: poor date parsing trips archiving Initial Comment: With Mail 2.1.2, running the arch script produced some bizarre output: messages whose date could not be parsed were assumed to be of the current date. I was able to cure the problem simply by updating mailman/pythonlib/email/_parseaddr.py to the most recent version from the python CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 From noreply at sourceforge.net Wed Feb 4 18:42:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 4 18:45:34 2004 Subject: [ mailman-Bugs-874760 ] Expose bug after a user change email address Message-ID: Bugs item #874760, was opened at 2004-01-11 04:50 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=874760&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Expose bug after a user change email address Initial Comment: If a user changed his email address and confirm by email, then hit a button on the (old email) options page, then he get; Bug in Mailman version 2.1.4 > > 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/options.py", line 226, in main > password, user): > File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate > ok = self.CheckCookie(ac, user) > File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie > ok = self.__checkone(c, authcontext, user) > File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone > key, secret = self.AuthContextInfo(authcontext, user) > File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo > secret = self.getMemberPassword(user) > File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword > raise Errors.NotAMemberError, member > NotAMemberError: old_user@address I atatch a patch to fix this. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-04 23:42 Message: Logged In: YES user_id=67709 withdrawing this patch because it is fixed with patch ID 869644 and already committed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=874760&group_id=103 From noreply at sourceforge.net Thu Feb 5 11:10:36 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 5 11:10:52 2004 Subject: [ mailman-Bugs-871050 ] Uncought runner exception: Empty module name Message-ID: Bugs item #871050, was opened at 2004-01-05 12:03 Message generated for change (Comment added) made by junkmale You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- Comment By: Dan Langille (junkmale) Date: 2004-02-05 11:10 Message: Logged In: YES user_id=27858 I am having a simlar problem. Mail comes in, but never goes out to the list. Everthing is shunted. I found this "patch" http://www.mail-archive.com/mailman-developers@python. org/msg06317.html and applied it. Then I ran unshunt. That's when this appeared in mailman/logs/error Feb 05 07:57:07 2004 (27060) Dequeuing message destined for missing list: planners Feb 05 07:57:07 2004 (27060) Uncaught runner exception: Empty module name Feb 05 07:57:07 2004 (27060) 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/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 90, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 131, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 304, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 311, in process t = t.encode(charset, 'replace') File "/usr/local/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-01-27 06:09 Message: Logged In: YES user_id=565663 I use 2.1.3 and have the same problem. Any solution in sight? ---------------------------------------------------------------------- Comment By: Marcel Meyer (meyerm) Date: 2004-01-14 05:56 Message: Logged In: YES user_id=66911 Hi, was this somehow resolved?? I just found to have the same problems! What can I do that the messages (the shunt directory is now 1,5 MB big! [not the contents of the dir, but the dir inode itself...!!] ) are written into the archives without loosing anything? unshunt just puts them back into the shunt directory. Is there some patch - anything? Thanks a lot Marcel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 From noreply at sourceforge.net Thu Feb 5 20:26:36 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 5 20:26:40 2004 Subject: [ mailman-Patches-891491 ] Scrubber.py patch Message-ID: Patches item #891491, was opened at 2004-02-06 01:26 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=891491&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py patch Initial Comment: Scrubber.py has number of bugs for processing various types of attachment and languages and many have submitted patches to fix them. This patch item is opened to collect such patches for convenience. This patch corrects: - if an attached text is composed by win notepad, it has no charset specified and actual charset may be different from message/list charset. This sometimes cause error in composing digest message. - sometimes, null charset is represented by '' as well as None. - embedded rfc-2822 message is lost if you don't use msg.walk() - special problem with japanese charsets. - t (stringfied part) may be None which you can't append a '\n'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 From noreply at sourceforge.net Thu Feb 5 20:28:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 5 20:28:49 2004 Subject: [ mailman-Patches-866238 ] Scrubber for multi-charset language Message-ID: Patches item #866238, was opened at 2003-12-27 07:59 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=866238&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber for multi-charset language Initial Comment: Mailman i18n allows multi-charset for one language eg. for Japanese, 'iso-2022-jp' for mail message and 'euc-jp' for HTML and internal texts. Scrubber.py fails to recognize the latter charset by using get_content_charset() which is getting the mail message charset. Example of this bug is in http://snow.is.kochi-u.ac.jp/pipermail2/mailman2/2003-December/000013.html while we want to get http://snow.is.kochi-u.ac.jp/pipermail2/mailman2/2003-December/000017.html (Compare using their source because your browser may not capable of displaying japanese fonts) This patch tries to use get_charset() first, and if it is empty, use get_content_charset(). Note that the former returns Charset instance not charset string. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-06 01:28 Message: Logged In: YES user_id=67709 closing because new item was opend -- #891491 ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-28 01:14 Message: Logged In: YES user_id=67709 Uploading a revised patch to include bug #759841 (multipart/alternative archive) patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=866238&group_id=103 From noreply at sourceforge.net Thu Feb 5 20:30:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 5 20:31:04 2004 Subject: [ mailman-Patches-796950 ] Mails get shunt for no apparent reason Message-ID: Patches item #796950, was opened at 2003-08-28 20:45 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=796950&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Nadim Shaikli (shaikli) Assigned to: Nobody/Anonymous (nobody) Summary: Mails get shunt for no apparent reason Initial Comment: Here's the patch that was noted on this thread, http://mail.python.org/pipermail/mailman-developers/2003-August/015547.html I hope it makes it ASAP as it has solved a major problem for us and could be of use to others (there is a bug report with symptoms very similar to what we saw, bug #707610 among others). --- Scrubber.py.orig 2003-08-13 23:19:19.000000000 -0700 +++ Scrubber.py 2003-08-14 00:23:47.000000000 -0700 @@ -305,6 +305,8 @@ t = unicode(t, 'ascii', 'replace').encode('ascii') try: # Should use HTML-Escape, or try generalizing to UTF-8 + if len(charset) == 0: + charset = 'us-ascii' t = t.encode(charset, 'replace') except (UnicodeError, LookupError): t = t.encode(lcset, 'replace') ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-06 01:30 Message: Logged In: YES user_id=67709 this bug is fixed by patch item #891491 (I believe) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=796950&group_id=103 From noreply at sourceforge.net Fri Feb 6 09:16:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 6 09:16:33 2004 Subject: [ mailman-Bugs-891807 ] zh_TW(big5) messages Message-ID: Bugs item #891807, was opened at 2004-02-06 22:16 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=891807&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: ?e???? (keanu) Assigned to: Nobody/Anonymous (nobody) Summary: zh_TW(big5) messages Initial Comment: In messages, the 'big5' folder should named 'zh_TW', not 'big5'. According to the Mailman/Defaults.py, the country code for "Chinese (Taiwan)" is 'zh_TW', so under the messages/big5 and the template/big5, both they should rename to 'zh_TW'. messages/big5 => messages/zh_TW templates/big5 => templates/zh_TW Also, the Makefile should be fix this bug, too. in messages/Makefile: original: LANGUAGES= big5 ca cs da de es et eu fi fr hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk fixed: LANGUAGES= zh_TW ca cs da de es et eu fi fr hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk also in templates/Makefile: original: LANGUAGES= big5 ca cs de en es et eu fi fr gb hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk fixed: LANGUAGES= zh_TW ca cs de en es et eu fi fr gb hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891807&group_id=103 From noreply at sourceforge.net Fri Feb 6 09:19:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 6 09:22:52 2004 Subject: [ mailman-Bugs-891807 ] The zh_TW messages and templates Message-ID: Bugs item #891807, was opened at 2004-02-06 22:16 Message generated for change (Settings changed) made by keanu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891807&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: ?e???? (keanu) Assigned to: Nobody/Anonymous (nobody) >Summary: The zh_TW messages and templates Initial Comment: In messages, the 'big5' folder should named 'zh_TW', not 'big5'. According to the Mailman/Defaults.py, the country code for "Chinese (Taiwan)" is 'zh_TW', so under the messages/big5 and the template/big5, both they should rename to 'zh_TW'. messages/big5 => messages/zh_TW templates/big5 => templates/zh_TW Also, the Makefile should be fix this bug, too. in messages/Makefile: original: LANGUAGES= big5 ca cs da de es et eu fi fr hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk fixed: LANGUAGES= zh_TW ca cs da de es et eu fi fr hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk also in templates/Makefile: original: LANGUAGES= big5 ca cs de en es et eu fi fr gb hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk fixed: LANGUAGES= zh_TW ca cs de en es et eu fi fr gb hr hu it ja ko lt nl no pl pt pt_BR ro ru sl sr sv uk ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891807&group_id=103 From noreply at sourceforge.net Fri Feb 6 09:27:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 6 09:27:18 2004 Subject: [ mailman-Bugs-891811 ] Unsubscribing user which is not approved yet Message-ID: Bugs item #891811, was opened at 2004-02-06 15:27 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=891811&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Niels Breet (xfade) Assigned to: Nobody/Anonymous (nobody) Summary: Unsubscribing user which is not approved yet Initial Comment: In Mailman version 2.1.4, you will get the "We're sorry, we hit a bug!"-page if you: - subscribe to a list that requires a moderator to validate your account and then: - unsubscribe via options page before a moderator has validated your account. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891811&group_id=103 From noreply at sourceforge.net Fri Feb 6 09:29:10 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 6 09:29:20 2004 Subject: [ mailman-Bugs-891811 ] Unsubscribing user which is not approved yet fails Message-ID: Bugs item #891811, was opened at 2004-02-06 15:27 Message generated for change (Settings changed) made by xfade You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891811&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Niels Breet (xfade) Assigned to: Nobody/Anonymous (nobody) >Summary: Unsubscribing user which is not approved yet fails Initial Comment: In Mailman version 2.1.4, you will get the "We're sorry, we hit a bug!"-page if you: - subscribe to a list that requires a moderator to validate your account and then: - unsubscribe via options page before a moderator has validated your account. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891811&group_id=103 From noreply at sourceforge.net Fri Feb 6 17:28:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 6 17:28:12 2004 Subject: [ mailman-Patches-892118 ] limit admin privs on user options page Message-ID: Patches item #892118, was opened at 2004-02-06 22:28 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=892118&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: limit admin privs on user options page Initial Comment: A list admin may reasonably modify your password, change your email address, flags etc. for his or her list, but has no business doing so for other lists, shouldn't even be able to see what other lists you subscribe to. This patch to options.py disables these global options, when the user in question is not the one authorized by the options page (i.e., the list admin.) It isn't bullet-proof - I can still change your password and then come back as you to do all this stuff. I haven't mentioned this to our support staff yet, but they take this kind of thing very seriously and I expect that shortly I will be turning off admin password access too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=892118&group_id=103 From noreply at sourceforge.net Fri Feb 6 17:38:55 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 6 17:39:01 2004 Subject: [ mailman-Patches-892118 ] limit admin privs on user options page Message-ID: Patches item #892118, was opened at 2004-02-06 22:28 Message generated for change (Comment added) made by donnc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=892118&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: limit admin privs on user options page Initial Comment: A list admin may reasonably modify your password, change your email address, flags etc. for his or her list, but has no business doing so for other lists, shouldn't even be able to see what other lists you subscribe to. This patch to options.py disables these global options, when the user in question is not the one authorized by the options page (i.e., the list admin.) It isn't bullet-proof - I can still change your password and then come back as you to do all this stuff. I haven't mentioned this to our support staff yet, but they take this kind of thing very seriously and I expect that shortly I will be turning off admin password access too. ---------------------------------------------------------------------- >Comment By: Donn Cave (donnc) Date: 2004-02-06 22:38 Message: Logged In: YES user_id=42839 File mangled. DISCLAIMER: I have not run this code, exactly. Our primary web authentication uses a global site user ID, and options.py and other CGI programs have a few changes to support that. These changes translated back to the options.py from CVS without a lot of trouble, but have not been tested. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=892118&group_id=103 From noreply at sourceforge.net Sun Feb 8 01:10:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 8 01:11:00 2004 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-08 06:10 Message: Logged In: YES user_id=67709 This patch for 2.1.3 is also applicable to 2.1.4. Though one patch fails to apply, it can safely be neglected. You can also get a newer and more convenient patch at: http://mm.tkikuchi.net/mailman-2.1.4+patch.20040123.gz Cheers, TK ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-09-29 01:21 Message: Logged In: YES user_id=67709 Now the patch includes instruction in General admin page. (in detail part). In source dir you should type: patch -p0 < /path/to/seqnum.patch ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-05-18 02:01 Message: Logged In: YES user_id=67709 Here is update of my patch for 2.1.2 ---------------------------------------------------------------------- Comment By: Mitchell Marks (jojoba2) Date: 2003-05-17 17:42 Message: Logged In: YES user_id=718482 Is there a version vor MM 2.1.2? I'm trying the older one but doesn't seem to work. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-27 05:33 Message: Logged In: YES user_id=67709 sorry for daily update but there was an error in i18n handling of '(no subject)' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 01:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Sun Feb 8 14:02:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 8 14:02:37 2004 Subject: [ mailman-Patches-891491 ] Scrubber.py patch Message-ID: Patches item #891491, was opened at 2004-02-05 20:26 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None >Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py patch Initial Comment: Scrubber.py has number of bugs for processing various types of attachment and languages and many have submitted patches to fix them. This patch item is opened to collect such patches for convenience. This patch corrects: - if an attached text is composed by win notepad, it has no charset specified and actual charset may be different from message/list charset. This sometimes cause error in composing digest message. - sometimes, null charset is represented by '' as well as None. - embedded rfc-2822 message is lost if you don't use msg.walk() - special problem with japanese charsets. - t (stringfied part) may be None which you can't append a '\n'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 From noreply at sourceforge.net Mon Feb 9 23:51:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 9 23:51:46 2004 Subject: [ mailman-Feature Requests-893870 ] allow signed postings from non-subscribers Message-ID: Feature Requests item #893870, was opened at 2004-02-10 15:51 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=893870&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ben Elliston (elliston) Assigned to: Nobody/Anonymous (nobody) Summary: allow signed postings from non-subscribers Initial Comment: It would be great if Mailman could permit posting from non-subscribers if the incoming message can be verified based on a per-list or site-wide GPG keyring. If per-list keyring could have a GPG key of the list owner, who in turn can sign keys of people they trust to post to the list. Furthermore, such posters could subscribe by email without needing to confirm. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=893870&group_id=103 From noreply at sourceforge.net Tue Feb 10 14:56:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 10 15:29:05 2004 Subject: [ mailman-Patches-851419 ] Clam AntiVirus handler for Mailman Message-ID: Patches item #851419, was opened at 2003-11-30 02:44 Message generated for change (Comment added) made by chomo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=851419&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Sean Reifschneider (jafo) Assigned to: Nobody/Anonymous (nobody) Summary: Clam AntiVirus handler for Mailman Initial Comment: Included is a Handler for passing messages through Clam AntiVirus, and holding or discarding messages that are determined to be viruses. Similar to modules that interface SpamAssassin, particularly useful with the "discard" option enabled so that list managers don't have to manually deal with viruses sent to their lists. Currently, this tar file is oriented towards installation by administrators into their existing setups, as it's likely to be a while before this functionality is available in the base. For the final release I imagine that a README.ClamAV, a section in the main README, or simply a good set of comments for the Defaults.py file would do the job. I'll build patches to support these, please provide feedback on which mechanism is preferred. Sean ---------------------------------------------------------------------- Comment By: alan johnson (chomo) Date: 2004-02-10 19:56 Message: Logged In: YES user_id=943591 need this does help ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=851419&group_id=103 From noreply at sourceforge.net Thu Feb 12 03:30:17 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 03:30:55 2004 Subject: [ mailman-Bugs-219808 ] Missing dependancy for 'configure'. Message-ID: Bugs item #219808, was opened at 2000-10-30 22:13 Message generated for change (Comment added) made by chomo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Thomas Wouters (twouters) Assigned to: Thomas Wouters (twouters) Summary: Missing dependancy for 'configure'. Initial Comment: The Mailman makefile is missing a dependancy on 'configure', so when 'configure' is updated, it isn't re-run automatically, and you aren't warned to reconfigure. (definately low-priority bug though :) (I also ran into something weird when running 'config.status' to do the reconfiguring for me... it set 'MAILMAN_UID' in Defaults.py to 'mailman', without quotes, instead of the numeric uid. That might be caused by a mix of an old config.status and a new configure, though, as I wasn't able to reproduce it on another box.) ---------------------------------------------------------------------- Comment By: alan johnson (chomo) Date: 2004-02-12 08:30 Message: Logged In: YES user_id=943591 seem to need it ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_id=103 From noreply at sourceforge.net Fri Feb 13 09:39:04 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 09:39:47 2004 Subject: [ mailman-Bugs-896524 ] Explicit (non-80) port sometimes missing from URL Message-ID: Bugs item #896524, was opened at 2004-02-13 09: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=896524&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Explicit (non-80) port sometimes missing from URL Initial Comment: I run my Mailman admin web site on a non-standard port which I stated back at build time using the configure tool. It works correctly but there is at least one link from which the port number is missing from the URL. It is the link for which the hyertext says "Overview of all myserver.mydomain.com lists". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896524&group_id=103 From noreply at sourceforge.net Fri Feb 13 10:14:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 10:15:30 2004 Subject: [ mailman-Bugs-896543 ] Explicit (non-80) port sometimes missing from URL Message-ID: Bugs item #896543, was opened at 2004-02-13 10:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896543&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Explicit (non-80) port sometimes missing from URL Initial Comment: I run my Mailman admin web site on a non-standard port which I stated back at build time using the configure tool. It works correctly but there is at least one link from which the port number is missing from the URL. It is the link for which the hyertext says "Overview of all myserver.mydomain.com lists". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896543&group_id=103 From noreply at sourceforge.net Fri Feb 13 10:34:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 11:19:08 2004 Subject: [ mailman-Bugs-896543 ] Explicit (non-80) port sometimes missing from URL Message-ID: Bugs item #896543, was opened at 2004-02-13 10:14 Message generated for change (Settings changed) made by unionchurch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896543&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Deleted Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Explicit (non-80) port sometimes missing from URL Initial Comment: I run my Mailman admin web site on a non-standard port which I stated back at build time using the configure tool. It works correctly but there is at least one link from which the port number is missing from the URL. It is the link for which the hyertext says "Overview of all myserver.mydomain.com lists". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896543&group_id=103 From noreply at sourceforge.net Mon Feb 16 05:28:10 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 16 05:29:16 2004 Subject: [ mailman-Bugs-897918 ] admin password is checked when it should not Message-ID: Bugs item #897918, was opened at 2004-02-16 11: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=897918&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Heiko Scheit (scheit) Assigned to: Nobody/Anonymous (nobody) Summary: admin password is checked when it should not Initial Comment: admin password is checked when it should ----------------------------------------- To see the problem you have to be the administrator of a list. Go to the members options login page .../mailman/options/ and enter something like a valid email address, e.g.: xxx@xxx.xxx and as password enter the ADMIN password! You will get something like: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! The problem seems to be that the password entered in the members options login page is also checked against the admin password, which should not be done. It should only be checked if the admin-cookie is set, so that the admin (who logged on via the admin page) can also modify user settings. What is worse: if you enter a valid email address (of a list member) and the admin password you are the admin. So, any list member that happens to choose the same password as the admin has full access to the administrative interface. Somehow I think it would be better to also have an admin username and not just an admin password. Or, for each member an admin flag can be set. The admin has to be a member and can login with email and password as anybody else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=897918&group_id=103 From noreply at sourceforge.net Tue Feb 17 17:13:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 17 17:15:02 2004 Subject: [ mailman-Bugs-870028 ] html in listinfo is quoted Message-ID: Bugs item #870028, was opened at 2004-01-03 14:09 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: html in listinfo is quoted Initial Comment: If you enter html into the 'info' text area, the listinfo page sees that html as quoted, not as valid html. This is a result of the XSS hole closure in 2.1.4, but some innocent tags should be allowed back in. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-17 17:13 Message: Logged In: YES user_id=12800 The original bug is now fixed in cvs, for 2.1.5. The one that hertell describes is not so much a bug but a byproduct of the design. If you want to include non-ascii characters in the welcome text, then you have to switch to a language that includes those characters in its encoding, enter them, then switch back to English. ---------------------------------------------------------------------- Comment By: Rene (hertell) Date: 2004-01-13 19:43 Message: Logged In: YES user_id=278485 I tracked down the encoding-problem to the following row in Defaults.py: add_language('en', _('English (USA)'), 'us-ascii') By changing the encoding to iso-8859-1 fixes the problem. add_language('en', _('English (USA)'), 'iso-8859-1') You probably ask why I don't use the admin-pages in my local language? The ansver is that I prefer English before anything else. ---------------------------------------------------------------------- Comment By: Rene (hertell) Date: 2004-01-13 19:23 Message: Logged In: YES user_id=278485 The same goes if you use Umlauts (???, or ? ? ?) in the welcome-tect text-area. First it converts the Umlaut-character to an decimal reference (ä), and after that it converts the & character into an Character entity. In other words; when the user gets the welcome-email that contains ? characters (?), it is converted twice: This is the code-soup for this character that finally arives: ä instead of the single ? character ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=870028&group_id=103 From noreply at sourceforge.net Tue Feb 17 17:16:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 17 17:17:57 2004 Subject: [ mailman-Bugs-881369 ] Double HTML encoding of non-ASCII list description Message-ID: Bugs item #881369, was opened at 2004-01-21 08:42 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=881369&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jouni K Sepp?nen (jouni) Assigned to: Nobody/Anonymous (nobody) Summary: Double HTML encoding of non-ASCII list description Initial Comment: I created in Mailman 2.1.4 a list whose description included some non-ASCII characters, e.g. "?". Both on the web page and in the List-ID header these were HTML-encoded twice. That is, the HTML source of the listinfo page replaces the character "?" by ten characters: ampersand, a, m, p, semicolon, hash, 2, 2, 8, semicolon, so that the user sees ampersand, hash, 2, 2, 8, semicolon. Also the List-ID header encodes "?" using these ten characters. It seems that if I change the list's preferred language to Finnish and re-enter the description, it gets encoded correctly: the HTML source simply uses the character directly, and the List-ID header uses RFC 2047 encoding. However, I don't like the Finnish translation of the Mailman pages, so I want to use English as the preferred language. (There seems to be a work-around: I can set the language to Finnish, then set the description, then change the language back to English.) It could be argued that if the language is set to English (USA), Mailman has no way of knowing *a priori* which encoding to use for eight-bit characters. In this case, would it make sense to add a language called "English (ISO Latin 1)", or "English (West-European)", or something similar, for those of us who like the English user interface but communicate in other languages? Or possibly a separate configuration option for the character set? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-17 17:16 Message: Logged In: YES user_id=12800 For now, the workaround you describe is the only way to do it. It might make sense to have a non-ASCII English language option, although something more universal, like utf-8 might make more sense than limiting it just to latin-1 (which makes most Europeans happy, but no one else :). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=881369&group_id=103 From noreply at sourceforge.net Tue Feb 17 17:17:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 17 17:18:48 2004 Subject: [ mailman-Bugs-897918 ] admin password is checked when it should not Message-ID: Bugs item #897918, was opened at 2004-02-16 05:28 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=897918&group_id=103 Category: security/privacy Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heiko Scheit (scheit) Assigned to: Nobody/Anonymous (nobody) Summary: admin password is checked when it should not Initial Comment: admin password is checked when it should ----------------------------------------- To see the problem you have to be the administrator of a list. Go to the members options login page .../mailman/options/ and enter something like a valid email address, e.g.: xxx@xxx.xxx and as password enter the ADMIN password! You will get something like: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! The problem seems to be that the password entered in the members options login page is also checked against the admin password, which should not be done. It should only be checked if the admin-cookie is set, so that the admin (who logged on via the admin page) can also modify user settings. What is worse: if you enter a valid email address (of a list member) and the admin password you are the admin. So, any list member that happens to choose the same password as the admin has full access to the administrative interface. Somehow I think it would be better to also have an admin username and not just an admin password. Or, for each member an admin flag can be set. The admin has to be a member and can login with email and password as anybody else. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-17 17:17 Message: Logged In: YES user_id=12800 This is fixed in cvs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=897918&group_id=103 From noreply at sourceforge.net Tue Feb 17 17:17:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 17 17:19:24 2004 Subject: [ mailman-Bugs-891811 ] Unsubscribing user which is not approved yet fails Message-ID: Bugs item #891811, was opened at 2004-02-06 09:27 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891811&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Niels Breet (xfade) Assigned to: Nobody/Anonymous (nobody) Summary: Unsubscribing user which is not approved yet fails Initial Comment: In Mailman version 2.1.4, you will get the "We're sorry, we hit a bug!"-page if you: - subscribe to a list that requires a moderator to validate your account and then: - unsubscribe via options page before a moderator has validated your account. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-17 17:17 Message: Logged In: YES user_id=12800 Fixed in cvs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=891811&group_id=103 From noreply at sourceforge.net Tue Feb 17 20:50:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 17 20:51:50 2004 Subject: [ mailman-Patches-899263 ] update to 2.1.5 Message-ID: Patches item #899263, was opened at 2004-02-18 01:50 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=899263&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: update to 2.1.5 Initial Comment: Update to 2.1.5 from 2.1.4 earlier checks pending.pck for duplicate ids and aborts if there is one such duplication. My mailman installation is fairly old, have long history and had orphaned pending-ids. It looked like we can safely ignore such duplication. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=899263&group_id=103 From noreply at sourceforge.net Fri Feb 20 12:28:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 20 12:33:50 2004 Subject: [ mailman-Bugs-890732 ] poor date parsing trips archiving Message-ID: Bugs item #890732, was opened at 2004-02-04 20:45 Message generated for change (Comment added) made by thoover You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Denys Duchier (duchier) Assigned to: Nobody/Anonymous (nobody) Summary: poor date parsing trips archiving Initial Comment: With Mail 2.1.2, running the arch script produced some bizarre output: messages whose date could not be parsed were assumed to be of the current date. I was able to cure the problem simply by updating mailman/pythonlib/email/_parseaddr.py to the most recent version from the python CVS. ---------------------------------------------------------------------- Comment By: Tom Hoover (thoover) Date: 2004-02-20 17:28 Message: Logged In: YES user_id=23321 I checked, and the _parseaddr.py on my system is identical to the latest in CVS...I still have the problem. The arch script won't parse dates in the format of: Date: Sat, 17 Jan 2004 16:32:00 -0600 so it therefore converts the date to the current date: Date: Fri Feb 20 09:43:05 2004 I wanted to change my local backup script to backup only the *.mbox files (I would then recreate the html files using 'arch' in the event of a crash, etc), but for now I'm still backing up everything. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 From noreply at sourceforge.net Fri Feb 20 19:03:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 20 19:04:49 2004 Subject: [ mailman-Bugs-901502 ] Edit Options for unsubbed user results in backtrace Message-ID: Bugs item #901502, was opened at 2004-02-21 00:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=901502&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Derek Atkins (mit_warlord) Assigned to: Nobody/Anonymous (nobody) Summary: Edit Options for unsubbed user results in backtrace Initial Comment: I was trying to test out a new installation of mailman. I tried to subscribe by the web site, and it sent me a response. I tried responding by email and simultaneously put my email in the "unsubscribe or edit options" box and clicked the button. When I clicked the button I received the following message: Bug in Mailman version 2.1.4 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 "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/var/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: XXXXX@YYYYY.ZZZ Python information: Variable Value sys.version 2.2.3 (#1, Oct 15 2003, 23:33:35) [GCC 3.3.1 20030930 (Red Hat Linux 3.3.1-6)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=901502&group_id=103 From noreply at sourceforge.net Sat Feb 21 14:01:19 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 21 14:06:15 2004 Subject: [ mailman-Bugs-890732 ] poor date parsing trips archiving Message-ID: Bugs item #890732, was opened at 2004-02-04 21:45 Message generated for change (Comment added) made by duchier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Denys Duchier (duchier) Assigned to: Nobody/Anonymous (nobody) Summary: poor date parsing trips archiving Initial Comment: With Mail 2.1.2, running the arch script produced some bizarre output: messages whose date could not be parsed were assumed to be of the current date. I was able to cure the problem simply by updating mailman/pythonlib/email/_parseaddr.py to the most recent version from the python CVS. ---------------------------------------------------------------------- >Comment By: Denys Duchier (duchier) Date: 2004-02-21 20:01 Message: Logged In: YES user_id=531638 thoover, you are mistaken - the version I fetched from the python CVS parses such dates just fine. Also you said: _parseaddr.py on your system - I am not sure what that means - I was not refering to the version in your python installation - that one is probably just fine - I was talking about the one in the mailman installation - that's the one which is outdated. Cheers, ---------------------------------------------------------------------- Comment By: Tom Hoover (thoover) Date: 2004-02-20 18:28 Message: Logged In: YES user_id=23321 I checked, and the _parseaddr.py on my system is identical to the latest in CVS...I still have the problem. The arch script won't parse dates in the format of: Date: Sat, 17 Jan 2004 16:32:00 -0600 so it therefore converts the date to the current date: Date: Fri Feb 20 09:43:05 2004 I wanted to change my local backup script to backup only the *.mbox files (I would then recreate the html files using 'arch' in the event of a crash, etc), but for now I'm still backing up everything. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 From noreply at sourceforge.net Sat Feb 21 18:00:05 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 21 18:01:54 2004 Subject: [ mailman-Bugs-890732 ] poor date parsing trips archiving Message-ID: Bugs item #890732, was opened at 2004-02-04 20:45 Message generated for change (Comment added) made by thoover You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Denys Duchier (duchier) Assigned to: Nobody/Anonymous (nobody) Summary: poor date parsing trips archiving Initial Comment: With Mail 2.1.2, running the arch script produced some bizarre output: messages whose date could not be parsed were assumed to be of the current date. I was able to cure the problem simply by updating mailman/pythonlib/email/_parseaddr.py to the most recent version from the python CVS. ---------------------------------------------------------------------- Comment By: Tom Hoover (thoover) Date: 2004-02-21 23:00 Message: Logged In: YES user_id=23321 I'd downloaded the latest version (1.7) of _parseaddr.py from the python CVS, and compared it to the copy on my system found at mailman/pythonlib/email/_parseaddr.py. They both have an md5sum of: 089bfb2cbae8f2e204f818d8c381d49e _parseaddr.py Since I am obviously mistaken, could you please check the md5sum of the file on your system, and let me know what it is? Even better, could you give me the exact URL of the correct file? (I downloaded mine from http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Lib/email/_parseaddr.py (version 1.7, dated 6-13-03). If this is the same file that you have, then there's evidently another problem causing the 'arch' script to fail to parse the dates correctly. (I am, however, running Mailman 2.1.4...maybe another bug was introduced between 2.1.2 and 2.1.4?) Thanks! ---------------------------------------------------------------------- Comment By: Denys Duchier (duchier) Date: 2004-02-21 19:01 Message: Logged In: YES user_id=531638 thoover, you are mistaken - the version I fetched from the python CVS parses such dates just fine. Also you said: _parseaddr.py on your system - I am not sure what that means - I was not refering to the version in your python installation - that one is probably just fine - I was talking about the one in the mailman installation - that's the one which is outdated. Cheers, ---------------------------------------------------------------------- Comment By: Tom Hoover (thoover) Date: 2004-02-20 17:28 Message: Logged In: YES user_id=23321 I checked, and the _parseaddr.py on my system is identical to the latest in CVS...I still have the problem. The arch script won't parse dates in the format of: Date: Sat, 17 Jan 2004 16:32:00 -0600 so it therefore converts the date to the current date: Date: Fri Feb 20 09:43:05 2004 I wanted to change my local backup script to backup only the *.mbox files (I would then recreate the html files using 'arch' in the event of a crash, etc), but for now I'm still backing up everything. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=890732&group_id=103 From noreply at sourceforge.net Sun Feb 22 12:25:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 22 12:27:33 2004 Subject: [ mailman-Patches-891491 ] Scrubber.py patch Message-ID: Patches item #891491, was opened at 2004-02-06 01:26 Message generated for change (Comment added) made by jifl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py patch Initial Comment: Scrubber.py has number of bugs for processing various types of attachment and languages and many have submitted patches to fix them. This patch item is opened to collect such patches for convenience. This patch corrects: - if an attached text is composed by win notepad, it has no charset specified and actual charset may be different from message/list charset. This sometimes cause error in composing digest message. - sometimes, null charset is represented by '' as well as None. - embedded rfc-2822 message is lost if you don't use msg.walk() - special problem with japanese charsets. - t (stringfied part) may be None which you can't append a '\n'. ---------------------------------------------------------------------- Comment By: Jonathan Larmour (jifl) Date: 2004-02-22 17:25 Message: Logged In: YES user_id=817601 I strongly recommend applying this patch. I received a mail bounce on a list with an empty charset in a part (i.e. "charset=") and it caused /var/mailman/cron/senddigest and thus all digest processing to fail because of this error: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') which is something this patch fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 From noreply at sourceforge.net Sun Feb 22 17:25:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 22 17:27:48 2004 Subject: [ mailman-Bugs-901502 ] Edit Options for unsubbed user results in backtrace Message-ID: Bugs item #901502, was opened at 2004-02-20 19:03 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=901502&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Derek Atkins (mit_warlord) Assigned to: Nobody/Anonymous (nobody) Summary: Edit Options for unsubbed user results in backtrace Initial Comment: I was trying to test out a new installation of mailman. I tried to subscribe by the web site, and it sent me a response. I tried responding by email and simultaneously put my email in the "unsubscribe or edit options" box and clicked the button. When I clicked the button I received the following message: Bug in Mailman version 2.1.4 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 "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/var/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: XXXXX@YYYYY.ZZZ Python information: Variable Value sys.version 2.2.3 (#1, Oct 15 2003, 23:33:35) [GCC 3.3.1 20030930 (Red Hat Linux 3.3.1-6)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-22 17:25 Message: Logged In: YES user_id=12800 Already fixed in cvs for 2.1.5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=901502&group_id=103 From noreply at sourceforge.net Sun Feb 22 17:46:53 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 22 17:49:00 2004 Subject: [ mailman-Patches-899263 ] update to 2.1.5 Message-ID: Patches item #899263, was opened at 2004-02-17 20:50 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=899263&group_id=103 Category: configure/install Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: update to 2.1.5 Initial Comment: Update to 2.1.5 from 2.1.4 earlier checks pending.pck for duplicate ids and aborts if there is one such duplication. My mailman installation is fairly old, have long history and had orphaned pending-ids. It looked like we can safely ignore such duplication. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-22 17:46 Message: Logged In: YES user_id=12800 Thanks! I changed the warning message a bit. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=899263&group_id=103 From noreply at sourceforge.net Mon Feb 23 07:41:15 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 23 07:43:12 2004 Subject: [ mailman-Bugs-902646 ] UnicodeEncodeError submitting admin request Message-ID: Bugs item #902646, was opened at 2004-02-23 13:41 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=902646&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Maurice Snellen (kiap) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeEncodeError submitting admin request Initial Comment: When submitting an admin request to have a number of addresses set to 'Ignore' processing the list of mails received from addresses not subscribed to the list, the following error is received by the list moderator. I have confirmed that the same error occurs with the site admin password. Bug in Mailman version 2.1.4 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 "/var/mailman/nlbdsmorg/scripts/driver", line 87, in run_main main() File "/var/mailman/nlbdsmorg/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/var/mailman/nlbdsmorg/Mailman/Cgi/admindb.py", line 694, in process_form forward, forwardaddr) File "/var/mailman/nlbdsmorg/Mailman/ListAdmin.py", line 184, in HandleRequest forward, addr) File "/var/mailman/nlbdsmorg/Mailman/ListAdmin.py", line 373, in __handlepost syslog('vette', note) File "/var/mailman/nlbdsmorg/Mailman/Logging/Syslog. py", line 40, in write self.write_ex(kind, msg, args, kws) File "/var/mailman/nlbdsmorg/Mailman/Logging/Syslog. py", line 58, in write_ex logf.write(msg + '\n') File "/var/mailman/nlbdsmorg/Mailman/Logging/StampedLogger. py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/var/mailman/nlbdsmorg/Mailman/Logging/Logger. py", line 91, in write f.write(msg) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 116: ordinal not in range(128) ------------------------------------------------------- --------------------- ---- Python information: Variable Value sys.version 2.3.3 (#1, Jan 23 2004, 17:15:25) [GCC 2.95. 3 20010315 (release)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------- --------------------- ---- Environment variables: Variable Value HTTP________________ ~~~~~ ~~~~~~~ HTTP_COOKIE bvj-operators+admin=2802000000690d3539407328000000 35313635333439656563666564 306432636330623136376634653138666139366537323037 626334 SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.3.2 mod_ssl/2.8.14 OpenSSL/0.9.7b SCRIPT_NAME /mailman/admindb SERVER_SIGNATURE Apache/1.3.27 Server at nl-bdsm. org Port 80 REQUEST_METHOD POST PATH_INFO /bvj-operators SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 891 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME nl-bdsm.org REMOTE_ADDR 80.126.99.148 PATH_TRANSLATED /var/www/prod/nl-bdsm. org/bvj-operators SERVER_PORT 80 SERVER_ADDR 212.238.194.176 DOCUMENT_ROOT /var/www/prod/nl-bdsm.org PYTHONPATH /var/mailman/nlbdsmorg SCRIPT_FILENAME /var/mailman/nlbdsmorg/cgi-bin/admindb SERVER_ADMIN webmaster@nl-bdsm.org HTTP_HOST nl-bdsm.org HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/admindb/bvj-operators 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________ ~~~~: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~ GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 1245 HTTP_ACCEPT_LANGUAGE nl CONTENT_TYPE application/x-www-form-urlencoded ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=902646&group_id=103 From noreply at sourceforge.net Wed Feb 25 05:42:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 25 05:45:10 2004 Subject: [ mailman-Patches-891491 ] Scrubber.py patch Message-ID: Patches item #891491, was opened at 2004-02-06 01:26 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py patch Initial Comment: Scrubber.py has number of bugs for processing various types of attachment and languages and many have submitted patches to fix them. This patch item is opened to collect such patches for convenience. This patch corrects: - if an attached text is composed by win notepad, it has no charset specified and actual charset may be different from message/list charset. This sometimes cause error in composing digest message. - sometimes, null charset is represented by '' as well as None. - embedded rfc-2822 message is lost if you don't use msg.walk() - special problem with japanese charsets. - t (stringfied part) may be None which you can't append a '\n'. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-25 10:42 Message: Logged In: YES user_id=67709 uploading revised patch. Now fixes a few more bugs which try to decode scrub plain text message and result in mojibake. Also, japanese filename tend to become so long that system limit may exceeded because of mime encoding, so add an option not to use the filename in the message but to use 'attachment' as filename. Because this patch spans two files (Defaults.py.in and Handlers/Scrubber.py) you have to cd mailman and patch -p1 < this_patch. (Well, I think it is -p1. If it didn't work, try -p0 ;-) ---------------------------------------------------------------------- Comment By: Jonathan Larmour (jifl) Date: 2004-02-22 17:25 Message: Logged In: YES user_id=817601 I strongly recommend applying this patch. I received a mail bounce on a list with an empty charset in a part (i.e. "charset=") and it caused /var/mailman/cron/senddigest and thus all digest processing to fail because of this error: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') which is something this patch fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 From noreply at sourceforge.net Thu Feb 26 01:02:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 26 01:04:24 2004 Subject: [ mailman-Patches-904850 ] Scrubber in regular delivery per list Message-ID: Patches item #904850, was opened at 2004-02-26 06:02 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=904850&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber in regular delivery per list Initial Comment: Mailman/Handlers/Scrubber.py is used to save attachments in separated area in the pipermail archive while processing the messages in archiving and digesting. We can also use this script in GLOBAL_PIPELINE to scrub all the messages for regular (non-digest) delivery. This patch makes this scrubbing configurable per list. This patch will work most of the environment (us-ascii only sites) but you are adviced to apply a separate scrubber patch #891491 to avoid i18n bugs. In mailman src dir, type patch -p1 < this_patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=904850&group_id=103 From noreply at sourceforge.net Thu Feb 26 20:33:20 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 26 20:35:53 2004 Subject: [ mailman-Bugs-905532 ] bin/update fail 2.1.5 Message-ID: Bugs item #905532, was opened at 2004-02-27 01:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=905532&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: bin/update fail 2.1.5 Initial Comment: pending.pck was moved from data directory to per list directories. bin/update script succesfully cares this when 2.1.4 to 2.1.5 version up but ends in error if you want updat from 2.1.5 to 2.1.5 (alpha version up from CVS). here is the error message. Traceback (most recent call last): File "bin/update", line 774, in ? errors = main() File "bin/update", line 698, in main update_pending() File "bin/update", line 563, in update_pending for key, val in db.items(): AttributeError: 'NoneType' object has no attribute 'items' I hope the attached patch may be useful. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=905532&group_id=103 From noreply at sourceforge.net Fri Feb 27 10:20:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 27 10:22:44 2004 Subject: [ mailman-Bugs-905910 ] Wrong headers sent with gzip'd Message-ID: Bugs item #905910, was opened at 2004-02-27 10: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=905910&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tim Altman (junyor) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong headers sent with gzip'd Initial Comment: The filename and/or headers for list archives are incorrect. This causes some browsers to choke in their handling of the files. The filename should have the ".gz" extension stripped, as the files are really just text files. Headers currently sent are as follows: GET /mailman//2004-February.txt.gz HTTP/1.1 User-Agent: Opera/7.50 (Windows NT 5.1; U) [en] Host: Accept: text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1 Accept-Language: en Accept-Charset: windows-1252, utf-8, utf-16, iso-8859-1;q=0.6, *;q=0.1 Accept-Encoding: deflate, gzip, x-gzip, identity, *; q=0 Referer: Cookie: Cookie2: $Version=1 Connection: Keep-Alive, TE TE: deflate, gzip, chunked, identity, trailers HTTP/1.1 200 OK Date: Fri, 27 Feb 2004 15:13:32 GMT Server: Apache/1.3.27 (Unix) (Red-Hat/Linux) Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: text/plain ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=905910&group_id=103 From noreply at sourceforge.net Sat Feb 28 23:41:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 28 23:41:55 2004 Subject: [ mailman-Bugs-905532 ] bin/update fail 2.1.5 Message-ID: Bugs item #905532, was opened at 2004-02-26 20:33 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=905532&group_id=103 Category: configuring/installing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: bin/update fail 2.1.5 Initial Comment: pending.pck was moved from data directory to per list directories. bin/update script succesfully cares this when 2.1.4 to 2.1.5 version up but ends in error if you want updat from 2.1.5 to 2.1.5 (alpha version up from CVS). here is the error message. Traceback (most recent call last): File "bin/update", line 774, in ? errors = main() File "bin/update", line 698, in main update_pending() File "bin/update", line 563, in update_pending for key, val in db.items(): AttributeError: 'NoneType' object has no attribute 'items' I hope the attached patch may be useful. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-02-28 23:41 Message: Logged In: YES user_id=12800 I found the same bug today before I saw report! I think the fix is actually to just return when db is still None (because it's already been updated, or otherwise doesn't exist). That's what I checked into cvs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=905532&group_id=103 From noreply at sourceforge.net Sun Feb 29 23:10:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 29 23:10:53 2004 Subject: [ mailman-Bugs-907272 ] URL given in INSTALL no longer valid Message-ID: Bugs item #907272, was opened at 2004-02-29 23:10 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=907272&group_id=103 Category: documentation Group: Out of Date Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: URL given in INSTALL no longer valid Initial Comment: I was just looking at the INSTALL document out of the CSV (both the HEAD version and v2.11.2.1 that was included in Mailman 2.1.4). This document mentions the URL http://mail.python.org/pipermail/mailman-users/2000-September/006826.html which is supposed to be a message about upgrading the list template files -- but the proper message is no longer found at that URL. I believe the intended message is now found at http://mail.python.org/pipermail/mailman-users/2000-September/006822.html If that's the right message, it problably makes sense to give a little info to help people find the correct message if it moves again (i.e. message dated Thu Sep 21 21:59:16 EDT 2000 and having a subject line of "quick note for those ugrading mailman". (Or, just quote the message directly in the INSTALL document; it's not too long...) Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=907272&group_id=103 From noreply at sourceforge.net Sun Feb 29 23:46:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 29 23:46:16 2004 Subject: [ mailman-Bugs-907272 ] URL given in UPGRADING no longer valid Message-ID: Bugs item #907272, was opened at 2004-02-29 23:10 Message generated for change (Settings changed) made by nathanst You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=907272&group_id=103 Category: documentation Group: Out of Date Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) >Summary: URL given in UPGRADING no longer valid Initial Comment: I was just looking at the INSTALL document out of the CSV (both the HEAD version and v2.11.2.1 that was included in Mailman 2.1.4). This document mentions the URL http://mail.python.org/pipermail/mailman-users/2000-September/006826.html which is supposed to be a message about upgrading the list template files -- but the proper message is no longer found at that URL. I believe the intended message is now found at http://mail.python.org/pipermail/mailman-users/2000-September/006822.html If that's the right message, it problably makes sense to give a little info to help people find the correct message if it moves again (i.e. message dated Thu Sep 21 21:59:16 EDT 2000 and having a subject line of "quick note for those ugrading mailman". (Or, just quote the message directly in the INSTALL document; it's not too long...) Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=907272&group_id=103 From noreply at sourceforge.net Sun Feb 29 23:47:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 29 23:47:36 2004 Subject: [ mailman-Bugs-907272 ] URL given in UPGRADING no longer valid Message-ID: Bugs item #907272, was opened at 2004-02-29 23:10 Message generated for change (Comment added) made by nathanst You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=907272&group_id=103 Category: documentation Group: Out of Date Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: URL given in UPGRADING no longer valid Initial Comment: I was just looking at the INSTALL document out of the CSV (both the HEAD version and v2.11.2.1 that was included in Mailman 2.1.4). This document mentions the URL http://mail.python.org/pipermail/mailman-users/2000-September/006826.html which is supposed to be a message about upgrading the list template files -- but the proper message is no longer found at that URL. I believe the intended message is now found at http://mail.python.org/pipermail/mailman-users/2000-September/006822.html If that's the right message, it problably makes sense to give a little info to help people find the correct message if it moves again (i.e. message dated Thu Sep 21 21:59:16 EDT 2000 and having a subject line of "quick note for those ugrading mailman". (Or, just quote the message directly in the INSTALL document; it's not too long...) Thanks. ---------------------------------------------------------------------- >Comment By: Nathan Stratton Treadway (nathanst) Date: 2004-02-29 23:47 Message: Logged In: YES user_id=987478 Sorry, the file I was looking at was "UPGRADING", not "INSTALL". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=907272&group_id=103