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

noreply at bugs.horde.org noreply at bugs.horde.org
Thu May 8 05:25:29 UTC 2014


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

Ticket URL: http://bugs.horde.org/ticket/13149
------------------------------------------------------------------------------
  Ticket             | 13149
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Filter rules fail depending on mumber of rules and
                     | all/any setting
  Queue              | Ingo
  Version            | 3.1.4
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-05-07 23:25) wrote:

Your IMAP server is broken.

Your AND search:

C: 3 UID SEARCH UNDELETED SUBJECT Webmail SUBJECT BSC SUBJECT "BSC Webmail"
S: * SEARCH 620
S: 3 OK UID SEARCH completed

This is OK.

Results from OR search:

C: 3 UID SEARCH UNDELETED OR (SUBJECT Hello) (OR (SUBJECT BSC)  
(SUBJECT Webmail))
S: 3 NO [BADCHARSET (US-ASCII)] unsupported CHARSET specified
>> Command 3 took 0.0041 seconds.

Specifying a charset in a SEARCH/UID SEARCH command is optional.  In  
lieu of specifying charset, the server *MUST* support US-ASCII.  See  
RFC 3501[6.4.4]: "US-ASCII MUST be supported; other [CHARSET]s MAY be  
supported.".

All strings in this query are in US-ASCII, so if the IMAP server is  
misparsing this SEARCH string, there's not much we can do about it.

(Note that the query generated by Ingo is actually: "All UNDELETED  
messages with a subject of either Hello, BSC, or Webmail".
But this is expected, as the UNDELETED query is added to the  
user-defined query - we don't filter messages already marked as  
deleted.)

In short, I guess I don't see this as an issue to be fixed in Horde  
but rather something that needs to be fixed in the IMAP server instead.





More information about the bugs mailing list