RBLs

• Enable Real-time Black Lists - If enabled, you will be able to set up RBL detection rules to help detect potential SPAM.
• Real-time Black Lists - This is a list of the existing RBL rules.
• Add Preset - This allows you to add preset RBL rules.

Add / Edit RBL

• Enable Real-time Black List - If enabled and Real-time Black Lists are enabled, this RBL will be evaluated.
• Name - This should be unique and descriptive of the RBL rule. This is used only as a display name and also within the logs.
• DNS Lookup String - This is the string which is formatted into a DNS lookup request. Each RBL server will have a particular method in which their DNS lookup string should be formatted. This information is usually provided by the organisation that operates the RBL.
• Refuse Mail Using Rejection Message - If this option is enabled and the RBL is triggered, the SMTP will refuse mails before they even enter the mail server. This is the strongest method of enforcing SPAM protection. This option allows the use of field tags. For more information please view the Tutorial: Using Field Tags page.
• Set SPAM Flag - If this option is enabled and the RBL is triggered, the mail’s SPAM flag will be set. Content Filtering or any account filtering rules can then process the mail accordingly.
• Add Custom Event - If this option is enabled and the RBL is triggered, the string will be appended to mail's custom event list. These custom events can then be read using Content Filtering, which allows more complex actions to be performed on the mail.

SPF

• Enable Sender Policy Framework - If enabled, SPF checking will be performed on mail arriving via SMTP to help detect potential SPAM.
• Auto-Detect DNS Hosts - To perform MX lookups, the mail server requires access to at least one valid DNS host. If this option is set, Ocean Mail Server will attempt to automatically detect a list of DNSs from the computer running the mail server.
• Use DNS Host(s) - This allows you to specify the DNS hosts which should be used for MX lookups. This is usually only required when Ocean Mail Server cannot automatically detect the DNS hosts. To set multiple DNS's, simply separate each with a semi-colon (‘;’).
• Test DNS - This will perform tests to ensure that the specified DNS hosts can be used to send mail successfully.
• Enable SPF IP White List - If enabled, the IPs and IP ranges in the list box will always be exempt from SPF checking. This allows backup mail servers and other trusted IPs to bypass SPF.

SPF Results

• Refuse Mail Using Rejection Message - If this option is enabled for the triggered SPF result, the SMTP will refuse mails before they even enter the mail server. This is the strongest method of enforcing SPAM protection. This option allows the use of field tags. For more information please view the Tutorial: Using Field Tags page.
• Set SPAM Flag - If this option is enabled for the triggered SPF result, the mail’s SPAM flag will be set. Content Filtering or any account filtering rules can then process the mail accordingly.
• Add Custom Event - If this option is enabled for the triggered SPF result, the string will be appended to the mail's custom event list. These custom events can then be read using Content Filtering, which allows more complex actions to be performed on the mail.

Bayesian Filtering

• Max Tokens - This option sets a limit on the number of tokens that can be generated in the Bayesian database as a result of Bayesian training.
• Auto-Train Non-SPAM Threshold - If this option is enabled, any mails scanned that are given a Bayesian score lower than this threshold will be used to train the Bayesian database as non-SPAM.
• Auto-Train SPAM Threshold - If this option is enabled, any mails scanned that are given a Bayesian score higher than this threshold will be used to train the Bayesian database as SPAM.
• Current Status - This shows the status of the Bayesian database including the number of tokens, good and bad mail counts used for training and any actions currently being performed.
• SPAM Detection Threshold - If mails are given a Bayesian score higher than this threshold, they are identified as SPAM by the Bayesian system and the appropriate action taken.
• Refuse Mail Using Rejection Message - If this option is enabled and the Bayesian filter identifies the mail as SPAM, the SMTP will refuse mails before they even enter the mail server. This is the strongest method of enforcing SPAM protection. This option allows the use of field tags. For more information please view the Tutorial: Using Field Tags page.
• Set SPAM Flag - If this option is enabled and the Bayesian filter identifies the mail as SPAM, the mail’s SPAM flag will be set. Content Filtering or any account filtering rules can then process the mail accordingly.
• Add Custom Event - If this option is enabled and the Bayesian filter identifies the mail as SPAM, the string will be appended to mail's custom event list. These custom events can then be read using Content Filtering, which allows more complex actions to be performed on the mail.

Bayesian Training

• User Directory - If this option is enabled, the specified user directory will be used for Bayesian training. User Directory training is highly prefered to using a physical directory as flags can be set within the mail to avoid duplicate training later.
• Domain - This is the domain that will be used to determine the directory used for Bayesian training.
• User - This is the user that will be used to determine the directory used for Bayesian training.
• Directory - This is the directory that will be used for Bayesian training.
• Physical Directory - If this option is enabled, a physical directory will be used for Bayesian training. Caution must be taken with training from a physical directory to avoid duplicate training of the same mails. User Directory training is highly prefered to using a physical directory as flags can be set within the mail to avoid duplicate training later.
• File Extionsions - These are the file extensions that will determine which files within the physical directory will be used for Bayesian training.

Relaying Exemption

• Ignore RBLs / SPF When Allowed Relaying Access - If a connection is allowed relaying access, the SPAM detection mechanisms will be ignored. This allows trusted connections to remain unaffected by the SPAM system.