Bug 132432

Summary: password prompt repeats asking even if one cancels the dialog
Product: [Applications] kmail Reporter: Sebastian Held <sebastian.held>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 1.9.4   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Sebastian Held 2006-08-15 08:18:32 UTC
Version:           1.9.4 (using KDE 3.5.4, Gentoo)
Compiler:          gcc version 3.4.6 (Gentoo Hardened 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.17-ck1-r2

My accounts are set up to look every 15 min for new mail. Now one server is in process of being restored, thus temporarily my login password is invalid.
Kmail's dialog box:
"Unable to login. Probably the password is wrong.
The server web47.merlin.rootbash.de replied:
LOGIN failed"
This dialog box only has a "OK" button.
After pressing this OK button, I am asked for my password. Now I would assume, if I press "Cancel", I am no longer bothered by this dialog, but after a few seconds this procedure starts again. Normal working is not possible.
Comment 1 Sebastian Held 2006-08-15 08:21:44 UTC
Now I've even disabled interval checking for both accounts (pop and imap) on this server, but this doesn't change anything. Both dialogs appear as before. And they are modal!
Comment 2 Sebastian Held 2006-08-15 08:27:45 UTC
I don't know, what's going on here... "Check mail on startup" is disabled, but this dialog appears shortly after starting kontact. I've also disabled "include in manual mail check" and "interval mail checking", so why kmail tries to contact the server?
Comment 3 Sebastian Held 2006-08-15 08:32:42 UTC
Now I've disabled "store POP password" and "store IMAP password". At the first startup of kontact after this change, kmail asks once for the password. Pressing "Cancel" dismissed that dialog and it no longer appears! a subsequent start of kontact doesn't ask for a password.
=> There seems to be some logic error concerning the password store feature and login failures.
Comment 4 Andreas Kling 2006-09-02 14:48:37 UTC

*** This bug has been marked as a duplicate of 109036 ***