SenderInspector 1.0

SenderInspector is a professional solution designed to enable you to block outgoing spam mails for IIS. A spammer's main weapon is a false identity of the envelope sender. The Tool disarms a spammer and allows recipient and admin to see the true sender of SPAM.

Install SenderInspector if you want always to know the true sender address and to avoid mass mailing of spam from your servers. There is nothing in the SMTP standard that can cause a sending site to send the true envelope sender identity. The SenderInspector is a middleware that corrects described disadvantage and causes a sending site to tell the truth in the envelope sender specification.

In order to do it tool provides two engines for fight against SPAM: the signature of a sender - extra (hidden) header in email messages and the mailing log - Event Log in a light data base. It allows you to track SPAM even if customers can send emails anonymously. You can use any one of these engines or both at once.

The tool includes a set of mail Helpers for parent components of IIS and the Tracker. Helpers on the fly insert a new extra header in the outgoing email messages. The extra header shows a path to the virtual directory and name of the email script. So you can easily find the unique customer name and his website and STOP SPAM.

The Tool supports Helpers for the following IIS components: aspSmartMail, CDO, CDONTS, JMail, Persits, SMTPsvg, System.Web.Mail, System.Net.Mail, ColdFusion. The Tracker is the second tool for fighting against SPAM. It works independently of Helpers and is ISAPI filter. Goal of Tracker - saving info about outgoing email in the light data base.

The tool saves in data base the following info: URL of site, date/time of message, fields: subject, to, from, cc, bcc. Helpers also save info about outgoing email in a own Event Log. Helpers save in Log the following info: URL of site, date/time of message, fields: subject, to, from, cc, and body of message. This info also allows you to TRACK and STOP SPAM

Limitations:

· Identic text of message body;
· Amount of attempts: 30 (however after restarting of IIS the algorithm can be repeated)