Kiefer, Sascha wrote: >>Possibly the confusion is that RFC-2015 was updated by >>RFC-3156. You should do things the 3156 way. >> >>David > > > Well, as far as i see there is no difference between the MIME format of > rfc2015 and rfc3156. > > So, what is right? > > RFC like: > > Content-Type: multipart/signed; micalg=pgp-md5 > protocol="application/pgp-signature"; boundary=bar > > --bar > Content-Type: text/plain; charset=us-ascii > > Test Message. > > --bar > Content-Type: application/pgp-signature > > -----BEGIN PGP MESSAGE----- > Version: PGP 8.1 > > iQA/AwUBQqI6/QInDejiptdCEQL7OwCgwhnncXMuL2gh4yzj8ZJryhGY0wsAoIof > z6j0B4UwYiLW0zLeAbEUZiTf > =F5ME > -----END PGP MESSAGE----- > > --bar-- > > > Or (enigmail like)
What you showed was not Enigmail like. Rather it looks like you're missing the (embedded) pgp mime part created from mailman. Enigmail creates correct RFC 3156 messages. Look e.g. at Dan's last message: Content-Type: multipart/mixed; boundary="foo" --foo Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bar" --bar Content-Type: text/plain; charset=us-ascii Test Message. --bar Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- WHATEVER -----END PGP MESSAGE----- --bar-- --foo Some text from mailman --foo--
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
