Version:           4.4.10 (using KDE 4.6.0) 
OS:                Linux

In accordance with RfC 2633 Chapter 3.8 a s/mime encrypted attachment should be also identified by the file suffixs p7m, p7s, p7m.

When a s/mine encrypted message is received with an attachemt descibed as

Content-type: application/octet-stream;
  name="smime.p7m"
Content-Disposition: attachment; filename="smime.p7m"
Content-transfer-encoding: base64

then the attachment is not recognised as a s/mime encrypted attachment.

A work-around is changing the content-type manualy to "application/pkcs7-mime" (with a filter).

This behavior may occure with some none complaied gateways (probably Lotus Notes or McAFee Scanner) which can't understand s/mime extensions and replace pkcs7-mime with octet-stream partly in an random manner.


Reproducible: Always

Steps to Reproduce:
Send a s/mime encryted mail to yourself, change the Content-Type from aplication/pkcs7-mime to application/octet-stream manualy.

Actual Results:  
smime.p7m is shown as an unknown attachment.

Expected Results:  
Decrypt, verify all attachments with the file name suffix p7m, p7s or p7c iaw RfC 2633 3.8 and display it in the same manner when it is received with contend type application/pkcs7-mime.


sed Filter for work around:

/^Content-type: application\/octet-stream;/,/^\ \ name="smime.p7m"/ s#octet-stream#pkcs7-mime#