I have a Maildir folder with about 1GB of old mail that doesn't show up in a KMail Tools->Find Messages. Thinking that the size was choking the indexing I tried creating subfolders in the maildir and moved messages into the subfolders. Oddly, the messages seem to have been both moved and not-moved - the counts in the original maildir and the messages seem to be there as well as in the sub-folders.

The search seems all messed up: A kmail "search in all local folders" for a single uncommon word seems to find some messages in the subfolders while a grep in the original maildir's "new" directory turns up considerably more and a search in the original large maildir with an "include sub-folders" turns up nothing. How do I get a folder to be indexed?

Further - I'm confused about what has happened with the "add folder" function. I expected a sub-directory to be created *somewhere* but a 'find / -name "*name*" -print' doesn't show anything, so I'm assuming that the creation of a folder in a maildir folder is more a tag in the index than anything else. If so then why on Earth should the move of some message occupy so much CPU and disk access?

Sorry to sounds like such a neophyte, but I can't understand what's happening here.

Qt: 4.8.1
KDE Development Platform: 4.8.2 (4.8.2)
KMail: 4.8.2
Akonadi Console: 0.99

Is indexing enabled for the folder? Right click on the Folder in question in KMail/Kontact > Folder Properties > Maintenance. Make sure "Enable Full Text Indexing" is checked.

"Enable Full Text Indexing" has been on and is on now - while having trouble I tried turning it off then back on but didn't see an effect.

I was able to index the major directory by deleting the old one and copying things back in from my archive. Still some really odd results - the search from kmail in that directory comes up with 13 results, the results from searching the "body of message" in the search tool choosing that directory comes up with no results and the result from a "grep -l -i "word" in the same directory comes up with 181 results. Looking at them says that most if not all of the results are in text.

How can I resolve the differences?

Qt: 4.8.1
KDE Development Platform: 4.8.2 (4.8.2)
Kontact: 4.8.2

I would recommend asking on the kdepim-users@kde.org list in this case - as it seems that something is going wrong here.

I'll try that, thanks.

After I subscribed I got this in the 'welcome' text:

<<
Please don't send bug reports or feature requests to this mailing
list. Go to bugs.kde.org instead.
>>

I sure feel welcome now!

You can still ask, as it's unsure if the behavior you're seeing is a bug or not.

Were you able to solve this problem?
I'm having the same trouble, seems like...

I asked on the kdepim-users mailing list and failed to get a response. I was able to get some searching in Subject: lines by reloading the mail folder, but the bodies of the messages are not being searched even using the "Find messages". Some other oddities in there - using the search text area above the list of messages in the folder initially shows up 7 messages, if I use "Find messages" searching for the same work in the subject I get 13 hits and the KMail2 list updates to the new count. Searching "body of message" comes up with one hit when greping in that directory comes up with more than 100 unique hits in files.

It's all very frustrating.

I've used search in the past using the current git (to be 4.9) and as far as I can tell there are no such issues. To rule out the possibility that you have found a bug that has been fixed for the next version, can you check in System Settings under Desktop Search whether email indexing is enabled?

einar wrote:I've used search in the past using the current git (to be 4.9) and as far as I can tell there are no such issues. To rule out the possibility that you have found a bug that has been fixed for the next version, can you check in System Settings under Desktop Search whether email indexing is enabled?

System Settings->Desktop Search->Email Indexing is checked as well as KMail2->Folder Properties->Maintenance-?Indexing "Enable Full Text Indexing". There is some indexing going on as I can search the subject lines but the bodies are not being indexed.

$ kmail -v
Qt: 4.8.1
KDE Development Platform: 4.8.2 (4.8.2)
KMail: 4.8.2

