Summary: | kmail/kleopatra selecting s/mime certificates and smtp authentification failures | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Christophe Prud'homme <prudhomm> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | enrico.tagliavini, Happy.Cerberus, pierre, robert.b.miller |
Priority: | NOR | ||
Version: | 1.11.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christophe Prud'homme
2009-03-23 09:37:04 UTC
I can confirm this bug. The certificate is considered valid by Kleopatra, but KMail considers it non-valid (displays a red crossed key) and refuses to add it to an account. Is the root certificate trusted? Open Kleo, then select Not Trusted Root Certificate in the right hand pull down. If the root cert is not trusted, then go to ~/.gnupg and edit trustlist.txt Copy the finger print of the root cert into the file and append an 'S', as shown below: # Verisign 90AEA26985FF14804C434952ECE9608477AF556F S I still have that problem on 4.4.2 too. Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback. |