Windows-PGP/Linux-GnuPG mails compatibility issues

[David T-G]

--+E165xXSMiO4rFaE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Graham, et al --

=2E..and then Graham said...
%=20
% -----BEGIN PGP SIGNED MESSAGE-----
% Hash: SHA1

[lots of useful background and infrastructure information deleted]


% PGP/MIME is not the correct version of PGP if your message cannot be
% decrypted or verified; take my advise and use inline PGP coding for ALL
% messages.

I think we can concede that signing/encrypting of attachments is
impossible with purely inline pgp (unless, I suppose, the uuencoded file
were pasted in, but LookOut! pukes on that, too), but has anyone gotten
inline pgp working with multibyte and non-"us-ascii" charsets to work?
I don't think that we can casually rule out PGP/MIME when sending
international email (but I certainly could be wrong).


%=20
%=20
% - --
%=20
% Regards
% Graham


TIA & HAND

:-D
--=20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


--+E165xXSMiO4rFaE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9A7F1Gb7uCXufRwARAl9OAJ9mP7rtsE5Zku29TNW4qQ5vkXPBvgCbB8zI
auBHSMHfu2U0r7HlcQI8dS0=
=EOpj
-----END PGP SIGNATURE-----

--+E165xXSMiO4rFaE--