Bug 266453 - Akonadi keeps asking about an SSL certificate it knows should be accepted
Summary: Akonadi keeps asking about an SSL certificate it knows should be accepted
Status: RESOLVED DUPLICATE of bug 233628
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 1.5.0
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Kevin Ottens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-16 14:15 UTC by Bernhard Rosenkraenzer
Modified: 2011-02-16 14:33 UTC (History)
2 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 Bernhard Rosenkraenzer 2011-02-16 14:15:31 UTC
Version:           1.5.0 (using KDE 4.6.0) 
OS:                Linux

Not 100% sure if this is an Akonadi or a kio-ssl issue...

I've configured kmail to use an SSL IMAP server with a bad certificate.
Akonadi (correctly) showed a dialog saying

The server failed the authenticity check (mail.XXXXX.ch). The certificate does not apply to the given host. The certificate is not signed by any trusted certificate authority.

(Both are expected, the server was running an out-of-the-box dovecot installation including its sample "imap.example.com" certificate).

I told Akonadi to accept it by clicking "Continue", and in the dialog that followed ("Would you like to accept this certificate forever without being prompted?"), "Forever".

However, the "The server failed the authenticity check (mail.XXXXX.ch)." dialog keeps popping up occasionally (even when kmail isn't running).

Reproducible: Always

Steps to Reproduce:
1. Set up an IMAP server with a bad SSL certificate
2. Connect to it with kmail
3. Confirm you want to accept the invalid certificate forever
4. Wait

Actual Results:  
Keeps prompting about the certificate several times a day

Expected Results:  
Warnings about the certificate go away

I know I should fix the certificate on the imap server instead ;)
Comment 1 Christophe Marin 2011-02-16 14:33:22 UTC

*** This bug has been marked as a duplicate of bug 233628 ***