From noreply at sourceforge.net Sat Jan 8 02:23:23 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 8 02:23:27 2005 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 10:54 Message generated for change (Comment added) made by toniw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-08 03:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-30 06:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Sat Jan 8 20:01:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 8 20:01:05 2005 Subject: [ mailman-Feature Requests-1098572 ] Confirmation for non-member posts Message-ID: Feature Requests item #1098572, was opened at 2005-01-08 11:01 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=1098572&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rich Pasco (pasco) Assigned to: Nobody/Anonymous (nobody) Summary: Confirmation for non-member posts Initial Comment: I would like to see an option to automatically send confirmation messages to non-members whose posts are approved by the moderator for distribution to the list. When I post to lists of which I am not a member, I am troubled by the absence of feedback as to whether the moderator approved my post for distribution or discarded it without comment. The list owners would be happy to enable such an automatic confirmation for non-members if this feature were provided by Mailman. - Rich ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1098572&group_id=103 From noreply at sourceforge.net Sun Jan 9 23:36:09 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 9 23:36:12 2005 Subject: [ mailman-Bugs-1099138 ] Scrubber.py traceback Message-ID: Bugs item #1099138, was opened at 2005-01-09 22:36 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=1099138&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Owen Taylor (otaylor) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py traceback Initial Comment: Outgoing mail on one of our lists on mail.gnome.org was being held up because of a error that was occuring sending out digests. Jan 09 16:07:24 2005 (22410) Uncaught runner exception: len() of unsized object Jan 09 16:07:24 2005 (22410) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 262, in process size = len(payload) TypeError: len() of unsized object Unfortunately, I don't know what mail was triggering this... was trying to get the mailing list going and didn't want to spend a lot of time investigating. It's also not immediately clear to me how payload could end up as None there... from reading the code in email.Message maybe part._payload was None due to an earlier problem. I'll attach a workaround patch... the if: also covers the call to save_attachment() since that also tracebacked when I just fixed the call to len(). Anyways, filing in case it makes sense to someone more familiar with the guts of email.Message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 From noreply at sourceforge.net Mon Jan 10 00:15:46 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 10 00:15:50 2005 Subject: [ mailman-Bugs-1099138 ] Scrubber.py traceback Message-ID: Bugs item #1099138, was opened at 2005-01-09 22:36 Message generated for change (Comment added) made by otaylor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Owen Taylor (otaylor) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py traceback Initial Comment: Outgoing mail on one of our lists on mail.gnome.org was being held up because of a error that was occuring sending out digests. Jan 09 16:07:24 2005 (22410) Uncaught runner exception: len() of unsized object Jan 09 16:07:24 2005 (22410) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 262, in process size = len(payload) TypeError: len() of unsized object Unfortunately, I don't know what mail was triggering this... was trying to get the mailing list going and didn't want to spend a lot of time investigating. It's also not immediately clear to me how payload could end up as None there... from reading the code in email.Message maybe part._payload was None due to an earlier problem. I'll attach a workaround patch... the if: also covers the call to save_attachment() since that also tracebacked when I just fixed the call to len(). Anyways, filing in case it makes sense to someone more familiar with the guts of email.Message. ---------------------------------------------------------------------- >Comment By: Owen Taylor (otaylor) Date: 2005-01-09 23:15 Message: Logged In: YES user_id=63124 Oh, forgot to add say, this is python-2.2.3 and mailman-2.1.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 From noreply at sourceforge.net Tue Jan 11 00:56:41 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 11 00:56:44 2005 Subject: [ mailman-Bugs-1099840 ] error with bad email with % in addError in htmlformat.py Message-ID: Bugs item #1099840, was opened at 2005-01-10 15:56 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=1099840&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: error with bad email with % in addError in htmlformat.py Initial Comment: If an e-mail address being added to any of several properties via the list admin Gui is "bad" and also happens to contain a '%' character an error similar to the following occurs. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm doc.addError( File "/usr/local/mailman/Mailman/htmlformat.py", line 340, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string The error actually occurs in evaluation of errmsg % args where errmsg is 'Bad email address for option %(property)s: %(val)s' and the value of 'val' in args contains a '%'. This occurs in many places in the admin Gui where the entry is an e-mail address, e.g owner, moderator, ban_list, accept_these_nonmembers, etc. but not for example in a mass subscribe list. email addresses which cause the problem include for example abc%def.ghi and ab%c@def@ghi but not ab%c@def.ghi since this latter address is not deemed invalid. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099840&group_id=103 From noreply at sourceforge.net Tue Jan 11 16:45:13 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 11 16:45:15 2005 Subject: [ mailman-Bugs-1100227 ] stops delivering messages Message-ID: Bugs item #1100227, was opened at 2005-01-11 15: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=1100227&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: steev hise (steev23) Assigned to: Nobody/Anonymous (nobody) Summary: stops delivering messages Initial Comment: Every once in a while, at random intervals (like after running fine for a few weeks or more), suddenly messages stop getting sent out to all mailing lists. They still go to the archives, they just don't get sent. can't find any clues in the logs. Is this a known bug? couldn't find one in tracker. Mailman Version: 2.1.5 python sys.version = 2.2.2 (#1, May 3 2003, 19:23:40) [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-81)] thanx, steev@detritus.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100227&group_id=103 From noreply at sourceforge.net Wed Jan 12 01:38:16 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 01:38:19 2005 Subject: [ mailman-Bugs-1100555 ] Too many banned emails cause error Message-ID: Bugs item #1100555, was opened at 2005-01-11 19:38 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=1100555&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jamie McClelland (jamiemcclelland) Assigned to: Nobody/Anonymous (nobody) Summary: Too many banned emails cause error Initial Comment: When I add a lot of banned emails (2,000), I get the following error: Bug in Mailman version 2.1.5 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/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 341, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string Python information: Variable Value sys.version 2.3.4 (#2, Dec 3 2004, 13:53:17) [GCC 3.3.5 (Debian 1:3.3.5-2)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE juviejustice+admin=2802000000698c6be441732800000033643636393736363938333663663931393038626136396563336235316637303261316364303166; support+admin=2802000000696f6de441732800000031313539613635393437653164613231303763393137306339363466643362393432666432396263 SERVER_SOFTWARE Apache/2.0.52 (Debian GNU/Linux) PHP/4.3.10-2 mod_ssl/2.0.52 OpenSSL/0.9.7e SCRIPT_NAME /mailman/admin SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 74313 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041128 Firefox/1.0 (Debian package 1.0-4) HTTP_CONNECTION keep-alive HTTP_REFERER https://xxx.xxx.xxx/mailman/admin/juviejustice/privacy/subscribing SERVER_NAME xxxx.xxxx.xxxx REMOTE_ADDR xxx.xxx.xxx.xxx PATH_TRANSLATED /srv/virtual_web/secure.mediajumpstart.net/public_html/juviejustice/privacy/subscribing SERVER_PORT 443 SERVER_ADDR 10.0.0.163 DOCUMENT_ROOT /srv/virtual_web/xxx.xxx.xxx/public_html PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /usr/lib/cgi-bin/mailman/admin SERVER_ADMIN apache@xxxx.xxx HTTP_HOST xxx.xxx.xxx HTTPS on REQUEST_URI /mailman/admin/juviejustice/privacy/subscribing HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 33792 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /juviejustice/privacy/subscribing ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100555&group_id=103 From noreply at sourceforge.net Wed Jan 12 03:28:21 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 03:28:26 2005 Subject: [ mailman-Bugs-1099840 ] error with bad email with % in addError in htmlformat.py Message-ID: Bugs item #1099840, was opened at 2005-01-10 23:56 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099840&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: error with bad email with % in addError in htmlformat.py Initial Comment: If an e-mail address being added to any of several properties via the list admin Gui is "bad" and also happens to contain a '%' character an error similar to the following occurs. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm doc.addError( File "/usr/local/mailman/Mailman/htmlformat.py", line 340, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string The error actually occurs in evaluation of errmsg % args where errmsg is 'Bad email address for option %(property)s: %(val)s' and the value of 'val' in args contains a '%'. This occurs in many places in the admin Gui where the entry is an e-mail address, e.g owner, moderator, ban_list, accept_these_nonmembers, etc. but not for example in a mass subscribe list. email addresses which cause the problem include for example abc%def.ghi and ab%c@def@ghi but not ab%c@def.ghi since this latter address is not deemed invalid. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 02:28 Message: Logged In: YES user_id=67709 Fixed in CVS and appear in 2.1.6 soon. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099840&group_id=103 From noreply at sourceforge.net Wed Jan 12 03:31:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 03:31:46 2005 Subject: [ mailman-Bugs-1100555 ] Too many banned emails cause error Message-ID: Bugs item #1100555, was opened at 2005-01-12 00:38 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100555&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jamie McClelland (jamiemcclelland) Assigned to: Nobody/Anonymous (nobody) Summary: Too many banned emails cause error Initial Comment: When I add a lot of banned emails (2,000), I get the following error: Bug in Mailman version 2.1.5 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/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 341, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string Python information: Variable Value sys.version 2.3.4 (#2, Dec 3 2004, 13:53:17) [GCC 3.3.5 (Debian 1:3.3.5-2)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE juviejustice+admin=2802000000698c6be441732800000033643636393736363938333663663931393038626136396563336235316637303261316364303166; support+admin=2802000000696f6de441732800000031313539613635393437653164613231303763393137306339363466643362393432666432396263 SERVER_SOFTWARE Apache/2.0.52 (Debian GNU/Linux) PHP/4.3.10-2 mod_ssl/2.0.52 OpenSSL/0.9.7e SCRIPT_NAME /mailman/admin SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 74313 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041128 Firefox/1.0 (Debian package 1.0-4) HTTP_CONNECTION keep-alive HTTP_REFERER https://xxx.xxx.xxx/mailman/admin/juviejustice/privacy/subscribing SERVER_NAME xxxx.xxxx.xxxx REMOTE_ADDR xxx.xxx.xxx.xxx PATH_TRANSLATED /srv/virtual_web/secure.mediajumpstart.net/public_html/juviejustice/privacy/subscribing SERVER_PORT 443 SERVER_ADDR 10.0.0.163 DOCUMENT_ROOT /srv/virtual_web/xxx.xxx.xxx/public_html PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /usr/lib/cgi-bin/mailman/admin SERVER_ADMIN apache@xxxx.xxx HTTP_HOST xxx.xxx.xxx HTTPS on REQUEST_URI /mailman/admin/juviejustice/privacy/subscribing HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 33792 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /juviejustice/privacy/subscribing ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 02:31 Message: Logged In: YES user_id=67709 Looks like an illegal email address is in the ban list. Same error as 1099840. Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100555&group_id=103 From noreply at sourceforge.net Wed Jan 12 03:34:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 03:34:32 2005 Subject: [ mailman-Bugs-1099138 ] Scrubber.py traceback Message-ID: Bugs item #1099138, was opened at 2005-01-09 22:36 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Owen Taylor (otaylor) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py traceback Initial Comment: Outgoing mail on one of our lists on mail.gnome.org was being held up because of a error that was occuring sending out digests. Jan 09 16:07:24 2005 (22410) Uncaught runner exception: len() of unsized object Jan 09 16:07:24 2005 (22410) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 262, in process size = len(payload) TypeError: len() of unsized object Unfortunately, I don't know what mail was triggering this... was trying to get the mailing list going and didn't want to spend a lot of time investigating. It's also not immediately clear to me how payload could end up as None there... from reading the code in email.Message maybe part._payload was None due to an earlier problem. I'll attach a workaround patch... the if: also covers the call to save_attachment() since that also tracebacked when I just fixed the call to len(). Anyways, filing in case it makes sense to someone more familiar with the guts of email.Message. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 02:34 Message: Logged In: YES user_id=67709 Well, the patch looks like for different project?? ---------------------------------------------------------------------- Comment By: Owen Taylor (otaylor) Date: 2005-01-09 23:15 Message: Logged In: YES user_id=63124 Oh, forgot to add say, this is python-2.2.3 and mailman-2.1.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 From noreply at sourceforge.net Wed Jan 12 03:59:07 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 03:59:15 2005 Subject: [ mailman-Bugs-1099138 ] Scrubber.py traceback Message-ID: Bugs item #1099138, was opened at 2005-01-09 22:36 Message generated for change (Comment added) made by otaylor You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Owen Taylor (otaylor) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py traceback Initial Comment: Outgoing mail on one of our lists on mail.gnome.org was being held up because of a error that was occuring sending out digests. Jan 09 16:07:24 2005 (22410) Uncaught runner exception: len() of unsized object Jan 09 16:07:24 2005 (22410) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 262, in process size = len(payload) TypeError: len() of unsized object Unfortunately, I don't know what mail was triggering this... was trying to get the mailing list going and didn't want to spend a lot of time investigating. It's also not immediately clear to me how payload could end up as None there... from reading the code in email.Message maybe part._payload was None due to an earlier problem. I'll attach a workaround patch... the if: also covers the call to save_attachment() since that also tracebacked when I just fixed the call to len(). Anyways, filing in case it makes sense to someone more familiar with the guts of email.Message. ---------------------------------------------------------------------- >Comment By: Owen Taylor (otaylor) Date: 2005-01-12 02:59 Message: Logged In: YES user_id=63124 Sorry about that ... that's what happens when you work on multiple computers and call patches things like 'diff'. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 02:34 Message: Logged In: YES user_id=67709 Well, the patch looks like for different project?? ---------------------------------------------------------------------- Comment By: Owen Taylor (otaylor) Date: 2005-01-09 23:15 Message: Logged In: YES user_id=63124 Oh, forgot to add say, this is python-2.2.3 and mailman-2.1.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 From noreply at sourceforge.net Wed Jan 12 05:11:32 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 05:11:41 2005 Subject: [ mailman-Bugs-1099138 ] Scrubber.py traceback Message-ID: Bugs item #1099138, was opened at 2005-01-09 22:36 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Owen Taylor (otaylor) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py traceback Initial Comment: Outgoing mail on one of our lists on mail.gnome.org was being held up because of a error that was occuring sending out digests. Jan 09 16:07:24 2005 (22410) Uncaught runner exception: len() of unsized object Jan 09 16:07:24 2005 (22410) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 262, in process size = len(payload) TypeError: len() of unsized object Unfortunately, I don't know what mail was triggering this... was trying to get the mailing list going and didn't want to spend a lot of time investigating. It's also not immediately clear to me how payload could end up as None there... from reading the code in email.Message maybe part._payload was None due to an earlier problem. I'll attach a workaround patch... the if: also covers the call to save_attachment() since that also tracebacked when I just fixed the call to len(). Anyways, filing in case it makes sense to someone more familiar with the guts of email.Message. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 04:11 Message: Logged In: YES user_id=67709 I believe I fixed this bug. it will appear in public CVS soon. ---------------------------------------------------------------------- Comment By: Owen Taylor (otaylor) Date: 2005-01-12 02:59 Message: Logged In: YES user_id=63124 Sorry about that ... that's what happens when you work on multiple computers and call patches things like 'diff'. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 02:34 Message: Logged In: YES user_id=67709 Well, the patch looks like for different project?? ---------------------------------------------------------------------- Comment By: Owen Taylor (otaylor) Date: 2005-01-09 23:15 Message: Logged In: YES user_id=63124 Oh, forgot to add say, this is python-2.2.3 and mailman-2.1.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 From noreply at sourceforge.net Wed Jan 12 11:47:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 11:47:12 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 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=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Wed Jan 12 11:51:06 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 11:51:12 2005 Subject: [ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address Message-ID: Bugs item #1100788, was opened at 2005-01-12 11:51 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=1100788&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 From noreply at sourceforge.net Wed Jan 12 12:41:56 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 12:42:02 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 11:41 Message: Logged In: YES user_id=67709 I believe this has been fixed. Can you show us an example message which is not decoded (scrubbed) in the archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Wed Jan 12 12:46:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 12:46:51 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 Message generated for change (Comment added) made by arnar You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- >Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 11:46 Message: Logged In: YES user_id=50086 My archive is not publically accessible, but I'l attach a message in html format, and in plain text with all headers (from the mbox archive). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 11:41 Message: Logged In: YES user_id=67709 I believe this has been fixed. Can you show us an example message which is not decoded (scrubbed) in the archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Wed Jan 12 13:47:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 13:47:37 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 12:47 Message: Logged In: YES user_id=67709 What is your mailman version? The latest CVS which I am testing at least can decode base64 encoded plain text message if charset and content-transfer-encoding are properly set as MIME compliant. I can test on my site if you can upload the original mail message (not the HTML page). ---------------------------------------------------------------------- Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 11:46 Message: Logged In: YES user_id=50086 My archive is not publically accessible, but I'l attach a message in html format, and in plain text with all headers (from the mbox archive). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 11:41 Message: Logged In: YES user_id=67709 I believe this has been fixed. Can you show us an example message which is not decoded (scrubbed) in the archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Wed Jan 12 15:25:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 12 15:25:33 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 Message generated for change (Comment added) made by arnar You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- >Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 14:25 Message: Logged In: YES user_id=50086 I'm using 2.1.5. I'm uploading the message with this commit, meant to do it earlier but got called away :o) Thank you for testing this for me, if it works with the CVS version I'll upgrade to that and stop whining :o) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 12:47 Message: Logged In: YES user_id=67709 What is your mailman version? The latest CVS which I am testing at least can decode base64 encoded plain text message if charset and content-transfer-encoding are properly set as MIME compliant. I can test on my site if you can upload the original mail message (not the HTML page). ---------------------------------------------------------------------- Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 11:46 Message: Logged In: YES user_id=50086 My archive is not publically accessible, but I'l attach a message in html format, and in plain text with all headers (from the mbox archive). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 11:41 Message: Logged In: YES user_id=67709 I believe this has been fixed. Can you show us an example message which is not decoded (scrubbed) in the archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Thu Jan 13 03:49:08 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 13 03:49:19 2005 Subject: [ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address Message-ID: Bugs item #1100788, was opened at 2005-01-12 10:51 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-13 02:49 Message: Logged In: YES user_id=67709 _badchars in Utils.py is essentially not for dompliance with the RFC2822. Any printable characters can appear in local part if you use 'quoted-string' (I vaguely suppose). This is mainly for security in Mailman and web interface I suppose. The character '/' was removed from this list in the CVS after close investigation. Problem was in the cookie which mailman send to the browser. '^' is a special character for regular expression and must be very careful in treating this. Another character which is listed in _badchars and allowd in RFC2822 is '|' which is used for pipeline commands and should be treated with care. Again, '/' will be removed from the next 2.1.6 release. BTW, I know '/' is used for X.400 gateway but how '^' is used? I want to assess this priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 From noreply at sourceforge.net Thu Jan 13 04:55:49 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 13 04:55:54 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-13 03:55 Message: Logged In: YES user_id=67709 Your message was properly decoded in my test site. (Sorry I don't want to expose it to public.) You may want to set your language charcter set as utf-8 in mm_cfg.py or your message may not be desplayed properly. (e.g. us-ascii is assumed in english list) ---------------------------------------------------------------------- Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 14:25 Message: Logged In: YES user_id=50086 I'm using 2.1.5. I'm uploading the message with this commit, meant to do it earlier but got called away :o) Thank you for testing this for me, if it works with the CVS version I'll upgrade to that and stop whining :o) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 12:47 Message: Logged In: YES user_id=67709 What is your mailman version? The latest CVS which I am testing at least can decode base64 encoded plain text message if charset and content-transfer-encoding are properly set as MIME compliant. I can test on my site if you can upload the original mail message (not the HTML page). ---------------------------------------------------------------------- Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 11:46 Message: Logged In: YES user_id=50086 My archive is not publically accessible, but I'l attach a message in html format, and in plain text with all headers (from the mbox archive). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 11:41 Message: Logged In: YES user_id=67709 I believe this has been fixed. Can you show us an example message which is not decoded (scrubbed) in the archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Thu Jan 13 09:39:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 13 09:39:23 2005 Subject: [ mailman-Bugs-1100786 ] base64 messages not decoded in archives Message-ID: Bugs item #1100786, was opened at 2005-01-12 10:47 Message generated for change (Comment added) made by arnar You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Arnar Birgisson (arnar) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: Bug 568456 has been marked out-of-date claiming that it "will be fixed in 2.1". I believe this hasn't been fixed. Please reopen 568456. ---------------------------------------------------------------------- >Comment By: Arnar Birgisson (arnar) Date: 2005-01-13 08:39 Message: Logged In: YES user_id=50086 That was it, I set DEFAULT_CHARSET to 'utf-8' and the message is properly decoded. Maybe I should have RTFM. :o) Thanks. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-13 03:55 Message: Logged In: YES user_id=67709 Your message was properly decoded in my test site. (Sorry I don't want to expose it to public.) You may want to set your language charcter set as utf-8 in mm_cfg.py or your message may not be desplayed properly. (e.g. us-ascii is assumed in english list) ---------------------------------------------------------------------- Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 14:25 Message: Logged In: YES user_id=50086 I'm using 2.1.5. I'm uploading the message with this commit, meant to do it earlier but got called away :o) Thank you for testing this for me, if it works with the CVS version I'll upgrade to that and stop whining :o) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 12:47 Message: Logged In: YES user_id=67709 What is your mailman version? The latest CVS which I am testing at least can decode base64 encoded plain text message if charset and content-transfer-encoding are properly set as MIME compliant. I can test on my site if you can upload the original mail message (not the HTML page). ---------------------------------------------------------------------- Comment By: Arnar Birgisson (arnar) Date: 2005-01-12 11:46 Message: Logged In: YES user_id=50086 My archive is not publically accessible, but I'l attach a message in html format, and in plain text with all headers (from the mbox archive). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 11:41 Message: Logged In: YES user_id=67709 I believe this has been fixed. Can you show us an example message which is not decoded (scrubbed) in the archive? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100786&group_id=103 From noreply at sourceforge.net Thu Jan 13 09:53:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 13 09:53:40 2005 Subject: [ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address Message-ID: Bugs item #1100788, was opened at 2005-01-12 11:51 Message generated for change (Comment added) made by reeg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- >Comment By: reeg (reeg) Date: 2005-01-13 09:53 Message: Logged In: YES user_id=1146038 Till now I had only a problem with the / because in one company the have adresses like "name/departmant/country@domain". Thanks for the change in CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-13 03:49 Message: Logged In: YES user_id=67709 _badchars in Utils.py is essentially not for dompliance with the RFC2822. Any printable characters can appear in local part if you use 'quoted-string' (I vaguely suppose). This is mainly for security in Mailman and web interface I suppose. The character '/' was removed from this list in the CVS after close investigation. Problem was in the cookie which mailman send to the browser. '^' is a special character for regular expression and must be very careful in treating this. Another character which is listed in _badchars and allowd in RFC2822 is '|' which is used for pipeline commands and should be treated with care. Again, '/' will be removed from the next 2.1.6 release. BTW, I know '/' is used for X.400 gateway but how '^' is used? I want to assess this priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 From noreply at sourceforge.net Thu Jan 13 16:35:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 13 16:35:45 2005 Subject: [ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address Message-ID: Bugs item #1100788, was opened at 2005-01-12 05:51 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-13 10:35 Message: Logged In: YES user_id=12800 Ideally, we'd allow any RFC 2822 legal address in, but I'd rather be secure than accept very uncommon corner cases. So where some characters cause Mailman problems, it's okay to leave them in _badchars. I think the number of people this will affect will be exceedingly small. ---------------------------------------------------------------------- Comment By: reeg (reeg) Date: 2005-01-13 03:53 Message: Logged In: YES user_id=1146038 Till now I had only a problem with the / because in one company the have adresses like "name/departmant/country@domain". Thanks for the change in CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-12 21:49 Message: Logged In: YES user_id=67709 _badchars in Utils.py is essentially not for dompliance with the RFC2822. Any printable characters can appear in local part if you use 'quoted-string' (I vaguely suppose). This is mainly for security in Mailman and web interface I suppose. The character '/' was removed from this list in the CVS after close investigation. Problem was in the cookie which mailman send to the browser. '^' is a special character for regular expression and must be very careful in treating this. Another character which is listed in _badchars and allowd in RFC2822 is '|' which is used for pipeline commands and should be treated with care. Again, '/' will be removed from the next 2.1.6 release. BTW, I know '/' is used for X.400 gateway but how '^' is used? I want to assess this priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 From noreply at sourceforge.net Fri Jan 14 10:00:06 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 14 10:00:09 2005 Subject: [ mailman-Bugs-1102176 ] Track invited emails Message-ID: Bugs item #1102176, was opened at 2005-01-14 11:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1102176&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Dwayne Bailey (dwaynebailey) Assigned to: Nobody/Anonymous (nobody) Summary: Track invited emails Initial Comment: Currently there is no tracking of people who have been sent invite emails. This cause a problem in that you might invite people from a given list of emails to join the mailing list. Then from some other list or at some other time you might issue another invite. Receiving a number of invites from a list that you are not interested looks bad. It would be great if Mailman could track email addresses that have been invited and just like invites are not sent to people already subscribed they are not sent to people already invited. The use could of course have the option to ignore the "already invited" list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1102176&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:11:18 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:11:24 2005 Subject: [ mailman-Patches-933762 ] fix for #880073 list-id can violate RFC2919 Message-ID: Patches item #933762, was opened at 2004-04-12 17:22 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for #880073 list-id can violate RFC2919 Initial Comment: To make sure RFC2919 is not violated. "<" and ">" will be added if no list description exists. The maxlinelen=998 is a precaution to keep the may line length of RFC2822. Fixes [ 880073 ] list-id might violate RFC2919 and RFC2822 https://sourceforge.net/tracker/index.php?func=detail&aid=880073&group_id=103&atid=100103 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:11 Message: Logged In: YES user_id=67709 This was already fixed in CVS/2.1.6b. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:12:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:12:32 2005 Subject: [ mailman-Bugs-880073 ] list-id might violate RFC2919 and RFC2822 Message-ID: Bugs item #880073, was opened at 2004-01-19 20:23 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: list-id might violate RFC2919 and RFC2822 Initial Comment: Code in http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/CookHeaders.py?rev=2.33.2.5&view=markup (as shipped with mailman 2.1.4) will use formataddr for the List-Id: listid_h = formataddr((desc, listid)) This will violate the RFC2919, if not(desc), because the angle-brackets might be left out. 3. The List-Id Header Field The List-Id header MAY optionally include a description by including it as a "phrase" [DRUMS] before the angle-bracketed list identifier. The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF Unlike most headers in [RFC822], the List-Id header does not allow free insertion of whitespace and comments around tokens. [Go inside ~mailman/bin] python Python 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. >>> import paths >>> from email.Utils import formataddr >>> formataddr(("A strange mailing list","strange.list.org")) 'A strange mailing list ' >>> formataddr((None,"strange.list.org")) 'strange.list.org' >>> formataddr(("","strange.list.org")) 'strange.list.org' Solution: go back to old code and check http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_id=57904&aid=665732 to limit the line length so you don't violate RFC2822 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:12 Message: Logged In: YES user_id=67709 This was already fixed in CVS/2.1.6b ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-12 17:23 Message: Logged In: YES user_id=113859 Added a fix for the problem: [ 933762 ] fix for #880073 list-id can violate RFC2919 https://sourceforge.net/tracker/index.php?func=detail&aid=933762&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-19 20:25 Message: Logged In: YES user_id=113859 I'm raising the priority to 6 because many people get annoyed if the List-ID headers change. Mailman 2.1.3 did better in the RFC2919 regard, 2.1.4 breaks it in an attempt to fix other bugs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:16:19 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:16:28 2005 Subject: [ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address Message-ID: Bugs item #1100788, was opened at 2005-01-12 10:51 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Later Priority: 5 Submitted By: reeg (reeg) Assigned to: Nobody/Anonymous (nobody) Summary: ^ and / are allowed charactes in email address Initial Comment: According RFC 2822 (section 3.4.1 and 3.2.4) the characters ^ and / are allowed in the localpart of an email address. But in the file Mailman/Utils.py line 201 they are listed as _badchars. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:16 Message: Logged In: YES user_id=67709 Closing because '/' was already fixed in 2.1.6. Others should be fixed in 3.0 (later). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-13 15:35 Message: Logged In: YES user_id=12800 Ideally, we'd allow any RFC 2822 legal address in, but I'd rather be secure than accept very uncommon corner cases. So where some characters cause Mailman problems, it's okay to leave them in _badchars. I think the number of people this will affect will be exceedingly small. ---------------------------------------------------------------------- Comment By: reeg (reeg) Date: 2005-01-13 08:53 Message: Logged In: YES user_id=1146038 Till now I had only a problem with the / because in one company the have adresses like "name/departmant/country@domain". Thanks for the change in CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-13 02:49 Message: Logged In: YES user_id=67709 _badchars in Utils.py is essentially not for dompliance with the RFC2822. Any printable characters can appear in local part if you use 'quoted-string' (I vaguely suppose). This is mainly for security in Mailman and web interface I suppose. The character '/' was removed from this list in the CVS after close investigation. Problem was in the cookie which mailman send to the browser. '^' is a special character for regular expression and must be very careful in treating this. Another character which is listed in _badchars and allowd in RFC2822 is '|' which is used for pipeline commands and should be treated with care. Again, '/' will be removed from the next 2.1.6 release. BTW, I know '/' is used for X.400 gateway but how '^' is used? I want to assess this priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100788&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:27:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:27:52 2005 Subject: [ mailman-Bugs-1090208 ] Password reminder bug (wrong "From" address, etc) Message-ID: Bugs item #1090208, was opened at 2004-12-23 05:13 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_id=103 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Brett Garrett (dolphyn) Assigned to: Nobody/Anonymous (nobody) Summary: Password reminder bug (wrong "From" address, etc) Initial Comment: Summary of bug: On a system with multiple domains and multiple lists, the password reminder sometimes contains information about a list to which the user is not subscribed, or in some cases, about a list that does not exist. Likewise, the "From" address of the password reminder can be incorrect. Details: The cron script "mailpasswds" contains the following code: siteowner = Utils.get_site_email(host, 'owner') sitereq = Utils.get_site_email(host, 'request') sitebounce = Utils.get_site_email (host, 'bounces') The problem is, this code is oblivious to the user's actual subscriptions. On a CPanel server, for example, it always defaults to mailman-owner@host, etc. This results in confusion among users. Since the "From" address of the reminder is mailman- owner@host and that address is also referenced in the mail, users send their questions to that address -- which may go to the server administrator, or to nobody at all, instead of the appropriate list owner. On my setup (a CPanel system) the following replacement code appears to correct most of the problem (in combination with an "import string" statement near the top of the script): siteowner = string.replace ( listaddr, '@', '- owner@' ) sitereq = string.replace ( listaddr, '@', '- request@' ) sitebounce = string.replace ( listaddr, '@', '- bounces@' ) I have not tested it thoroughly, but I think it corrects the siteowner and sitereq values. (For some reason the corrected sitebounce address does not have any effect. The reminder messages still have a return-path of mailman-bounces@servername instead of the appropriate listname-bounces@host. But, I don't think this matters as much as making sure the siteowner and sitereq addresses are correct.) Thank you! ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:27 Message: Logged In: YES user_id=67709 The feature that monthly password reminder is sent from 'mailman-owner' and not from the list owner is introduced from 2.1. This is because a member can subscribe to multiple lists and we cannnot decide which list should be picked for the sender. So was introduced the 'site list.' From NEWS: o There is now a `site list' which is a mailing list that must be created first, and from which all password reminders appear to come from. It is recommended that this list be called "mailman@your.site". ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-12-23 11:12 Message: Logged In: YES user_id=75166 CPanel sells a modified version of Mailman as part of its commercial hosting product. They have not made their modifications available to the Open Source developers and users of Mailman. Unless you can identify that this problem is present with unmodified, stable Mailman distribution source from sourceforge you will have to take this matter up with your ISP/or CPanel. This is not least because without the source code of the CPanel modifications it will be problematic diagnosing the cause of the problem you observe. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:37:55 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:37:59 2005 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 08:54 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-17 00:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-08 01:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-30 04:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:39:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:39:31 2005 Subject: [ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii Message-ID: Bugs item #1090439, was opened at 2004-12-23 16:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 Category: None Group: 2.1 (stable) Status: Open >Resolution: Later Priority: 5 Submitted By: Bernhard Reiter (ber) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:42:31 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:42:35 2005 Subject: [ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii Message-ID: Bugs item #1090439, was opened at 2004-12-23 16:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: Later Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:42 Message: Logged In: YES user_id=67709 Sorry but fix will be after 2.1.6 release. In the meantime, the site owner can reset the password of this person from bin/withlist script. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:52:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:52:47 2005 Subject: [ mailman-Bugs-1100227 ] stops delivering messages Message-ID: Bugs item #1100227, was opened at 2005-01-11 15:45 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100227&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: steev hise (steev23) Assigned to: Nobody/Anonymous (nobody) Summary: stops delivering messages Initial Comment: Every once in a while, at random intervals (like after running fine for a few weeks or more), suddenly messages stop getting sent out to all mailing lists. They still go to the archives, they just don't get sent. can't find any clues in the logs. Is this a known bug? couldn't find one in tracker. Mailman Version: 2.1.5 python sys.version = 2.2.2 (#1, May 3 2003, 19:23:40) [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-81)] thanx, steev@detritus.net ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:52 Message: Logged In: YES user_id=67709 Too few information to answer. Have you checked both Mailman and MTA logs? Are you sure all the qrunnders are running (paticularly OutgoingRunner)? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1100227&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:56:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:57:15 2005 Subject: [ mailman-Feature Requests-1102176 ] Track invited emails Message-ID: Feature Requests item #1102176, was opened at 2005-01-14 09:00 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1102176&group_id=103 Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dwayne Bailey (dwaynebailey) Assigned to: Nobody/Anonymous (nobody) Summary: Track invited emails Initial Comment: Currently there is no tracking of people who have been sent invite emails. This cause a problem in that you might invite people from a given list of emails to join the mailing list. Then from some other list or at some other time you might issue another invite. Receiving a number of invites from a list that you are not interested looks bad. It would be great if Mailman could track email addresses that have been invited and just like invites are not sent to people already subscribed they are not sent to people already invited. The use could of course have the option to ignore the "already invited" list. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:56 Message: Logged In: YES user_id=67709 This is more of a feature request. So moving this to RFE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1102176&group_id=103 From noreply at sourceforge.net Mon Jan 17 01:58:16 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 01:58:23 2005 Subject: [ mailman-Bugs-1082913 ] Digest-lists wont work with 2.1.6a Message-ID: Bugs item #1082913, was opened at 2004-12-10 13:47 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tommi Tervo (tomtervo) Assigned to: Nobody/Anonymous (nobody) Summary: Digest-lists wont work with 2.1.6a Initial Comment: If some lists uses digests mailman will crash with following backtrace. Headers from mail which caused crash: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.4i Dec 09 14:39:27 2004 (4051) Traceback (most recent call last): File "/p/appl/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/p/appl/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/p/appl/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests payload = unicode(payload, mcset, 'replace' LookupError: unknown encoding: %charset ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-11 01:38 Message: Logged In: YES user_id=67709 Thank you for the report. I believe I fixed this in 2.1.6a2. Please try. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_id=103 From noreply at sourceforge.net Mon Jan 17 09:42:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 09:43:12 2005 Subject: [ mailman-Bugs-1082913 ] Digest-lists wont work with 2.1.6a Message-ID: Bugs item #1082913, was opened at 2004-12-10 15:47 Message generated for change (Comment added) made by tomtervo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Tommi Tervo (tomtervo) Assigned to: Nobody/Anonymous (nobody) Summary: Digest-lists wont work with 2.1.6a Initial Comment: If some lists uses digests mailman will crash with following backtrace. Headers from mail which caused crash: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.4i Dec 09 14:39:27 2004 (4051) Traceback (most recent call last): File "/p/appl/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/p/appl/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/p/appl/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests payload = unicode(payload, mcset, 'replace' LookupError: unknown encoding: %charset ---------------------------------------------------------------------- >Comment By: Tommi Tervo (tomtervo) Date: 2005-01-17 10:42 Message: Logged In: YES user_id=1094436 I've been busy lately but I upgraded my mailman installation to current cvs branch on Saturday and this problem seems to fixed. Thanks for your work. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-11 03:38 Message: Logged In: YES user_id=67709 Thank you for the report. I believe I fixed this in 2.1.6a2. Please try. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_id=103 From noreply at sourceforge.net Mon Jan 17 10:02:26 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 10:02:29 2005 Subject: [ mailman-Patches-1103745 ] Danish translation update Message-ID: Patches item #1103745, was opened at 2005-01-17 10:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1103745&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish translation update Initial Comment: Here's the promised update... - Fix new fuzzies - Add missing translations ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1103745&group_id=103 From noreply at sourceforge.net Mon Jan 17 10:02:49 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 10:02:54 2005 Subject: [ mailman-Patches-1103745 ] Danish translation update Message-ID: Patches item #1103745, was opened at 2005-01-17 10:02 Message generated for change (Settings changed) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1103745&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish translation update Initial Comment: Here's the promised update... - Fix new fuzzies - Add missing translations ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1103745&group_id=103 From noreply at sourceforge.net Mon Jan 17 12:27:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 12:27:51 2005 Subject: [ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii Message-ID: Bugs item #1090439, was opened at 2004-12-23 17:31 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: Later Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2005-01-17 12:27 Message: Logged In: YES user_id=113859 If a user changes his password and just types a character on the keyboard that is non-usascii. :-) Restricting the password characters to usascii seems to be a bad idea because it will lower the possibilities for passwords, making them cryptographically weaker. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 01:42 Message: Logged In: YES user_id=67709 Sorry but fix will be after 2.1.6 release. In the meantime, the site owner can reset the password of this person from bin/withlist script. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 01:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 From noreply at sourceforge.net Mon Jan 17 14:06:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 17 14:06:04 2005 Subject: [ mailman-Patches-1103745 ] Danish translation update Message-ID: Patches item #1103745, was opened at 2005-01-17 09:02 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1103745&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish translation update Initial Comment: Here's the promised update... - Fix new fuzzies - Add missing translations ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 13:05 Message: Logged In: YES user_id=67709 Thank you, Tom. Commited in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1103745&group_id=103 From noreply at sourceforge.net Tue Jan 18 01:11:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 01:11:27 2005 Subject: [ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii Message-ID: Bugs item #1090439, was opened at 2004-12-23 16:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-18 00:11 Message: Logged In: YES user_id=67709 OK, fix was in time for 2.1.6 for password reminder from web interface only; monthly reminder has already been fixed. Password retrieval by mail command is still not fixed. 8bit password by mail command needs more study because the request mail might be encoded (quoted or base64). I would prefer restricting password characters within ascii-printables because there is no cryptography in mailman user passwords. You only get (steal) the config file to get the plain text password. You don't have to run 'crack' to guess the password from crypted passwd entry like in Unix. In any event, next major version of mailman should be free of user password. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2005-01-17 11:27 Message: Logged In: YES user_id=113859 If a user changes his password and just types a character on the keyboard that is non-usascii. :-) Restricting the password characters to usascii seems to be a bad idea because it will lower the possibilities for passwords, making them cryptographically weaker. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:42 Message: Logged In: YES user_id=67709 Sorry but fix will be after 2.1.6 release. In the meantime, the site owner can reset the password of this person from bin/withlist script. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 00:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 From noreply at sourceforge.net Tue Jan 18 01:24:57 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 01:25:01 2005 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: Bugs item #1080508, was opened at 2004-12-07 10:12 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Tommi Tervo (tomtervo) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6a + python 2.4 crashes Initial Comment: I upgraded first to 2.1.6a from 2.1.5 -> chinese (gb2312) lists stopped working. Then I upgraded python from 2.3.4 to 2.4 and that problem disappeared. But now I'll get crashes like this: Dec 07 11:24:52 2004 (16871) Traceback (most recent call last): File "/p/appl/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/p/appl/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/p/appl/mailman/Mailman/Archiver/Archiver.py", line 217, in ArchiveMail h.close() File "/p/appl/mailman/Mailman/Archiver/pipermail.py", line 314, in close self.write_TOC() File "/p/appl/mailman/Mailman/Archiver/HyperArch.py", line 1067, in write_TOC toc.write(self.html_TOC()) File "/p/appl/mailman/Mailman/Archiver/HyperArch.py", line 752, in html_TOC accum.append(self.html_TOC_entry(a)) File "/p/appl/mailman/Mailman/Archiver/HyperArch.py", line 773, in html_TOC_en try templ = '[ ' + _('Gzip\'d Text%(sz)s') \ File "/p/appl/mailman/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character '?' (0xffffffe4) at index 16 Dec 07 11:24:53 2004 (16871) SHUNTING: 1102411483.73262+a65edf245b1a5299df373b8f a4871f229f16e83a ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-09 10:17 Message: Logged In: YES user_id=1094436 Many thanks to you, I updated that .po file and it seems to work! ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-08 23:36 Message: Logged In: YES user_id=67709 I found a bug in Finlandic translation catalog. This will be fixed before final release of 2.1.6. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 16:45 Message: Logged In: YES user_id=1094436 I can send you privately a bunch of problematic qfiles/shunts if those help more than my poor guesses. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 11:41 Message: Logged In: YES user_id=1094436 This type of crash doesn't come from chinese lists. I suspect that Subject line =E4 which is ? ( a umlaut) is cause of this crash. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [RKK] =?iso-8859-1?q?Taas_meit=E4_raha=24tettiin!?= ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 13:42 Message: Logged In: YES user_id=67709 Currently, Chinese (both China and Taiwan) are not supported. I am curious how you manage gb2312 list. And also, what language message caused this error? There may be incomplete translations and may cause such error. Particularly, big5 (zh_TW) may contain '%' in the second byte of a 16bit character and may cause trouble. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 From noreply at sourceforge.net Tue Jan 18 13:12:37 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 13:12:58 2005 Subject: [ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii Message-ID: Bugs item #1090439, was opened at 2004-12-23 17:31 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 Category: None Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Tokio Kikuchi (tkikuchi) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2005-01-18 13:12 Message: Logged In: YES user_id=113859 It might not be the right place to discuss it, but the restriction of character sets makes it easier to guess and try the password and less usable for non-English users because they probably have a harder time remembering the password. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-18 01:11 Message: Logged In: YES user_id=67709 OK, fix was in time for 2.1.6 for password reminder from web interface only; monthly reminder has already been fixed. Password retrieval by mail command is still not fixed. 8bit password by mail command needs more study because the request mail might be encoded (quoted or base64). I would prefer restricting password characters within ascii-printables because there is no cryptography in mailman user passwords. You only get (steal) the config file to get the plain text password. You don't have to run 'crack' to guess the password from crypted passwd entry like in Unix. In any event, next major version of mailman should be free of user password. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2005-01-17 12:27 Message: Logged In: YES user_id=113859 If a user changes his password and just types a character on the keyboard that is non-usascii. :-) Restricting the password characters to usascii seems to be a bad idea because it will lower the possibilities for passwords, making them cryptographically weaker. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 01:42 Message: Logged In: YES user_id=67709 Sorry but fix will be after 2.1.6 release. In the meantime, the site owner can reset the password of this person from bin/withlist script. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-17 01:39 Message: Logged In: YES user_id=67709 I have no idea how laten-1 8bit characters to be included in a us-ascii english list password reminder. Maybe we should restrict password within us-ascii printables. I want to work on this direction so I am assigning this to myself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 From noreply at sourceforge.net Tue Jan 18 13:44:43 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 13:44:46 2005 Subject: [ mailman-Bugs-1104433 ] Configurable per-user/per-subscription subject prefix Message-ID: Bugs item #1104433, was opened at 2005-01-18 12:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104433&group_id=103 Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable per-user/per-subscription subject prefix Initial Comment: I've had a request from a list member who would like us to add a subject prefix to all the lists on our server (mail.gnome.org), as his mail client can't do any kind of automatic filtering. We are obviously reluctant to change the status quo, as many people (e.g. PDA/mobile users) would then respond asking us to remove them. Instead, I decided to file this feature request to make it (per-subscription) configurable. It would have one of three possible values; use the default list setting, override on or override off. This would allow users to please themselves, and in some cases overcome problems caused by limitations in their mailclient. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104433&group_id=103 From noreply at sourceforge.net Tue Jan 18 18:19:52 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 18:19:55 2005 Subject: [ mailman-Bugs-1104635 ] building with old msgmerge (without option "-U") Message-ID: Bugs item #1104635, was opened at 2005-01-18 18:19 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=1104635&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: building with old msgmerge (without option "-U") Initial Comment: Building mailman 2.1.6beta1 on Debian woody yields an error message during make: /usr/bin/python2.2 ../build/bin/msgfmt.py -o zh_CN/LC_MESSAGES/mailman.mo zh_CN/LC_MESSAGES/mailman.po Merging new template file with existing translations msgmerge -U zh_TW/LC_MESSAGES/mailman.po mailman.pot || touch zh_TW/LC_MESSAGES/mailman.po msgmerge: invalid option -- U Try `msgmerge --help' for more information. /usr/bin/python2.2 ../build/bin/msgfmt.py -o zh_TW/LC_MESSAGES/mailman.mo zh_TW/LC_MESSAGES/mailman.po woody's msgmerge is too old to support -U (or --update). It seems as if mailman.po did not get updated for zh_TW, all other languages are ok. It's only a cosmetic bug, because make doesn't abort. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104635&group_id=103 From noreply at sourceforge.net Tue Jan 18 18:30:44 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 18:30:48 2005 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 03:54 Message generated for change (Comment added) made by egagnon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- >Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-18 12:30 Message: Logged In: YES user_id=15365 I am attaching a screen shot of the content filtering settings (see the options.png attachment I have added to this bug report). In short, content filtering is disabled, so I don't think it is the cause of the problem. :-/ Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-16 19:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-07 20:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-29 23:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Tue Jan 18 18:32:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 18:32:24 2005 Subject: [ mailman-Bugs-1104645 ] INSTALL points to wrong location in 2.1.6b1 Message-ID: Bugs item #1104645, was opened at 2005-01-18 18:32 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=1104645&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL points to wrong location in 2.1.6b1 Initial Comment: INSTALL in 2.1.6b1 says: For installation or upgrading instructions, please see the doc/mailman-install/index.html file. But there is only admin/www/mailman-install/index.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104645&group_id=103 From noreply at sourceforge.net Tue Jan 18 18:34:55 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 18 18:34:58 2005 Subject: [ mailman-Bugs-1104646 ] Messages Duplicated to Similar List Names Message-ID: Bugs item #1104646, was opened at 2005-01-18 12:34 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=1104646&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: istvans (istvans) Assigned to: Nobody/Anonymous (nobody) Summary: Messages Duplicated to Similar List Names Initial Comment: We have 2 mailings lists for students: One is called "undergrads", and the other is called "grads". When a message is posted to either list alone the messages process correctly. Subscribers receive only one copy for each list to which they are subscribed. However if BOTH lists are included in a single TO: in a message (So To: grads@host, undergrads@host) the end result is 3 (THREE) messages: One message from [Grads] One message from [Undergrads] One message from [Grads][Undergrads] these lists are not configured to be umbrella lists. All other lists behave correctly so if messages are sent to the lists called: Faculty, Staff, General the message processing behaves correctly. A single message addressed as follows: TO: staff@host, faculty@host, general@ host, grads@host delivers only a single message to each subscriber. However if the To is modified to include both the Grads and Undergrads a message will be sent to [Grads][Undergrads] The only issue seems to be with the word "grads" being a complete subset of the word "undergrads" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104646&group_id=103 From noreply at sourceforge.net Wed Jan 19 03:25:52 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 03:25:57 2005 Subject: [ mailman-Bugs-1104635 ] building with old msgmerge (without option "-U") Message-ID: Bugs item #1104635, was opened at 2005-01-18 17:19 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104635&group_id=103 Category: configuring/installing Group: 2.1 beta >Status: Closed Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: building with old msgmerge (without option "-U") Initial Comment: Building mailman 2.1.6beta1 on Debian woody yields an error message during make: /usr/bin/python2.2 ../build/bin/msgfmt.py -o zh_CN/LC_MESSAGES/mailman.mo zh_CN/LC_MESSAGES/mailman.po Merging new template file with existing translations msgmerge -U zh_TW/LC_MESSAGES/mailman.po mailman.pot || touch zh_TW/LC_MESSAGES/mailman.po msgmerge: invalid option -- U Try `msgmerge --help' for more information. /usr/bin/python2.2 ../build/bin/msgfmt.py -o zh_TW/LC_MESSAGES/mailman.mo zh_TW/LC_MESSAGES/mailman.po woody's msgmerge is too old to support -U (or --update). It seems as if mailman.po did not get updated for zh_TW, all other languages are ok. It's only a cosmetic bug, because make doesn't abort. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-19 02:25 Message: Logged In: YES user_id=67709 mailman.po files are essentially 'msgmerge'd before shipping in the tar ball. So, this error is safely ignored unless you are going to generate your own mailman.po catalog by yourself. There is also a problem in Chinese(Taiwan) charset (Big5) that it allows special characters (like '\') in the second byte of 16bit code. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104635&group_id=103 From noreply at sourceforge.net Wed Jan 19 03:33:05 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 03:33:09 2005 Subject: [ mailman-Bugs-1104645 ] INSTALL points to wrong location in 2.1.6b1 Message-ID: Bugs item #1104645, was opened at 2005-01-18 17:32 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104645&group_id=103 Category: documentation Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL points to wrong location in 2.1.6b1 Initial Comment: INSTALL in 2.1.6b1 says: For installation or upgrading instructions, please see the doc/mailman-install/index.html file. But there is only admin/www/mailman-install/index.html ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-19 02:33 Message: Logged In: YES user_id=67709 Thank you. This was fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104645&group_id=103 From noreply at sourceforge.net Wed Jan 19 03:45:40 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 03:45:44 2005 Subject: [ mailman-Feature Requests-1104433 ] Configurable per-user/per-subscription subject prefix Message-ID: Feature Requests item #1104433, was opened at 2005-01-18 12:44 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_id=103 >Category: None Group: None Status: Open Resolution: None >Priority: 3 Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable per-user/per-subscription subject prefix Initial Comment: I've had a request from a list member who would like us to add a subject prefix to all the lists on our server (mail.gnome.org), as his mail client can't do any kind of automatic filtering. We are obviously reluctant to change the status quo, as many people (e.g. PDA/mobile users) would then respond asking us to remove them. Instead, I decided to file this feature request to make it (per-subscription) configurable. It would have one of three possible values; use the default list setting, override on or override off. This would allow users to please themselves, and in some cases overcome problems caused by limitations in their mailclient. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-19 02:45 Message: Logged In: YES user_id=67709 This should be submitted as Feature Request. BTW, many mailing list users are happy with subject prefixes. Why not GNOME users? ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_id=103 From noreply at sourceforge.net Wed Jan 19 05:31:38 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 05:31:43 2005 Subject: [ mailman-Bugs-1104646 ] Messages Duplicated to Similar List Names Message-ID: Bugs item #1104646, was opened at 2005-01-18 17:34 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104646&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: istvans (istvans) Assigned to: Nobody/Anonymous (nobody) Summary: Messages Duplicated to Similar List Names Initial Comment: We have 2 mailings lists for students: One is called "undergrads", and the other is called "grads". When a message is posted to either list alone the messages process correctly. Subscribers receive only one copy for each list to which they are subscribed. However if BOTH lists are included in a single TO: in a message (So To: grads@host, undergrads@host) the end result is 3 (THREE) messages: One message from [Grads] One message from [Undergrads] One message from [Grads][Undergrads] these lists are not configured to be umbrella lists. All other lists behave correctly so if messages are sent to the lists called: Faculty, Staff, General the message processing behaves correctly. A single message addressed as follows: TO: staff@host, faculty@host, general@ host, grads@host delivers only a single message to each subscriber. However if the To is modified to include both the Grads and Undergrads a message will be sent to [Grads][Undergrads] The only issue seems to be with the word "grads" being a complete subset of the word "undergrads" ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-19 04:31 Message: Logged In: YES user_id=67709 This does not occur in my similar environment. Isn't this a MTA problem? It might occur if you are using procmail as a local mailer and utilizing regular expressions in sorting the messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1104646&group_id=103 From noreply at sourceforge.net Wed Jan 19 09:43:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 09:43:58 2005 Subject: [ mailman-Feature Requests-1104433 ] Configurable per-user/per-subscription subject prefix Message-ID: Feature Requests item #1104433, was opened at 2005-01-18 12:44 Message generated for change (Comment added) made by rossigee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable per-user/per-subscription subject prefix Initial Comment: I've had a request from a list member who would like us to add a subject prefix to all the lists on our server (mail.gnome.org), as his mail client can't do any kind of automatic filtering. We are obviously reluctant to change the status quo, as many people (e.g. PDA/mobile users) would then respond asking us to remove them. Instead, I decided to file this feature request to make it (per-subscription) configurable. It would have one of three possible values; use the default list setting, override on or override off. This would allow users to please themselves, and in some cases overcome problems caused by limitations in their mailclient. ---------------------------------------------------------------------- >Comment By: Ross Golder (rossigee) Date: 2005-01-19 08:43 Message: Logged In: YES user_id=20872 Some lists use prefixes, some don't. Some users that subscribe to many lists want consistency, but we don't want to have to determine and enforce a site-wide policy and deal with all the ensuing arguments. This feature shifts the decision from the list/site managers to the individuals users. Basic headache prevention. The main argument for prefixes seems to be 'I can quickly identify what the mail is about in my inbox', where users haven't got or don't use their client's header filtering features. The main argument against prefixes seems to be 'I just get a screenful of list prefixes when I try to view my list folders', where users are trying to use mail clients in a low screen resolution (e.g. old VGA screen, palm/PDA device, mobile phone, small desktop window whatever). Sorry for misfiling it. Haven't used SF for a while - forgot that feature requests and bugs aren't mixed like in bugzilla. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-19 02:45 Message: Logged In: YES user_id=67709 This should be submitted as Feature Request. BTW, many mailing list users are happy with subject prefixes. Why not GNOME users? ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_id=103 From noreply at sourceforge.net Wed Jan 19 22:18:59 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 22:19:02 2005 Subject: [ mailman-Bugs-1105595 ] Add a date submitted column to Administrative requests page Message-ID: Bugs item #1105595, was opened at 2005-01-19 13:18 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=1105595&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: Add a date submitted column to Administrative requests page Initial Comment: When managing a list with a moderated membership policy, it is useful to see how old a pending request is. For one list, we are emailing all new subscribers and asking them why they want to join, and if they haven't replied after 7 days then I want to automatically reject their membership request. I can't easily do this on the Administrative requests page because the requests are not in date order and do not have the date they were submitted. The date submitted is on the daily reminder email, so I know it's there in mailman, and it would be ever so useful to have it on the Administrative requests page as well. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1105595&group_id=103 From noreply at sourceforge.net Wed Jan 19 22:19:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 22:19:46 2005 Subject: [ mailman-Feature Requests-1105595 ] Add a date submitted column to Administrative requests page Message-ID: Feature Requests item #1105595, was opened at 2005-01-19 13:18 Message generated for change (Settings changed) made by jcdill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1105595&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: Add a date submitted column to Administrative requests page Initial Comment: When managing a list with a moderated membership policy, it is useful to see how old a pending request is. For one list, we are emailing all new subscribers and asking them why they want to join, and if they haven't replied after 7 days then I want to automatically reject their membership request. I can't easily do this on the Administrative requests page because the requests are not in date order and do not have the date they were submitted. The date submitted is on the daily reminder email, so I know it's there in mailman, and it would be ever so useful to have it on the Administrative requests page as well. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1105595&group_id=103 From noreply at sourceforge.net Wed Jan 19 22:20:40 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 19 22:20:42 2005 Subject: [ mailman-Feature Requests-1012925 ] cc rejects to admins Message-ID: Feature Requests item #1012925, was opened at 2004-08-20 07:27 Message generated for change (Settings changed) made by jcdill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1012925&group_id=103 Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Aahz (aahz) Assigned to: Nobody/Anonymous (nobody) Summary: cc rejects to admins Initial Comment: It'd be useful if you could optionally cc reject messages to the admin address of a list (so that multiple admins keep track of what's going on). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1012925&group_id=103 From noreply at sourceforge.net Thu Jan 20 14:36:09 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 20 14:36:12 2005 Subject: [ mailman-Bugs-1105972 ] archive permissions Message-ID: Bugs item #1105972, was opened at 2005-01-20 13:36 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=1105972&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jason Gallagher (windowlicker) Assigned to: Nobody/Anonymous (nobody) Summary: archive permissions Initial Comment: Mailman archive directories are created with owner apache:mailman and permissions drwxrwsr-x (substitute whatever user the webserver runs as for 'apache'). This means the contents are vulnerable to being renamed (or in the case of index.html deleted/modified) by any CGI script running as the default user on the same webserver. One fix would be to use the SuexecUserGroup directive in the case where apache is being used. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1105972&group_id=103 From noreply at sourceforge.net Sat Jan 22 03:54:44 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 22 03:54:48 2005 Subject: [ mailman-Patches-1107169 ] Re-use member_moderation_notice for generic_nonmember_action Message-ID: Patches item #1107169, was opened at 2005-01-22 02:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1107169&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Re-use member_moderation_notice for generic_nonmember_action Initial Comment: With Mailman 2.1.5, it's possible to create a fairly nicely worded rejection/moderation message in the member_moderation_notice field, and be able to maintain that via the web as opposed to a template file. However, there is no corresponding way to create a nice notice for people who are trying to post to the list but are not members. It is not uncommon to want to set the list so that no members are moderated by default (so that the member_moderation_notice does not apply), but to set the generic_nonmember_action to be Reject or Hold. Unfortunately, default standard text is hard-coded into Mailman/Handlers/Moderate.py for these instances. I'd be fine with a template file that I could modify, along the lines of postheld.txt -- at least that would allow me to put in URLs properly formatted with less-than and greater-than signs which don't get HTML-escaped when the text is saved. ;( Alternatively, a separate field should probably be created, probably something like generic_nonmember_notice, or somesuch. That way you could have two different notices for the two different cases, as appropriate. However, I don't grok Python, and I'm not a real programmer. So, I have hacked together a little patch that allows me to re-use the member_moderation_notice as a result of the setting of generic_nonmember_action. I hope you find this useful. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1107169&group_id=103 From noreply at sourceforge.net Sun Jan 23 05:01:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 23 05:01:06 2005 Subject: [ mailman-Patches-1107631 ] changeMemberAddress does not preserve nomail or topics Message-ID: Patches item #1107631, was opened at 2005-01-23 13:01 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=1107631&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jim Tittsler (jtittsler) Assigned to: Nobody/Anonymous (nobody) Summary: changeMemberAddress does not preserve nomail or topics Initial Comment: OldStyleMemberships's changeMemberAddress() is preserving neither the nomail status/time nor the topic subscriptions. (First noticed when using bin/clone_member.) Here is one way to fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1107631&group_id=103 From noreply at sourceforge.net Sun Jan 23 22:56:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 23 22:56:27 2005 Subject: [ mailman-Bugs-1107972 ] privacy bug in Mailman 2.1.4 Message-ID: Bugs item #1107972, was opened at 2005-01-23 17:56 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=1107972&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Leonardo Gregianin (leogregianin) Assigned to: Nobody/Anonymous (nobody) Summary: privacy bug in Mailman 2.1.4 Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 203, in main change_options(mlist, category, subcat, cgidata, doc, mlist_language) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1384, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 154, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 347, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_id=103 From noreply at sourceforge.net Mon Jan 24 01:24:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 24 01:24:16 2005 Subject: [ mailman-Feature Requests-849711 ] Challenge/Response for held postings Message-ID: Feature Requests item #849711, was opened at 2003-11-26 10:33 Message generated for change (Comment added) made by shi_bmz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=849711&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin Schr?der (oneiros) Assigned to: Nobody/Anonymous (nobody) Summary: Challenge/Response for held postings Initial Comment: With moderated or member-only lists the lists get a multitude of spam which the admin has to discard manually (Listserv does this automagically). Mailman could discard most of the spam automatically if it would implement a challenge/response for all messages hold for moderator approval: Mail the sender (usually forged) and ask them to confirm the message (by mail or www). If the message isn't confirmed after 24h, drop it silently and don't bother the admin. ---------------------------------------------------------------------- Comment By: Shi Sherebrin (shi_bmz) Date: 2005-01-23 19:24 Message: Logged In: YES user_id=630999 hear, hear! I just spent many hours trying to kludge a TMDA-based solution together, only to find that my host won't allow the required changes to Exim for this to work. Please let me know if there's anything development-wise I could do to help this along. Or is there another approach pending elsewhere that would accomplish this in a different way? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=849711&group_id=103 From noreply at sourceforge.net Mon Jan 24 12:35:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 24 12:35:34 2005 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 09:54 Message generated for change (Comment added) made by shevek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-01-24 12:35 Message: Logged In: YES user_id=42389 I checked the source, and this appears to be a bug in Python. It can read and write e-mails, including headers, and they are interpreted. However, it doesn't preserve their whitespace, which is of course fatal for pgp signatures. The bug is filed for python here: http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=5470&atid=105470 ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-18 18:30 Message: Logged In: YES user_id=15365 I am attaching a screen shot of the content filtering settings (see the options.png attachment I have added to this bug report). In short, content filtering is disabled, so I don't think it is the cause of the problem. :-/ Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-17 01:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-08 02:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-30 05:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Tue Jan 25 04:04:47 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 25 04:04:49 2005 Subject: [ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail Message-ID: Bugs item #1108814, was opened at 2005-01-24 22:04 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=1108814&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug.

