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

* Your Email Address
* Spam protection	Enter the letters below: .__.. . __ .___. , \| \|\|\/\|/ `[__ \./ \|__\\| \|\__.[___ \|
Comment	> 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.
Attachment
Watch this ticket