S/MIME handling

[Sertaç Ö. Yıldız <sertac.liste@xxxxxxxxx>]

Hi,

I'm having some difficulties with verifying the signatures of some
messages I receive with mutt. These messages generally have this
pattern:

| MIME-Version: 1.0
| Content-Type: multipart/signed;
|       protocol="application/x-pkcs7-signature";
|       micalg=SHA1;
|       boundary="----=_NextPart_000_8FAF4_01C6EBA2.320E8700"
| Content-Transfer-Encoding: quoted-printable
| X-Mailer: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
| Status: RO
| Content-Length: 6711
| Lines: 126
| 
| This is a multi-part message in MIME format.
| 
| ------=_NextPart_000_8FAF4_01C6EBA2.320E8700
| Content-Class: urn:content-classes:message
| Content-Type: text/html;
|       charset="iso-8859-9"
| Content-Transfer-Encoding: quoted-printable
| [..snipped..]
| ------=_NextPart_000_8FAF4_01C6EBA2.320E8700
| Content-Disposition: attachment;
|       filename="smime.p7s"
| Content-Type: application/pkcs7-signature;
|       name="smime.p7s"
| Content-Transfer-Encoding: base64
| [..snipped..]
| ------=_NextPart_000_8FAF4_01C6EBA2.320E8700--

Since the Content-Type headers do not conform to RFC1847, I get
"Inconsistent multipart/signed structure" error. But both evolution and
openssl can display/verify the same message without problem. Shouldn't
mutt be a little more tolerant about this kind of standards violations?

Furthermore, If I edit the content type with ctrl-e to fix it, I still
receive an error saying "Error reading S/MIME message". When I checked
the temporary file mutt feeds to OpenSSL, it had part of the message
message and part of the signature. Might there be a bug in parsing the
message?

-- 
~sertaç