Bug 288868

Summary: Importing old kmail maildir either crashes or the result is unuseable slow
Product: [Applications] kmail2 Reporter: Michael Gerdau <mgd>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: dan.mera, gdr-kde, mgd, montel
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Michael Gerdau 2011-12-13 07:44:45 UTC
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

On an working openSUSE 11.4 I did a systemupgrade to 12.1. This resulted in a catastrophe due to a completely broken migration tool from kmail to kmail2.

After several days of unsuccessful tinkering and reading lots of inet forums about people having exactly the same probs as I had I eventually decided to drop on this and do a fresh install. The rest deals with the problems I encountered there.


On a freshly installed openSUSE 12.1 (stock version; KDE 4.7.2) I had tried to import my old kmail maildir tree with all my old msgs. These are several 100k msgs and about 2-3 GB in size.

First try the importer "vanished" for no apparent reason after being about 2/3 through. Selecting some of the imported folders to check whether they had been properly imported took ages - I had to wait several 10s of seconds (didn't measure the exact time - it was way too long to be workable; I'm on a RAID with a recent quadcore processor and 16GB of RAM).

I then tried to reimport, checking "ignore dublicated msgs". This time it got through. However the result was unworkably slow. Clicking on a mailfolder with just a handful of msgs resulted in heavy diskload and ages of waiting.

I then decided to delete the whole akonadi DB stuff and restart from scratch. Basically the result was unchanged. After some inet research I decided to upgrade my KDE to the current stable released branch as of openSUSE buildservice which currently is KDE 4.7.4.

I removed all kmail2 and akonadi configurations and started from scratch - or so I think.

The import process still does not go though but crashes somewhere midway. Only improvement is that the result seems to be reasonably fast in that now after a click on a mailfolder the response is acceptably fast.

I then tried to repeat the crashed import (ignore dublicates checked) which just stopped working for no apparent reason after a short time - the importer window just "hang".

In light of all the other problems I find it almost neglectable that all information about mails being read/unread/marked are completely lost during import.

Reproducible: Always

Steps to Reproduce:
see above

Actual Results:  
The import does either crash, hang or the result is unacceptably slow.

Expected Results:  
The import should just not crash and import all messages and the result should be workable in that it should be at least as fast as it was with the previous kmail (without akonadi)

The whole import process takes roughly a day and severely hinders other work on the system, not to speak about email being a core component of my daily workflow.

From my perspective the whole akonadi/kmail2 combo is not ready for primetime.

The migration tool is alpha or early beta at most. The importer IMO has definitely beta status.

I wonder how kmail2 together with akonadi made it into the KDE stable branch.
Comment 1 Laurent Montel 2011-12-13 08:07:12 UTC
Backtrace ?
Comment 2 Michael Gerdau 2011-12-13 08:16:23 UTC
The importer windows just disappears, no backtrace selectable. I also don't have debug symbols installed. I'd be willing to install them, should that help debugging the stuff.

On the other hand the problems I'm experiencing and that according to many posts in inet forums other have as well I wonder whether this really worked in any reallife scenario.
Comment 3 Gulraj Rijhwani 2012-02-20 13:25:41 UTC
kmail2 should not be out there as "stable". It clearly doesn't even recognise "mbox" format mail.
Comment 4 Denis Kurz 2016-09-24 18:15:54 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 5 Denis Kurz 2017-01-07 22:27:31 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.