https://bugs.kde.org/show_bug.cgi?id=260265
--- Comment #1 from Nassos Kourentas <nassos kourentas com> 2010-12-17 15:26:47 --- After further investigation and googling around, I found a _workaround_ of the reported issue: It appears that a modification concerning the authentication mechanism (that is related with KWallet) resulted to the problem: Once I deleted the respective Akonadi resource and recreated it (using the exact values and credentials), the problem seized to exist. But, as far as I am concerned, such a requirement (to delete and recreate the respective POP3 Akonadi resource) to rectify the issue, should _not_ be an acceptable solution... The following comment might be out of topic, but it's worth reporting: Furthermore, I would like to mention the fact that, in the event of connecting with a server whose certificate is not valid/safe (The Akonadi resourse generates a warning that the server failed the authenticity check), leads to the user taking the responsibility upon herself whether to accept the certificate (either for the current session, or forever), or decline it altogether... If the user chooses to accept the provided certificate _forever_, the akonadi resource will periodically (each and every time it is invoked that is) keep on complaining about the very same certificate issue, thus, _ignoring_ the specific user request for the system to accept the (less safe) certificate! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs