[Mailman-Developers] Testing different email structures with MUAs

[Abhilash Raj]

Hi,

So I was testing which kind of message structure would be the best fit
for sending out messages with more than one signature part. I tried 3
things:

1) Message according to [1]this(having two signature parts in a
'multipart/mixed' part inside 'multipart/signed' message. My
MUA(*mu4e*[2]) fails to find any signature part at all in this

2) A 'multipart/alternative' message with each part having same
structure and each one having different signature. Now although from
rfc2046[3] it is not a thumb rule to have different 'content-type' for
each alternative part in a 'multipart/alternative', but I think MUAs
would get confused if they find both alternative parts completely
same(in structure). My MUA shows both parts and thus repeats data.
Although it shows two signature parts too.

3) This third type was just my idea, does not follow rfc3156 obviously.
I simply added another signature part to the original message and my MUA
reads it nicely showing two signatures.

I have attached all 3 type of message, each in a different file. Please
can you place it in your maildir and check how your MUAs respond to it
and report here? The message signature will not be verified(the
signature text is actually gibberish), this experiment is just to check
how the MUAs handle the message with such a structure.



[1]: http://tools.ietf.org/html/draft-ietf-openpgp-multsig-02
[2]: http://www.djcbsoftware.nl/code/mu/mu4e.html
[3]: http://tools.ietf.org/html/rfc2046#section-5.1.4
-- 
Abhilash Raj
-------------- next part --------------
From: anne at example.com
To: test at example.com
Subject: A Message with non-ascii body
Message-ID: <ant>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="===============0165780934=="
protocol: multipart/mixed

--===============0165780934==
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

A message body.
--===============0165780934==
Content-Type: multipart/mixed; boundary="===============1396434060=="
MIME-Version: 1.0

--===============1396434060==
Content-Type: application/pgp-signature
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
HOxEa44b+EI==ndaj
-----END PGP SIGNATURE-----

--===============1396434060==
Content-Type: application/pgp-signature
                          

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
HOxEa44b+EI==ndaj
-----END PGP SIGNATURE-----
--===============1396434060==--
--===============0165780934==--
-------------- next part --------------
From: anne at example.com
To: test at example.com
Subject: A Message with non-ascii body
Message-ID: <ant>
MIME-Version: 1.0
content-type: multipart/alternative; boundary="===============1658465758=="

--===============1658465758==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="===============1005232601=="

--===============1005232601==
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

A message body.
--===============1005232601==
Content-Type: application/pgp-signature
                          

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
HOxEa44b+EI==ndaj
-----END PGP SIGNATURE-----
--===============1005232601==--
--===============1658465758==
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="===============1174598811=="

--===============1174598811==
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

A message body.
--===============1174598811==
Content-Type: application/pgp-signature
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
HOxEa44b+EI==ndaj
-----END PGP SIGNATURE-----

--===============1174598811==--
--===============1658465758==--
-------------- next part --------------
From: anne at example.com
To: test at example.com
Subject: A Message with non-ascii body
Message-ID: <ant>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary=bar; micalg=pgp-md5;
 protocol="application/pgp-signature"

--bar
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

A message body.
--bar
Content-Type: application/pgp-signature
                          

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
HOxEa44b+EI==ndaj
-----END PGP SIGNATURE-----
--bar
Content-Type: application/pgp-signature
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
HOxEa44b+EI==ndaj
-----END PGP SIGNATURE-----

--bar--