On Thu, Sep 30, 2010 at 12:50:03PM +0200, Jostein Berntsen wrote: > On 30.09.10,11:21, Stephan Seitz wrote: > > Hi! > > > > Since some Thunderbird updates mutt (1.5.20) doesn’t recognise > > anymore that the mail is SMIME encrypted. > > > > If the mail contains the following headers, everything is working: > > Content-Type: application/x-pkcs7-mime; name="smime.p7m" > > Content-Transfer-Encoding: base64 > > Content-Disposition: attachment; filename="smime.p7m" > > Content-Description: S/MIME Encrypted Message > > > > However the last header line is missing in mails from newer > > Thunderbird versions and mutt can’t handle it. If I manually add the > > header line, it works again. > > > > Is this a bug in Thunderbird or in mutt? > > > > Shade and sweet water! > > > > Stephan > > > > This sounds like something that has happened to Thunderbird, but I'm not > sure. You can check if mutt 1.5.21 can handle this. You can also check > on the Content-Type header in procmail and make formail add the > Content-Description header before it is delivered to mutt.
From a quick glance at the RFC's, I think mutt is not doing the right thing here. The Content-Description field doesn't appear to be mandatory, but even if it is, it's meant to be a description for human readers and not computers. As such, mutt probably should make no assumptions based on its presence or content. The Content-Type header should be sufficient for mutt to decide if it's dealing with an S/MIME message or not. Remco
signature.asc
Description: Digital signature
