Hi!

I have an akonadi ressource for local folders - it point to

".local/share/local-mail"

But when I add a folder in Kmail it doesn't appear in this folder!
Instead it appears in ".local/share/.local-mail.directory"

In this folder (the last hidden one) I get some hidden folder for some subfolders also:

I've got one "archive" and also get ".archive.directory"!
This doesn't happen to all folders but to some ...

What happens here?

(Yes I double checked the akonadi ressource folder settings!)

How do I get all the folders from the hidden .local-mail.directory to show up in kmail?

thx for reading,
more and more frustrated,
piedro

I believe the "strange" layout is due on how a local Maildir mail storage works.

Hello einar!

that's what I thought ... but then there should be corresponding hidden *.directory to all folders with subfolders, or what is it I am missing?

It isn't in my setup and as stated before I have no clue how to solve the local folder confusion.

I deleted the local folers and set them up again.
> some folders are missing

I deleted again and I let akonadi create a new set of local folders
> the default folders disappeared after restarting kmail (and they stayed lost)

I used the imoprt feature of kmail to import a few thousand mails an there archive folder strucuture
> after restarting kmail these new imported folders give me the reported "invalid collection" problem

I deleted again and copied the default folder structure into .local/share(local-mail
> now the default folders work but the imported archve folders disappear

I guess this is not just the way local mail storage is supposed to work!


My question is: How to setup the local folder correctly (in way it works afterwards!) and how is the relation beetween the two folders mentioned in the OP?

thx for reading,
piedro

Unfortunately I'm at a loss here, as I mostly use IMAP, and my local folders are only the ones used for trash, outbox, and sent mail.

Piedro, All,

Have you understood all these local folders related mechanics? Say, why are all messages placed into ~/.local/share/.local-mail.directory directory while akonadi service has ~/.local/share/local-mail directory in configuration? Why does searching ('S') find nothing? What does that collection error mean? And so on... Is something clear for you now?

Frankly speaking, I feel like kmail is almost leaved by KDE team

With regards to ~/.local/share/local-mail/ and ~/.local/share/.local-mail.directory/ - This is part of the Maildir standard. Changes have recently been made to KMail to change this slightly to allow the .local-mail.directory folder to be inside the ~/.local/share/local-mail/ directory. I'm not sure if they will be in 4.8.1 however, or if they are waiting for KDE 4.9.

@bcooksley

Yes, ~/.local/share/local-mail/ contains cur, new, tmp, as well as subdirectories (in accordance with Local Folders tree) inside ~/.local/share/.local-mail.directory/ contain cur, new, tmp also. But I can not understand a relation between ~/.local/share/.local-mail.directory/ (which really contains all my messages) and ~/.local/share/local-mail/ (which is just single maildir direcory with forever empty cur, new, tmp subdirs). And last one is set as config for akonadi agent.

- Can this ... duality be a reason full text search doesn't work for mail messages?
- Or - is there a way to force reindexing of all the messages inside ~/.local/share/.local-mail.directory/?
- Does fulltext search mean message charset respecting?
- Does reindexing take place when a message is moving form one folder to another one using manual filtering (with shortcut assigned to the filter)?

Sorry for this big list of questions - I'm addicted to kmail1 and would be happy to avoid switching to another mail client and am ready to try any hints (including manual interventions) to make kmail2 working expected way. Thanks!

The duality should have no impact upon the ability of KMail to search your email. If KMail can access your mails, they should be searchable as well.

I'm not aware of any direct ways to force indexing to be restarted or completely redone - but you can stop Nepomuk, remove it's database and restart it. This will by convention cause a reindex to be done - as the existing index has been deleted.

I believe Message Charsets will be respected yes. Not sure however, one would need to check the code or ask the appropriate developers to be sure.

Messages are reindexed when they change state, which includes being marked as read, moved, etc. as far as I am aware.

@bcooksley

Tanks for your optimistic answer

At any case I still can not guess how to be sure indexing is taking place. Nepomuk controller just show desktop files searching explicitly. And I have not see any activity (HDD reading/writing, CPU eating - some operations are needed for full text indexing of ~7K messages) besides that one. I have tried to delete nepomuk and akonadi data (leaving X11 at that moment), delete Local Folders (stopping akonadi; Local Folders agent is re-creating automatically later) and so on, but nothing changes.

I have found to be not alone:

https://bugs.kde.org/show_bug.cgi?id=282891

Probably your explanation says more how it must be rather how it is.

The Nepomuk database is located at ~/.kde4/share/apps/nepomuk

Be aware that removing it will also delete any tags or comments you have filed in it, and will require that Nepomuk reindex all your files as well.

@bcooksley

Yes, I have found this place also. In fact, all I need to reconfigure after deleting akonadi and nepomuk data are destination folders in filters and destination folders in POP3 accounts.

After deleting the data that bug still takes place. And I don't see any workstation resources consumption reflecting messages indexing.

Your system should have started indexing once Nepomuk was started back up again. Please send a email to the kdepim-users mailing list concerning this, as others may have ideas on how to fix this.

Unfortunately, I am out of ideas at this point in time.

@bcooksley

KMail2 users are frustrated already.. and there are not too many of them now. Still hope that (and related) bugs will find interested developers. For now, I have completely tied to fight with KMail and think to wait for fixing search-related and few other outstanding bugs sitting on another mail client