(In reply to comment #45)
> between 1.5 and 2.0, we starting running filters after the fact on the local
> database instead of the imap server, which is what broke this for imap. We did
> this partly because some imap servers don't support search, or their search
> support is broken, and people complained that filters worked on incoming mail,
> but not after the fact...
>
I am still using 1.5.0.12. I still see the behavior where it works on incoming, but not after-the-fact. I see others commenting that this broke with 2.x. Or are they saying that with 2.0 filtering on custom headers no longer works even on incoming?
Also: you say that it is searching on the local db rather than the imap server that has broken it ... why would it not work on the local db?
(In reply to comment #45)
> between 1.5 and 2.0, we starting running filters after the fact on the local
> database instead of the imap server, which is what broke this for imap. We did
> this partly because some imap servers don't support search, or their search
> support is broken, and people complained that filters worked on incoming mail,
> but not after the fact...
>
I am still using 1.5.0.12. I still see the behavior where it works on incoming, but not after-the-fact. I see others commenting that this broke with 2.x. Or are they saying that with 2.0 filtering on custom headers no longer works even on incoming?
Also: you say that it is searching on the local db rather than the imap server that has broken it ... why would it not work on the local db?