GNU bug report logs -
#9862
23.3; [Gnus/EasyPG] Mixing PGP/MIME signature with RFC822 forwarded multipart message results in an invalid MIME message
Previous Next
Full log
View this message in rfc822 format
Daiki Ueno <ueno <at> unixuser.org> writes:
> Well, I couldn't actually reproduce it. With the MML from the Debian
> bug and got the following. The boundary strings look legal, but
> interestingly the rendering seems to be broken. I see
> "--====-=-=--\n----------\n" after the line "Foo".
>
> From nobody Tue Oct 25 17:04:52 2011
> Message-ID: <m3vcrda4c6.fsf-ueno <at> unixuser.org>
> From: Daiki Ueno <ueno <at> unixuser.org>
> To: ueno <at> unixuser.org
> Subject: test
> Date: Tue, 25 Oct 2011 17:04:45 +0900
> MIME-Version: 1.0
> Content-Type: multipart/signed; boundary="=====-=-=";
> micalg=pgp-sha1; protocol="application/pgp-signature"
> Lines: 39
> Xref: localhost.localdomain outgoing.gpg:392
> X-Gnus-Article-Number: 392 Tue, 25 Oct 2011 17:04:52 +0900
>
> --=====-=-=
> Content-Type: multipart/mixed; boundary="=-=-="
>
> --=-=-=
> Content-Type: message/rfc822
> Content-Disposition: inline
>
> --====-=-=
> Content-Disposition: inline
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="====-=-="
>
> Foo
>
> --====-=-=--
This part is wrong. The boundary line "--====-=-=" needs to be moved
after the rfc822 headers, like this:
--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline
Content-Disposition: inline
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="====-=-="
--====-=-=
Foo
--====-=-=--
Andreas.
--
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
This bug report was last modified 13 years and 256 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.