Version: 1.11.1 (using KDE 4.2.1) OS: Linux Installed from: Debian testing/unstable Packages The bug might be related to interaction between kmail and kwallet (I HATE kwallet because the security it offers never exceeds the problem it causes). First I want to clarify this: my debian (testing + experimental) suffers an accidental crash due to the unstable wifi driver for my wireless card. I am pretty sure about this, since it never happens when I am using the cable network. Neither madwifi nor ath5k driver will work with crash. So I have to tolerate it. The crash happens when I am using the network. Now I talk about the bug. Today my OS crashed just when I was sending an email and checking all email accounts. After rebooting, I can still send emails but I can't check my emails. So I checked the configuration of kmail. Well, I found all my receiving accounts gone! Luckily my sending accounts are still there. Then in desperation, I checked the directory ~/.kde4/apps/kmail/, where I find several ``configuration files'' are still there, but encrypted I guess, e.g. sigmastudio@gmail.com:pop.gmail.com:995. I don't know how I can decrypt these configuration files or inform my kmail program about their existence. I remember kwallet caused a similar problem a long time ago. That is: if I do not enter the password when I quit kmail/kontact without opening kwallet (the weird thing is I don't understand why kwallet asks for password then), kmail will lose all the passwords for my accounts when I restart it (the account exists but kmail asks for password for each account). I have to add them manually one by one afterwards. So I think this ``bug'' can be reproduced in the following way, set up a few receiving accounts (so it takes a while when you check), check them and shut down your computer intensionally. Then you will lose these receiving accounts. I think it might be caused by kwallet. The kmail must ask kwallet for configurations and the kwallet should always keep the configurations intact even when it is providing them to kmail. In this way, unforeseeable crashes will not disturb their interaction afterwards. But I am not very clear about what kwallet does :-(
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.