-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Searle wrote:
> Does anyone know of an authoritive statement regarding MS Outlook
> and its lack of support for pgp/mime, that I can point complaining
> Outlook using recipients of my emails at. Nothing too snarky, but
> something they are likely to comprehend.
It's hard to know what is likely to be comprehended by a typical
Outlook user. The bottom line is that if their MUA is displaying
PGP/MIME formatted messages as attachments, their MUA is not following
the various MIME RFC's properly.
The analogy I try to make with users who aren't hip to RFC lingo is
that not following the RFC's is much like refusing to use the same
definitions of words that we all use. It makes communication
difficult when one party insists on speaking the same language.
I've read various sites and some claim that Outlook 2000 and 2003 will
render a PGP/MIME message properly (though won't verify it). But that
doesn't seem to work in the very limited testing I did when I was
drafting a presentation on secure email for a group of Windows using
lawyers a few months ago.
An authoritative statement would be RFC 1847 Security Multiparts for
MIME: Multipart/Signed and Multipart/Encrypted. It's dated 1995, so
it's probably too new to have been fully implemented in the latest MS
products. ;-)
- --
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
======================================================================
I do not pretend to know where many ignorant men are sure - that is
all that agnosticism means.
-- Clarence Darrow
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iQFDBAEBAgAtBQJE71/7JhhodHRwOi8vd3d3LnBvYm94LmNvbS9+dG16L3BncC90
bXouYXNjAAoJEEMlk4u+rwzjK2EIAJA/Jx/v9sbH++LbJx6ff0TlA0Vy3bsN0tMC
FtE0EDTgxBj55n6rRku9LjnLErUjjgYC9zwQfNKsqwe9Zb77jUdmHX864ORnlK96
y2fSlDNniGzBoEi0U1EMtzrU9//K00jgiy1vCuCEeIm2gjIsrid5zd3payIo3AhN
JkzYDQjISp784nc9aP+XbhuE4yJ2+ufzaA1qjNDz9HL6C1DTuWpsn/cbiaJCPzxH
RGyAIaGXaZYX4YgIFfwDliMY1jNuBbSZq6zJkbkD/E7k9W7ampbh2/mJeyALlYWP
ByAZIbTLvO5MYg7pFMRqPm8p6AgjW8BPhS+HfgJdrV8yuw3nGzw=
=0Wqf
-----END PGP SIGNATURE-----
