https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6777
Kevin A. McGrail <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Kevin A. McGrail <[email protected]> 2012-03-19 22:05:28 UTC --- First, please realize that SpamAssassin doesn't really care about CAN-SPAM. That's a US law that says what is illegal. We generally use the definitive of SPAM as being mostly about permission and less about content or legal definitions. In the end, we use a lot of heuristics to best categorize what is most likely to be SPAM. Sometimes we make mistakes and sometimes there are unfortunately collateral damage trying to stop spammers. Unfortunately, your sample below isn't in a format that we can comment because it needs to include full headers including the received, for example. It would also be nice to have the report or the header showing what rules hit on the spam sample so we can see if there are rules that the SA project needs to tweak. Many installations use rules and configurations that are outside the project so we may or may not be able to do anything to help. Please add some samples and more information about what rules fired that led to it being tagged as spam. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
