Tickets :: [#2851] cannot view multipart/related message

6.0.0-beta1

7/22/25

Summary	cannot view multipart/related message
Queue	Horde Framework Packages
Queue Version	FRAMEWORK_3
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	steveh (at) eecs (dot) umich (dot) edu
Created	10/26/2005 (7209 days ago)
Due
Updated	11/01/2005 (7203 days ago)
Assigned
Resolved	11/01/2005 (7203 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/01/2005 03:30:02 AM	Michael Slusarz	Comment #9 State ⇒ Not A Bug	Reply to this comment
Finally could reproduce if I turn text/html inline display off. This is actually a duplicate (more accurately an offshoot) of ~~Bug 1863~~ and ~~Bug 1866~~. I have added a workaround until those bugs can be resolved.

10/26/2005 08:35:31 AM	Jan Schneider	Comment #8 New Attachment: Lexware Newsletter.eml	Reply to this comment
Another example

10/26/2005 08:02:30 AM	Jan Schneider	Comment #7 State ⇒	Reply to this comment
FWIW, I can reproduce this too, no parts to be displayed inline.

10/26/2005 07:58:21 AM		New Attachment: message-source.txt

10/26/2005 07:57:50 AM		New Attachment: no-message2.png

10/26/2005 07:57:04 AM	steveh (at) eecs (dot) umich (dot) edu	Comment #6 New Attachment: no-message1.png	Reply to this comment
You're definitely not crazy, but I don't think I am either? :-) I've attached a screen shot of what I see (no-message1.pn), as well as the Horde / IMP versions (no-message2.png), and finally, the exact message source after resending it to myself. I completely cleared out my Horde & Imp directories. Did a cvs checkout from HEAD for both horde, framework, and imp. I did preserve my config files, however. Is there a configuration option that might explain the difference between our two experiences? Thanks for looking into this even though it works for you, by the way...

10/26/2005 06:58:05 AM	Michael Slusarz	Comment #5 New Attachment: Clipboard01.png	Reply to this comment
Just to prove I am not crazy...

10/26/2005 06:54:38 AM	Michael Slusarz	Comment #4	Reply to this comment
Commits that fixed this bug: http://cvs.horde.org/diff.php/framework/MIME/MIME/Message.php?r1=1.85&r2=1.86&ty=h (for HEAD) http://cvs.horde.org/diff.php/framework/MIME/MIME/Message.php?ws=0&r1=1.76.10.8&r2=1.76.10.9&ty=u (for Horde 3.0.6) Running HEAD here and the message renders perfectly.

10/26/2005 06:47:31 AM	steveh (at) eecs (dot) umich (dot) edu	Comment #3	Reply to this comment
Duplicate of ~~Bug 2537~~. According to ~~bug 2537~~, the problem there was resolved in Horde 3.0.6 and in HEAD. I just reinstalled horde using CVS HEAD Wed Oct 26 02:37:1 and it made no difference. The message attached in this bug still does not display inline or even appear as an external viewable attachment.

10/26/2005 05:59:53 AM	Michael Slusarz	Version ⇒ FRAMEWORK_3 Queue ⇒ Horde Framework Packages

10/26/2005 05:57:58 AM	Michael Slusarz	Comment #2 State ⇒ Not A Bug	Reply to this comment
Duplicate of ~~Bug 2537~~.

10/26/2005 05:45:18 AM	steveh (at) eecs (dot) umich (dot) edu	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ cannot view multipart/related message Queue ⇒ IMP New Attachment: mime-related.txt State ⇒ Unconfirmed	Reply to this comment
The attached email does not get displayed in IMP either inline or as a separate viewable attachment. It does display inline in Outlook express. I noticed that if you change the content-type from "multipart/related" to "multipart/alternative", then at least the HTML text becomes viewable as a separate attachment.