GNOME Bugzilla – Bug 234067
Filters mostly not working with Exchange 5.5 IMAP
Last modified: 2003-02-24 09:29:44 UTC
As requested by fejj :) Mostly (like 99% of mails as far as I can tell) to not get correctly filtered by Evolution 1.2 for me. My server is Exchange 5.5 (eew) and I connect to it by IMAP. Will be attaching the same mail log generated with CAMEL_VERBOSE_DEBUG set to 1 as on #33798 as well as my filters.xml and a couple of example mails that should have been filtered, but were not. Note that when I select mails and do ^Y to apply filters, all mails are filtered correctly. I'll attach one mail from a mailing list and one that was automatically generated by one of our UNIX servers.
Created attachment 41737 [details] filters.xml
Created attachment 41738 [details] This is an email from a list that was not filtered correctly
Created attachment 41739 [details] CAMEL_VERBOSE_DEBUG=1 log
Created attachment 41740 [details] Mail from a server that should have been filtered, but wasn't
wait... you mean POP right? because according to the log, you are only checking POP mail.
ok, n/m - your sample messages claim to be from IMAP so the only thing I can think of is that you don't have evolution configured to filter your IMAP folder (there's a checkbox you need to check in the account editor)
Nope, it's not that, I've noticed subsequently that mail in the INBOX on the IMAP server is filtered correctly when Evolution starts, it's mail that arrives while Evo is open that doesn't get filtered correctly. (sorry had forgot to mention I also have a profile with POP3)
Just wondered whether any progress had been made on this, if there was any further testing you'd like me to do?
Just to mention, I have the same problem with 1.2.1
this is another duplicate of the "my IMAP server isn't marking my messages as \Recent" bug, which is like impossible to work around.
*** This bug has been marked as a duplicate of 230470 ***
The thing is that this worked fine in every version up to 1.0.8, it only stopped working when I upgraded to 1.2.0, so obviously it's something that's changed in Evo that's broken it. :/