GNOME Bugzilla – Bug 245885
Filters do not apply properly after startup
Last modified: 2003-07-09 22:16:12 UTC
Description of Problem: I have many filters. When evolution starts, it will go and fetch new messages from several mail services. The filters however, are not applied until I select the source folder that contains the messages to be filtered. After I select a message to read, the filtering is applied. After the filtering is applied, there is usually one message that should have been filtered but isn't. I have to filter this one explicitly. Steps to reproduce the problem: 1. Start evolution and wait for messages to arrive 2. Watch source folder fill up with mail that should be filtered. 3. Select a message to read (that wouldn't normally be filtered). Watch mail filter being applied and note that there is always one message left behind. Actual Results: No filtering until folder is selectde. One e-mail left behind. Expected Results: I expect the filters to be applied immediately and without leaving the odd e-email unfiltered. How often does this happen? Whenever I start evolution. Additional Information: I have many filters because I subscribe to many mailing lists. This feature is important to me.
this is a duplicate - you should use server-side filtering, it'd be much more reliable for you (it's really hard to get client-side imap filtering to work) closing because there's a dup
"Use server side filtering" is not an answer. If there is a feature and I want to use it, I jolly well expect it to work. As for "It's really hard to get client side filtering to work", well I hear the violins. Do you really expect me to beleive that after so many years of people writing open source IMAP clients (that have filtering capability BTW) such as Mozilla/Netscape that this is a near impossible task. Hogwash. There is a very good reason I use filtering on the client side -it is because I have over 5 e-mail accounts. Think about it. If this is a duplicate of another bug, could we at least have the bug number of the one that considered to be the reference.
*** This bug has been marked as a duplicate of 242637 ***
perhaps you'd be willing to send us a patch? :-)