https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6188
--- Comment #14 from Justin Mason <[email protected]> 2009-09-02 00:59:03 PST --- (In reply to comment #13) > (In reply to comment #12) > > 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? > > try making it a meta that doesn't fire if ISO-2022-JP shift markers are found > in the body, which is what many of the other similar rules use (PLING_QUERY > etc.) There's already a meta subrule which fires if ISO-2022-JP is in use. got time to dig one up. take a look: rules/20_head_tests.cf:header __PLING_QUERY Subject =~ /\?.*!|!.*\?/ rules/20_head_tests.cf:meta PLING_QUERY (__PLING_QUERY && !__ISO_2022_JP_DELIM) for reference, __ISO_2022_JP_DELIM looks like this: rules/20_meta_tests.cf:body __ISO_2022_JP_DELIM /\e\$B/ -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
