From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020510 BuildID: 2002051006 When recieving a S/Mime signed message with the content type multipart/mixed the attachment is not recognized as a signature but presented as a downloadable attachment. Messages that I've signed myself look fine. Reproducible: Always Steps to Reproduce: Du. Example: NOT OK: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=____1021524480381_flU9Hj5bkX" THIS IS OK: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000707080104010008010900" I can't verify this bug better, since I don't recieve a lot of signed messages, and I also don't if the "bad" example actually breaks the S/Mime spec - but even in that case it would be nice to be able to import the certificate.

Reporter, please attach a full test message to this bug report. Thanks Reassign to Kai

The PKCS#7 sig in this mail is presented as a downloadable attachment.

This is an outbox-copy of a mail I signed myself. The signature in this mail is displayed correctly.

Obviously, the signature isn't recognized in OE either AND the person from which it came does not even know why her mail was signed (or what signing is). I'm still investigating this...

*** Bug 295118 has been marked as a duplicate of this bug. ***

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.