Kmails quickfilter only includes the email-body of emails which have been opened in kmail before. This is a problem because it ignores emails which have been opened via webmail or on another computer. It should ask the user if it should download the missing emails or simply append the bodyless emails to the hitlist. Reproducible: Always
??????????????????
Example: 1. Open your inbox 2. Write an email with text "This is a test" to yourself. 3. Note the new email but don't open it. 4. enter "test" into the quickfilter field Expected result: The filtered list should contain the email you just send to yourself Actual result: The list does not contain the email you just send to yourself. 5. Now open the email and filter again Result: The list contains the email you just send to yourself. I hope it's clearer now.
Yes but it's async So don't think that it will index directly So it's not because you open mail that it will index. It just that it will take time.
Hi, it's not a syncing problem but an iterference with the offline mode. Due to the offline mode, it can happen, that the message body is not available during indexing. Perhaps the indexer can trigger a message download? Or tell the user, that the list may be incomplete due to missing message bodies?
Where did you write that it was in offline mode ? Ok perhaps it's it. I will look at
Created attachment 85613 [details] screen-shot of configuration dialog Thanks! Just do avoid a misunderstanding, I am talking about the offline-mode which can be activated in the account-settings (see screenshot) and not about "Work offline" under file.
imap-disconnected ok
I also use imap disconnected and suffer from the same issue (quick filter does not return all the results it should). Indeed, the Inbox folder is partially indexed: from Properties->Maintenance I see that only 10.933 items out of 34.253 have been indexed. Is there a way to force the indexing of all the emails in a folder? Thanks!
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
This bug is not present anymore, I believe it can be marked as resolved.
Great, thanks Stefano.