I receive the following message when I send an email with one of my email addresses:
The server certificate failed the authenticity test
The certificate is good to 2016, but something else must trigger this dialog. I don't know how the code logic inspects certificates to send those dialogs. Perhaps I have something configured incorrectly.
A second dialog prompts:
Would you like to accept this certificate forever without being prompted?
I select Forever but the next time I send an email I see the same dialogs, which implies kmail is not saving that option correctly.
Can anybody confirm this behavior? I don't see anything obvious in the bug tracker.
Darrell
On Tuesday 23 of October 2012 21:18:06 Darrell Anderson wrote:
I receive the following message when I send an email with one of my email addresses:
The server certificate failed the authenticity test
The certificate is good to 2016, but something else must trigger this dialog. I don't know how the code logic inspects certificates to send those dialogs. Perhaps I have something configured incorrectly.
A second dialog prompts:
Would you like to accept this certificate forever without being prompted?
I select Forever but the next time I send an email I see the same dialogs, which implies kmail is not saving that option correctly.
Can anybody confirm this behavior? I don't see anything obvious in the bug tracker.
Darrell
When you open the window with information about the certificate, are there reasons for not accepting the certificate?
Slavek --
When you open the window with information about the certificate, are there reasons for not accepting the certificate?
I did not notice anything when I looked, but I could have missed something.
I will read more carefully next time.
Darrell
When you open the window with information about the certificate, are there reasons for not accepting the certificate?
Apparently there is some kind of timeout period as I was unable to retest this problem for several hours.
Yes, the details dialog says "certificate signing authority is unknown or invalid."
I don't know how to fix, although obtaining an updated certificate makes sense. I haven't figured out how to do that as I believe kmail is supposed to fetch the certificate automatically when using SSL. Therefore on a whim, I deleted $HOME/.gnupg.
Regardless, there is a bug here. Selecting the Forever button should resolve the problem. I found this bug report and comment:
https://bugs.kde.org/show_bug.cgi?id=116723#c15
The comment implies a patch but I haven't a clue where to start looking. Only the date of the comments hints at about when the patch might have been pushed. The comment does not provide help about where the patch was applied.
I want to file a bug report against the Forever button failure, but I'd like to have a clue to where the root cause lies. :)
Darrell
-
Darrell Anderson -
Slávek Banko