Fri, 10 Apr 2026 14:37:25 +0000 https://bugs.horde.org/ticket/3313 putting commas in text to match generates bad rules 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. Fri, 20 Jan 2006 21:28:39 +0000 https://bugs.horde.org/ticket/3313#t15779 This is the intended behaviour, see ticket 1105. But maybe we should check if one of the values is empty. Sat, 21 Jan 2006 00:33:33 +0000 https://bugs.horde.org/ticket/3313#t15787 A check has been added to make sure that no empty headers or addresses can be added to the test accidentally. Mon, 24 Apr 2006 12:41:06 +0000 https://bugs.horde.org/ticket/3313#t19378 The sieve script now says: header :comparator "i;ascii-casemap" :contains "Subject" "Amazing" The trailing comma is missing. Tue, 25 Apr 2006 03:16:21 +0000 https://bugs.horde.org/ticket/3313#t19434 Try now? Wed, 26 Apr 2006 17:26:00 +0000 https://bugs.horde.org/ticket/3313#t19492 Looks good. Wed, 26 Apr 2006 19:10:19 +0000 https://bugs.horde.org/ticket/3313#t19494