Preventing Spam And Getting Even

Blocking those nasty spambots is a real pain I agree. I have seen bots that go through the trouble of parsing e-mail addresses after processing the web page through a browser. What's worse is that spam, like viruses, change in their formats and delivery methods.

So how do we kill SPAM and get even all at once?

Hide E-mail Information: First use form based e-mail that is run though server side programs so that your e-mail address is not revealed in the first place. CGI is ideal for this. At the end of the article I will have a scripts for download for you to use for free. Several hundred scripts are avalible on the web in almost every programming language free to download in varying complexity of features and use.

The Block: IP addresses, which compose the basis of Internet traffic are logged by each user with the date to prevent abuse with a maximum number of messages defined to accept (such as 3 messages an hour). If they hide their IP address they will be blocked altogether. Additionally cookies can be sent to the user to keep a count of how many messages they sent. This is a easy script to write in any server side language such as CGI/perl/php etc. A e-mail at the end of a time period can then be sent to notify you of any gross offenders through an agent scanning your logs.

The Detection: Detecting SPAM should be done at three stages on an e-mail server to provide a maximum amount of protection from viruses and SPAM alike for a single organization. Advertisements can then be sought out, filtered, deleted, or rejected.

   

Stage 1: When the e-mail is going to be received by the e-mail server, it should be     scanned by e-mail address, originating server, subject, and message content. Messages     that fit the shape of Spam will then be rejected. A simple log working with an agent     can be used here to find repeat offenders to notify your administrator.         ergonomie

Stage 2:     Use the best filters of all to generate rules about what is constituted as Spam are     your user base, therefore it makes sense to have a feedback based agent to monitor     what your users mark as Spam. At this levels users should be able to set up filter     rules to add to what is considered as Spam for their inbox. Some sort of filters     set up for categories such as "Spam" and "virus" should be in affect on all servers.         Клиника лазерная коррекция зрения стоимость. Ботанический сад.

Stage 3:     Complete the circle by tying personal filter rules to the servers rejection rules.     An agent can keep track of what e-mails are Spam for each user, then triangulate     these rules through multiple users.

Getting Even: Knowing what these bots look for, and how they operate is key. They spider hyperlinks over your entire site where there will be likely e-mail address. We have a bsadress@bsdomain.com generator, which is hyperlinked and named directory.cgi to our contacts section. Imagine if the spammer was caught in the mail out by getting tens of thousands of mailer daemons. Any competent server admin from an ISP would catch them with all the complaints being sent to them.

The Next Level of Spam Prevention will be to link your mail program agent to a channel used by the FBI or other organization with a copy of your log files. Law enforcement can then go nab the offender easily. Unfortunately neither an established channel has been put into place, nor has an solid amount of legislation been put into place as of the writing of this article.

I first published this article in part at "A List Apart" where I was encouraged by email to expand on this article.

Spam Prevention Scripts