Version: (using KDE 4.1.2) Installed from: Ubuntu Packages Here's the problem dialog: === The server failed the authenticity check (ozlabs.org). The host name did not match any of the valid hosts for this certificate The root certificate of the certificate chain is self-signed, and untrusted === I hit Continue, then: === Would you like to accept this certificate forever without being prompted? === I hit "Forever", but I still get this same dialog every time I send mail... (Side note: the word "forever" in the question above should probably be deleted)
I've had this problem too, but since some days I'm no more able to reproduce this issue in current trunk.
Same here, using KDE 4.2.0. This occurs with kmail, konqueror and akregator (In all cases, the server being accessed has a cert signed by a non-trusted CA). Perhaps the bug is in part of the generic KDE SLL infrastructure?
This bug still exists on Debian SID with experimental branch of kde-4.2.1 (kmail 1.11.1). I encountered the following: it seams that the actual certificate (the one from the mail-server) is trusted. The problem is that the corresponding CA (self-signed root-ca) is still not trusted. Maybe that's why this dialog pops up every time. When I select "Forever" the mail-server certificate gets added to the "~/.kde4/share/config/ksslcertificatemanager" - the rootca doesn't. To clarify this: root.ca (not trusted, self-signed) | \--> mail.root.ca (trusted)
Bug still exists for kde-4.2.2 Debian/SID but I think I can pinpoint this issue a bit further: it seams to only happen on hosts which use SSL for SMTP _and_ POP3. The "Forever" switch seams to work as long as I only use POP3. As soon as I send a mail (with SSL on) I get the certificate warning again. When using POP3 again I get the warning again and so on. But only in cases when I switch between POP3 and SMTP.
*** This bug has been marked as a duplicate of bug 233628 ***