Hide Forgot
Created attachment 566904 [details] A message which causes Evolution to display badly Description of problem: A message sent to the Linux kernel mailing list encoded in UTF-8 and MIME encoded is displayed with garbage at the end of the message. Also Evolution wants to download a font called N'Ko to display the garbage with. The garbage is not actually in the message. Downloading the message source and MIME decoding with a different tool results in a clean message. Version-Release number of selected component (if applicable): Evolution 3.2.3 How reproducible: Every time the message is viewed. Steps to Reproduce: 1. View the attached message source in Evolution. 2. 3. Actual results: The message ends with garbage like this: "Thanks.NrybXǧv^){.n+{zXܨ}Ơz&j:+vzZ++zfh~izw?&)ߢf^jǫym@Aa0hi" Expected results: The message should end with "Thanks." Additional info:
Created attachment 566905 [details] The actual message instead of Evolution'
(In reply to comment #1) > Created attachment 566905 [details] > The actual message instead of Evolution' This comment was meant to say: The actual message instead of Evolution's misguided attempt to decode it before saving. On the plus side the first attachment shows the bad decoding.
Thanks for a bug report. I'm afraid that this is not evolution's fault, but the list's fault. The message clearly states that its body is base64 encoded, but the list robot appends to it its signature unencoded, which is simple no-no. If they really want to have there their footer, then they should either add it as a new part, or respect sender's Content-Transfer-Encoding and Content-Type. I suppose nobody noticed this earlier, because sending text/plain message base64 encoded is rather rare.