This manual was updated in June 2005 and corresponds to v2.1 of Praetor which was released in April 2005.
Resource leaks in the Praetor filtering components: prLog and COM+ applications causing memory usage to increase over time. At some point resources would be exhausted and Praetor would no longer be able to log message summary entries into the SQL database.
If a triggered rule involved an on-the-fly list with many entries, the logging would fail because the reason text was excessively long. The application and system event logs would show that PrLog.EXE abnormally terminated and restarted.
When viewing a quarantined message in the administration program, it was not possible to add the sender address or domain to the appropriate list and caused the program to crash.
If a message addressed to multiple local recipients was quarantined, only the first recipient would be able to see it in PLGV. Upon releasing that message for all the recipients, only the person releasing would receive the message.
PLGV error when the IIS web server uses a regional date format different from MM-DD-YYYY.
Bayesian token database is now cached in memory to speed up filtering almost doubling the message through-put. This also extends the usability of the free Microsoft SQL Desktop Engine (MSDE), allowing it to accommodate more users than previously.
Administration program now has additional searching capabilities based on message properties: direction, triggered rule name, From, To, and Subject.
Custom condition now allows testing for more fields:
RFC-2821 protocol: MAIL FROM, RCPT TO
Message header: From, Sender, To, and Cc addresses, subject and message body
CMS now recommends the use of message rule level DNS blacklist lookup and filtering instead of the protocol level due to spammers' changing tactics that can simulate a denial-of-service attack.
Several tools are provided to help manage the Praetor SQL log database.
FAQ on how to add an IP address, range, or domain name to the local IP blacklist.
This manual corresponds to Praetor v2.0 which we call Praetor G2 or just G2, the second generation of our email filtering product.
Change of SMTP server to the native Windows server resulting in greater performance.
New techniques were added to combat the growing problem with unsolicited commercial email known as spam.
Bayesian statistical filtering of the message content
Message heuristics based on tests performed on the message header and body
Weighted words to test the message body
Self-service features so that local users can release their own quarantined messages.
Ability to create your own user list for use with a custom condition that allows you to choose what message header to test.
Those upgrading from Praetor G2 v2.0 to v2.x can read about the upgrade process on this page.
If you are upgrading from the older Praetor v1.5 to Praetor G2 you can read about the differences between these versions by clicking here. With the Bayesian statistical processing, Praetor G2 performs numerous computations for each message so the PC requirements are higher. Click here to see our equipment recommendations.