The IMAP server that I have to use does some strange things to the Content-Type header of PGP-encrypted messages:
A correctly sent message (as generated by mutt) with | MIME-Version: 1.0 | Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; | boundary="PmA2V3Z32TCmWXqI" | Content-Disposition: inline (and the two attachments | Content-Type: application/pgp-encrypted | Content-Disposition: attachment [...] | Content-Type: application/octet-stream | Content-Disposition: attachment; filename="msg.asc" ) (which is - of course - handled perfectly if received by mutt) is modified by the IMAP server to this form: | MIME-Version: 1.0 | Content-Type: multipart/mixed; | boundary="_003_20130725160657GB18564hostnamewithoutdots_" (and the attachments: | --_003_20130725160657GB18564hostnamewithoutdots_ | Content-Type: text/plain; charset="us-ascii" | Content-Transfer-Encoding: quoted-printable [...] | --_003_20130725160657GB18564hostnamewithoutdots_ | Content-Type: application/pgp-encrypted; name="ATT00001" | Content-Description: ATT00001 | Content-Disposition: attachment; filename="ATT00001"; size=76; | creation-date="Thu, 25 Jul 2013 15:57:21 GMT"; | modification-date="Thu, 25 Jul 2013 15:57:21 GMT" | Content-Transfer-Encoding: base64 [...] | --_003_20130725160657GB18564hostnamewithoutdots_ | Content-Type: application/octet-stream; name="msg.asc" | Content-Description: msg.asc | Content-Disposition: attachment; filename="msg.asc"; size=2389; | creation-date="Thu, 25 Jul 2013 15:57:21 GMT"; | modification-date="Thu, 25 Jul 2013 15:57:21 GMT" | Content-Transfer-Encoding: base64 ) i.e., the PGP/MIME contents seems to be base64-re-encoded and encapsulated in another MIME layer(?) The problem is: mutt (1.5.21) does not understand/know what to do with this message. On the other hand, icedove/thunderbird + enigmail does understand this strangely encoded message (and asks for the gpg passphrase etc.). Is there anything I can do to make mutt recognize that this is a kind of PGP/MIME message? Or can I patch mutt such that it looks not only after the Content-Type: headers but also into the attachments' Content-Type:s? (I wouldn't mind changing the source of mutt locally if this helps.) Thanks in advance, Olaf
