I am currently using mutt 1.5.1 and the S/MIME functions have proved to
work without problems. But today I received an encrypted and signed
S/MIME message which could not be neither verified nor decrypted by mutt
(openssl). Here are the significant headers from two different mails,
the first mail is created by Lotus Notes R5 and the second is created
by some Microsoft MUA (don't know which, no MUA header). Both are
signed and encrypted. The Notes mail works, the MS mail doesn't:
Lotus Notes:
Content-Transfer-Encoding: base64
Content-Type: application/x-pkcs7-mime;
smime-type=enveloped-data;
name=smime.p7m
Content-Disposition: attachment; filename="smime.p7m"
Content-Description: S/MIME Enveloped Data
Microsoft unknown MUA:
Content-Type: application/x-pkcs7-mime;
name="smime.p7m"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="smime.p7m"
One difference is that the "smime-type=enveloped-data;" row is missing
from the MS mail. I inserted this row in the MS mail and opened the
mail in mutt: now both signature check and decrypt works.
My question is: Is the MS MUA not following the S/MIME standard by
omitting this row or is mutt wrong by not being able to handle it
without this row?
Any comments?
--
Timo T. Rajala
