From kdepim-users  Tue May 09 12:59:47 2017
From: Anders Lund <anders () alweb ! dk>
Date: Tue, 09 May 2017 12:59:47 +0000
To: kdepim-users
Subject: Re: Goodbye for now, kmail
Message-Id: <20170509145947.7862698e () alweb ! dk>
X-MARC-Message: https://marc.info/?l=kdepim-users&m=149433480211138

P=C3=A5 Tue, 09 May 2017 11:10:35 +0100
ianseeks <bingmybong@btinternet.com> skrev:
> > KMail isn=C2=B4t at fault here. It *waits* for Akonadi. There is nothing
> > it can do about that. So using your language: It is not KMail that
> > is silly, but Akonadi is. (Well some may consider KMail to be silly
> > since it relies on Akonadi tough=E2=80=A6 but I remember KMail pre-akon=
adi
> > times and its own index file management had its flaws as well. It
> > has been more than once that I deleted some broken index files back
> > then and KMail then just didn=C2=B4t show its main window until it has
> > rebuild all those index files. Also KMail GUI was basically blocked
> > on retrieving new mails via POP or moving lots of mails.) =20
>=20
> Thats the problem because kmail gets the kicking as its the UI and
> most of us who are not developers are unsure where the separation is
> so bugs (and rants) get posted against kmail instead of akonadi.

I'm sorry, but from a user point of view there is no difference. When I
can't read my mail in kmail, kmail gets the blame. For me, the
situation is that I really want to use kmail, because it is such a
wonderful mail client - but I can't, due to akonadi. It would be nice
to see a solution to that.

Btw, akonadi developers hopefully also reads this mailinglist, afterall
akonadi is part of kdepim.

How can we get started finding a solution?

Kindly,
Anders