OK, this is the hotmail test.
_Glen

>
>
>OK, the next message from me will come from hotmail, as a test.
>-Glen
> > >
> > Well, the thing to do is, now that we've got a clue, go back to the
> > original email agent and make a couple of test posts, & we'll see
>who
> > gets what now that we know to look for it.
>
> > >>
> > >> > -- John.
> > >
> > >Brought to you by the 6809, the 6803 and their cousins!
> > >Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > Cheers, Gene
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > 99.32% setiathome rank, not too shabby for a WV hillbilly
> > Yahoo.com attorneys please note, additions to this message
> > by Gene Heskett are:
> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
>
>
>
>
>
>Brought to you by the 6809, the 6803 and their cousins!
>Yahoo! Groups Links
>
><*> To visit your group on the web, go to:
>     http://groups.yahoo.com/group/ColorComputer/
>
><*> To unsubscribe from this group, send an email to:
>     ColorComputer-unsubscribe@yahoogroups.com
>
><*> Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
>
>
>
>
---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 From noreply at sourceforge.net Tue Jan 25 16:09:45 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 25 16:09:48 2005 Subject: [ mailman-Feature Requests-1109135 ] more informative rejection message Message-ID: Feature Requests item #1109135, was opened at 2005-01-25 10:09 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=1109135&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: more informative rejection message Initial Comment: Mailman/Handlers/Hold.py: class SuspiciousHeaders: it would be nice if the rejection message contained the name of the Suspicious Header. (it is much easier for the moderator to remove that if she wants to than to match the actual headers to the "privacy rules"). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_id=103 From noreply at sourceforge.net Tue Jan 25 16:12:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 25 16:12:37 2005 Subject: [ mailman-Feature Requests-1109139 ] a common custom explanation for all rejection messages Message-ID: Feature Requests item #1109139, was opened at 2005-01-25 10:12 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=1109139&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: a common custom explanation for all rejection messages Initial Comment: it would be very nice if there were a customization parameter where I could put some common text for all rejections messages. right now, I have to manually insert "For more information on the mailing list policy, please see ." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_id=103 From noreply at sourceforge.net Tue Jan 25 20:44:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 25 20:44:12 2005 Subject: [ mailman-Bugs-1109325 ] Bug with upgrading to Mailman 2.1.4 in SuSE 9.1 Message-ID: Bugs item #1109325, was opened at 2005-01-25 13:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_id=103 Category: Web/CGI Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tim Smith (jallen13) Assigned to: Nobody/Anonymous (nobody) Summary: Bug with upgrading to Mailman 2.1.4 in SuSE 9.1 Initial Comment: [NOTE: This is a "I did it!" story.. the fix is at the bottom of this post :) ) Just wanted to make a report here about some problems I had upgrading Mailman from 2.1.3 to 2.1.4 using Yast Online Update (YOU) in Suse 9.1 AMD64. It broke my web-based GUI, and spit this error into my apache error logs: [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [----- Mailman Version: 2.1.4 -----] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR [----- Traceback ------] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] Traceback (most recent call last): [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 241, in ? [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] run_main() [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 69, in run_main [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] import xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] ImportError: No module named xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [Mailman: low level unrecoverable exception] And the output of the Web browser going to the mailman location gives this error: 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. --------------------------------------------------------------------- So, I googled around, and found that this error is very common in 2.1.4 version. Just google for "Mailman Low level failure" and you'll get a lot of web pages like the one I just pasted, all for 2.1.4. I got some help from Don Burns from mailman-users list, he told me all I need to do is install python-xml. (Thanks Don!!) So, I used the trusty YAST and searched for python-xml and installed it. Wham-Bam, it works. I guess 2.1.4 version expects python-xml as a depends, whereas the earlier versions didn't care about that. I wanted to document this so maybe it''ll come up quicker for some poor sucker like myself googling around for this answer :) Cheers, Tim Smith ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_id=103 From noreply at sourceforge.net Fri Jan 28 10:47:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 10:47:38 2005 Subject: [ mailman-Bugs-1111321 ] cron failures are sent to mailman list Message-ID: Bugs item #1111321, was opened at 2005-01-28 10:47 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=1111321&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Wim Heirman (wheirman) Assigned to: Nobody/Anonymous (nobody) Summary: cron failures are sent to mailman list Initial Comment: When a cronjob fails (e.g. nightly_gzip has a permission problem), the output is sent to mailman@localhost. However, mailman is by default a mailing list (at least it was on my older Debian system, I copied the /var/mailman/lists from there to a new Fedora Core 3 installation). Since root is not on the mailman list, I get "message awaits moderator approval" messages. Shouldn't the error go straight to root? For instance, with a MAILTO=root directive in /etc/cron.d/mailman ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_id=103 From noreply at sourceforge.net Fri Jan 28 11:25:12 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 11:25:36 2005 Subject: [ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail Message-ID: Bugs item #1108814, was opened at 2005-01-25 03:04 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug.

