Fixing things Akonadi doesn't with some SQL-fu

[Paul Vixie]

René J.V. Bertin wrote:
...
> It's not that this recipe prevents all issues either (because I don't
> also quit akonadi itself?): there are still times where new mail just
> doesn't come in, for instance. Which is hard to detect if you don't
> have an independent means of checking for new email.

i had a lot of trouble convincing kmail to check for upstream e-mail. F5 
didn't force the matter. restarting kontact, no help. restarting 
akonadi, no help. restarting the imap transport via akonadiconsole, no 
help. telling the transport to resynch via akonadiconsole, no help. 
rebooting the VM, no help.

then i found that if i carefully control which transport starts first, 
so that kolabsys gets the first IMAP slot, which means IDLE will be 
sent, then all is well. so now i restart everything, go offline, then 
rescan my kolabsys inbox which asks if i want _that transport_ to be 
brought online, and i say yes. then i bring the rest online.

this is more likely to be a bug in kolabsys, but it could be supported 
by a leaning bug in akonadi -- it doesn't happen with my other IMAP 
server. but i can tell you that i used to be technical, and noone who 
was never technical is going to be able to find nor willing to use 
workarounds at this level.

> [to Paul]
>> If you want to be unhappy, that is entirely and solely your choice
>
> Can we please keep that kind of remark out of the (any) discussion?

agreed, but do note, i am undaunted. "if you don't like the news, go out 
there and make some of your own." akonadi is currently horrible for a 
lot of people, and those people should not be discouraged from speaking 
here. "boots in lab" is not an reasonable acceptance criteria.

> On Tuesday March 20 2018 15:49:42 Paul Vixie wrote:
>> i need kontact to Just Work, without giving it an SSD and 16GBytes
>> of RAM to live in.
>>
>> perhaps that's where the disconnect lies.
>
> Quite possibly - why would you not want a recent gaming-grade hot-rod
> to read your email and do some wordprocessing? ;)

it's an x1c6 with a ~2GHz mobile pentium, 16G of RAM, and an SSD. 
however, i don't want to dedicate it to kmail -- i have a lot of other 
work i must also do. and i can't leave akonadi running except when i 
need to use PGP, or else my battery will be dead in less than 1 hour.

> On Wednesday March 21 2018 09:13:50 Mathias Homann wrote:
>
>> ... wouldn't that mean that akonadi can have all kind of trouble as
>> soon as the mail servers are not on the same physical lan? Which in
>> fact I can confirm, sort of
>
> My experience also. The times I do have to restart akonadi there has
> usually been some kind of LAN glitch that wasn't picked up properly
> by the IP stack on the host (which *usually* happens when you
> suspend/wake the machine, change the WIFI network etc).

race conditions are the norm now. we have to save endpoint state and be 
very careful about how we restore it every time any part of the 
distributed system becomes temporarily unreachable. that's the law (of 
physics) and we can either respect it or lose.

-- 
P Vixie