Al Danks wrote:Matt Yackley <sare <at> yackley.org> writes:
header SUBJ_CANSPAM_SE Subject =~ /SEXUALLY-EXPLICIT/
The new rule(s) should also look for /SEXUALLY EXPLICIT/ (without the hyphen).
We've already gotten more of them than with the hyphen. My guess is that we will
need the rule(s) cover "innocent" mispellings like SEXUALY or EXPLICET.
But all in all this should make it easier to block this spam.
would doing:
header SUBJ_CANSPAM_SE Subject =~ /sexually\-?explict/i do that?
No, you'll want something more like: header SUBJ_CANSPAM_SE Subject =~ /sexually[\- ]explicit/i since you'll want to catch it with a space, or even: header SUBJ_CANSPAM_SE Subject =~ /sexually.?explicit/i if you want to catch *any* separator (or lack thereof).
Kelson Vibber
SpeedGate Communications <www.speed.net>
