Version: Git (master) OS: Linux Very often I receive mail from some services that don't contain encoding description in subject. And non-ascii symbols are displayed like "???" in message list. Here is example: http://wstaw.org/m/2011/06/20/plasma-desktopcH2810.jpg The Subject field in mail headers looks like this: Subject: Âàø ñàéò íå ãîòîâ / Your site is under construction In kmail 1.x I was successfully see those subjects when set fallback encoding to cp1251, but in kmail 2.1 this option don't change the headers, but acts normally on message body. So in kmail 1.x I see this subject normally: Ваш сайт не готов / Your site is under construction But in kmail 2.x - like this: ��� ���� �� ����� / Your site is under construction So, this is regression with decode mail headers from kmail 1.x to 2.x. I can give you some more examples if you needs it and can test this bug in git versions. Maybe message subject decoding process in 2.x don't look to fallback encoding and always use UTF-8 or Latin-1. Can you tell me some way how to fix this problem? Reproducible: Always
When subject contains encoding, it displayed normally: Subject: =?windows-1251?B?ze7i7vHy6CDx4Ony4CBDYXRhbG94eS5ydQ==?= in kmail 1: Новости сайта Cataloxy.ru in kmail 2: Новости сайта Cataloxy.ru
I confirm this problem with Kmail 4.7.2 on Kubuntu 11.10. I think Kmail should assume the encoding from "Content-Type:" in the case when "Subject:" of "From:" is a raw 8-bit text without encoding information.
Outlook, Windows Live, Thunderbird, TheBat and many other mail clients displays headers like described normally (they gets encoding from Content-Type if in Subject it isn't described. So the problem is only in KMail2.
Confirm this issue. KDE 4.7.2, Ubuntu 11.10. Problem only with "Subject", everything else detect encoding right.
can one of you save one of these wrongly displayed mail in mbox format and attach it to this report please
Created attachment 65815 [details] test message An old message that demonstrates the wrong behavior of Kmail2.
*** Bug 259051 has been marked as a duplicate of this bug. ***
Created attachment 65885 [details] msg1.mbox
Created attachment 65886 [details] msg2.mbox
Created attachment 65887 [details] msg3.mbox
I have attached 3 more examples.
Question: I see two different string in messagelist and subject in viewer. Ok it's not good. But for you subject in viewer is correct ? I tested msg3.mbox. Could you add screenshot please ? (for msg3) Thanks.
For msg3 correct subject must be: Resume-Bank.Ru: Баланс Вашего лицевого счета I use KDE 4.8 Release, it looks for me like this: http://wstaw.org/m/2012/01/26/plasma-desktoprD2300.png
What is your default encoding ? for me it's not "?" but other letters. But it's right it's not good because in message list and subject it's not the same
I have use English interface with Russian locale. Here is screenshots of my settings: http://wstaw.org/m/2012/01/26/plasma-desktopYv2300.png http://wstaw.org/m/2012/01/26/plasma-desktopla2300.png http://wstaw.org/m/2012/01/26/plasma-desktopPu2300.png http://wstaw.org/m/2012/01/26/plasma-desktoplq2300.png http://wstaw.org/m/2012/01/26/plasma-desktoplq2300.png I can try to change some settings for checking, tell me what to try. But, I think, better is to use encoding for mail subject as used for message body (if in subject encoding is miss), instead of try to autodetecting it.
KDE 4.9.3, Ubuntu 12.10 - problem still exists. For example: http://i7.minus.com/iViCWcY2gSyVI.png Subject and body have similar text, but subject is garbled. There is correct encoding in the headers.
I have tested it in KDE 4.10 RC3 and this but is still here. Can I help or provide more info for testing and resolving this bug?
On KDE 4.12 this bug is still active and annoying: http://wstaw.org/m/2014/03/12/plasma-desktopdk2247.png Please create some workaround for setup custom encoding for mail headers!
Kde 4.13 bug still present and very annoying
KDE 4.13.3 - problem still exists!
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.