Bug 283345

Summary: sent, drafts, templates and trash folders configs scrambled surreptitiously
Product: [Applications] kmail2 Reporter: Cristian Tibirna <tibirna>
Component: config dialogAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: major CC: kdenis
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Cristian Tibirna 2011-10-04 20:22:11 UTC
Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

Given the incredible instability of KMail2 with akonadi, I can't even begin to guess what triggered the behavior described below. But it is critical and a huge showstopper

I have a kmail2 new configuration (created anew on empty  .kde config dir) with 4 imap servers and a local folder. For all the imap servers I configured the trash folder location upon account config creation. I also created a number of identities (roughly associated one to one with the imap configs) and I configured sent, draft and template folders for each identity.

All of a sudden, after 2 days of use of kmail2, after having to restart akonadi in order to unstuck a non-displaying message from one of the imap servers, I discovered that all my folder configs were utterly scrambled. Not deleted, but scrambled. That meant that my sent mail from one identity was saved in a randomly chosen folder from another imap server than the one associated with the identity.

This is a huge showstopper, and a huge security hole (surreptitiously saving private emails on the inappropriate imap server is a big no).

Reproducible: Didn't try

Steps to Reproduce:
I don't even dare to think this will happen again on my current config.

I'm not sure what triggers the behavior. I guess it is akonadi that becomes utterly confused about the way it identifies items/folders and saves the wrong state to the config database.


Expected Results:  
Folder configurations (especially for sent and trash) should be preserved religiously.
Comment 1 Denis Kurz 2016-09-24 18:17:22 UTC
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.
Comment 2 Cristian Tibirna 2016-10-11 01:01:55 UTC
I didn't see the described behaviour for a long time. I guess this could be closed. Sorry for not having closed it myself when appropriate.