[Bug 250373] New: kmail2 migration fails for cached imap

[José Matos]

https://bugs.kde.org/show_bug.cgi?id=250373

           Summary: kmail2 migration fails for cached imap
           Product: kmail2
           Version: unspecified
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: jamatos at fep.up.pt


Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

The problems I report were using the kdepim-4.4.93-2.fc13 from kde-redhat for
Fedora 13.

I have 9 dimap accounts configured in kmail. One is for my home dovecot server
where I archive my email, one is for a imap proxy for an exchange server,
several are based on google mail, and more.

The migration process did not went well overall. It worked for some server, in
particular the gmail based (although for one account only at the second try).

Even after the migration process was marked as completed kmail would not show.
The memory consumption was very high and this 4 GB RAM was trashing memory.

I waited for some time with no evident result.

Recalling kmail again would again bring the migratory program again with the
resulting of adding failed accounts in to a local archive. Since I had repeated
this procedure four times this meant that in the end I had four copies of the
failed accounts. Worse than that calling the akonadi console I was not able to
remove them, neither did I found it how to do it in kmail.

The only way to finally see kmail was to rename the ~/.kde/share/apps/kmail

kmail would show up but then the system would be very slow, with lots of memory
being used by mysql run from akonadi and with several copies of akonadi
running.

Several quirks from the process, akonadi throws several pop-ups if some 
message is not well downloaded, complaining that the named message did not
match any message on the server. This is disastrous, you can end with more than 
300 pop-ups open (357 to be exact). Clearly a pop-up to tell such a trivial
thing is not a solution, and the plasma panel does not behave nicely in this
case.

During the migration process I got funny messages like this:
Error while creating item: Unknown error. (NO Unable to write item changes 
into the database)

(Note: this is direct copy from the error).

The system was unusable at the end so I had to downgrade to the previous 
version (4.4.5).

Due to all the work that was done to insure that a downgrade works I had no 
problem reverting to the previous version.
 had to reset the ~/.local/share/akonadi directory because the previous one had
14 GB, and akonadi would take long time to start. For reference I get here:
$ du -sh /home/jamatos/.kde/share/apps/kmail                                    
12G     /home/jamatos/.kde/share/apps/kmail                                     

Reproducible: Always

Steps to Reproduce:
migrate from kmail1 to kmail2

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.