So there I am sending an email, and realize right after I click Send that I forgot to include some important tidbit. Luckily I haven't send an email in more than 10 minutes, so KWallet pops up to unlock the password to my SMTP provider. So I click Cancel, and the send is aborted. "GREAT SUCCESS" :) Unfortunately, from then on every time KMail would have accessed KWallet for passwords (i.e. POP3, further SMTP) it prompts me to enter the password manually. But the password is there in the wallet, I just need to unlock it, but KMail won't ask me to :( Expected behavior is that if the entry is available in the Wallet that KMail attempt to use it even if it was previously canceled. Now this could be a KWallet bug I suppose (in that it doesn't return a "Canceled by user" error when calling openWallet() or because KWallet itself is caching the status of openWallet()). If so, my humblest apologies oh PIMsters. :)
I think the problem is, as long as the wallet is closed, kmail can not now which password are stored there
*** Bug 250933 has been marked as a duplicate of this bug. ***
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.