There was a thread on this mailing list back in March, http://marc.info/?l=mutt-users&m=130016436305546&w=2 List: mutt-users Subject: application/pgp-signature is unsupported From: Joseph < xxx () gmail ! com> Date: 2011-03-15 4:44:57
which doesn't seem to have had a resolution. I am facing the same problem now, but may have a bit more information. The copy of mutt I'm using is fully supporting signed/encrypted emails. Point in case, the earlier, signed message to this list Date: Wed, 22 Jun 2011 04:10:36 -0400 From: Athanasius <m...@miggy.org> To: Joseph <syscon...@gmail.com>, "mutt-users@mutt.org" <mutt-users@mutt.org> Subject: Re: EXITCODE==255 presents no problems whatsoever. But there are some messages mutt fails to interpret correctly. I think this all started when $work moved to Exchange. Exchange seems to have the nice and friendly habit of rewriting all sorts of things on delivery, although in this case I have no proof without the original message (MIME info and attachments are scrubbed from the corresponding mailing list archive). The messages that fail have the following MIME structure: I 1 <no description> [text/plain, quoted, windows-1251, 1.6K] A 2 This is a digitally signed message part.[applica/pgp-signat, base64, 0 A 3 ATT00001.c [text/plain, base64, us-ascii, 0.2K] Part two is the signature, encoded in base64, and part three is a mailing list footer, also in base64. Also note that the header Content-Type: is multipart/mixed rather than multipart/signed.
