Bug 285242

Summary:	reinstallation procedure of kmail
Product:	[Applications] kmail2	Reporter:	Daniel Moyne <daniel.moyne>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	Martin
Priority:	NOR
Version First Reported In:	1.99.0
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Daniel Moyne 2011-10-29 10:03:33 UTC

Version:           1.99.0 (using KDE 4.7.2) 
OS:                Linux

Please propose a procedure to reinstall properly kmail2 ; something like :
- saving data in archive,
- clearing all folder architecture,
- clearing all identities,
- clearing all accounts,
- reinstalling the minimum folder structure in the proper language,
- reinstalling identities,
- reinstalling accounts,
- migration of data in a temporary folder in the new folder architecture for the user to move those internally within the new structure.

This whould at least demonstrate tha you have full control of data location and data strucure of kmail2 for users like me in trouble due to the new changes ; after this you may start to think to redevelop kmail not around akonadi + msql + nepomuk but from what a kmail client is supposed to propose as features for users ; for example there is no justification for a filtering process when opening kmail ; filtering is supposed to take place immediately when either sending or receiving mails ; when you change the definition of a filter or create a new one the user is not supposed to loose control of the application for a while as there no logics in those except for some obscure akonadi specifications ; etc ...

Reproducible: Didn't try


Actual Results:  
an application that shows regression

Expected Results:  
an application where the user has full control of its valuable data not supposed to be mishandled as is now

OS: Linux (x86_64) release 3.0.0-12-generic
Compiler: gcc

Comment 1 Martin Steigerwald 2015-09-11 10:00:47 UTC

Hello Daniel. Thank you for your report and sorry for taking long time to answer. As I think this is mostly a duplicate of your other bug I am marking it as such.

Also the locations where Akonadi stores data are clearly known.

For now I recommend to always backup the following at least:

- ~/.local/share/akonadi
- Data from the resources:
  - Maildir: ~/.local/share/local-mail or wherever you pointed it to
  - Contacts: ~/.local/share/contacts or wherever you pointed it to
  - Calender: ~/.kde/share/apps/kabc/std.vcf (I think) or wherever you pointed it to
  - see ~/.kde/share/config/akonadi* for the locations the resources point to for example:

martin@merkaba:~/.kde/share/config> cat akonadi_maildir_resource_0rc
[General]
Path[$e]=$HOME/.local/share/local-mail
TopLevelIsContainer=true

- ~/.config/akonadi
- ~/.kde/share/config/akonadi*
- Configuration of the apps

In other to start new from scratch you would delete these.

It is known to the dev team that things are spread around quite a bit. And there are discussions, ideas to simply / unify this. This may take some more time tough. And as usual no promises.

*** This bug has been marked as a duplicate of bug 284252 ***