I have a contact who uses UTF-7 encoding in Evolution to stop Exchange from base64'ing his emails as vger.linux.org apparently breaks the base64 encoded emails by adding lines in plain text. Thunderbird displays his messages correctly but Kmail shows his > quote character as the encoded form of +AD4- instead (and the same for any other quoted-printable parts). His messages are labelled as: Content-Type: text/plain; charset="utf-7" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 and are otherwise unremarkable. Reproducible: Always Steps to Reproduce: 1. Get an email from someone in utf-7 (directly, or via a mailing list). Actual Results: Looks odd, doesn't display correctly. Expected Results: It should be decoded from UTF-7 quoted-printable.
Could you attach an example (as mbox) please ?
Created attachment 84461 [details] Sample UTF-7 encoded email As requested, an email from the btrfs mailing list encoded in UTF-7 which when viewed in Kmail looks odd.
Thanks I will investigate it
I confirm it. Work fine in evolution/thunderbird.
I confirm this or maybe similar bug. Today I have received mail from Gmail (probably, by header), with charset iso-8859-2 and quoted printable encoding. Text is displayed twice and characters with diacritics are encoded. See attachment. Other mails from Gmail are OK. Squirellmail (web client) display message correctly. After response from web client, reply was OK in Kmail. Kmail 4.12.2, OpenSuse 12.3
Created attachment 85118 [details] Message with ISO-8859-2 and quoted printable encoding
UTF-7 handling is still broken in 4.13.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.