On Tuesday 29 Dec 2015 12:39:18 J. Roeleveld wrote: > On Tuesday, December 29, 2015 10:51:57 AM Mick wrote: > > On Tuesday 29 Dec 2015 10:20:23 J. Roeleveld wrote: > > > On Tuesday, December 29, 2015 09:53:24 AM Mick wrote:
> > This is good to know. An earlier akonadi bug would actually delete files > > on the server. O_O > > Hmm... must have missed that one... > Are you sure that also affected IMAP connections? Yes, I remember reading about some bug between akonadi and mysql. akonadi would push its corruption to the IMAP4 server, deleting a tonne of messages. I also remember a Mr A McKinnon having a well earned rant on this same M/L when he was trying out Kmail2, quite likely still in ~arch at the time. > > I take this to mean that the Kmail interface does not freeze up and you > > can continue to read/delete messages, change folders, etc.? > > Yes, with only the following comment: When moving large (1000+) amounts of > messages to a different folder, let the interface show it as finished > before doing something else with KMail. Cool, so as long I delete a few messages at a time, it should be OK. > > Thank you Joost, this is very useful to know. What do you mean by > > "haven't had to restart the mail cache"? Do you mean you did not have > > to delete the akonadi database(s) and restart it? > > Yes, restarting the mail cache is: delete everything and start over.... > > Don't forget, akonadi-storage has 2 parts: > 1) The database (mysql or postgresql) > 2) Files > > The 2 are linked and need to be kept in sync. > This is important for backups and cleanup. Yes, there are a number of files and databases in my current setup (Kmail1 with sqlite3) under .local/share/ including akonadi, baloo, et al. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
