|
SMTPTracker 3.0.D
Anti-SPAM Protection
and Message Tracking
for Windows Based SMTP Servers, SpamAssassin and Exchange Integration Solution.
3.0.D2 with Assassin2Exchange filter available for download here
SMTPTracker extends your windows based SMTP server with message tracking, mail capture and content saving, Active Directory integration, sql logging, spamassassin spam score to scl value conversion (with Exchange 2003) and various other anti-spam abilities. SMTPTracker works with Microsoft SMTP service, Exchange Server 2000, Exchange Server 2003 and other systems based on IIS smtp service.
Assassin2Exchange filter (SpamAssassin to Exchange Spam Confidence Level conversion utility) which was released with v2.0 is now a part of SMTPTracker. This utility offers custom header conversion from spamassassin spam score (level or stamp based) to Exchange 2003 SCL value - Exchange server with S-Tracker installed is able to route messages to user junk mail folders according to front-end spamassassin server spam score. If you need some advice how to enable it see the FAQ or send questions to info@smtptracker.com.
Key benefits: low cpu usage, realtime anti-spam filtering, message content tracking, logging and saving, Active Directory integration, SpamAssassin support, logging to SQL database, Spam Confidence Level based routing, DNS based blacklists and whitelists... check features section.
SMTPTracker's core binds itself to smtp service transport core. When enabled, it filters all messages passing through SMTP server. SMTPTracker can co-exist with other smtp filters installed on server.
Partner for Germany - Seceidos GmbH&Co. KG
Download trial and mail to info@smtptracker.com for information how to register.
Also available via 
|
| |
We constantly monitor the demand for porting s-tracker to Exchange
2007. If this is what you need, please give us an info.
ADCheck was updated in 3.0.D1 version - ADCheck can now handle multiple RCPT TO commands and filter non-existent recipients without dropping connection. In prior versions connection is always dropped after first RCPT TO command for non-existent recipient. That saves server resources but may cause messages for multiple recipients not being delivered when one of the recipients does not exist. If you prefer this behavior, check "Drop connection immediately when rcpt not found".
|
|
|
