sylpheed GPG compatibility

[Ryan Malayter]

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

Ahh... I misunderstood the issue. I still use ASCII armored
format for most of my mail for similar reasons.

So sylpheed supports *only* PGP/MIME? That sounds a bit odd.
IIRC, ASCII armor capabilities are a "MUST" according to
RFC2440, but OpenPGP/MIME is only a "SHOULD" for OpenPGP enabled
messaging applications.


:::Ryan Malayter, MCSE
:::Bank Administration Institute
:::Chicago, Illinois, USA


- -----Original Message-----
From: Guy [mailto:unixuser@flashmail.com] 
Sent: Thursday, November 01, 2001 2:16 PM
To: Gnupg-users@gnupg.org
Subject: Re: sylpheed GPG compatibility


Hello Ryan

Thanks for your answer, but the problem is not the compatibility
between Gnupg and PGP, but with compliance to PGP/MIME. Sylpheed
uses this to sign and encrypt mails, kmail e.g. doesn't. When I
mail from sylpheed+GPG on Linux to Eudora+PGP on Windows, I
can't decrypt the message, signatures are correctly verified.
When I do the same from kmail, which uses clearsigning and
standard ascii armored encryption, it works correctly.

As some of the people I mostly encrypt to have Eudora+PGP, it's
a very irritating problem...

Guy



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32) - GPGshell v2.01
Comment: For info see http://www.gnupg.org

iD8DBQE74dMW9wZiZHyXot4RAv4YAKDrNn6IDDeXTXzvzuRMRNp+jvr6bQCeNOZt
mV5NfIBAgtgOxNXHDj77ZUg=
=GqXz
-----END PGP SIGNATURE-----