[Tickets #13696] IMP no display test/plain mime part

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13696
------------------------------------------------------------------------------
  Ticket             | 13696
  Created By         | patrice.borel at univ-tlse3.fr
  Summary            | IMP no display test/plain mime part
  Queue              | IMP
  Version            | 6.1.7
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


patrice.borel at univ-tlse3.fr (2014-11-17 14:27) wrote:

Hi,
IMP don't display text/plain mime part in this case:
The message is enclosed in Multipart/Alternative messages with 2 subparts:
- A "text/plain" mime part
- A "multipart/relative" mime part which enclose several basic mime  
type (text/html, image/png)...
IMP don't display text/plain message inline in the main browsing  
panel. We need to open the message part separately.

It's possible to display mime text/plain sub-part if another sub-parts  
are not multipart/relative.

The RFC spécification 1342  
(http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html)  says that:
In general, user agents that compose multipart/alternative entities  
should place the body parts in increasing order of preference, that  
is, with the preferred format last. For fancy text, the sending user  
agent should put the plainest format first and the richest format  
last. Receiving user agents should pick and display the last format  
they are capable of displaying. In the case where one of the  
alternatives is itself of type "multipart" and contains unrecognized  
sub-parts, the user agent may choose either to show that alternative,  
an earlier alternative, or both.

So, it seems IMP's behavior is not correct. Is it just ? Is there a  
patch or a configuration's rule to correct that ?
I join an example.
Best regards,
Patrice Borel