--===============1695938823==
Content-type: multipart/signed; boundary=nextPart13141323.Pk9BiJH1nN;
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart13141323.Pk9BiJH1nN
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thursday 18 August 2011, Hauke Laging wrote:
> Hello,
>=20
> probably all of you know the problem that users of that one *******
> kind of mail client tell you that they cannot read your emails like
> the ones from other people. There was just an "attachment" which
> they have to open in order to read the text. And of course, that
> other one attachment with nonsense data...
>=20
> This is more an email question than a GnuPG question: Mail clients
> are capable of sending both an HTML and a plain text version of the
> content within one email. I wonder whether it is possible to send
> emails in the same way with a plain text part and an alternative
> PGP/MIME part. "Solving" the outlook problem this way might increase
> the acceptance of OpenPGP.

It is certainly possible to do this, but
=2D I doubt that any existing mail client supports this out-of-the box
=2D it might not help because apparently this one mail client does not=20
handle multipart-mime correctly, so why should it support something=20
strange like a multipart/alternative message with a text/plain part and=20
a PGP/MIME part.

I don't think it's worth the effort thinking about this. In fact, it=20
might be better to ignore the problem because everytime a user of such a=20
mail client asks you why you've sent him such a strange message you can=20
tell him that his mail client is broken and that he'd be much better off=20
with standard-compliant mail client <insert your favorite mail client>.

Apart from that I'm pretty sure that only very old versions of Outlook=20
[Express] have those problems.


Regards,
Ingo

--nextPart13141323.Pk9BiJH1nN
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEABECAAYFAk5NXFYACgkQGnR+RTDgudhIlQCeP3lXY+kdmP/HLLa8GSJ3io9k
2IcAoKIp3yOR97pY2GMJ4t5jpX/qBOme
=8qNH
-----END PGP SIGNATURE-----

--nextPart13141323.Pk9BiJH1nN--


--===============1695938823==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

--===============1695938823==--