Bug 222804

Summary: "No HTML Message" when message contains HTML
Product: [Applications] kmail Reporter: Glenn Burkhardt <gbburkhardt>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: rossi.f
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Kmail does not display the HTML part of this message

Description Glenn Burkhardt 2010-01-15 03:04:05 UTC 
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    openSUSE RPMs

The HTML part of some email is not displayed.  In fact, for the message I've attached, the text portion is not displayed, either.  If the HTML part is extracted, Firefox can process and display the HTML code.  Both Evolution and Thunderbird can display the message after importing the attached file.

This might be a duplicate of or related to Bugs 99683 and 205626.
Comment 1 Glenn Burkhardt 2010-01-15 03:04:50 UTC 
Created attachment 39912 [details]
Kmail does not display the HTML part of this message
Comment 2 Torgny Nyblom 2010-01-15 09:24:06 UTC 
Not 100% sure, but the boundary in this message looks wierd. It looks like this:
Content-type: multipart/alternative;
  boundary*0=----000000000000000000000000000000000000;
  boundary*1=000000000000000000000000000

Shouldn't this be
Content-type: multipart/alternative;
  boundary=----000000000000000000000000000000000000000000000000000000000000000

or
Content-type: multipart/alternative;
  boundary*0=----000000000000000000000000000000000000
  000000000000000000000000000

?
That is the trailing ';' should not be present in line 1 and the header for line two should not be there as well as the boundary header should not contain the '*0' part.

But as I said I'm not 100% sure...
Comment 3 Thomas McGuire 2010-01-15 10:50:35 UTC 
This actually looks valid, the *0 and *1 are used to spread a parameter value over multiple lines, see RFC2331 section 3, "Parameter Value Continuations".

I wonder if we have tests for this in KMime...
Comment 4 Torgny Nyblom 2010-01-15 15:22:04 UTC 
RFC2231 you mean? ;)
Yeah that seem to be correct, my bad.

This is working in KMime and is tested for (headertest::testContentTypeHeader).