[Tickets #5610] Re: Filters do not work if they contain OR

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5610
-----------------------------------------------------------------------
 Ticket             | 5610
 Updated By         | robin.west at dal.ca
 Summary            | Filters do not work if they contain OR
 Queue              | Ingo
 Version            | 1.1.2
 Type               | Bug
 State              | Feedback
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


robin.west at dal.ca (2007-08-16 10:37) wrote:

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

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