OK, this is the hotmail test.
_Glen

>
>
>OK, the next message from me will come from hotmail, as a test.
>-Glen
> > >
> > Well, the thing to do is, now that we've got a clue, go back to the
> > original email agent and make a couple of test posts, & we'll see
>who
> > gets what now that we know to look for it.
>
> > >>
> > >> > -- John.
> > >
> > >Brought to you by the 6809, the 6803 and their cousins!
> > >Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > Cheers, Gene
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > 99.32% setiathome rank, not too shabby for a WV hillbilly
> > Yahoo.com attorneys please note, additions to this message
> > by Gene Heskett are:
> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
>
>
>
>
>
>Brought to you by the 6809, the 6803 and their cousins!
>Yahoo! Groups Links
>
><*> To visit your group on the web, go to:
>     http://groups.yahoo.com/group/ColorComputer/
>
><*> To unsubscribe from this group, send an email to:
>     ColorComputer-unsubscribe@yahoogroups.com
>
><*> Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
>
>
>
>
---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like ? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 From noreply at sourceforge.net Fri Jan 28 11:28:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 11:28:37 2005 Subject: [ mailman-Bugs-1111321 ] cron failures are sent to mailman list Message-ID: Bugs item #1111321, was opened at 2005-01-28 09:47 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Wim Heirman (wheirman) Assigned to: Nobody/Anonymous (nobody) Summary: cron failures are sent to mailman list Initial Comment: When a cronjob fails (e.g. nightly_gzip has a permission problem), the output is sent to mailman@localhost. However, mailman is by default a mailing list (at least it was on my older Debian system, I copied the /var/mailman/lists from there to a new Fedora Core 3 installation). Since root is not on the mailman list, I get "message awaits moderator approval" messages. Shouldn't the error go straight to root? For instance, with a MAILTO=root directive in /etc/cron.d/mailman ? ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:28 Message: Logged In: YES user_id=18417 This sounds like an OS/distribution-specific issue. I get no such problems with Mailman on FreeBSD (for ntp.isc.org), nor with Mailman on Debian (for python.org). Feel free to try out your suggested change, and if it works, then recommend that to the people at Redhat for inclusion in future versions of their RPM. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_id=103 From noreply at sourceforge.net Fri Jan 28 11:30:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 11:30:50 2005 Subject: [ mailman-Feature Requests-1109135 ] more informative rejection message Message-ID: Feature Requests item #1109135, was opened at 2005-01-25 15:09 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: more informative rejection message Initial Comment: Mailman/Handlers/Hold.py: class SuspiciousHeaders: it would be nice if the rejection message contained the name of the Suspicious Header. (it is much easier for the moderator to remove that if she wants to than to match the actual headers to the "privacy rules"). ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:30 Message: Logged In: YES user_id=18417 IIRC, you can't name the suspicious header, otherwise you'll get caught by the same rule. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109135&group_id=103 From noreply at sourceforge.net Fri Jan 28 11:32:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 11:32:51 2005 Subject: [ mailman-Feature Requests-1109139 ] a common custom explanation for all rejection messages Message-ID: Feature Requests item #1109139, was opened at 2005-01-25 15:12 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: a common custom explanation for all rejection messages Initial Comment: it would be very nice if there were a customization parameter where I could put some common text for all rejections messages. right now, I have to manually insert "For more information on the mailing list policy, please see ." ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:32 Message: Logged In: YES user_id=18417 I've got one attempt to address this issue at . However, please note that text entered via the admin web interface will get HTML-escaped when it is saved, so you can't use angle brackets around URLs and expect that to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1109139&group_id=103 From noreply at sourceforge.net Fri Jan 28 14:40:08 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 14:40:18 2005 Subject: [ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail Message-ID: Bugs item #1108814, was opened at 2005-01-24 22:04 Message generated for change (Comment added) made by kalvos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug.

