GNOME Bugzilla – Bug 368417
Filters not automatically applied to Inbox
Last modified: 2013-01-22 18:12:25 UTC
Please describe the problem: Connecting to an Exchange 5.5 server using IMAP mode, filters on the inbox are not automatically run. "Apply filters to new messages in INBOX on this server" is checked. Incoming mail, once manually selected, and 'ctrl-y' is hit, are filtered as expected and, occasionally, filters -will- automatically run, usually just after a manual filter or an expunge, but never if there is already mail that is not filtered in the inbox. Steps to reproduce: 1. Wait. 2. New mail fails to be filtered. 3. Select mail and apply filters works as expected. Actual results: New mail is not filtered. Expected results: New mail should automatically be filtered since "Apply filters to new messages in INBOX on this server" is checked. Does this happen every time? This happens 99.9% of the time. New mail occasionally filters just after a manual filter or an expunge. Other information: I have tried completely deleting and recreating the account in Evolution, but this has had no effect.
same here, but not with a different imap server ...
Same here. Version is 2.10.2, remote IMAP server is Zimbra.
Same here with imap-accounts. If I apply filters manually with <ctrl>y in inbox of imap accounts, mails are moved to correct target folders.
Version 2.10.3 using gmail imap server. 90% of the time it will not apply filters to imap inbox. ctrl+y works fine and all pop3 accounts work. I have "Apply filters to new messages in INBOX on this server" checked. This is quite annoying and I've found similar reports dating way back on user lists and other distro support lists (I use fedora mostly).
I am seeing this bug on 2.12.0 as well. IMAP server is "Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1". What must be done to remove the "UNCONFIRMED" status from this bug? The original report is over a year old now.
*** Bug 494275 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 444503 ***
I have this bug still in Fedora 12 using Evolution 2.28.2 Any updates on this bug?
I have this bug still in CentOS 6.3 using Evolution 2.28.3 Any updates on this bug?