Goodbye for now, kmail

[Gianluca Montecchi]

On Wed, May 03, 2017 at 09:15:20AM +0200, Ren? J.V. Bertin wrote:
> On Wednesday May 03 2017 08:47:36 Anders Lund wrote:
> 
> >Good to hear kmail works for you. In my case, where my mailaccount is
> >with my provider, it does not work at all. It may have to do with the
> >IMAP server they use, but that does not help me much, except maybe I
> >can find a provider using a IMAP server that works with kmail.
> >
> >Since the last update, I am basically not able to view mail in kmail.
> >Akonadi simply chokes
> 
> Do you by any chance have to set an "IMAP prefix" to point the IMAP client to a specific location under your account on the server and use that as the "root"? 
> That kind of thing is not described in any IMAP standard and thus not implemented in Akonadi's IMAP client. Given how the protocol works the client will indeed choke if it has to trawl through a huge list of (huge) files on the server, scanning each of them for email. I've seen that happen with the UW IMAP server I run on my Mac - I ended up submitting a patch for it which allows server-side specification of the email archive folder (on the server).
> 
> R.
> 

The problem is that kmail&akonadi choke also when used with
POP3 and all the mail are downloaded on the local machine. Once you 
read a message, when trying to read another one give as result the 
message "fetching message..." and stay there. 
The only thing you can do is to try to restart akonadi some times 
(2, 3 or more) and hope it start to work again. 

I hope you will understand that this IS a problem for a normal
user, which just want to read his/her message, maybe for work.


While I consider the idea behind akonadi to be a good idea, the
implementation is terrible and it is clear that it is not 
working right.

Moreover, the really big problem is that you cannot use kmail
without akonadi, which render kmail useless for any serious
work.

bye
Gianluca