[ingo] Ingo filter logic problem

[w3sz]

I seem to be seeing a problem with Ingo's filter logic that I will describe
below. 

I am running Horde 3.1.7 on Ubuntu 8.04 with kernel 2.6.24-19-generic #1
SMP.

I am using Courier-IMAP v. 4.3.0.20081027-1ul

My Horde Application versions are:

    * Chora: H3 (2.0.2)
    * Forwards: H3 (3.0.1)
    * Gollem: H3 (1.0.3)
    * Horde: 3.1.7
    * Imp: H3 (4.1.4)
    * Ingo: H3 (1.1.3) 
    * Kronolith: H3 (2.1.5)
    * Mnemo: H3 (2.1.1)
    * Nag: H3 (2.1.3)
    * Passwd: H3 (3.0) 
    * Turba: H3 (2.1.7) 
    * Vacation: H3 (3.0.1)

My PHP Version is PHP Version: 5.2.4-2ubuntu5.3
   
The problem with the Ingo filter logic is with the 'and' function.  The Ingo
filter always removes any message that satisfies the last item in the 'and'
string, just as if that item was 'or'ed, not 'and'ed.

Here are some examples:

A.  Rule 1 says "delete if subject contains 'delete' and subject contains
'big'".
Rule action for message with:

1.  Subject "delete big''  --> deleted
2.  Subject "delete" --> not deleted 
3.  Subject "big" --> deleted

Actions 1 and 2 are correct, 3 is not.


B.  Rule 2 says "delete if subject contains 'large' and subject contains
'small'".
Rule action for message with:

1.  Subject "large small''  --> deleted
2.  Subject "large" --> not deleted 
3.  Subject "small" --> deleted

Actions 1 and 2 are correct, 3 is not.


C.  Rule 3 says "delete if From contains 'Garrett' and Subject contains
'FW:'"
Rule action for message with :

1.  From "Garrett" and Subject "FW:" -->  deleted
2.  From "Catherine and Subject "real" --> not deleted
3.  From "Catherine" and Subject "FW:" --> deleted

Actions 1 and 2 are correct, 3 is not.


D.  Rule 4 says "delete if subject contains 'large' and subject contains
'small' and subject contains '#######'"
Rule action for message with:

1. Subject "large" --> not deleted
2. Subject "large and small" --> not deleted
3. Subject "small" --> not deleted
4. Subject "large and small and #######" --> deleted
5. Subject "#######" --> deleted

Actions 1 and 2 and 3 and 4 are correct, 5 is not.

This seems to be a simple logic error in the coding of Ingo.  It is
consistent in every example I try. I do not think it would relate to my
particular setup.  Since I create the filter just by making selections from
the Ingo GUI, I do not think the incorrect behavior is a result of anything
that I am doing wrong.  I post these results here for comment.

Thanks!



-- 
View this message in context: http://www.nabble.com/Ingo-filter-logic-problem-tp18924015p18924015.html
Sent from the Horde - Ingo mailing list archive at Nabble.com.