| Summary: | The validity of the signature cannot be verified | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Michael S. <michael.saalfeld> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Chakra | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
Seems to be the same problem as described in bugreport 286035. So I marked the bug as 'duplicate. *** This bug has been marked as a duplicate of bug 286035 *** |
Created attachment 61475 [details] Screenshot Version: 2.1.0 (using KDE 4.6.4) OS: Linux When I receive a signed mail, kmail2 always complains, that the validity of the signature cannot be verified because of an unknown key. But the key kmail2 complains about, exists in the gpg-keyring, it's valid and even certified with my own key. Messages signed with my own key are verified correctly. Reproducible: Always Steps to Reproduce: Open a signed message and check the signature. Expected Results: The signature should be marked as 'trusted' because the signature exists in the keyring and is certified with my own trusted key.