https://bugs.kde.org/show_bug.cgi?id=478474

Marc Joliet <mar...@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mar...@gmx.de

--- Comment #3 from Marc Joliet <mar...@gmx.de> ---
This hit me, too.  The key difference to the reporter is that I see this with a
pre-existing account, and only *after* upgrading to Plasma 6 and Gear 24.02
(OpenSuse TW).  The full entry in my user journal is:

org.kde.pim.kmanagersieve: "session1" No job for reporting this error message!
"Authorization failed, Authentifizierung fehlgeschlagen.\nHöchstwahrscheinlich
ist das Passwort falsch.\nDie Serverantwort lautet:\nNO \"Authentication fa
iled.\" authentication not supported" host "[REDACTED]" error -1

(The German bits are: "Authentication failed", "Most likely the password is
wrong", and "The server response is:".  This is most likely from me cancelling
or leaving the password field empty out of frustration.)

Double-checking, I also have several log entries that looks like this:

org.kde.pim.kmanagersieve: "session1" No job for reporting this error message!
"Authorization failed, SASL(0): successful result:  authentication not
supported" host "barry" error -1

I tried things out and those log entries come from cancelling the password
dialog (I also get an error prompt showing it).

I tried two things to get rid of the password prompts:

1.) Simply turn off sieve on the offending IMAP server.
2.) First uncheck "Reuse host login configuration", save settings, restart
KMail(?), *then* turn off sieve.

Of those two only the second option actually got rid of the password prompts. 
I also deleted the sieve password from KWallet.  Even so, I just had an
instance of starting KMail where it asked me for the password again.  Then I
quit and started it again, and this time no password prompt :-/ .  So far
that's one third of launches showing a password prompt.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to