When sending a mail the first time after akonadi/kmail startup I get asked to enter my SMTP password. When I enter the wrong password, sending the message of cource fails. But instead of asking me again for another password, kmail tries again and again with the first password and keeps telling me that the SMTP server would not support PLAIN Auth, which ir wrong. (I use PLAIN Auth via SSL on submission port 587) Reproducible: Always Steps to Reproduce: 1. Have a SMTP Server that requires auth and supports PLAIN auth via submission port 587 using SSL (mayb that error happens with other setups as well, I didi not test) 2. Send a mail so that you will be asked for the password 3. enter a wrong password, you will noct be asked again Actual Results: kmail keeps trying to send the mail using wrong password Expected Results: should correctly detect that the password was wrong and ask the user again. What is a bit strange here for some time now, which I should mention: I have enabled "Save password" anywhere so kmail/akonadi should remember my SMTP password in kwallet, but in fact it will always ask me the first time after akonadi startup. This is not the case for my IMAP resources, there it always uses the saved password...
Any news on this? Its really a PITA if you mistype your SMTP password when sending a mail. Kmail will keep trying to use th wrong password instead of asking the user again. -Marc
It's also a fault that the error message is misleading. Kmail says: > Failed to transport message. Your SMTP server does not support PLAIN. Choose a different authentication method. Fortunately, in this case my SMTP server is more informative. The message continues: > "The server responded: "5.7.0 Incorrect username or password." This bug goes back to kmail1 (see bug 120661, reported over seven years ago).
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.