Re: [KDE-pim] New Install: AKONADI wit PostgreSQL

Am 01.01.21 um 10:44 schrieb Andreas Mair:
> Hakan, you're so right. That's exactly my experience. I loved KDEPIM
> before akonadi. I also liked what they promised that akonadi could be.
>
> But I didn't get akonadi to work reliable here. No special setup, just
> IMAP in the beginning. As I needed a reliable solution I moved to
> thunderbird years ago. It simply works. No need to be any DB admin. No
> need to think about what DB to use. No need to tune any DB engine. No
> need to know any workarounds to get akonadi back on track again.
>
> As you can see, I'm still subscribed to this mailing list. Every now and
> then I try the latest release because I like KMail's and Kontact's
> usability. But to be true, I never dared to move back to KDEPIM because
> I can't forget the data-loss I had while testing. By reading this
> mailing list I have no hopes it could work better for me. Sorry.
>
> I really don't want too negative and I *really* appreciate all the works
> anybody brings in KDEPIM, KDE and Open Source in general, but I
> personally lost faith in akonadi.
>
> Happy new year 2021 and best regards,
> Andreas
++

>
> Am Do., 31. Dez. 2020 um 17:56 Uhr schrieb Hakan E. Duran
> <[email protected] <mailto:[email protected]>>:
>
>     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
>      >
>      >
>

--
Es sprach der Fürst zum Herrn Kaplan:
"Halt' Du sie dumm, ich halt sie arm!"