Overview
From this page you can check and maintain the Bayesian Database and manage the Bayesian Engine service.
The icon at the top of the page gives a general indication of the service:
- Green Icon (bayesian engine up, running and healthy)
- Yellow Icon (bayesian engine is up but insufficient data learned up to now)
- Red Icon (the bayes service has been stopped)
To disable the Bayesian Engine you can click the Disable yellow button in the top of the page. This is not suggested, but in some rare configurations this makes sense.
Bayes Database Information
The database health is very important to have a good performance on your system.
Bayes Service is a statistical process and as with all statistical analysis, low numbers can generate wrong information. The minimum quantity of spam and ham (not spam) messages learned is 200, or the service will not return a result.
Another important aspect is, as opposite, Bayesian database growth: a too-large database will impact seriously timing while analyzing the email body. To avoid this LibraCyber ESG will do automatic token expiration daily. You can force a manual expiration by clicking the Clean expired tokens green button. The expiration process will simply trash old tokens, keeping only the new ones.
In case the database gets corrupted or if the database contains a lot of bad information, the solution is to re-start with a clean Bayes database. To do this click on Reset Bayes red button in the bottom left of the page.
Note: For optimal performance, you should definitely keep the size of your bayesian database under 500.000 tokens.
TxRep Database Information
In order to improve the accuracy of the Bayesian Engine, the TxRep service keeps track of the average spam score for senders. TxRep then uses the average score to reduce the variability in scoring from message to message, and modifies the final score by pushing the result towards the historical average.
In this section are displayed how many tokens there are in the TxRep database. You can destroy all the tokens by clicking the Reset TxRep red button at the bottom of the page. The goal of this operation is to fix the TxRep behavior in case of wrong data learned.
As the Bayesian Engine database size, the TxRep database growth is an essential aspect. A too-large database will impact seriously timing while analyzing the email. To avoid this LibraCyber ESG will do automatic token expiration. You can force a manual expiration by clicking the Clean expired tokens green button. The expiration process will simply trash old tokens, keeping only the new ones.