https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6934
--- Comment #3 from John Hardin <[email protected]> --- (In reply to comment #2) > Oh sorry for I do not describe clearly I using MySQL for userpref and the > database is using utf-8 character set, > as I try to disable your mentioned plugin > Mail::SpamAssassin::Plugin::WhiteListSubject, I got; > > info: config: failed to parse line, skipping, in "(no file)": > blacklist_subject VIAGRA The config error is not surprising, you turned off the code that interprets "blacklist_subject". > In my database I have the following entry; > @GLOBAL blacklist_subject 清純可愛的學生妹 14 If you re-enable the WhiteListSubject plugin and remove that blacklist_subject entry from your database, does SA stop misclassifying messages? > and finally what do you mean "false positive message" the email header or > the debug LOG ? "positive message" = SA scored it as Spam "negative message" = SA scored it as Ham "true positive" = SA correctly classified it as Spam. "false positive" = SA incorrectly classified it as Spam, it's actually Ham. Thanks for posting your blacklist_subject lines. I think now that's all we need to reproduce the problem, but you are welcome to attach the headers from a misclassified ham message so that we have more evidence to examine. The Perl version change may indeed have broken the WhiteListSubject plugin with respect to non-ASCII target text. You will probably have to disable that blacklist entry until it can be fixed. -- You are receiving this mail because: You are the assignee for the bug.
