So I think I found my new mails...

[Martin Steigerwald]

Martin Steigerwald - 24.03.18, 16:48:
> Ian Douglas - 23.03.18, 13:08:
> > As previously mentioned / ranted either here or on a bug report, since the
> > last update in late January, KMail has been storing my mails "somewhere
> > else" rather than in
> > /home/ian/.local/share/.local-mail.directory/
> > where it did previously.
> > 
> > Deleted mails are now put in
> > /home/ian/.local/share/local-mail/trash/new/
> > 
> > I think I have finally found where the new mails are, and they're buried
> > in
> > a long string of numbered directories by Akonadi.
> > 
> > See attached.
> > 
> > Issues:
> > 
> > 1. This is not a maildir.
> 
> This is actually the place where Akonadi stuffes payloads (i.e. mails,
> events, contacts) that are too large to stuff into the database. There is a
> threshold there. Why does Akonadi store them? It is a cache – for various
> reasons. But… and that is the thing: The resource puts those payloads into
> the final destination, i.e. the maildir. However: If this, for some reason,
> does not work, it never tries again to do so. And these are items without
> RID, without remote identifier.
> 
> When you use akonadictl fsck it should tell.
> 
> Please, really please, before I explain it all here again and probably using
> an hour or more for that, read through the architecture document by Dan.
> 
> https://community.kde.org/KDE_PIM/Akonadi/Architecture
> 
> Especially the section about change replay.
> 
> Server-side change recording is one of the four major changes to the low
> level architecture that will fix that. Unfortunately it is not yet
> (completely implemented). I personally think that this is one of the most
> important changes as the current situation can lead to data loss if for
> some reason the Akonadi database (including the filedb part of it) becomes
> broken.
> 
> So for now all you can probably do is make sure you keep your Akonadi
> database safe and not delete it or so, until it Akonadi is able to replay
> the changes again.

Of course it could also be that Akonadi just did not come around replaying the 
changes to the maildir and you just need to wait a little longer.

-- 
Martin