Hi Chuck - I just did some testing using 1.2-alpha (with horde 3.1.4) 
and the filters seem to be working just fine now (both AND and OR 
cases).

I've just tested both the Or and the And cases, with at least three 
rules, and they work as they should. I'm testing with Horde 3.2-cvs 
and Ingo 1.2-cvs; there have been a lot of bugfixes in Ingo recently 
so unless someone can reproduce this with the current code I see this 
as a fix in 1.2.

We're at Horde 3.1.4.



-Robin

What Horde version are you using? There were fixes for OR searches in 
Horde 3.1.1.

Hi - we just upgraded to 1.1.3. When using an 'OR' filter (i.e. "match 
any of the following"), it seems to miss the first item. For example, 
if I set up a filter with these criteria:



Subject Contains 'foo'

OR Subject Contains 'bar'

OR Subject Contains 'baz'



then it filters messages with 'bar' or 'baz' in the subject line, but 
not messages with 'foo'.



Also, when using 'AND' ("match all of the following") ... it seems to 
be matching the last rule in the filter regardless of the previous 
rules. So for example if the filter is set up like this:



Subject Contains 'foo'

AND Subject Contains 'bar'

AND Subject Contains 'baz'



Then any message with 'baz' in the subject gets filtered, even though 
it does not contain 'foo' and 'bar'.



Hope this helps. We are using Ingo 1.1.3 with Horde 3.1.4, IMP 4.1.4. 
I'm not sure which backend it uses, how do I check that? We haven't 
changed anything in backends.php. Our preferences backend is postgres 
7.3.19-RH.



-Robin

Please try either Ingo 1.1.3 or 1.2-ALPHA, and if you still have 
problems, say which filtering backend you're using.

Filters stop working with this release... previously they have always 
worked...

I tried to remove all the filters and start adding new filters and 
noticed that filters work only if they contain only one condition: if 
I use "match any of the following" they don't work anymore... (they 
are simply not applied: I get no error message)