Keys not trusted

[Malte Gell]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Am Dienstag, 6. Mai 2003 02:03 schrieb Wolfgang Bornath:
> Hi,
>
> Being fairly new in this I joined this list and received some
> messages by people who signed their messages. I always imported the
> keys (using the gpg option --auto-key-retrieve) and kmail tells me
> "Message is signed by XY (blahblub) (Key-ID: 0x12345678).
> Signature is valid but the key is not trusted."


KMail (other clients too ?) will only accept such keys, if they're=20
signed. You could (locally) sign this key and then KMail will accept=20
it. By the way, does someone know, whether this behaviour completely=20
depend on the MUA or is this some OpenPGP recommendation ?

By the way, if you want to get subscribed to lots of mailing lists, the=20
=2D --auto-key-retrieve option may bloat your key ring in the long run. It=
=20
may contain lots of keys from people you may never have contact with.=20
So it happens now with my key, because this message is signed ;-) If=20
you want to contact a person whose message is signed you can get=20
his/her key at a later point of time anyway. KMail always shows the key=20
ID of a signed message, no matter if you have the key locally on your=20
keyring, you still can get it if really needed.

Regards
Malte
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iEYEAREDAAYFAj64IhcACgkQGzg12gD8wBatrwCgvTRol2r/7RPAIvyYHOLhJNQd
wQsAn1licf9XAgmcX+nsV4xJFJlTRCa+
=3DLK2X
=2D----END PGP SIGNATURE-----