Just how do I get kmail to keep my password for kmail without using kwallet which I despise! I don't need some off the wall software package to remember all my passwords for me!

I want to set it up like I had it set in 4.6 where kwallet was disabled and kmail kept my incoming kmail password! I never ever put an outgoing password in for sending mail, that password I'm A OK with typing in when I want to send mail, but constant nagging to type in a password to retreive email in 4.7.4 is a real pain in my you knw where!

How to fix this terrible oversite on the developers part!

And yes for those of you wondering I do have a different password for every site I visit and have a totally different password to log into my system them any of the passwords used on the net and for kmail! I have a total of at least a dozone passwords and have no problem remembering them.

I used to be a sys admin at one time and was forced to have multiple passwords along with being forced to change all those passwords each and every month not to mention passwords could not be reused, had to be a minimum of 8 non repeating characters that had to contain at least 1 number 1 letter in caps and 1 non-alphanumeric character!

ANYONE PLEASE HELP TO FIX THIS SERIOUS ISSUE!

If I can't get it fixed I am seriously considering dumping KDE for a desktop that does NOT force me to use a password saving software package to save passwords for email to function without constantly being nagged for a password!

ALL COMPUTERS ARE ONLY AS SECURE AS THE MACHINE, AND YES THAT INCLUDES THIS IDIOTIC KWALLET WHICH CAN BE HACKED JUST AS EASILY AS ANY OTHER SOFTWARE PACKAGE!

I already reported this as a bug on 2011-08-21, thats aver 5 months ago.
Looks like none of the developers are interested in fixing this.
I abandoned kmail/kontact because of the gazillion other showstopper bugs.
I don't need a fancy, feature rich email client that cannot send or receive emails or takes 100% CPU 24/7 just to show emails.
I switched to evolution and I'm more or less happy. Not looking so good, some features are missing, but it is reliable and lets me enter passwords and saves them!
But most important, I start it monday morning and close it friday evenening without rebooting, restart, killing akonadi or doing some dbus magic like I needed to do to keep kmail working for another few hours.

Please try the following workaround: Configure KWallet to have a blank password. If KWallet has no password, then you will not be prompted.

This can be done for existing wallets by opening KWalletManager, which is usually present in your system tray if a wallet is open, then Right click on the appropriate wallet > Change password.

I tried that ~ 5 Months ago and it did not work for me.
I'm running my home dir on a NFS. Sometimes from multiple machines at the
same time. Good apps can cope with that, kwallet not. It destroyed its DB several times (along with ALL of the KDE PIM Apps).

bcooksley wrote:Please try the following workaround: Configure KWallet to have a blank password. If KWallet has no password, then you will not be prompted.

This can be done for existing wallets by opening KWalletManager, which is usually present in your system tray if a wallet is open, then Right click on the appropriate wallet > Change password.

Tried this to no avail, still promtps for a password everytime I click on check mail!
Not to mention, but I will yet another issue has shown its uggly face, for some reason everything that ends up in my spam folder is being triple and quadroopled. And at times those triple and quadroople emails manifest into hundreds of duplicate emails. Last night I checked my email and the spam folder had 350 unread messages all dupilcates of originals of marked as spam. When I checked this morning there were 30 spam emails again with multiple copies of each message marked sam.

What did the devolopers do to the KDE pims that are causing all thse problems?

I too was very annoyed by the fact that kmail needed to get the password from kwallet.
Seems kmail's resources are handled by Akonadi now. Did some fiddling around with qdbus. The following little script seems to work for me in Fedora 16. I don't know if it will work in other distros, but it's worth a try. Just replace copy & paste into your favorite text editor and replace "yourpassword" with your own password (without the quotes) , give the file a name and save it:

#! /bin/bash
qdbus org.freedesktop.DBus / StartServiceByName \
org.freedesktop.Akonadi.Control 0
sleep 10
qdbus org.freedesktop.Akonadi.Agent.akonadi_pop3_resource_0 /Settings \
org.kde.Akonadi.POP3.Settings.setUnitTestPassword "yourpassword"

Just Don't forget to make it executable. You might want to play with the sleep number a little. The idea is to give DBus time to start the required service before you give it the next command. If you have trouble, try increasing it. I just use system settings to have it startup when I log in.

Your password won't be secure. But hey, I'm just a home user and the only one on this system, so it doesn't really matter to me. I believe people should be allow to choose the level of security they require. Until the developers see the folly of making people type a password every time they check email, we will just have to work around it.
Hope this helps someone.

I'll repeat this as I have before - you do not need to enter a password to unlock your KDE password wallet if you change the wallet to have no password.

OK. I checked that out.It can not work when first setting up the pop3 account, because the system has to store the password somewhere. However if you let the wallet store it and then configure it with no password, it seems to act as you say. It stores it somewhere, I guess. Except that you are still prompted to open the wallet, but are not required to enter a password., which seems a bit silly. And now when I open the wallet configuration screen, under the access control tab, I see that the pop3 account is not listed, even though it has access to the password somehow. If it has acces to the password by other means, then why am i prompted to open the wallet? The whole thing seems a bit convoluted at this point. IMHO, the idea of a wallet system is not inherently bad, if it is implemented in an easily understandable and easily configurable way. If there is to be a centralized place for passwords then it needs to be configurable *from* that location. Should have different levels such as "always allow", "allow with password", "never allow", etc. Don't get me wrong, I'm all for security. I don't keep my paypal, or my internet banking, or *any* other password on the computer at all. They're either in my head or in my cash box under lock & key. But I'd like to keep some passwords for forum sites and such in the wallet. It just needs to be implemented better if it is to survive. Hopefully as things progress, it will be. Thanks for the help.

Next time you are requested for permission to permit the POP resource to open the Wallet, select "Always allow" instead of just "Allow" and that dialog should no longer prompt you.