https://bugs.kde.org/show_bug.cgi?id=322708
--- Comment #4 from Hauke Laging <ha...@laging.de> --- (In reply to comment #3) > I understand the bug in that way, that I got a private key which I'm not > fully trusting. Private keys are neither valid nor trusted. Certificates (public keys) are (in)valid and (un)trusted. > Nevertheless KMail shouldn't deny to use the key but give a clear warning. Indeed. > I can manually select a key for which I set the trust-level to anything less > then "Ultimately" (using Kgpg) for signing but I CAN'T select it for > encryption. GnuPG doesn't care about the trust level but about the validity level. The trust level doesn't change the validity level (exception: ultimate). You should never use ultimate trust in order to make a key valid. > If I set a full-trusted key as default for a KMail identity You mean ultimately trusted? > This is important! If someone forgot to create a new key or to send me a new > key I should be able so send him an encrypted email asking for that! And it must be possible to encrypt to an invalid key because otherwise the user is forced to pretend a key validation (unless he knows certain tricks). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs