Bug 120660 - unable to get rid of password dialog when having a sasl auth method configured that the server not supports
Summary: unable to get rid of password dialog when having a sasl auth method configure...
Status: RESOLVED DUPLICATE of bug 93199
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-23 15:53 UTC by Sebastian Reitenbach
Modified: 2007-09-14 12:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Reitenbach 2006-01-23 15:53:35 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

I fiddled a bit around with the smtp auth configuration in kmail and found the following odd behaviour:

I configured the smtp auth method to use to cram-md5, sth. the server does not understand. And yes, I got the warning telling me the server does not support this method, but I ignored and went on. Then writing a mail and hitting the send button, kmail presents me the password dialog for the smtp auth mechanism. I enter sth., then kmail complains correctly that the server does not understand the cram-md5 mechanism:

The authentication method CRAM-MD5 is not supported by the server.

And I can click the OK button. Now the bug happens:

The window, asking for the password for sending comes up again.
whatever I enter therer, however i try to close it, the above mentioned error message comes again. There it also does not matter what i click to close the window, e.g. the ok button or the cross in the upper right corner to close the window. After it is closed the authorization dialog comes back again.

expected behaviour:
after the error message, the login dialog shall not appear a second time. The user shall be able to reconfigure kmail and then try again.
now my workaround is to remove the sending account from kmailrc.
Comment 1 Sebastian Reitenbach 2006-01-23 16:05:36 UTC
also after killing and restarting kmail, kmail still hangs in this infinite loop.
Comment 2 Kern Sibbald 2006-06-03 11:09:24 UTC
I found the same problem as this, but in my case, it was because kmail crashed for some reason, and that apparently corrupted the information about my mail account.  Then when I restarted Kontact (and thus Kmail), I got a dialog:

Need to supply a user name and password to access this mailbox

After giving the correct information, I got:

Unable to authenticate via PLAIN server replied SASL(-4) no mechanism available: No worthy mechs found

Then back to the previous dialog box, over and over again, with no possibility to access the configuration because these dialogs are modal.  After *much* hair pulling, I finally killed Kontact and restarted it, and before attempting to enter any IMAP mail box, I was able to delete my old configuration, and create a new IMAP configuration, kill Kontact again, and restart it, at which point it worked.  Any time I attempted to access an IMAP account, the infinite loop started again.

I consider this a catastrophic high priority bug. Any non-experienced user is going to be totally blocked.

I suspect that kmail is way overly fragile during shutdown especially in unusual situations, and not conservative enough in startup to correct such problems.
Comment 3 Marcelo Bartsch 2006-06-17 15:47:47 UTC
I got the same behavior here too, KDE 3.5.2 , compiled in Gentoo Linux, and yes is really annoying... 
Comment 4 Robert Marmorstein 2006-07-20 23:45:39 UTC
I also have this behavior (KDE 3.5.3, Gentoo).  When clicking the "cancel" button I get back into the "dialog loop."  This bug is a complete showstopper for me (and probably for most users).  If this can be marked "critical", it ought to be. :-)
Comment 5 Frederic Heem 2006-08-22 14:13:04 UTC
Similar problem with Kmail 1.9.4 when the smtp password is wrong, the authentication always shows up again, even when clicking on Cancel.
 
Comment 6 Bram Schoenmakers 2007-03-11 00:28:01 UTC

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