Bug 187913 - kmail/kleopatra selecting s/mime certificates and smtp authentification failures
Summary: kmail/kleopatra selecting s/mime certificates and smtp authentification failures
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.11.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-23 09:37 UTC by Christophe Prud'homme
Modified: 2015-04-12 09:52 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Prud'homme 2009-03-23 09:37:04 UTC
Version:           1.11.1 (using 4.2.1 (KDE 4.2.1), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.26-1-amd64

When I try to select an s/mime certificate imported in kleopatra
the selection window shows me two certificates (which is OK) but does not allow me to select any of them. On the left side of the selection box there are two little icons which are red-crossed when I select the corresponding certificate.

I cannot then sign my messages and send emails through our smtp server 

what kind of information would be useful for you ?

The certificates are ok and I already use them in konqueror for accessing our intranet using firefox. However it fails for konqueror. I will certainly file a bug for konqueror too.
Comment 1 Simon Toth 2009-05-01 17:00:55 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.
Comment 2 Robert B Miller 2009-11-28 06:03:04 UTC
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
Comment 3 Pierre Graber 2010-04-05 23:04:32 UTC
I still have that problem on 4.4.2 too.
Comment 4 Laurent Montel 2015-04-12 09:52:10 UTC
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.