1119300 - wrong attachment flagging of smime signed mails

Status: RESOLVED WORKSFORME

(Thunderbird :: Folder and Message Lists, defect)

Description

[Maik Holtkamp]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141126041045

Steps to reproduce:

I send messages both with s/mime sig and without and an attachment. 


Actual results:

The message without sig is flagged correcty with the clip showing it contains an attachment. The message with s/mime sig isn't flagged correspondingly, though it contains the very same attachment - the attachement itsself is ok and shown in the preview window, but not in the list.


Expected results:

Both mails should be flagged with attachemt symbol in the list. Most important filtering/searching for mails containing attachments that are s/mime signed isn't working either :(.

Comment 1

[Maik Holtkamp]

Attachment: MissingFlag.JPG

Marked red what I am missing. Most important, filtering for mails with att. doesn't work either :(.
Rel. message headers here:
---cut---
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090600010505040203050005"

This is a cryptographically signed message in MIME format.

--------------ms090600010505040203050005
Content-Type: multipart/mixed;
 boundary="------------030404080709020803010305"

This is a multi-part message in MIME format.
--------------030404080709020803010305
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
...
--------------030404080709020803010305
Content-Type: application/pdf;
 name="Schaltplan-MCU_R8C25V05_Page1.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Schaltplan-MCU_R8C25V05_Page1.pdf"
...
--------------030404080709020803010305
Content-Type: application/pdf;
 name="Schaltplan-MCU_R8C25V05_Page2.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Schaltplan-MCU_R8C25V05_Page2.pdf"
...
--------------ms090600010505040203050005
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
---cut---

Comment 2

[Maik Holtkamp]

Already switched IMAP server from courier to dovecot - same problem :(

Comment 3

[Maik Holtkamp]

In the present Version 45.5.0 this issue is fixed.