Windows-PGP/Linux-GnuPG mails compatibility issues

[Graham]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Virginie wrote:

|
| So I would really enjoy some advises or solution or simple experiences
| From GnuPG experts working in heterogeneous environment.
|
| (I saw that GnuPG plugins for windows/outlook exist, but unfortunately I
| can't ask my society's customers to install Cygwin-gnupg+plugin to be
| compatible with me. Simple PGP use is already a challenge for them :)
|
|
|

Here we go...

PGP/MIME is a function of the mailer, not of GPG or PGP, and of those
mailers in Windows that support PGP/MIME most do as a result of the PGP
plugin that comes with PGP that changes the mailer, not PGP.

Until recently, with the advent of PGP 7.x those plugins were not
PGP/MIME compliant to RFC 2015; unfortunately most people who know what
they are about in the Windows PGP environment prefer to use PGP 6.5.8 or
the unofficial PGP 6.5.8ckt which come with plugins that are not wholly
compatible with RFC2015.

You get the example of Eudora which used PGP/MIME of a kind that only
other Eudora users could verify or decrypt.

That is not to say that some PGP compatible mailers come with a suitable
PGP/MIME extension (eg. Becky with its PGPB2 plugin) that is compatible
to RFC2015, but by and large it is best not to use PGP/MIME with Windows
PGP users.

Most mailing lists strip attachments that are a feature of PGP/MIME and
many Windows users automatically delete attachments unless they are sure
of them for fear of viruses.

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.


- --

Regards
Graham

GPG Key ID E935DB9D

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Please sign and encrypt for internet privacy

iD8DBQE9A65oIwtBZOk1250RAhOPAJ4xSJ3BIjyjEU++40iU/u9w0bI14ACeMcKB
LpPP8NyLYvrqrmmlrUOPgpg=
=9+bK
-----END PGP SIGNATURE-----