OK, this is the hotmail test.
_Glen

>
>
>OK, the next message from me will come from hotmail, as a test.
>-Glen
> > >
> > Well, the thing to do is, now that we've got a clue, go back to the
> > original email agent and make a couple of test posts, & we'll see
>who
> > gets what now that we know to look for it.
>
> > >>
> > >> > -- John.
> > >
> > >Brought to you by the 6809, the 6803 and their cousins!
> > >Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > Cheers, Gene
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > 99.32% setiathome rank, not too shabby for a WV hillbilly
> > Yahoo.com attorneys please note, additions to this message
> > by Gene Heskett are:
> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
>
>
>
>
>
>Brought to you by the 6809, the 6803 and their cousins!
>Yahoo! Groups Links
>
><*> To visit your group on the web, go to:
>     http://groups.yahoo.com/group/ColorComputer/
>
><*> To unsubscribe from this group, send an email to:
>     ColorComputer-unsubscribe@yahoogroups.com
>
><*> Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
>
>
>
>
---------------------------------------------------------------------- >Comment By: Kalvos (kalvos) Date: 2005-01-28 08:40 Message: Logged In: YES user_id=1204060 Hello, Thanks for the response. In my original post, there was a link the defectively received message, and it is just like the one you found. The other message was as sent through Yahoo and received by Yahoo list members -- the content is pasted above. According to the author, it is what he sent. Pasted above is exactly what would have been received by Mailman. The Yahoo Groups list is a member of our list (with dupes turned off) so both groups can share posts. Dennis ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 05:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like ? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 From noreply at sourceforge.net Fri Jan 28 16:03:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 16:03:13 2005 Subject: [ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail Message-ID: Bugs item #1108814, was opened at 2005-01-25 03:04 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug.

OK, this is the hotmail test.
_Glen

>
>
>OK, the next message from me will come from hotmail, as a test.
>-Glen
> > >
> > Well, the thing to do is, now that we've got a clue, go back to the
> > original email agent and make a couple of test posts, & we'll see
>who
> > gets what now that we know to look for it.
>
> > >>
> > >> > -- John.
> > >
> > >Brought to you by the 6809, the 6803 and their cousins!
> > >Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > Cheers, Gene
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > 99.32% setiathome rank, not too shabby for a WV hillbilly
> > Yahoo.com attorneys please note, additions to this message
> > by Gene Heskett are:
> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
>
>
>
>
>
>Brought to you by the 6809, the 6803 and their cousins!
>Yahoo! Groups Links
>
><*> To visit your group on the web, go to:
>     http://groups.yahoo.com/group/ColorComputer/
>
><*> To unsubscribe from this group, send an email to:
>     ColorComputer-unsubscribe@yahoogroups.com
>
><*> Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
>
>
>
>
---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 15:03 Message: Logged In: YES user_id=18417 Pasting the content of the message body is not useful. There is MIME structure outside of the message body that is not included, and it is this MIME structure information that we need in order to find out what has happened. This is why I said that we needed to be able to look at the *COMPLETE* message contents, both before and after processing by Mailman. You can't just cut-n-paste the message body. ---------------------------------------------------------------------- Comment By: Kalvos (kalvos) Date: 2005-01-28 13:40 Message: Logged In: YES user_id=1204060 Hello, Thanks for the response. In my original post, there was a link the defectively received message, and it is just like the one you found. The other message was as sent through Yahoo and received by Yahoo list members -- the content is pasted above. According to the author, it is what he sent. Pasted above is exactly what would have been received by Mailman. The Yahoo Groups list is a member of our list (with dupes turned off) so both groups can share posts. Dennis ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like ? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 From noreply at sourceforge.net Fri Jan 28 17:07:28 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 28 17:07:31 2005 Subject: [ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail Message-ID: Bugs item #1108814, was opened at 2005-01-24 22:04 Message generated for change (Comment added) made by kalvos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug.

OK, this is the hotmail test.
_Glen

>
>
>OK, the next message from me will come from hotmail, as a test.
>-Glen
> > >
> > Well, the thing to do is, now that we've got a clue, go back to the
> > original email agent and make a couple of test posts, & we'll see
>who
> > gets what now that we know to look for it.
>
> > >>
> > >> > -- John.
> > >
> > >Brought to you by the 6809, the 6803 and their cousins!
> > >Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > Cheers, Gene
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > 99.32% setiathome rank, not too shabby for a WV hillbilly
> > Yahoo.com attorneys please note, additions to this message
> > by Gene Heskett are:
> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
>
>
>
>
>
>Brought to you by the 6809, the 6803 and their cousins!
>Yahoo! Groups Links
>
><*> To visit your group on the web, go to:
>     http://groups.yahoo.com/group/ColorComputer/
>
><*> To unsubscribe from this group, send an email to:
>     ColorComputer-unsubscribe@yahoogroups.com
>
><*> Your use of Yahoo! Groups is subject to:
>     http://docs.yahoo.com/info/terms/
>
>
>
>
---------------------------------------------------------------------- >Comment By: Kalvos (kalvos) Date: 2005-01-28 11:07 Message: Logged In: YES user_id=1204060 Hi, Thanks again. I'm just a list administrator, so I need my hand held. The list members have been warned off HTML posting in the meantime, so these are the only headers I've got. If they don't help, I'll wait until we get another blank email with a Hotmail return address and try to trace it back to the original submission. Here is the header of the original email (as sent to me by another list member) before it goes from Yahoo Groups to the Mailman list: >From glenvdb@h... Mon Jan 24 13:11:23 2005 Return-Path: X-Sender: glenvdb@h... X-Apparently-To: ColorComputer@yahoogroups.com Received: (qmail 63953 invoked from network); 24 Jan 2005 21:11:22 -0000 Received: from unknown (66.218.66.172) by m21.grp.scd.yahoo.com with QMQP; 24 Jan 2005 21:11:22 -0000 Received: from unknown (HELO hotmail.com) (65.54.247.12) by mta4.grp.scd.yahoo.com with SMTP; 24 Jan 2005 21:11:22 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 24 Jan 2005 13:11:01 -0800 Message-ID: Received: from 198.53.120.64 by by2fd.bay2.hotmail.msn.com with HTTP; Mon, 24 Jan 2005 21:10:01 GMT X-Originating-Email: [glenvdb@h...] X-Sender: glenvdb@h... To: ColorComputer@yahoogroups.com Bcc: Date: Mon, 24 Jan 2005 14:10:01 -0700 Mime-Version: 1.0 Content-Type: text/html; format=flowed X-OriginalArrivalTime: 24 Jan 2005 21:11:01.0201 (UTC) FILETIME=[34DA8C10:01C50259] X-eGroups-Remote-IP: 65.54.247.12 From: "Glen VanDenBiggelaar" X-Originating-IP: [198.53.120.64] Subject: RE: [Coco] [Color Computer] Re: Blank Emails X-Yahoo-Group-Post: member; u=22654116 X-Yahoo-Profile: glenvdb Complete "blank" (HTML stripped) email with all headers shown by Eudora full-header mode, from the same poster as it comes out of Mailman to the list members: Return-Path: Delivered-To: bathory-maltedmedia:com-dennis@maltedmedia.com X-Envelope-To: dennis@maltedmedia.com Received: (qmail 3612 invoked by uid 3002); 24 Jan 2005 00:26:11 -0000 Delivered-To: bathory-maltedmedia:com-bathory@maltedmedia.com Received: (qmail 3605 invoked from network); 24 Jan 2005 00:26:10 -0000 Received: from five.pairlist.net (216.92.1.121) by qs281.pair.com with SMTP; 24 Jan 2005 00:26:10 -0000 Received: from five.pairlist.net (localhost [127.0.0.1]) by five.pairlist.net (Postfix) with ESMTP id 6E36A1A7CF; Sun, 23 Jan 2005 19:26:05 -0500 (EST) X-Original-To: coco@lists5.maltedmedia.com Delivered-To: coco@five.pairlist.net Received: from qs281.pair.com (qs281.pair.com [216.92.131.37]) by five.pairlist.net (Postfix) with SMTP id 5E2BE1A7BB for ; Sun, 23 Jan 2005 19:26:04 -0500 (EST) Received: (qmail 3596 invoked by uid 3002); 24 Jan 2005 00:26:04 -0000 Delivered-To: bathory-maltedmedia:com-coco@maltedmedia.com Received: (qmail 3593 invoked from network); 24 Jan 2005 00:26:04 -0000 Received: from n8a.bulk.scd.yahoo.com (66.94.237.42) by qs281.pair.com with SMTP; 24 Jan 2005 00:26:04 -0000 Received: from [66.218.69.5] by n8.bulk.scd.yahoo.com with NNFMP; 24 Jan 2005 00:26:03 -0000 Received: from [66.218.66.27] by mailer5.bulk.scd.yahoo.com with NNFMP; 24 Jan 2005 00:26:03 -0000 X-Yahoo-Newman-Property: groups-email X-Sender: glenvdb@hotmail.com X-Apparently-To: ColorComputer@yahoogroups.com Received: (qmail 13033 invoked from network); 24 Jan 2005 00:26:02 -0000 Received: from unknown (66.218.66.172) by m21.grp.scd.yahoo.com with QMQP; 24 Jan 2005 00:26:02 -0000 Received: from unknown (HELO hotmail.com) (65.54.247.42) by mta4.grp.scd.yahoo.com with SMTP; 24 Jan 2005 00:26:02 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 23 Jan 2005 16:26:01 -0800 Message-ID: Received: from 198.53.120.64 by by2fd.bay2.hotmail.msn.com with HTTP; Mon, 24 Jan 2005 00:25:58 GMT X-Originating-Email: [glenvdb@hotmail.com] X-Sender: glenvdb@hotmail.com In-Reply-To: To: ColorComputer@yahoogroups.com X-OriginalArrivalTime: 24 Jan 2005 00:26:01.0788 (UTC) FILETIME=[4888AFC0:01C501AB] X-eGroups-Remote-IP: 65.54.247.42 From: "Glen VanDenBiggelaar" X-Originating-IP: [198.53.120.64] X-Yahoo-Profile: glenvdb Mailing-List: list ColorComputer@yahoogroups.com; contact ColorComputer-owner@yahoogroups.com Delivered-To: mailing list ColorComputer@yahoogroups.com Precedence: bulk Date: Sun, 23 Jan 2005 17:25:58 -0700 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: [Coco] RE: [Color Computer] Re: Floppy drives on E-bay X-BeenThere: coco@maltedmedia.com X-Mailman-Version: 2.1.5 Reply-To: ColorComputer@yahoogroups.com, CoCoList for Color Computer Enthusiasts List-Id: CoCoList for Color Computer Enthusiasts List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: coco-bounces@maltedmedia.com Errors-To: coco-bounces@maltedmedia.com X-Spam-Filtered: 2339d97e2cf80afbc3f9b452dd9fb067 X-Spam-Status: No, hits=-4.2 required=4.0 tests=MSGID_FROM_MTA_HEADER,BAYES_00 X-Spam-Flag: NO X-Spam-Level: -- Coco mailing list Coco@maltedmedia.com http://five.pairlist.net/mailman/listinfo/coco ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:03 Message: Logged In: YES user_id=18417 Pasting the content of the message body is not useful. There is MIME structure outside of the message body that is not included, and it is this MIME structure information that we need in order to find out what has happened. This is why I said that we needed to be able to look at the *COMPLETE* message contents, both before and after processing by Mailman. You can't just cut-n-paste the message body. ---------------------------------------------------------------------- Comment By: Kalvos (kalvos) Date: 2005-01-28 08:40 Message: Logged In: YES user_id=1204060 Hello, Thanks for the response. In my original post, there was a link the defectively received message, and it is just like the one you found. The other message was as sent through Yahoo and received by Yahoo list members -- the content is pasted above. According to the author, it is what he sent. Pasted above is exactly what would have been received by Mailman. The Yahoo Groups list is a member of our list (with dupes turned off) so both groups can share posts. Dennis ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 05:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like ? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_id=103 From noreply at sourceforge.net Sat Jan 29 05:17:57 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 29 05:17:59 2005 Subject: [ mailman-Patches-1111899 ] SMTPDirect.py can hang indefinitely Message-ID: Patches item #1111899, was opened at 2005-01-28 20:17 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=1111899&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: thienvu (thienvu) Assigned to: Nobody/Anonymous (nobody) Summary: SMTPDirect.py can hang indefinitely Initial Comment: SMTPDirect.py connects to an SMTPHOST that may terminate its TCP connection incorrectly. This will result in the OutgoingRunners hanging, especially if the SMTPHOST still accepts connections. This is a patch that wraps the SMTP transcaction in an alarm() to prevent OutgoingRunners from hanging indefinitely. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1111899&group_id=103 From noreply at sourceforge.net Sat Jan 29 18:08:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 29 18:08:15 2005 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 03:54 Message generated for change (Comment added) made by egagnon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- >Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-29 12:08 Message: Logged In: YES user_id=15365 Dear Bas, Thanks a lot for identifying the source of this bug and flagging an upstream bug on Python. Etienne ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-01-24 06:35 Message: Logged In: YES user_id=42389 I checked the source, and this appears to be a bug in Python. It can read and write e-mails, including headers, and they are interpreted. However, it doesn't preserve their whitespace, which is of course fatal for pgp signatures. The bug is filed for python here: http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=5470&atid=105470 ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-18 12:30 Message: Logged In: YES user_id=15365 I am attaching a screen shot of the content filtering settings (see the options.png attachment I have added to this bug report). In short, content filtering is disabled, so I don't think it is the cause of the problem. :-/ Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-16 19:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-07 20:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-29 23:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Sat Jan 29 23:57:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 29 23:58:01 2005 Subject: [ mailman-Bugs-1109325 ] Bug with upgrading to Mailman 2.1.4 in SuSE 9.1 Message-ID: Bugs item #1109325, was opened at 2005-01-25 14:44 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_id=103 Category: Web/CGI Group: 2.0.x >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Tim Smith (jallen13) Assigned to: Nobody/Anonymous (nobody) Summary: Bug with upgrading to Mailman 2.1.4 in SuSE 9.1 Initial Comment: [NOTE: This is a "I did it!" story.. the fix is at the bottom of this post :) ) Just wanted to make a report here about some problems I had upgrading Mailman from 2.1.3 to 2.1.4 using Yast Online Update (YOU) in Suse 9.1 AMD64. It broke my web-based GUI, and spit this error into my apache error logs: [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [----- Mailman Version: 2.1.4 -----] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR [----- Traceback ------] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] Traceback (most recent call last): [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 241, in ? [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] run_main() [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 69, in run_main [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] import xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] ImportError: No module named xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [Mailman: low level unrecoverable exception] And the output of the Web browser going to the mailman location gives this error: 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. --------------------------------------------------------------------- So, I googled around, and found that this error is very common in 2.1.4 version. Just google for "Mailman Low level failure" and you'll get a lot of web pages like the one I just pasted, all for 2.1.4. I got some help from Don Burns from mailman-users list, he told me all I need to do is install python-xml. (Thanks Don!!) So, I used the trusty YAST and searched for python-xml and installed it. Wham-Bam, it works. I guess 2.1.4 version expects python-xml as a depends, whereas the earlier versions didn't care about that. I wanted to document this so maybe it''ll come up quicker for some poor sucker like myself googling around for this answer :) Cheers, Tim Smith ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-29 17:57 Message: Logged In: YES user_id=12800 This is really a problem with your Python installation since nothing in Mailman directly imports xml.sax.saxutils. But you knew that because your fix installed whatever bits of Python Suse didn't deem important enough to include by default . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_id=103 From noreply at sourceforge.net Sun Jan 30 01:32:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 30 01:32:44 2005 Subject: [ mailman-Bugs-1107972 ] privacy bug in Mailman 2.1.4 Message-ID: Bugs item #1107972, was opened at 2005-01-23 13:56 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Leonardo Gregianin (leogregianin) Assigned to: Nobody/Anonymous (nobody) Summary: privacy bug in Mailman 2.1.4 Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 203, in main change_options(mlist, category, subcat, cgidata, doc, mlist_language) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1384, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 154, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 347, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-01-29 16:32 Message: Logged In: YES user_id=1123998 This is bug# 1099840 which is fixed in 2.1.6. See https://sourceforge.net/tracker/?func=detail&aid=1099840&group_id=103&atid=100103 for a more complete description of the cause. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_id=103 From noreply at sourceforge.net Sun Jan 30 02:57:23 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 30 02:57:26 2005 Subject: [ mailman-Bugs-1112349 ] Upper-case chars in acceptable_aliases pattern fail to match Message-ID: Bugs item #1112349, was opened at 2005-01-29 17:57 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=1112349&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Upper-case chars in acceptable_aliases pattern fail to match Initial Comment: The HasExplicitDest() method in MailList.py first lower-cases all the To: and Cc: addresses. Then if the list address doesn't match any of these explicit addresses and there are acceptable_aliases, it goes on to attempt to match the lower-cased explicit addresses against the acceptable_aliases patterns using re.match() without an IGNORECASE flag. Thus, for example if acceptable_aliases is MyAddress@example.com and the message is To: MyAddress@example.com, the match will fail because the To: will be lower-cased and the match will be effectively re.match('MyAddress@example.com', 'myaddress@example.com') Clearly, this behavior is wrong, but it is not clear to me what the correct behavior is. We could just add an IGNORECASE flag to the re.match() in the domatch() helper. This would be consistent with matching against the lower-case list name, but according to RFC 2822, the local part of the address is locally interpreted so MyAddress@example.com may in fact not be the same as myaddress@example.com. Thus, it may be that the correct behavior is to build the recips[] list with case-preserved addresses so that the case-sensitive match works. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1112349&group_id=103 From noreply at sourceforge.net Sun Jan 30 19:34:56 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 30 19:34:59 2005 Subject: [ mailman-Bugs-1112349 ] Upper-case chars in acceptable_aliases pattern fail to match Message-ID: Bugs item #1112349, was opened at 2005-01-29 20:57 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1112349&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Upper-case chars in acceptable_aliases pattern fail to match Initial Comment: The HasExplicitDest() method in MailList.py first lower-cases all the To: and Cc: addresses. Then if the list address doesn't match any of these explicit addresses and there are acceptable_aliases, it goes on to attempt to match the lower-cased explicit addresses against the acceptable_aliases patterns using re.match() without an IGNORECASE flag. Thus, for example if acceptable_aliases is MyAddress@example.com and the message is To: MyAddress@example.com, the match will fail because the To: will be lower-cased and the match will be effectively re.match('MyAddress@example.com', 'myaddress@example.com') Clearly, this behavior is wrong, but it is not clear to me what the correct behavior is. We could just add an IGNORECASE flag to the re.match() in the domatch() helper. This would be consistent with matching against the lower-case list name, but according to RFC 2822, the local part of the address is locally interpreted so MyAddress@example.com may in fact not be the same as myaddress@example.com. Thus, it may be that the correct behavior is to build the recips[] list with case-preserved addresses so that the case-sensitive match works. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-30 13:34 Message: Logged In: YES user_id=12800 In general, Mailman's philosophy for member addresses is case-preserving, case-folding, meaning that FOO@example.com and foo@example.com are considered the same member, but if they were subscribed with the former, we will send the message to the former. I think it's valid to extend this philosophy to acceptable_aliases, and so I think the right thing to do is to treat an alias such as FOO@example.com the same as foo@example.com. I will commit a change that adds the IGNORECASE flag. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1112349&group_id=103 From noreply at sourceforge.net Sun Jan 30 19:37:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 30 19:37:29 2005 Subject: [ mailman-Bugs-1107972 ] privacy bug in Mailman 2.1.4 Message-ID: Bugs item #1107972, was opened at 2005-01-23 16:56 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_id=103 Category: None Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Leonardo Gregianin (leogregianin) Assigned to: Nobody/Anonymous (nobody) Summary: privacy bug in Mailman 2.1.4 Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 203, in main change_options(mlist, category, subcat, cgidata, doc, mlist_language) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1384, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 154, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 347, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-01-29 19:32 Message: Logged In: YES user_id=1123998 This is bug# 1099840 which is fixed in 2.1.6. See https://sourceforge.net/tracker/?func=detail&aid=1099840&group_id=103&atid=100103 for a more complete description of the cause. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_id=103 From noreply at sourceforge.net Mon Jan 31 18:43:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 31 18:43:25 2005 Subject: [ mailman-Bugs-1113318 ] translation of 1st-4th quarter in archive Message-ID: Bugs item #1113318, was opened at 2005-01-31 18:43 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=1113318&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: translation of 1st-4th quarter in archive Initial Comment: Mailman/Archiver/HyperArch.py contains this code: if each == 'quarter': d =["", _("First"), _("Second"), _("Third"), _("Fourth") ] ord = d[int(match.group('quarter'))] return _("%(ord)s quarter %(year)i") "First" to "Fourth" are very generic, therefore the german translation (and probably others, too) look very ugly: Erste(s) Quartal Zweite(r) Quartal Erste(s) Quartal Vierte(s) Quartal It should be: Erstes Quartal Zweites Quartal Drittes Quartal Viertes Quartal I suggest changing the strings to include "quarter": if each == 'quarter': d = ["", _("First quarter"), _("Second quarter"), _("Third quarter"), _("Fourth quarter")] ord = d[int(match.group('quarter'))] return _("%(ord)s %(year)i") Looking at the .po file there are other uses of 1st to 4th, where a similar change would be important for translators. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1113318&group_id=103