It seems that the akonadi imap resource tries to log in into my mailserver without waiting for kwallet to open (for example when I start kontact, leave the computer and come back after a few minutes). As it does not have the password, but tries multiple times, I finally get blocked from accessing my email account for a while, which is bothersome. It ao shows a "multiple wrong login" error. The funny thing is, I have to other imap accounts (one on the same server) that don't show this behaviour. But I recently changed the password on this specific account. The password in kwallet is the new, correct one, but I wonder whether kmail has stored the old (wrong) one somewhere else? Reproducible: Always Steps to Reproduce: 1. Start kontact/kmail 2. do not open kwallet for a while 3. Actual Results: One account shows "login blocked because of too many failed login attempts" error, other accounts are fine Expected Results: It shouldn't try to login without waiting for kwallet to open
Additional information: I actually have several akonadi resources connected to the same server and the same login information: an Imap resource (already mentioned) a Caldav resource with several caldav and carddav collections a ldap addressbook resource and an ical resource for tasks (caldav tasks support with this server doesn't work) So the error could lie in any of those resources, although the error message i normally get is with the imap resource. Additionally I have two more resources connecting to the same server, but with different credentials (another user account). Anything I can do to clarify what's happening? I have akonadiconsole installed, should I enable the debugger and then try to trigger this behaviour?
The IMAP resource has a new maintainer, reassigning to him.
Workaround: Open kwallet cancel all akonadi requests that are not for opening kwallet, e.g. manual password requests for accounts open akonadiconsole You will find some resource cannot connect to kwallet - right-click and restart those. Same for resources that show the not-connected - icon. Finished (it would still be better to not have to do that every time I'm not in front of my computer when it starts up...)
*** This bug has been marked as a duplicate of bug 298954 ***