http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5701
------- Additional Comments From [EMAIL PROTECTED] 2007-10-25 11:50 ------- > In the case of phishes, I'd suggest that we mark the mail as spam, and have a > new "PHISHING" rule, which always fires if the mail is considered phish. > Therefore we have 3 states: > > nonspam (score < required_score threshold, "X-Spam-Flag=NO") > spam (score >= required_score threshold, "X-Spam-Flag=YES", > "X-Spam-Status !~ /PHISHING/) > spam,phish (score >= required_score threshold, "X-Spam-Flag=YES", > "X-Spam-Status =~ /PHISHING/) > > Conceptually, "phish" is just considered a subset of "spam", and conveniently > enough we don't have to change the SpamAssassin code APIs ;) > > This is also similar to how ClamAV treat phishing, too. We just wouldn't want the plugin's decisions to effect the training of the spam emails later on. What you suggest sounds like a good option, especially if it works well with ClamAV. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
