1353856 - Empty reading pane for message with Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";

Status: NEW

(Thunderbird :: Message Reader UI, defect)

Description

[Justin Bell]

Attachment: [CIT Program News] Replacements for CIT 41200.eml

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce:

Tried to read an email signed by s/mime


Actual results:

Message pane is blank


Expected results:

Message should be shown

Comment 1

[Jorg K (CEST = GMT+2)]

Seems to be a problem with S/MIME:

Changing the header
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=SHA1; boundary="----=_NextPart_000_011A_01D2AE04.8C79A410"
to
Content-Type: multipart/alternative;
	micalg=SHA1; boundary="----=_NextPart_000_011A_01D2AE04.8C79A410"
displays the message just fine.

Comment 2

[Justin Bell]

this is still a problem

Comment 3

[Justin Bell]

Attachment: [CIT Program News] Dean's Student Town Hall.eml

this is still happening

Comment 4

[Curt Esser]

My Thunderbird was updated to 78.0 (32-bit) last night and today I have the same problem. This morning when I open an email in a new tab, the subject line is there but the email is blank. If I open an email in a new window, it opens properly. If I use T-bird in safe mode, emails display properly in a new tab. I have no add-ons, and the issue still occurs if I turn off my security software.

As a work around I have changed my settings to open messages in a new message window, but would prefer using a new tab. Thunderbird 78 has a new look and the menu options have changed too. To get to this setting: Tools > Options > General > Reading & Display > Open messages in > A new message window.

Comment 5

[Gideon]

THIS BUG IS ESSENTIALLY IDENTICAL TO THE ONE I REPORTED A FEW DAYS AGO, BUG 1654579.
It seems to be classified as "unconfirmed".

Comment 6

[Gideon]

Discovered how to fix it. Somehow, in Options / Reading and Display,
"Open messages in" was bulleted as "a new tab".
If I change that to "a new message window", the problem is cured!

Comment 7

[Wayne Mery (:wsmwk)]

Kai, Magnus, this now has a testcase per comment 3.

Comment 8

[Wayne Mery (:wsmwk)]

Gideon, Curt, your issue is something different. Perhaps bug 1653168. There is no need to comment there, just CC yourself to the bug report.

Comment 9

[Gideon]

Wayne, thanks. There's a difference, yes, but Curt's workaround solved MY problem completely. Thanks, guys. And, good luck!

Comment 10

[Curt Esser]

sfhowes reply on Mozillazine support page worked to open in new tab. They wrote "If it works in safe mode, try this: start in safe mode, check 'Reset toolbars and controls', click 'Make changes and restart'."

Comment 11

[Gideon]

Curt, your quote above solved my problem completely, and enabled me to have messages open in a TAB, just like in the old days.
Many thanks to Curt and to Wayne! It's black magic to me, but it's so nice to be back to normal.

Comment 12

[Justin Bell]

opening in new window does not solve this for me

I will attach an example from today

Comment 13

[Justin Bell]

Attachment: [CIT Program News] Themed Entertainment Engineering and Design Club - Meeting on Tuesday!.eml

Comment 14

[Mark Sapiro]

I have just noticed this with Thunderbird 102.7.1 (64-bit) on Ubuntu 20.0.4. Here is a heavily edited message That shows the issue:

From: User <[e-mail]>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_B2DAD841-AF42-4BD5-B759-74CEAC79EAF2";
	protocol="application/pkcs7-signature";
	micalg=sha-256
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <[e-mail]>
Date: Wed, 8 Mar 2023 12:37:29 -0800
To: User <[e-mail]>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Subject: [GPC] S. Park ride tonight, b/c of rain tomorrow

--Apple-Mail=_B2DAD841-AF42-4BD5-B759-74CEAC79EAF2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear Grizzlies,

Since the weather is clear today but high chance of rain tomorrow =
...

--Apple-Mail=_B2DAD841-AF42-4BD5-B759-74CEAC79EAF2
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit


___________________________________________
Mailman's content filtering has removed the
following MIME parts from this message.

Content-Type: image/png
    Name: XXX.png

Content-Type: application/pkcs7-signature
    Name: smime.p7s

Replaced multipart/alternative part with first alternative.

--Apple-Mail=_B2DAD841-AF42-4BD5-B759-74CEAC79EAF2--

When this message is rendered, the headers From, To and Subject are shown along with the timestamp, but there is no content displayed.

The original message was actually the second of 4 messages in a multipart/digest the structure of which is:

    text/plain
    text/plain
    multipart/digest
        message/rfc822
            text/plain
        message/rfc822
            multipart/signed
                text/plain
                text/plain
        message/rfc822
            text/plain
        message/rfc822
            text/plain
    text/plain

The rendering of that digest was correct up to:

ForwardedMessage.eml
Subject: [GPC] S. Park ride tonight, b/c of rain tomorrow
From: User <[e-mail]>
Date: 3/8/23, 12:37
To: User <[e-mail]>
CC: User <[e-mail]>

But everything after that was missing including the content of this message, the two following messages and the final text/plain digest footer.

Note that changing the Content-Type of this message part from multipart/signed to multipart/mixed allows the entire digest to render correctly.

In some sense, we can blame Mailman's content filtering for removing the signature, but I don't think it's correct to truncate an entire multipart message just because one message/rfc822 subpart claims to be signed and doesn't have a valid signature.

Comment 15

[Mark Sapiro]

I've done some more testing and it appears that for the the issue to occur, there needs to be multiple subparts to the multipart/signed message and the absence of a signature is not important.

This message renders properly

Message-ID: <[e-mail]>
Date: Wed, 10 Mar 1999 23:06:43 -0600
From: User <[e-mail]>
MIME-Version: 1.0
To: User <[e-mail]>
Subject: Some subject
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msCEB52D8E38A9FA026513AD23"

This is a cryptographically signed message in MIME format.

--------------msCEB52D8E38A9FA026513AD23
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

First part content

--------------msCEB52D8E38A9FA026513AD23
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIKmQYJKoZIhvcNAQcCoIIKijCCCoYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC

--------------msCEB52D8E38A9FA026513AD23--

But this message with an added text/plain part does not.

Message-ID: <[e-mail]>
Date: Wed, 10 Mar 1999 23:06:43 -0600
From: User <[e-mail]>
MIME-Version: 1.0
To: User <[e-mail]>
Subject: Some subject
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msCEB52D8E38A9FA026513AD23"

This is a cryptographically signed message in MIME format.

--------------msCEB52D8E38A9FA026513AD23
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

First part content

--------------msCEB52D8E38A9FA026513AD23
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Another part

--------------msCEB52D8E38A9FA026513AD23
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIKmQYJKoZIhvcNAQcCoIIKijCCCoYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC

--------------msCEB52D8E38A9FA026513AD23--

Comment 16

[Mark Sapiro]

(In reply to Mark Sapiro from comment #15)

Also, it doesn't matter if the added part is before or after the signature part. This message also does not render properly.

Message-ID: <[e-mail]>
Date: Wed, 10 Mar 1999 23:06:43 -0600
From: User <[e-mail]>
MIME-Version: 1.0
To: User <[e-mail]>
Subject: Some subject
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msCEB52D8E38A9FA026513AD23"

This is a cryptographically signed message in MIME format.

--------------msCEB52D8E38A9FA026513AD23
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

First part content

--------------msCEB52D8E38A9FA026513AD23
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIKmQYJKoZIhvcNAQcCoIIKijCCCoYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC

--------------msCEB52D8E38A9FA026513AD23
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Another part

--------------msCEB52D8E38A9FA026513AD23--