Created attachment 65035 [details] Double-decoding of subject string in message list. The string as shown in the message window is actually correct, as the subject was encoded twice by accident. Version: 4.7 (using KDE 4.7.2) OS: Linux The subject line display in the message list apparently gets unescaped / decoded too often. I don't know if this could have negative effects if the first decoding pass yields strings with special characters. This seems to happen always. Reproducible: Always Steps to Reproduce: I have some mails with a messed-up subject line that somehow got encoded twice in quoted-printable encoding: Subject: =?UTF-8?Q?=3D=3Fiso-8859-15=3FQ=3FTODO!=5F=28update=29=5FWRT-Verfugebar?= =?UTF-8?Q?keitsberechnung=5Fbeginnt=5Fzu=5Ffr=3DFCh=3F=3D?= Actual Results: This string is (correctly) displayed as "=?iso-8859-15?Q?TODO!_(update)_WRT-Verfugebarkeitsberechnung_beginnt_zu_fr=FCh?=" in the message header as shown in the message window. The outermost encoding has been decoded, showing the embedded string which also is encoded. The message list, however, shows a completely decoded string only containing the original clear text, as if the subject had been encoded only once. (See screenshot.) Expected Results: The message list should show the subject the same way as the message window does.
could you send me in private your message please ? (if possible)
Sent to you by mail.
still valid in last kdepim ?
Still valid in: KMail, Version 4.8.2, Unter KDE 4.8.2 (4.8.2) I just received a new mail which shows this behaviour: Actual subject header: Subject: =?UTF-8?Q?=3D=3Futf-8=3FB=3FR2VzY2jDpGZ0c21vZGVsbGUgaW4gZGVyIFNvZnR3YXJ?= =?UTF-8?Q?laW5kdXN0cmllOiBFaW5lIFVtZnJhZ2UgZGVyIFRVIERhcm1zdGFkdA=3D=3D?= =?UTF-8?Q?=3F=3D?= In the message window, this is correctly displayed as: =?utf-8?B?R2VzY2jDpGZ0c21vZGVsbGUgaW4gZGVyIFNvZnR3YXJlaW5kdXN0cmllOiBFaW5lIFVtZnJhZ2UgZGVyIFRVIERhcm1zdGFkdA==?= In the message list, it's fully decoded and readable, which I consider to be wrong.
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.
Apparently fixed in kMail 5.3.x.