On Donnerstag, 26. Dezember 2013, 14:02:13 Alan McKinnon wrote:
> On 25/12/2013 16:19, Mick wrote:
> +1
>
> I ran into this too in the kde-4.4 era (when kmail2 was showing first
> signs of being releasable) and I honestly have not seen any signs since
> that the kmail devs have any clue at all. This mailing list has many
> stories of folks experiencing data loss when they just follow the
> instructions.
I know, and I think one of them was mine ...
However, I always were able to fix it in away so I could live with it, but if a
piece of software does not allow you to do what it is ment to do, it becomes a
useless waste of bytes. So I had to restore from backup, which showed me two
things:
1) My backup works (yeah !!)
2) I should have restored *all* user data as well, because:
akonadi's mail filter agent stores in its config only a numerical id of a
directory where to put the filtered mails to ('Move to folder') instead of its
name. When recreating the database, it messed up these numbers, so the filters
put the mail into the wrong folders. Hence, it *requires* that both the fiter-
configfile *and* the database must be kept *syncronous*. Unless you have a
database+filesystem which can handle modifications in one *single* transaction,
this is IMHO a bad idea, and AFAIK no such combination exists so far.
>
> Nowadays I use Tbird and all issues just go away.
>
I tried Tbird as well, but it has also serious problems keeping the folders
synchronized. See my next mail I'm writing to this forum.
> It's unbelievable the chaos kamil2 can inflict on a system, and the
> worst is that everything they do is a complete 100% already-solved
> system, there's nothing new in it - it does mail and contacts plus a few
> other bits! Classic case of 2nd major project syndrome (read mythical
> man Month if you don't get the reference)
Well, I think the idea behind akonadi is not that bad, but some times I have
the impression that the implementation is either incomplete or buggy or highly
inefficient.
