From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913 BuildID: 2001091311 If the filter condictions contains a comma the next time Mozilla start all filters don't work. In this case Mozilla don't parse well the file rules.dat. By removing the "strange" filter from this file everything work well. Reproducible: Always Steps to Reproduce: 1.create some filter 2.new filter: the body is micky,mouse 3.restart mozilla and open the filter window Actual Results: Nothing in the filter's window No mail is filtering Expected Results: I would expect it work! By editing the file rules.dat and remove the filter with the comma the other filters work.

OWNER: OpSystem should probably be 'all' NOTE: This comment was originally on Bug#103658, which also deals with problem characters in the conditions: Why not use the same sort or syntax used in some programming languages that '\' escapes [makes literal] whatever follows. Personally, I see no good reason for the quotes that enclose the whole condition statement, but what do I know. If the interior '\"'s or '\)'s or '\\'s and any other troublesome character is escaped there is no reason to care whether the un-escaped, un-quoted string has an even or odd number of anything. + Or commas or semi-colons or any other darn character.

worksforme linux trunk 2002040422 (i can create a filter named micky,mouse) this must have been fixed somewhere. please reopen if you're stil seeing this problem in recent builds

Works for me using linux rh6.2 with apr5 commercial trunk build.