KDE 3.4 / KMail 1.8 Wallet Hell and Authorization Failures
Hi, I upgraded to the KDE 3.4 supplementary packages. I'm running a SuSE 9.1 that was upgraded along the way with all the supplementary KDE releases, meaning just prior to this I was running KDE 3.3 and KMail 1.7. Up til now, everything was working swimmingly. Since the upgrade, KMail is badgering me to use the wallet contraption to store my passwords. I don't want to do this. How can I get it to leave me alone and just store the passwords obfuscated in its settings file the way it has all along? Secondly, some of my mail servers require an authentication or security mode that KMail no longer seems to be able to supply. I'm getting alerts when transferring mail with some servers that state: "Authorization failed, An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found authentication not supported" [ By the way, everything between those quote marks is exactly what's in the alert I see, bad spelling and poor punctuation included. ] Can anybody tell me what's up and how I can fix it? I have both logged out and back in and rebooted and these symptoms persist. Thanks. Randall Schulz
Since the upgrade, KMail is badgering me to use the wallet contraption to store my passwords. I don't want to do this. How can I get it to leave me alone and just store the passwords obfuscated in its settings file the way it has all along?
I had the same problem. I couldn't track down exactly what happend since I don't remember my kwallet setup before the upgrade but here is what I did to fix this behavior. It seems that kwallet sets up a local wallet (which I think I deleted in the setup before the upgrade) and makes it default for local passwords. The kmail password gets stored in the kdewallet but it seems to be treated as a local password so whenever you run kmail it looks into the localwallet, does not find the password and gets confused. I deleted the localwallet (which was empty on my machine) and disabled the different wallet option for local passwords. To do this right-click on the wallet icon in the system tray and select configure wallet, then uncheck the "Different wallet for local passwords". In Access Control make sure that kmail has an "Always Allow" policy and that's it. If you leftclick on the wallet icon you can delete the localwallet if you don't use it. By the way, 3.4 seems much faster and nicer. Brana
"Authorization failed, An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found authentication not supported"
Had the same problem. You have to install in YAST the other cyrus rpms, i.e. cyrus-sasl, -crammd5, - digestmd5, - plain, -gssapi. Then kmail is working again. Udo
On Friday 18 March 2005 02:14, udo wrote:
You have to install in YAST the other cyrus rpms, i.e. cyrus-sasl, -crammd5, - digestmd5, - plain, -gssapi.
I just updated to KDE 3.4, and this message was a big help. Thank you. I only pulled out half my hair before I found it. Now, if we could just figure out a way to have KMail mark messages as "Important" ... BEFORE we need them... :-) Kevin
Hi! Am Freitag, 18. März 2005 02:59 schrieb Randall R Schulz:
Since the upgrade, KMail is badgering me to use the wallet contraption to store my passwords. I don't want to do this. How can I get it to leave me alone and just store the passwords obfuscated in its settings file the way it has all along?
As kwallet is considered safer than storing it in a config file, the kmail devels decided to take the safer option. I am not sure, if there is a way to store the password in the file anymore, there was in beta1, but they might have removed it due to it being too confusing to have the option to chose a less safe storage. If you are looking for an answer, you might try #kontact on freenode, or subscribe to the kmail-devel list on www.kde.org.
Secondly, some of my mail servers require an authentication or security mode that KMail no longer seems to be able to supply. I'm getting alerts when transferring mail with some servers that state:
You should try to install the remaining SASL-packages, SuSE missed those dependencies. Sven
Sven, On Friday 18 March 2005 00:51, Sven Burmeister wrote:
Hi!
Am Freitag, 18. März 2005 02:59 schrieb Randall R Schulz:
Since the upgrade, KMail is badgering me to use the wallet contraption to store my passwords. I don't want to do this. How can I get it to leave me alone and just store the passwords obfuscated in its settings file the way it has all along?
As kwallet is considered safer than storing it in a config file, the kmail devels decided to take the safer option. I am not sure, if there is a way to store the password in the file anymore, there was in beta1, but they might have removed it due to it being too confusing to have the option to chose a less safe storage. If you are looking for an answer, you might try #kontact on freenode, or subscribe to the kmail-devel list on www.kde.org.
I'm sure it is, probably. I find it inconvenient, and I'm not sure how I'm going to deal with making sure mail gets retrieved when I'm away from home for extended periods and I don't want my mail to pile up at the various servers. I'll admit there's one upshot I hadn't originally considered. I have one password stored in my KMail configuration that I'd forgotten! Now I know what it is. Whew!
Secondly, some of my mail servers require an authentication or security mode that KMail no longer seems to be able to supply. I'm getting alerts when transferring mail with some servers that state:
You should try to install the remaining SASL-packages, SuSE missed those dependencies.
Damn their oily hides! (-- C. M. Burns) Udo said the same. Doing so fixed the problem.
Sven
Randall Schulz
Have you tried playing with the options in Control Centre/Security & Privacy/KDE wallet? Ian On Friday 18 Mar 2005 14:40, Randall R Schulz wrote:
Sven,
On Friday 18 March 2005 00:51, Sven Burmeister wrote:
Hi!
Am Freitag, 18. März 2005 02:59 schrieb Randall R Schulz:
Since the upgrade, KMail is badgering me to use the wallet contraption to store my passwords. I don't want to do this. How can I get it to leave me alone and just store the passwords obfuscated in its settings file the way it has all along?
As kwallet is considered safer than storing it in a config file, the kmail devels decided to take the safer option. I am not sure, if there is a way to store the password in the file anymore, there was in beta1, but they might have removed it due to it being too confusing to have the option to chose a less safe storage. If you are looking for an answer, you might try #kontact on freenode, or subscribe to the kmail-devel list on www.kde.org.
I'm sure it is, probably. I find it inconvenient, and I'm not sure how I'm going to deal with making sure mail gets retrieved when I'm away from home for extended periods and I don't want my mail to pile up at the various servers.
I'll admit there's one upshot I hadn't originally considered. I have one password stored in my KMail configuration that I'd forgotten! Now I know what it is. Whew!
Secondly, some of my mail servers require an authentication or security mode that KMail no longer seems to be able to supply. I'm getting alerts when transferring mail with some servers that state:
You should try to install the remaining SASL-packages, SuSE missed those dependencies.
Damn their oily hides! (-- C. M. Burns)
Udo said the same. Doing so fixed the problem.
Sven
Randall Schulz
Ian, On Sunday 27 March 2005 14:13, ianseeks wrote:
Have you tried playing with the options in Control Centre/Security & Privacy/KDE wallet?
Oh my, yes. See my posting today where I explained my "solution" to another afflictee of this disorder. It was in SuSE-Linux-E under the subject thread "kmail & kwallet". Randall Schulz
participants (6)
-
Branimir Vasilic -
elefino -
ianseeks -
Randall R Schulz -
Sven Burmeister -
udo