Bad signature (was: Re: GPG support in Mahogany)

[Graham]

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

On Friday 13 Dec 2002 3:38 am, Dave Barton wrote:

[snipped]
> So, if signatures are failing to verify then it is likely that
> either:
>
> 1) the signature was created according to rfc2015 rules or...
> 2) the signature is broken (assuming that gpg doesn't have any bugs)
[snipped]

Evolution's developers have admitted that if PGP/MIME messages are=20
generated to RFC2015, the sig will fail to verify.  However the=20
majority of MUAs don't support PGP/MIME and where they do, the vast=20
majority support only RFC2015 not the later RFC3156.  This means the=20
majority of messages generated by PGP/MIME will have a sig that fails=20
to verify in Evolution.......

That is why I send me messages by inline coding and why I haven't up to=20
now used Evolution.  I see from the list that Evo is now supporting=20
inline coding, so it might be worth another look.
- --=20

Graham
GPG Keys at encryption.keys@ntlworld.com

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

iD8DBQE9+cOiIwtBZOk1250RApNPAKCYs3IymDervmJiRpVuHSPaCLOd9gCgn0uL
jLrMUR2B1cdtl2NlxYAw7BY=3D
=3D80Rn
-----END PGP SIGNATURE-----