base64 messages not decoded in archives

[Arnar]

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.

[http://sourceforge.net/tracker/index.php?func=detail&aid=1100786&group_id=103&atid=100103]

[Tokio Kikuchi (tkikuchi)]

I believe this has been fixed. Can you show us an example
message which is not decoded (scrubbed) in the archive?

[Arnar (arnar)]

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).

[Tokio Kikuchi (tkikuchi)]

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).

[Arnar (arnar)]

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)

[Tokio Kikuchi (tkikuchi)]

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)

[Arnar (arnar)]

That was it, I set DEFAULT_CHARSET to 'utf-8' and the
message is properly decoded. Maybe I should have RTFM. :o)

Thanks.