Tim Becker wrote on 28.02.12 19:10:
> I'm surprised I've not been able to find anything about this, as it
> affects both me and a colleague independently.
> With a current setup:
> Thunderbird 10.0.2, Enigmail 1.3.5 (20120116-1733) OSX 10.7.3
> I'm not able to automatically decrypt pgp/mime message, the base64
> contained in `encrypted.asc` is displayed as an inline attachment,
> saving the attachment and decrypting it on the command line works
> fine. I initially thought this was due to the mails being sent by
> osx's Mail.app, but Enigmail won't even decrypted pgp/mime mails that
> I send to myself, i.e. that it produces.
> The only plausible bug similar that would explain this phenomenon was this:
> http://forums.gentoo.org/viewtopic-t-881831-start-0.html >
> I guess, that TB oder Eningmail aren't able to map the
> 'encrypted.asc's mime-type from 'application/octetstream' as stated in
> the mime message to 'application/pgp-encrypted', the workaround in the
> bug above is to append `asc` to the entry for
> 'application/pgp-encrypted' in `/etc/mimetypes` but, alas, OSX does
> not have an `/etc/mime.types` and I'm not sure what the equvalent
> mechanism in OSX is.
> Any ideas? Is this a known bug, or would some debug output be helpful?
Sent messages should work. So in a first step, could you please check if
you can decrypt a message in TBs sent folder?
Could you please excerpt the complete MIME structure of such a