[jira] [Resolved] (SLING-11784) Email with both HTML and Text parts only display the text part in GMail

["Oliver Lietz (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Lietz resolved SLING-11784.
----------------------------------
    Resolution: Fixed

Thanks, [~sdumitriu]!

> Email with both HTML and Text parts only display the text part in GMail
> -----------------------------------------------------------------------
>
>                 Key: SLING-11784
>                 URL: https://issues.apache.org/jira/browse/SLING-11784
>             Project: Sling
>          Issue Type: Bug
>    Affects Versions: Commons Messaging Mail 2.0.0
>            Reporter: Sergiu Dumitriu
>            Assignee: Oliver Lietz
>            Priority: Minor
>             Fix For: Commons Messaging Mail 2.0.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When displaying a list of alternatives, [rfc1341|https://datatracker.ietf.org/doc/html/rfc1341] considers that the preferred order is from the last to the first, so the richest alternative (HTML) should be placed after the basic text.
> {quote}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.
> NOTE: From an implementor's perspective, it might seem more
> sensible to reverse this ordering, and have the plainest
> alternative last. However, placing the plainest alternative
> first is the friendliest possible option when
> mutlipart/alternative entities are viewed using a non-MIME-
> compliant mail reader. While this approach does impose some
> burden on compliant mail readers, interoperability with
> older mail readers was deemed to be more important in this
> case.{quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)