Outlook express messes up when it receives gpg-signed mail?

[Jan Niehusmann]

--wac7ysb48OaltWcw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Sep 04, 2003 at 08:35:21AM -0400, Eugene Smiley wrote:
> You will find that the number of people who use an email program that
> doesn't support PGP/MIME is quite high. Until more mainstream software
> supports it, it's better to use PGP-Inline signing unless you are part
> of a group where everyone is known to be able to handle PGP/MIME.

The problem is not that Outlook doesn't support PGP/MIME. Many programs
do not support PGP/MIME and still display the message correctly (and add
one attachment of unknown type with the signature).

But Outlook, for some unknown reason, ignores the following MIME headers
in the message:
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline

These headers clearly state that the part is not an attachment but
should be shown inline, and that it contains pure text that doesn't need
a special handler to be displayed.

But Outlook still chooses to show the message part as an attachment. I'd
say this is clearly a bug (and not just a missing feature).

So I prefer to use PGP/MIME instead of inline-pgp, because it works very
reliable (I still have to see a single PGP/MIME message with a broken
signature because of some ill reencoding) and supports signing of
attachments.

Jan


--wac7ysb48OaltWcw
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/Vzj3nIUccvEtoGURApR7AJoDyMGanYR+ZxT4FTitcW6dfYS2mQCgihSv
Gh7dF8cffxGnF2rfWVFRRcc=
=K2+1
-----END PGP SIGNATURE-----

--wac7ysb48OaltWcw--