properly display "smime-type=signed-receipt" inside "application/x-pkcs7-mime"



14 years ago
3 years ago


(Reporter: hauser, Unassigned)


(Depends on: 1 bug)

Firefox Tracking Flags

(Not tracked)




(1 attachment)

8.02 KB, application/x-zip-compressed


14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

As per the above URL Outlook 2003 is created signed receipts of type 

Content-Type: application/x-pkcs7-mime;

When receiving such a receipt, Thunderbird is not capable to display the
signature properly and shows the icon "key with a x-ed red dot"

Reproducible: Always defines application/x-pkcs7-mime but
astonishingly, it and do not mention "smime-type=signed-receipt".

Comment 1

14 years ago
Created attachment 172085 [details]

here an example of the message thunderbird got from my outlook and the receipt
an outlook generated in response to that message.

Since I found no "Disposition-Notification-To" header or alike
I assume the fact that such a signed receipt shall be returned is coded in a
proprietary way into Outlooks long "Message-ID" header.

Comment 2

14 years ago
as per
receiptRequest attribute to the signedAttributes field of the SignerInfo object
should trigger the creation of such a receipt.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED


13 years ago
Resolution: EXPIRED → ---

Comment 5

12 years ago
openssl unfortunately cannot do this either, they make this dependent on the v3 smime as per .

BC has been alerted to this in 


12 years ago
Ever confirmed: true
QA Contact: front-end
Assignee: mscott → nobody

Comment 6

9 years ago
I assume this bug report is still valid (since it's an RFE)?

Comment 7

8 years ago
This issue will be resolved with bug 386313.
Depends on: 386313
You need to log in before you can comment on or make changes to this bug.