(On edit - I can't tell if the bodies are being indexed, it's possible that the query to return results isn't working on correctly indexed bodies. I did a quick test on a small folder and found that it was correctly finding words in the body of those emails. The larger directory is quite a bit larger at 52K messages.)

(On second edit: I manually created a new MailDir directory and copied the messages that contained the work backplate. Since it seemed to be that new mail directories were index on startup I logged out and logged back in. 12 CPU minutes virtuoso-t was done and the nepomukservices were idling and I tried searching - didn't find a thing in the new directory. So I manually created a new directory and had kmail copy everything over into the new directory, search still didn't find anything in the body, only the Subject:.)

Are you able to see any relevant details in ~/.xsession-errors as to why searching or indexing might be failing? (Anything related to Nepomuk in particular is relevant here)

bcooksley wrote:Are you able to see any relevant details in ~/.xsession-errors as to why searching or indexing might be failing? (Anything related to Nepomuk in particular is relevant here)

Nothing that jumps out as "error" to me. I thought that I might have a handle on this by touch()ing 10% of the messages (selecting by *0.main, etc.) but while it caused a whole bunch of activity (22 minutes of CPU in mysqld and 225 minutes of CPU in virtuoso-t) the indexing didn't change. I still find the same number of messages searching subject and none searching the body of the message.

I'd be glad to send the result of `grep -i Nepomuk xsession-errors` if you want to see it. (I restarted my session and saved the .xsession-errors).

This has to be something basic about my setup - I do have other issues like the 'zombie' messages - delete a message and it comes back as a new message when you return to the folder. Messages that are expired from spam come back the same way. The only way I can removed messages is to manually move them into a folder then remove them from the file system.

bcooksley wrote:Are you able to see any relevant details in ~/.xsession-errors as to why searching or indexing might be failing? (Anything related to Nepomuk in particular is relevant here)

I seem to be having the same problem here.
Issuing "grep -i -e nepomuk .xsession-errors" I got the following messages concerning Nepomuk:
---------------------------
nepomukservicestub: No service name specified
nepomukservicestub: Use --help to get a list of available command line options.
Nepomuk Query Server not available
PLUGINS: ("akonadinepomukfeederagent.desktop", "akonotesresource.desktop", "birthdaysresource.desktop", "calendarsearchagent.desktop", "contactsresource.desktop", "davgroupwareresource.desktop", "icalresource.desktop", "imapresource.desktop", "invitationsagent.desktop", "kabcresource.desktop", "kalarmdirresource.desktop", "kalarmresource.desktop", "kcalresource.desktop", "kdeaccountsresource.desktop", "knutresource.desktop", "kolabproxyresource.desktop", "localbookmarksresource.desktop", "maildirresource.desktop", "maildispatcheragent.desktop", "mailfilteragent.desktop", "mboxresource.desktop", "microblog.desktop", "mixedmaildirresource.desktop", "mtdummyresource.desktop", "nepomuktagresource.desktop", "nntpresource.desktop", "notesresource.desktop", "openxchangeresource.desktop", "pop3resource.desktop", "vcarddirresource.desktop", "vcardresource.desktop")
PLUGINS inserting: "akonadi_nepomuk_feeder" 0 ("Unique", "Autostart", "NoConfig")
PLUGINS inserting: "akonadi_nepomuktag_resource" 0 ("Resource", "Virtual", "Unique", "NoConfig")
void AgentManager::load() Reference to unknown agent type "akonadi_nepomuk_calendar_feeder" in agentsrc
void AgentManager::load() Reference to unknown agent type "akonadi_nepomuk_contact_feeder" in agentsrc
void AgentManager::load() Reference to unknown agent type "akonadi_nepomuk_email_feeder" in agentsrc
Known subscriber "akonadi_nepomuk_feeder" subscribes again
akonadi_nepomuk_feeder(1803) FeederPluginloader::feederPluginsForMimeType: No feeder for type "inode/directory" found
akonadi_nepomuk_feeder(1803) ItemQueue::removeDataResult: "No such object path '/datamanagement'"
akonadi_nepomuk_feeder(1803) ItemQueue::batchJobResult: "No such object path '/datamanagement'"
akonadi_nepomuk_feeder(1803) ItemQueue::fetchJobResult: Not all items were fetched: 47 100
akonadi_nepomuk_feeder(1803) ItemQueue::removeDataResult: "No such object path '/datamanagement'"
akonadi_nepomuk_feeder(1803) ItemQueue::batchJobResult: "No such object path '/datamanagement'"
< lots of the same messages>
akonadi_nepomuk_feeder(1803) ItemQueue::fetchJobResult: Not all items were fetched: 25 74
<lots of the messages above>
QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed!
...
akonadi_nepomuk_feeder(1803) ItemQueue::fetchJobResult: Not all items were fetched: 8 18
akonadi_nepomuk_feeder(1803) ItemQueue::removeDataResult: "No such object path '/datamanagement'"
akonadi_nepomuk_feeder(1803) ItemQueue::batchJobResult: "No such object path '/datamanagement'"
...
-----------------------------------------------------------------------
There are lots of the messages with the events: ItemQueue::fetchJobResult, ItemQueue::removeDataResult or ItemQueue::batchJobResult.

Is this relevant to the problem in question?

It appears that your Nepomuk installation has problems, as core Nepomuk components are missing.
Please ensure your system is fully up to date, and all Nepomuk related packages, if they are split are installed.