martin at lichtvoll.de
Sat Oct 8 10:00:32 BST 2016
Am Samstag, 8. Oktober 2016, 10:53:41 CEST schrieb Martin Steigerwald:
> Am Samstag, 8. Oktober 2016, 10:24:45 CEST schrieb René J.V. Bertin:
> > Akonadi also appears to choke without any sign of that happening, apart
> > from
> > >the lack of new mail. Then a restart is required.
> > Yes, I've also seen that, though fortunately it's very rare and since I
> > have a copy running on 2 machines (plus my phone telling me about new
> > email) I usually detect it soon enough.
> > I see one solution that shouldn't be too hard to implement and also
> > doesn't
> > require pouring the akonadi koolaid ("akonaid" :)) down the drain: make
> > the
> > imap agent optional and implement a version of it as part of the KMail
> > process. That should make it possible to address most if not all issues if
> > indeed this "BSOD" is due to a comms problem where KMail keeps waiting for
> > the imap agent. * add an imap account through the akonadi KCM -> adds an
> > imap agent (shows up in KMail too) * add an imap account in KMail ->
> > default setting will use an imap "agent" running as a procedure in KMail,
> > optionally create an akonadi imap agent.
> > Akonadi can of course continue to provide an imap agent for other
> > applications, but how many are there exactly that query this agent?
> KDEPIM team decided to tailor Akonadi only for KDEPIM and Plasma usage some
> time ago.
Or to clarify: Not take care that it works for apps outside of KDE anymore. I
think developers wouldn´t deliberatly break it for those without a good
reason. That said: Who uses Akonadi anyway except KDE apps? AFAIR that was one
reason for the decision of the KDEPIM team.
More information about the kdepim-users