Features in detail
SMTPTracker's features are described here in detail

Features
Assassin2Exchange filter - message routing to user junk mail folders on Exchange 2003 based on SpamAssassin front-end server score (see scrrenshots)
Spam Confidence Level based routing
SCL Router chaining
Active Directory integration
Message tracking and saving
Tested and proved filtering methods
Dual point message filtering
DNS blacklists based connection filtering
DNS whitelists support
IP blacklist and whitelist
Blocked senders list
Content filtering
Online/Onscreen statistics
Log Viewer
Co-existence and requirements

Spam Confidence Level based routing (Exchange 2003)
When SMTPTracker is installed on Exchange Server 2003, messages detected as unsolicitated (spam) by Connection or Content Filters can be dropped or routed to users' Junk Mail folders. This feature (SCL Routing) is provided by adding Spam Confidence Level headers to passing messages. These headers are then resolved by Exchange Server and messages are routed to Junk Mail folders. Administrator can decide, whether to apply SCL Routing to Connection Filter, Content Filter or both.
Message placed in a user's Junk mail folder can be designated as "not spam" by user. All future mailings from marked sender will be delivered to the user's Inbox, regardless of the SMTPTracker's detection. Users can manage their SPAM-Lists by themselves using Outlook client or Outlook Web Access.
This feature extends Exchange Server 2003 features, where messages detected by blacklist or DNS based blacklist connection filter are always dropped. With SMTPTracker they can be passed to users' Junk Mail folders. Administrator can decide, what action will be taken. With SCL Routing administrators do not need to answer questions about lost messages.
Top

SCL Router chaining
If the front-end server is not running Exchange 2003 and SCL Routing is required, SMTPTracker offers a feature called SCL Router Chaining . If SCL Router Chaining is enabled, SMTPTracker (or SpamAssassin) running on front-end server marks incoming messages detected as SPAM with it's own signature. SMTPTracker running on back-end server then resolves this signature and adds SCL headers to the message. Back-end server can also route messages on SpamAssassin score basis.
This feature adds ability to use Spam Confidence Level based routing when front-end server is not running Exchange 2003. Version 3.0 includes Assassin2Exchange filter, which converts spam score headers provided by fron-end server running SpamAssassin to Exchange SCL value.
Top

Message tracking and saving
Information about each passing message can be logged to SQL server, logged fields are Sender, Sender's IP, Sender's hostname, Recipients, Date and Time, Server, Subject, Attachments and Content Size. Copies of messages matching specified sender or recipient can be saved to disk. Each rule has it's own folder for saving, so messages of particular sender or recipient are easy to find.
Top

Active Directory integration
SMTPTracker integrates with Active Directory and enables rejecting messages sent to non-existent users before they enter your system. This feature reduces system resources usage, as tons of NDR's are no longer generated.
Top

Tested and proved filtering methods
SMTPTracker does not contain filtering methods which were not proved useful. SMTPTracker is designed with performance in mind.
Top

Dual point message filtering
SMTPTracker filters messages before arrival and on arrival. Detected SPAM is dropped, redirected to spambox or SCL routed and can be logged to SQL server. Logged fields are Sender, Sender's IP, Sender's hostname, Recipient, Date and Time, Server and Rule which blocked the connection. You can set up your own custom message, which is sent back to sender, if the connection is to be dropped. SMTPTracker's unique feature - Software Confidence Level based routing - enables redirecting messages detected as SPAM by well-known connection filters (DNS blacklists, IP blacklists...) to user's junk mail folders.
Top

DNS blacklists based connection filtering
One of the SMTPTracker's key features is DNSBL connection filtering, which is proved to be the most effective way to block unsolicitated messages. SMTPTracker supports multiple DNS blacklist services (like www.spamhaus.org or www.dsbl.org) used simultaneously. SMTPTracker comes with a predefined set of DNSBL services, which can be extended with services of your choice.
Top

DNS whitelists support
SMTPTracker supports public DNS based whitelists like Bonded Sender. These services provide lists of trusted senders.
Top

IP blacklist and whitelist
SMTPTracker allows you to block specific IP addresses (or IP network ranges) from sending messages to your system by adding them to your blacklist. Specific IP addresses (e.g. your local servers, business partners) can be excluded from filtering by adding them to your whitelist.
Top

Blocked senders list
Last rule used with connection filtering (before arrival) is Blocked Senders List. If sender matches one from the list, message is detected as SPAM.
Top

Content filtering
Content filter scans full content (including all message headers) for specified keywords or phrases. Each specified phrase has four options, which define how is the scan performed - exact match, word starts with keyword, ends with keyword, contains keyword. These options have one sub-option specifying whether the search is case sensitive or not. Content checker has a property called Threshold, which defines how many of specified keywords must message contain to be considered unsolicitated (SPAM). You can also set IP Exclusion list, which defines IP addresses from which the messages are not content checked (you want to exclude your local smtp servers from content check usually).
Detected SPAM messages can be dropped, redirected to spambox or delivered to users. When detected messages are passed to users, content checker includes custom prefix before message subject. With this prefix included, detected messages can be redirected to user's custom folder using Outlook (or other client) rules.
If SMTPTracker is installed on Exchange 2003, detected messages can be routed to users' Junk Mail folders by SCL routing. In this case prefix is not added. When using SCL routing drop, pass and redirect options are disabled.
Some of the anti-spam content filters are not able to check all mail headers, SMTPTracker does it.
Top

Online/Onscreen Statistics
SMTPTracker displays online statistic and trafficlog. Message counts, infos and status information are displayed.
Top

LogViewer
SMTPTracker installation includes simple Log Viewer , which can be used for quick preview of tracked data stored on SQL Server. Detailed analysis of log tables can be performed using any kind of SQL tool.
Top

Co-existence and requirements
SMTPTracker can co-exist with any of Exchange or SMTP plug-ins, McAfee Groupshield for Exchange, McAfee Spamkiller for Exchange or other AV software.
Requirements: Microsoft® Windows 2000/2003/XP, Microsoft® SMTP service (or Exchange Server 2000/2003) installed, MDAC 2.7+, Microsoft® SQL Server or Microsoft® SQL Server Desktop Engine for logging, Microsoft® .NET Framework.
Top