https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6188
--- Comment #12 from Warren Togami <wtog...@redhat.com> 2009-09-01 17:57:48 PST --- - rawbody __OBFUSCATING_COMMENT_B /[^\s>](?:<![^>]*>)+[^\s<]/ + rawbody __OBFUSCATING_COMMENT_B /[^\s>!\x23](?:<![^>]*>)+[^\s<]/ I was able to make it skip #<! and !<! with the above change. I now discover that there are clearly too many possible characters that can be immediately before a <! in legitimate ISO-2022-JP encoded text. ^[$B:#=5$N%a%k%^%,$O!"7HBS$d%]!<%?%V%k%*!<%G%#%*$G;H$($k^[(BBluetooth(R)^[$BBP1~^[(B ^[$B%]!<%?%V%k%9%T!<%+!<$H!"%*%H%/$J%-%c%s%Z!<%s$N$4>R2p$+$i$G$9!#^[(B This sample alone has ] and a few ASCII letters. I believe this is unfixable. Even with decoding you run into linguistic reasons why the English-based assumptions of this rule fail. We are probably best off disabling this rule for 3.3.0? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
