Red Hat Bugzilla – Bug 446095
[RHEL5.2Beta] filter is not applied on exchange mailboxes
Last modified: 2010-10-22 20:56:07 EDT
Description of problem:
incoming mail is not being filtered in exchange mailboxes. None of my filters
are working as mail comes in. Selecting mail after it has arrived and applying
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Subscribe to exchange mailbox
2. Create filters
3. Wait for them to be applied
filters should be applied
suspect upstream bugzilla -
and the patch for the same
Regression - filters used to work with Evo2.8/RHEL5.1
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being proposed as a blocker for this release.
Please resolve ASAP.
Confirmed. I found that same bug and patch independently, and then realized you
already referenced it! Easy fix. Unfortunate that it slipped through.
Just checked the bug was reproduced with evolution-connector-2.12.3-10.el5.
Step1: Subscribe to exchange mailbox.
Step2: Add a filter for testing.
Step3: The new mail received in Inbox, not in filtered folder.
Step4: Click the new mail, then click Message->Apply Filter, the mail will move to the filtered folder as expected.
The new mail not move to the filtered folder as expected
The new mail should move to the filtered folder as expected
Just checked and works fine for me.
My Incoming message filter is very simple, if sender contains redhat.com move message to the exchange folder personal/Inbox/RedHat
Then, in account preferences I've set on the Receiving options tab:
- automatically check for new mail every...
- Apply filters to new messages in Inbox on this server
With this set (and to be sure closed evolution and reopend it), when such message is received to the Inbox it's properly moved to the folder I set in the rule.
My evolution packages are:
Refer to Comment #20, verified this bug was fixed with:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.