[KDE-pim] New Install: AKONADI wit PostgreSQL

[Hakan E. Duran]

I have used KDEPIM since KDE 3.5 I believe. When the transition to
akonadi was first introduced/discussed, I remember the argument was that
once the optimizations were realized KDEPIM would integrate with the DE
better and the experience would be more natural. I also heard several
arguments about how an akonadi backend was the conceptual right choice
for this purpose. I do not have a technical background and I respect
those people, who were saying these. I still believe that they know
better than me, and they probably have a lot valid points in those
arguments. What I did experience personally was pain and suffering, with
a long time of patient waiting for things to evolve into that utopia
that was promised. There were times improvements were visible, there
were times they weren't. After more than 10 years' time though, I
concluded that KDEPIM with the akonadi backend did not provide me the
experience that I loved with KDEPIM 3.5. I don't think it will ever do
that; 10+ years is a long time. It was time for me to move on and I
don't regret that decision. I do understand those who would like to
stick with it further and don't blame them; I was one of them for so
long. I am still a subscriber of this group for heaven's sake. However,
I cannot deal with database administration for my emails, that is too
much to ask from a user; I agree with Martin.

Regards,

Hakan
On 20/12/31 12:39PM, Martin Steigerwald wrote:
> Anders Lund - 31.12.20, 12:25:53 CET:
> > torsdag den 31. december 2020 08.49.36 CET skrev Paul Vixie:
> > > while i agree that pgsql's upgrade process could be simpler
> >
> > An easy way is to just delete the database. Akonadi will then create a
> > new, functional one. Maybe evil - but simple. Works for me, with mail
> > stored on IMAP and contacts and calendar on nextcloud. :)
>
> Unfortunately Akonadi is not just a cache as I understood it initially.
>
> For IMAP a mail that it could not yet store onto the IMAP server due to
> whatever may just sit in the database. To my knowledge possibly
> indefinitely as Akonadi would not try again. That are those payloads
> without remote id.
>
> For POP3 with local folders AFAIK this can happen as well. On top of
> that filters you defined would point to invalid folders after recreating
> the database. Meanwhile KMail seems to detect that and it will ask to
> select the folder for every filter, which can be tedious, if you have
> many.
>
> I defended Akonadi many times. Meanwhile I think there are just too many
> conceptional issues with it, that I think it may be beneficial to re-
> think all of it and start from scratch. But that is a major undertaking
> as well.
>
> I think it is too much to ask from the user of a PIM suite to deal with
> database administration tasks of any kind. And now, IMHO an automatic
> update of PostgreSQL from Akonadi is not going to solve it. Especially
> as there are many failure points for such an automatic update, if you
> ask me.
>
> I am using Evolution at work due to Office 365 and EWS plugin just being
> so much more reliable for Evolution. I never ever dealt with how
> Evolution stores mails. Actually I do not even know it. IMHO that is how
> it is supposed to be.
>
> Best,
> --
> Martin
>
>