Bug 473052
Summary: | "Message filter" can not filter messages. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Suqin Huang <shuang> | ||||
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | desktop-bugs <desktop-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.2.z | CC: | mcrha, msolberg | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-03-09 11:34:27 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Suqin Huang
2008-11-26 10:17:52 UTC
I'm suffering from the same issue. If I select all mail in my INBOX and select "Apply filters", mail is filtered. But, the "Apply filters to new messages in INBOX on this server" setting in my account preferences is not honored. I'm pretty sure it's the same issue as RH BZ 460261 and GNOME BZ 324804. There's a patch available on the GNOME BZ. http://bugzilla.gnome.org/attachment.cgi?id=104647 Michael. Created attachment 330409 [details]
Fix for the issue
This is the patch from the GNOME bugzilla - it cleanly applies to the latest evolution-data-server SRPM.
I haven't seen this issue since I applied the patch.
Thanks for the update. There was some updates on the patch too, and it has a little side-effect, when you drag&drop message from one folder to the other, where are filters applied (to Inbox, usually), the dropped message is processed by filters again. There is an upstream bug about that too. I'm marking this as a duplicate of the bug #247779 because that one is approved. *** This bug has been marked as a duplicate of bug 247779 *** |