6.0.0-RC7
6/29/26

[#1185] Inlined content is not shown
Summary Inlined content is not shown
Queue IMP
Queue Version 4.0.1
Type Bug
State Not A Bug
Priority 1. Low
Owners Horde Developers (at) , slusarz (at) horde (dot) org
Requester imp (at) mavetju (dot) org
Created 1/17/05 (7833 days ago)
Due
Updated 1/20/05 (7830 days ago)
Assigned 1/18/05 (7832 days ago)
Resolved 1/20/05 (7830 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
218 Chuck Hagenbuch Comment #5
State ⇒ Not A Bug
Reply to this comment
Jan is correct. The outer message needs to be multipart/mixed. That 
message should contain 2 parts - the multipart/related message with 
the HTML and images, and the PDF. Putting the PDF inside the 
multipart/related isn't correct.
2111 imp (at) mavetju (dot) org Comment #4 Reply to this comment
Let me explain how the message looks like:



- There is an text/html and a text/plain segment. Yes, these two are 
alternative of each other, but most mailreaders pick the text/html 
segment to display.



- The text/html segment has two inlined images: the logo and the fax preview



- The PDF fax itself is an attachment.



When changing to multipart/alternative, the mailreaders I tested it on 
will display the all the attachments on its own, depending on which 
selected.



When changing to multipart/related, it displayed the text/html one 
with the inlined images and the attached pdf.



When changing to mutlipart/mixed, it displayed the text/html but 
failed to load the images or to display the attachment.



I even went so far as to remove the text/plain attachment, it made no 
difference for IMP.



I use the perl5 module MIME::Lite to create the messages, and used 
their example called "Send an HTML document... with images included!" 
as my example.



Hope this will clear up things a little bit, Edwin


5510 Jan Schneider Assigned to Michael Slusarz
Assigned to Horde DevelopersHorde Developers
 
4110 Jan Schneider Comment #3
State ⇒ Feedback
Reply to this comment
AFAICS the message has a wrong mime type. It should be 
multipart/alternative, not multipart/related.
1511 imp (at) mavetju (dot) org Comment #2 Reply to this comment
The filename "imap4" was originally "imp4". The problem has nothing to 
do with the IMAP protocol in any way shape or form.
211 imp (at) mavetju (dot) org Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Inlined content is not shown
Queue ⇒ IMP
Reply to this comment
Please see the email at http://www.mavetju.org/~edwin/imap4-fails.txt



This email is displayed properly with horde2/imap3, but is not with 
horde3/imap4; All I get is:



<pre>Date:           Tue, 18 Jan 2005 09:38:17 +1100 (EST) [09:38:17 EST]

From:          Barnet DeskFax operator <faxmaster@barnet.com.au> Australia

To:          Edwin Groothuis - fax <61292100600@fax-processing.barnet.com.au>

Subject:          Fax from 02 9335 3000 to +61 2 9210 0600

Headers:          Show All Headers

<i>There are no parts that can be displayed inline.</i>

</pre>



Suggestions?


Saved Queries