1612465 - MIME parts with a Content-ID referenced in HTML are not found if the Content-ID; is RFC2047 encoded.

Status: RESOLVED INVALID

(MailNews Core :: MIME, defect)

Description

[Mark Sapiro]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Received a message with the following MIME structure.
Content-Type: multipart/alternative
Content-Type: text/plain

    plain text alternative part
Content-Type: multipart/related
    Content-Type: text/html

        html part with an img tag referencing src="cid:85d06102a59862e3af98226ebaacf7dfcc86f20a2dd9b31c125b8b9dab559b1c@phpmailer.0"
    Content-Type: image/jpeg
    Content-Transfer-Encoding: base64
    Content-ID: <=?us-ascii?Q?85d06102a59862e3af98226ebaacf7dfcc86f20a2dd9b31c125b8b9dab55?=
     =?us-ascii?Q?9b1c@phpmailer.0?=>
    Content-Disposition: inline

        the base64 encoded jpeg

Actual results:

The HTML was rendered with a missing image. The image was only visible as an attachment

Expected results:

The image should have been displayed at the point referenced in the html.

Note that editing the raw message to change the Content-ID header to
Content-ID: <85d06102a59862e3af98226ebaacf7dfcc86f20a2dd9b31c125b8b9dab559b1c@phpmailer.0>
allowed the message to be displayed as intended.

Comment 1

[era+mozilla]

This is squarely a bug in Python; the Content-Id should not be RFC2047-encoded. See https://github.com/python/cpython/issues/100293

Comment 2

[Mark Sapiro]

It is correct that Content-ID must not be RFC 2047 encoded, however in this case, Python is not involved as the offending message was produced by PHP, not Python. In any case, I'm closing this as INVALID.