GNOME Bugzilla – Bug 274176
Filter does not apply scores
Last modified: 2012-02-08 16:16:48 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Major Version: GNOME2.10.0 2.2.1 Gnome-Distributor: Ubuntu Synopsis: Filter does not apply scores Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.2.1 Description: Description of Problem: The only really useful tests that filters and vfolders have in common is the score. When Spamassassin marks junk mail on the server, I use a filter to read the X-Spam-Flag and set the score to 3 (negative values give errors). I then have a vfolder set up which only shows new mail with a score of 0. However, spam still shows up, implying that the score is not being applied. Steps to reproduce the problem: 1. Create filter to assign a score to a message 2. Create vfolder to filter out any messages with assigned score Actual Results: The messages still show - i.e. the score is not being applied. Expected Results: I don't see junk in my new mail vfolder. How often does this happen? Always Additional Information: Why are there different criterion for filters and vfolders? Why can't a vfolder just scan for spam header so I don't have to set up a filter first? This is less than ideal. Evolution is extremely cool! :-) Unknown reporter: j.quigley@serviomatic.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
vfolders have to be fast, so they cannot rely on parsing messages on the fly (slow). filters can parse messages on the fly :) anyways... dunno about the problem. this is with evo 2.2.1?
jeff, did you try to recreate the problem?
no, haven't had time yet.
I have to congratulate you on the first real usage case for scoring in evolution thus far, so congratulations... you win... a bug :) I have confirmed that negative values cause a warning... however, if I create a filter "if specific-header x-spam-flag exists; set score to 3" and then create a vfolder that matches all messages with a score of 3, I see every message that is supposed to match. I also tested a vfolder where the rule was score!=0 and again, that matched all the appropriate messages. perhaps another filter (or the ordering of your filetrs) is clobbering the score(s)? remember that if you move a message as the first action and then set the score, the resulting message in the destination folder will not have the score applied to it - you need to set the score first, and then move (I mention this only because it is a common mistake)
Hi Jeff! I dropped a stop processing action into the filter and the score seems to be sticking. It appears then that cascading through the other rules resets the score back to zero. I set up just a couple of rules on another machine and only the first one set a score. This score was recognised by the vfolder (match on score = 3) when using the stop processing action and ignored when not, confirming my observation. Cheers, Jason.
Okay, it appears that when firing the rules manually, the score is applied with the same characteristics as above. When fired automatically, the score doesn't seem to be getting applied. Cheers, Jason.
adding keyword; reopening, retargetting
removing old target milestone.
As far as I can tell the 'score' is set on the message when the filter rule is processed by an automatic update in 3.3.5, which is roughly a version I tested this with. Thus I'm closing this as fixed. (The vfolders are kinda confused, but there are other bug reports about it after sqlite summary change.)