Attachments with non latin-1 character encoding are not readable in MS Outlook. I know, it is first problem of Microsoft and his "not-compatible politic", but too many people have Out-shit-look installed in work... Attachments with spaces and diacritics in title are renamed by Outlook like AT00025.dat Attachments with "clean title" are OK. Renaming attachments compatible with Outlook in Kmail settings checked. Reproducible: Always
Could you give me an example ? for example an attachement title in kmail and this attachement title renamed by outlook etc. thanks or screenshot of result etc.
Created attachment 79053 [details] attachment-24965-0.html Hello Laurent, I am sending screenshots of attachments. I haven´t Outlook, but install MS Live Mail produce the same: renaming attachments as ATTxxxxx.dat. Renaming is probably inner MS algorithm. regards Michael ---------- Původní zpráva ---------- Od: Laurent Montel <montel@kde.org> Datum: 18. 4. 2013 Předmět: [kmail2] [Bug 318535] Renaming attachments with "Outlook compatible" doesn´t work "https://bugs.kde.org/show_bug.cgi?id=318535 Laurent Montel <montel@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |montel@kde.org --- Comment #1 from Laurent Montel <montel@kde.org> --- Could you give me an example ? for example an attachement title in kmail and this attachement title renamed by outlook etc. thanks or screenshot of result etc.
Created attachment 79054 [details] attachment-24965-1.dat
Created attachment 79055 [details] snímek9.png
Created attachment 79056 [details] outlook-attachments.jpg
I looked at code, and it seems perfect. Perhaps I need outlook to test it...
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.