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

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