1 |
> On 4.9.3 you are still experiencing something similar. Hmmm. Indicates |
2 |
> to me a high probability of a systemic problem with the projects |
3 |
> approach, something that is unlikely to ever get really fixed. In my |
4 |
> opinion kdepim2 is vastly over-engineered and an attempt to solve a |
5 |
> problem that does not actually exist. I recommend you use a different |
6 |
> mail app. |
7 |
|
8 |
After an indescribable amount of pain and time wasted I was able to regain |
9 |
control over my mail. |
10 |
|
11 |
I recently migrated a kmail used nearly for ten years to the latest kmail2. |
12 |
Migration took around a month of struggle. |
13 |
|
14 |
It's mandatory to have nepomuk+akonadi running (I configured file indexing to |
15 |
run only on a folder containing a few files), it has to be checked for mail |
16 |
too. |
17 |
|
18 |
In the migration you'll lose your filters, your profiles, and the flag of the |
19 |
mail will be randomly changed (thousands of read mail will come up unread, |
20 |
"important" flag will be lost... And so on). |
21 |
|
22 |
If you try to reimport (after deleting the akonadi database as somewhere |
23 |
advised) the mail from ~/Mail you'll discover the the import tool is unable to |
24 |
handle maildir (or mailbox, I don't remember) format. If, like me, you used |
25 |
kmail for several years, then not all mail folders have the same format, given |
26 |
the fact that the default was changed during time. |
27 |
|
28 |
Beware also that full text indexing is on per default for every mail folder |
29 |
created. So, as soon as I imported a mail folder, I deselected this option by |
30 |
hand (under folder properties -> maintenance). |
31 |
|
32 |
So, this is the step-by-step guide to migrate to kmail2: |
33 |
|
34 |
* backup your ~ folder, especially ~/Mail, ~/.config and ~/.kde4 |
35 |
|
36 |
* make sure akonadi, nepomuk & co are running (with the command "akonadictl |
37 |
status" for example). |
38 |
|
39 |
* look carefully in ~/.xsession-errors if some errors appear related to |
40 |
akonadi, nepomuk, mysql, soprano, virtuoso... Do not migrate if you see any |
41 |
errors, fix them first. |
42 |
|
43 |
for example the following error is guaranteed to slowly and painfully drain |
44 |
all of your setup and mail to a black hole: |
45 |
|
46 |
Soprano: "Could not connect to server at /tmp/ksocket-sko/nepomuk-socket (No |
47 |
such file or directory)" |
48 |
|
49 |
* Delete everything no more necessary (mail messages, old accounts...). |
50 |
|
51 |
* Archive every folder you want to migrate and delete them from the old client |
52 |
|
53 |
* Take note of your filters, especially if some of them makes elaborate |
54 |
operations, mail account settings, profile preferences... |
55 |
|
56 |
* backup again, just to be sure |
57 |
|
58 |
* upgrade kmail, and start kmail2, let it run for the time needed (one night |
59 |
or more is normal) until the I/O and CPU load are back to a reasonable level |
60 |
|
61 |
* reimport archived folder (and disable for each one full text indexing before |
62 |
is started) |
63 |
|
64 |
* reconfigure filters, accounts, profiles... |
65 |
|
66 |
* backup for the last time |
67 |
|
68 |
Hoping to save someone else the waste of time I went through. |
69 |
|
70 |
F. Talamona |