Bug 205626

Summary: content-location header in multipart/related message does not work
Product: [Applications] kmail Reporter: Martin Koller <kollix>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bjoern, opensource
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: the multipart mail

Description Martin Koller 2009-08-30 00:18:15 UTC 
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I'll attach a mail, which is a multipart/related one.
It was obviously Produced By Microsoft Exchange V6.5
and can be viewn with M$-outlook express in the way that I only see the image as content.
(The attachment is a modified example but still shows the problem)

In kmail instead of the image I see an empty frame with the "unknown" image in the top left corner.

In thunderbird it's the same.

I assume the bug is in the mail itself, but don't know the details of the mail format.

I tracked down the problem to objecttreeparser.cpp
ObjectTreeParser::defaultHandling()
where the image is saved to a tmp file and passed to
htmlWriter()->embedPart( ...) but as the HTML part of the message does not contain a cid URL, it is never used in
KHtmlPartHtmlWriter::resolveCidUrls()


Now I don't know what to do ...
Comment 1 Martin Koller 2009-08-30 00:19:05 UTC 
Created attachment 36567 [details]
the multipart mail
Comment 2 Thomas McGuire 2009-09-06 19:45:54 UTC 
Seems like KMail does not properly deal with the Content-Location header at all, see RFC 2557, especially section 9, the examples.
Comment 3 Mathieu Jobin 2010-02-26 15:56:50 UTC 
please fix this

it is very annoying, all the html messages I receive does not display pictures

maybe only kmail to kmail works
Comment 4 Mathieu Jobin 2010-02-26 15:57:13 UTC 
see bug 205791 as well
Comment 5 Björn Ruberg 2010-03-05 18:22:33 UTC 
If both bugs refer to the same problem, lets join them

*** This bug has been marked as a duplicate of bug 205791 ***