Re: Revisiting: application/pgp-signature is unsupported
> > I presume mutt needs multipart/signed. > > Sounds like a reasonable guess. I don't suppose you could send in a > message that has been mangled this way? It would make it easier to > test. I'm attaching a tgz archive with both versions, most of the headers stripped that are not relevant to this discussion. I don't necessarily ask that mutt supports this form of broken email, but it would be nice to have a workaround. Chances are slim that our hoster will address the issue. broken-pgp.tgz Description: application/tar-gz
Re: Revisiting: application/pgp-signature is unsupported
On Friday, 24 June 2011 at 00:00, Lars Hecking wrote: > > > I am facing the same problem now, but may have a bit more information. > > Original message has a multipart/signed structure with a qp text and > a signature part, all of which is wrapped into a multipart/mixed > structure, presumably done by the list server for the purpose of adding > a (text, 7-bit) footer. Exchange flattens the struture into a multipart/ > mixed with a qp text part, a application/pgp-signature part in base64, > and another base64 text part. > > I presume mutt needs multipart/signed. Sounds like a reasonable guess. I don't suppose you could send in a message that has been mangled this way? It would make it easier to test.
Re: Revisiting: application/pgp-signature is unsupported
> I am facing the same problem now, but may have a bit more information. Original message has a multipart/signed structure with a qp text and a signature part, all of which is wrapped into a multipart/mixed structure, presumably done by the list server for the purpose of adding a (text, 7-bit) footer. Exchange flattens the struture into a multipart/ mixed with a qp text part, a application/pgp-signature part in base64, and another base64 text part. I presume mutt needs multipart/signed.
Revisiting: application/pgp-signature is unsupported
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 To: Joseph , "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 [text/plain, quoted, windows-1251, 1.6K] A 2 This is a digitally signed message part.[applica/pgp-signat, base64, 0 A 3 ATT1.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.
