[English] Allow HTML not working with Content-Type: multipart/signed

wojtek · December 14, 2017 at 7:04 PM

Um Rückfragen vorzubeugen, bitten wir um folgende Angaben:

Thunderbird-Version: 52.5.0 (64-bit)
Betriebssystem + Version: macOS High Sierra
Kontenart (POP / IMAP): IMAP
Postfachanbieter (z.B. GMX): various

Hi, appologies for writing in English but my German knowledge is utterly basic (ja/nein/retchts/links…)

I love the above extension and it works great in the past years. However, recently I've noticed that it doesn't detect correctly HTML part if the message has Content-Type: multipart/signed; instead of usual Content-Type: multipart/alternative;

Would it be possible to handle HTML messages that are also signed? Thunderbird can display them just fine if forced in the settings.

Thunder · December 14, 2017 at 10:13 PM

Hi, thank you for your feedback!

I'll have a look into it. At the moment the addon looks for "text/html" in the message body. Would it be possible to forward a few comparable example messages to me? I need the whole message source code, to have a look into it.

Regards

Thunder · December 15, 2017 at 3:32 PM

Hi,

I believe that I have found and fixed it completely for S/MIME encrypted messages.

Unfortunately it's not possible to parse encrypted PGP/MIME messages for the existence of HTML parts. In case of PGP/MIME encrypted messages the addon will now activated the button regardless of the existence of an HTML part.

The fixed version is attached in this post for download:

Updates zu "Allow HTML Temp" und "Abrufen-/Senden-Schaltfläche" für Thunderbird 57+

Regards

wojtek · December 16, 2017 at 12:21 PM

Unfortunately I wasn't able to prepare complete case messages (will try to manage that shortly) however problematic mail has following sections:

HTML

Content-Type: multipart/signed;
    boundary="Apple-Mail=_EE3EC72C-1BBF-4371-93F2-C3AACC07B942";
    protocol="application/pgp-signature";
    micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
…
X-Mailer: Apple Mail (2.3445.4.7)


--Apple-Mail=_EE3EC72C-1BBF-4371-93F2-C3AACC07B942
Content-Type: multipart/alternative;
    boundary="Apple-Mail=_496E59ED-40BE-4A97-A5ED-73C1407AA052"


--Apple-Mail=_496E59ED-40BE-4A97-A5ED-73C1407AA052
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
    charset=utf-8

…
--Apple-Mail=_496E59ED-40BE-4A97-A5ED-73C1407AA052
Content-Type: multipart/related;
    type="text/html";
    boundary="Apple-Mail=_487F0D23-111E-400E-9AFF-B310AE3F37F8"


--Apple-Mail=_487F0D23-111E-400E-9AFF-B310AE3F37F8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
    charset=utf-8

<html><head>…</html>=

--Apple-Mail=_487F0D23-111E-400E-9AFF-B310AE3F37F8
Content-Transfer-Encoding: base64
Content-Disposition: inline;
    filename=image001.png
Content-Type: image/png;
    x-unix-mode=0644;
    name="image001.png"

…

--Apple-Mail=_487F0D23-111E-400E-9AFF-B310AE3F37F8
Content-Transfer-Encoding: base64
Content-Disposition: inline;
    filename=image002.png
Content-Type: image/png;
    x-unix-mode=0644;
    name="image002.png"
…
--Apple-Mail=_487F0D23-111E-400E-9AFF-B310AE3F37F8--

--Apple-Mail=_496E59ED-40BE-4A97-A5ED-73C1407AA052--

--Apple-Mail=_EE3EC72C-1BBF-4371-93F2-C3AACC07B942
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
    filename=signature.asc
Content-Type: application/pgp-signature;
    name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

…
-----END PGP SIGNATURE-----

--Apple-Mail=_EE3EC72C-1BBF-4371-93F2-C3AACC07B942--

Display More

What's more - those are not *encrypted*, only *signed* messages.

I've tried the new version and it seems to be working ok -- even signed messages are detected correctly. Thanks!

[English] Allow HTML not working with Content-Type: multipart/signed

Thunder January 7, 2019 at 5:49 PM

Community-Bot September 3, 2024 at 8:30 PM

Thunderbird 152.0.1 veröffentlicht

Thunderbird 140.12.1 ESR veröffentlicht