Settings and activity
6 results found
-
179 votes
Mr_Pool_Shot
supported this idea
·
An error occurred while saving the comment -
5 votesMr_Pool_Shot
supported this idea
·
-
20 votesMr_Pool_Shot
supported this idea
·
-
3 votesMr_Pool_Shot
supported this idea
·
-
9 votesMr_Pool_Shot
supported this idea
·
-
39 votesMr_Pool_Shot
supported this idea
·
Faced with a similar problem about 20 years ago in the way of spam about the trademark V pill and when SpamAssassin was just a baby. We created and sold an eMail filtering package that included a program we called WordAssassin to identify bad words. Users were able to add good and bad words to a couple of lists and every time an eMail came in Procmail would run WordAssassin which would give the desired output. Actions included removing the word, returning "bad word" found, adjusting the subject line, return value, and so on.
Most of the world and ourselves started with a REGEX but that didn't really work too well to catch the message and every time an eMail came in a Perl program would run the tests. Needless to say, this overloaded the 450Mghz servers and would still be quite the task given the workload here. Furthermore, it didn't catch all the manipulations of the words very well. We created a C++ program to handle all the fun stuff spammers were doing to get their message thru spam filters and to the user. My old sales pitch seems to fit here so, here we go.
It was always difficult to explain how spammers were using different character sets, spaces, etc, but they were already seeing it anyway. I would explain we had built an extremely fast C binary that performed a variety of tests to detect and provide short ***** protection, longer ***** protection, mangled ***** protection, HTML ***** protection, and so on. YEP, It got a lot of laughs and the product is still running somewhere most likely today.
The core engine.cpp would solve this problem and has been available for licensing or for some good use for quite some time now at wordassassin.com