Bug 135329 - CA certificate available in kmail standalone but not embedded in kontact
Summary: CA certificate available in kmail standalone but not embedded in kontact
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-09 10:57 UTC by Peter Eisentraut
Modified: 2015-04-12 09:42 UTC (History)
0 users

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 Peter Eisentraut 2006-10-09 10:57:08 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Debian testing/unstable Packages

I have created by own little SSL CA.  I have made and signed a certificate for a remote IMAP server and installed it.  Then I imported the CA into KDE (I just clicked on it, something asked to import it, probably kleopatra).  Then I was asked whether I want to make the certificate available to KMail; I answered yes.  And indeed, the CA certificate is available in KMail, so I don't get any questions about the certificate of the IMAP server.  But in Kontact's email component, this does not happen.  I still get asked those questions about the certificate.

Maybe this is really a deficiency in kleopatra or somewhere below there, but it manifests itself in Kontact, so I'm starting here.
Comment 1 Will Stephenson 2006-10-30 09:39:17 UTC
Hmm, why would kmail behave differently when running standalone or as part of Kontact?
Comment 2 Laurent Montel 2015-04-12 09:42:26 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.