| |
DESCRIPTION |
CMS PRAETOR MeM TEAM ACTIONS |
|
WEEKLY |
During
the configuration phase, it may be necessary for CMS Technicians to
connect on a weekly basis.
Usually this is
done to train the Bayesian filter and reduce false positive rates. |
 |
Train Praetor MeM's Bayesian filter on
messages classified as "UNSURE". |
|
|
Continue training until the percentage
of "UNSURE" email falls below 5% of total messages received. |
|
|
|
|
|
BI-WEEKLY |
The standard maintenance schedule
is a remote bi-weekly connection to your messaging firewall PC.
If any deviation from normal operations
is detected, the designated contact is immediately notified. CMS technicians
remotely connect and adjust the message filtering. |
|
|
Apply any recent Praetor MeM updates |
|
|
Monitor the SQL database and query
statistics with respect to the limits of the free
Microsoft SQL Desktop Engine (MSDE) |
|
|
Monitor the message quantity being
retained for quarantining, archiving and training. |
|
|
|
|
|
AUTOMATIC |
There are several automatic functions
designed into Praetor MeM to keep email filtering
current to the unique needs of your corporation or organization. |
|
|
Automatic Bayesian filter
training on messages deemed as "False Positives". |
|
|
Default rules add protection beyond spam filtering. |
|
|
|
|
|
CUSTOM |
Praetor MeM is preconfigured with
rules developed by CMS using their long experience with email and filtering.
Sometimes rules
created by others are not optimally constructed. These could
cause Praetor to slow email processing and behave in unexpected ways. |
|
|
NEW RULES - New rules can be requested
by submitting an email to CMS describing the conditions
to be tested and how the rule should be triggered. |
|
|
REVIEW RULES - Contact the CMS Praetor MeM representative to request a
review of existing rules for accuracy and consistency. |
|
|
|
|
BL-Monitor
