I've tried kmail2 several times now, but every time it was a failure - I have just too big IMAP-accounts or smth. After I'd realized I still need KDE PIM 4.4, I just downgraded and continued to use "old" kmail in KDE 4.5.

As new betas come out, I'd like to try new KDE PIM again, but I think it would be wise to first wipe all the configuration and data that has been created by previous kmail2 migrations etc. How could I do that?

atrox wrote:I've tried kmail2 several times now, but every time it was a failure - I have just too big IMAP-accounts or smth. After I'd realized I still need KDE PIM 4.4, I just downgraded and continued to use "old" kmail in KDE 4.5.

As new betas come out, I'd like to try new KDE PIM again, but I think it would be wise to first wipe all the configuration and data that has been created by previous kmail2 migrations etc. How could I do that?

The configs should be in $HOME/.kde4/share/config/$APPNAME

You can backup or just delete them

Regards

As new KDE PIM converts my accounts to Akonadi store or smth, should I also delete something (data and/or config) from there too?

Akonadi adds your data to a database - it doesn't touch the actual data, so you don't need to do anything about that. As Damnshock said, just renaming $HOME/.kde4/share/config/$APPNAME to $HOME/.kde4/share/config/$APPNAME_old, or deleting the directory, should be sufficient. (Personally I always feel safer with a rename, but the choice is yours.)

annew wrote:Akonadi adds your data to a database - it doesn't touch the actual data, so you don't need to do anything about that.

Duh.. of course it doesn't touch my actual data. I meant the data added to Akonadi database.

atrox wrote:

annew wrote:Akonadi adds your data to a database - it doesn't touch the actual data, so you don't need to do anything about that.

Duh.. of course it doesn't touch my actual data. I meant the data added to Akonadi database.

./kde4/share/config/akonadi*
./config/akonadi/

That's it

Regards

Damnshock wrote:

atrox wrote:

annew wrote:Akonadi adds your data to a database - it doesn't touch the actual data, so you don't need to do anything about that.

Duh.. of course it doesn't touch my actual data. I meant the data added to Akonadi database.

./kde4/share/config/akonadi*
./config/akonadi/

That's it

Regards

Um.. are you sure that configuration (not data) may be something that would bother new migration? Just wiping out the whole Akonadi configuration seems a bit odd too - I'd lose my settings from KDE 4.5 this way.

Anyway.. I'm not asking where is Akonadi data or configuration, but rather that can any of these become a problem when starting a new migration. If no, it's cool

atrox wrote:Um.. are you sure that configuration (not data) may be something that would bother new migration? Just wiping out the whole Akonadi configuration seems a bit odd too - I'd lose my settings from KDE 4.5 this way.

Anyway.. I'm not asking where is Akonadi data or configuration, but rather that can any of these become a problem when starting a new migration. If no, it's cool

I had no problem with the transition to the Akonadi system

If you have concerns, do as annew said: make a backup.

Or even better: try it with a new different user

Regards

If you just want to test KMail2 pre-release without any migration, just run it with a different user account

No risk for your main user setup, no interference with old config.

Cheers,
_