Bug 286569

Summary:	Apply all filters does not work reliably on imap messages
Product:	[Applications] kmail2	Reporter:	Paul Eggleton <bluelightning>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	amantia, dominique, null, thomas
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Paul Eggleton 2011-11-14 09:47:21 UTC

Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

When you select Apply All Filters with a number of messages selected in an IMAP folder, quite often not all of the messages are processed.

Reproducible: Sometimes

Steps to Reproduce:
1. Ensure you have some rules set up to move messages to other IMAP folders (based on List-Id in my case)
2. Select multiple messages in an IMAP folder (in this case the Inbox)
3. Right click and select Apply Filters->Apply All filters (or press Ctrl+J)

Actual Results:  
Some of the messages are moved and then processing stops; occasionally it only moves the last message selected. Re-selecting the messages that did not get moved will result in some of those getting processed in the same fashion and you can repeat until they all do, so the filters are matching.

Expected Results:  
All messages matching the filters are processed (and for the filters I have set up, this would mean all get moved).

Message list is using "Activity by Date, Threaded" aggregation and the "Fancy" theme. 

It seems if I move the messages manually to a local folder and try this it works as expected, so it might be something to do with the delay in fetching the message or perhaps the interaction with the list selection.

Comment 1 Paul Eggleton 2011-11-14 09:59:01 UTC

Addendum: if you click on each message individually beforehand (which caches the email contents) it seems to make it more likely that all of the messages get processed.

Comment 2 András Manţia 2011-12-10 08:00:08 UTC

As the filter code was reworked for 4.8, would be nice to see if this happens with 4.8beta2.

Comment 3 Paul Eggleton 2012-01-21 14:19:07 UTC

Have just tried 4.8 rc2, the behaviour is exactly the same as far as I can tell. It might be as simple as the filter not applying to messages that haven't yet been cached (because I haven't viewed them yet).

Comment 4 Thomas Arend 2012-03-31 16:14:01 UTC

Filter does not work on 4.8.1 or works only on some messages. Some of mein corn messages are move do a folder some are not. To all the same criteria apply. X-Cron-Env: <SHELL=/bin/sh>

This ans all the other bugs are extremly boring. I regret updating.

Comment 5 Thomas Arend 2012-05-19 13:06:30 UTC

As far as I could tell this problem is in all Versions since 4.7.x

What I have found so far is:

When you receive a lot messages 10 better 100 or 200 then some messages are not filtered, some are filtered more than once and some message are duplicated in the message list. The duplicates may go after some time (several minutes up to several hours). Some duplicates vanish when your read a copy.

In one case I could re-receive the messages multiple times. Even stoping and starting did not effect the re-receiving only "akonadictl stop / akonadictl start" endet this loop..

Comment 6 Unknown 2013-01-23 10:01:41 UTC

Please, make a control with "akonadi console"
Choose "DB Browser", "collectiontable", "Refresh"
Get a look to the column "remoteId".
Are there any cell(s) with nothing? If yes, let me/us know by copying the raw(s).

Comment 7 Denis Kurz 2016-09-24 18:22:13 UTC

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.

Comment 8 Denis Kurz 2017-01-07 21:27:12 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.