David B Funk wrote:
I would like to suggest expanding the FS_TEEN_BAD test to handle this new case:
##{ FS_TEEN_BAD
header FS_TEEN_BAD Subject =~
/(?:teen|girl|boy).{1,15}(?:pussy|sex|slut|ass|fuck|rape)/i
describe FS_TEEN_BAD Subject says something bad about teens
##} FS_TEEN_BAD
Unbounded matches are FP fodder,
Use '\b' (word boundary) metasymbols to bound matches.
EG:
/\b(?:teen|girl|boy)\b.{1,15}\b(?:pussy|sex|slut|ass|fuck|rape)\b/i
Of course then you get into the plural(s) and other variation match
chase. (EG, "teen" vs "teens" etc).
David, excellent point. Let me see if I can adjust what you added and catch
some of the many variations.
##{ FS_TEEN_BAD
header FS_TEEN_BAD Subject =~
/\b(?:teens?|girls?|boys?).{1,15}\b(?:pussy|sex(?:xy|ual)?|slut(?:s|ty)?|ass(?:es|fuck(?:ing|ed)?|whip(?:ing|ped)?|spank(?:ing|ed)?)?|fuck(?:ing|ed)?|rap(?:e|ed|ing)+)\b/i
describe FS_TEEN_BAD Subject says something bad about teens, girls, boys
##} FS_TEEN_BAD
I considered leaving off the final end word boundary because there are so many
possibilities. But I decided to try getting in touch with my "dark side" and
cover as many variations as I could think of. :-)
As written above, this still triggers on the original email that set off this
quest. And I think with the most recent changes it will be very unlikely to FPs.
But those could always be "famous last words".
Did I miss anything?
--
Andy Dorman
Ironic Design, Inc.
AnteSpam.com, HomeFreeMail.com, ComeHome.net
