Bug 337179

Summary: Kmail loses attachment filename encoding
Product: [Applications] kmail2 Reporter: Kryol <kryol>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: kryol
Priority: NOR    
Version: 4.13.2   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Kryol 2014-07-07 12:03:06 UTC
During .docx document sending to Outlook client Kmail loses atachment filename encoding.
This information was correct at the sent-mail folder but bad on receiver side, e.g.
sent-mail:
--nextPart2170179.eotn1eU03S
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"


--nextPart2170179.eotn1eU03S
Content-Disposition: attachment; filename="=?UTF-8?B?0KLQtdGB0YLQvtCy0YvQuSDQtNC+0LrRg9C80LXQvdGCLmRvY3g=?="
Content-Transfer-Encoding: base64
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="=?UTF-8?B?0KLQtdGB0YLQvtCy0YvQuSDQtNC+0LrRg9C80LXQvdGCLmRvY3g=?="

on receiver side:
--nextPart2170179.eotn1eU03S
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"


--nextPart2170179.eotn1eU03S
Content-Disposition: attachment; filename*=''%D0%A2%D0%B5%D1%81%D1%82%D0%BE%D0%B2%D1%8B%D0%B9%20%D0%B4%D0%BE%D0%BA%D1%83%D0%BC%D0%B5%D0%BD%D1%82%2Edocx
Content-Transfer-Encoding: base64
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name*=''%D0%A2%D0%B5%D1%81%D1%82%D0%BE%D0%B2%D1%8B%D0%B9%20%D0%B4%D0%BE%D0%BA%D1%83%D0%BC%D0%B5%D0%BD%D1%82%2Edocx

and outlook could not recognize attachment filename.

Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 18:23:02 UTC
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.
Comment 2 Denis Kurz 2017-01-07 22:33:13 UTC
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.