[Tickets #13149] Filter rules fail depending on mumber of rules and all/any setting

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13149
------------------------------------------------------------------------------
  Ticket             | 13149
  Created By         | aria at bsc.gwu.edu
  Summary            | Filter rules fail depending on mumber of rules and
                     | all/any setting
  Queue              | Ingo
  Version            | 3.1.4
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


aria at bsc.gwu.edu (2014-04-25 15:02) wrote:

Hi,
Let me preface by saying that my IMAP server does not support UTF8  
characters and this is how I noticed this bug.

Create a filter rule as follows:

1-Select 'ANY of the following'
2-For field, pick anything (I used Subject or Sender).  Then select  
'Contains', then type in any string to check.
3-Now add two more like the one in the above step for a total of 3  
checks to be 'ORed' together in this single filter rule.
4-Save the rule.

When a rule contains 3 or more checks as in the above and they are  
ORed, you will get this error on the server and no filter is executed  
and no response or error is given to the user:

ERR: HORDE [imp] Charset used in search query is not supported on the  
mail server. unsupported CHARSET specified [pid 18030 on line 570 of  
"/data/www/horde/imp/lib/Imap.php"]

Here is the interesting part:

a) If you edit the rule and remove just one of the criterion, leaving  
just 2 possible checks.  Then the rule executes without error.

OR

b) if you edit the rule with the 3 or more criteria and change the  
selection from 'Any' to 'All the following' causing them to be 'ANDed'  
then all is well and the rule executes with 3 or more criteria!

Thanks,

Aria