[#3580] alternative part not displayed
Summary alternative part not displayed
Queue IMP
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners slusarz@horde.org
Requester vilius@lnk.lt
Created 2006-03-08 (5706 days ago)
Due
Updated 2009-08-13 (4452 days ago)
Assigned 2008-11-09 (4729 days ago)
Resolved 2008-11-19 (4719 days ago)
Milestone 5
Patch No

Comments
vilius@lnk.lt 2006-03-08 13:45:35
Multipart messages with alternative parts are not longer displayed in 
recent CVS. Example message attached.

Jan Schneider <jan@horde.org> 2006-03-10 00:19:56
Works perfectly for me.

vilius@lnk.lt 2006-03-10 16:32:55
Still don't work for me. I only see one plain/text part and only as 
attachment.



2 weeks (or so) before it was shown like plain/text message with 
alternative html/text part.

Chuck Hagenbuch <chuck@horde.org> 2006-03-10 21:42:31
I'm guessing you have html inline turned off? We're now matching the 
behavior of other email clients much more closely for alternative 
parts; we show the richest one we can, and ignore the others. I see 
the HTML part just fine if I have html inline turned on.

vilius@lnk.lt 2006-03-10 22:51:27
Yes, I have HTML inline parts set to off.



Can IMP then show plain part inline if HTML is disabled? And I still 
think IMP must keep access to HTML part somewhere (e.g. in alternative 
part/attachment list).

Michael Slusarz <slusarz@horde.org> 2006-03-10 22:59:14
> Can IMP then show plain part inline if HTML is disabled? And I still

> think IMP must keep access to HTML part somewhere (e.g. in

> alternative part/attachment list).



If you want the "old" behavior, you need to activate the preference 
'alternative_display'.

vilius@lnk.lt 2006-03-10 23:01:10
Actually I have it activated and set to 'below'.

Chuck Hagenbuch <chuck@horde.org> 2006-03-11 00:10:17
I can reproduce this now if I turn off inline html. I'm guessing you 
don't see the alternative display because the text part isn't 
displayed, and that's where the alternative text would be.



I think the problem may be that the 2nd part isn't text/html, it's 
multipart/related, so when we're looking at what we can display, we 
see text/plain vs. multipart/related and we blindly go with the 
multipart/related. Then we get there and inline html is off, so we 
don't have anything to display.



Michael, that sound right? Any idea what we can do about it?

vilius@lnk.lt 2006-03-11 10:55:59
I must note, that MIME structure of the example message was created by 
Thunderbird. And also, I personally asked Michael a couple of months 
ago is it correct, and he said it is.

Chuck Hagenbuch <chuck@horde.org> 2006-03-11 14:01:02
> I must note, that MIME structure of the example message was created

> by Thunderbird. And also, I personally asked Michael a couple of

> months ago is it correct, and he said it is.



No one said it's invalid. It's perfectly valid, we just don't have 
good logic for figuring out if a multipart/* part is "displayable" - 
we assume we'll find something in it to display, even if that ends up 
not being the case.

Jan Schneider <jan@horde.org> 2006-04-12 22:46:39
Chuck, has this been fixed with your changes regarding inline 
configuration of the plain viewer in mime_drivers.php?

Chuck Hagenbuch <chuck@horde.org> 2006-04-13 01:12:53
No. There is no plaintext part in the multipart/related part anyway.

vilius@lnk.lt 2006-04-14 13:48:41
Another sample of message where no parts is displayed if HTML inline 
is turned off.



IMP displays only a link to multipart/alternative and if you click on 
it, IMP downloads an empy file.

Michael Slusarz <slusarz@horde.org> 2006-04-14 15:17:16
Unfortunately, I don't know if we can fix this issue (given the 
current MIME rendering code) without either breaking BC and/or without 
breaking rendering of other messages.

Chuck Hagenbuch <chuck@horde.org> 2006-04-14 18:52:36
> Another sample of message where no parts is displayed if HTML inline

> is turned off.

>

> IMP displays only a link to multipart/alternative and if you click on

> it, IMP downloads an empy file.



Well, for this one we should just say there are no parts that can be 
displayed inline. Probably we're tripped up by the 
multipart/alternative, but since it only has one part, not much else 
we can do if you've turned off display of that part.

vilius@lnk.lt 2006-04-14 22:05:05
I turned off display of the part inline, but I still must have a link 
(or any other method) to access it. In this case I get a link with a 
part, but as I said I get only empty file. This is definetely not right.

Michael Slusarz <slusarz@horde.org> 2006-05-09 03:57:17
As mentioned previously, there is not much we can do about displaying 
this message with the current status of the code without breaking 
display of another message.

Michael Slusarz <slusarz@horde.org> 2006-07-06 04:50:29
See Bug 4073.

vilius@lnk.lt 2006-07-06 06:36:32
I suggest raising the priority to at least Medium, because HTML inline 
rendering is turned off by default in IMP. And this bug is serious 
enough with that setting.

Michael Slusarz <slusarz@horde.org> 2006-07-07 02:43:14
No need to raise priority since this is not something that can/will be 
fixed before 5.0.

Chuck Hagenbuch <chuck@horde.org> 2008-11-09 02:19:07
un-stalling

Michael Slusarz <slusarz@horde.org> 2008-11-19 05:43:49
This is fixed in IMP 5.0.

julien.gresse@gecko.fr 2009-08-13 09:22:23
> This is fixed in IMP 5.0.

Hi,

I'm rellay interested in that correction. I see it's not a patch but 
is it possible to apply it to an existing system ?



I'm working under Debian an the IMP 5.0 version is not going to be 
accepted soon...



Could you give me some hints to correct this problem ?



Thanks in advance.

Michael Slusarz <slusarz@horde.org> 2009-08-13 15:44:09
>> This is fixed in IMP 5.0.

> Hi,

> I'm rellay interested in that correction. I see it's not a patch but

> is it possible to apply it to an existing system ?



No.  The entire MIME system has been rewritten for Horde 4.