[Tickets #3313] NEW: putting commas in text to match generates bad rules

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=3313
-----------------------------------------------------------------------
 Ticket             | 3313
 Created By         | liamr at umich.edu
 Summary            | putting commas in text to match generates bad rules
 Queue              | Ingo
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


liamr at umich.edu (2006-01-20 13:28) wrote:

Another report from our help desk..  basically, if you create a sieve rule
that tries to match a subject string with a comma in it ( eg...  "Amazing,"
), the comma gets mistranslated when the sieve script is generated.

SQL sez..

    [field] => Subject
    [type] => 1
    [match] => contains
    [value] => Amazing,

but, the sieve script sez...

    header :comparator "i;ascii-casemap" :contains "Subject" ["Amazing",
""]

and the "" ends up matching ALL rules.  

I've tried this with CVS HEAD from this PM (1/20/06) and w/ Ingo 1.0.2.