Mailman 3 January 2005 - Mailman-coders

[ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address
by SourceForge.net Jan. 13, 2005

Jan. 13, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 13, 2005

Jan. 13, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 13, 2005

Jan. 13, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address
by SourceForge.net Jan. 13, 2005

Jan. 13, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 12, 2005

Jan. 12, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 12, 2005

Jan. 12, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 12, 2005

Jan. 12, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 12, 2005

Jan. 12, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100788 ] ^ and / are allowed charactes in email address
by SourceForge.net Jan. 12, 2005

Jan. 12, 2005

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_… 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_…

1 0

[ mailman-Bugs-1100786 ] base64 messages not decoded in archives
by SourceForge.net Jan. 12, 2005

Jan. 12, 2005

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_… 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_…

1 0