Bug 118179 - Wrong 8-bit subject show with correct Content-Type
Summary: Wrong 8-bit subject show with correct Content-Type
Status: RESOLVED DUPLICATE of bug 95157
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-12 14:07 UTC by Andrey Cherepanov
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Cherepanov 2005-12-12 14:07:53 UTC 
Version:           1.9 (using KDE 3.5.0, compiled sources)
Compiler:          gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
OS:                Linux (i686) release 2.6.9-1.667smp

I get email with headers:
...
Content-Type: text/plain;
  charset=KOI8-R;
  format=flowed
Content-Transfer-Encoding: 8bit
...
Subject: [Qt] "горячие клавиши"
...

KDE with locale ru_RU.UTF-8. KMail show text correct but cyrillic in subject line is shown as squares. Does KMail handle charset in Content-Type: correct?
Comment 1 Thiago Macieira 2005-12-14 22:43:30 UTC 
Subject: lines MUST be 7-bit ASCII. Anything else is a bug, so please be sure to report this bug to the mailer that sent that message.

*** This bug has been marked as a duplicate of 95157 ***
Comment 2 Andrey Cherepanov 2005-12-15 07:40:21 UTC 
According RFC 822:
"3.1.2.  STRUCTURE OF HEADER FIELDS":
"The field-body may be composed of any ASCII characters, except CR or LF."

In what RFC is it defined 7-bit ASCII ?
Comment 3 Maksim Orlovich 2005-12-15 07:43:13 UTC 
ASCII is by definition 7-bit
Comment 4 Thiago Macieira 2005-12-15 11:23:32 UTC 
There is an open report about having KMail decode the 8-bit headers with the body's encoding. That's bug 95157, which I marked this report a duplicate of.

Even so, it doesn't make the 8-bit headers any less buggy. Please report to the sender that his mailer is broken and should be fixed, as per RFC 2045, 2046, 2047, 2048, 2049 and 2822.