Resolving issues with spam scanning

Follow these steps if you experience issues with the anti-spam module.

( For the full Guide on Server and Email security please click below to view the guide in PDF format:

Email and server security admin guide )

If Email and Server Security incorrectly classifies an email message as spam, see the following article for more information: Email messages are incorrectly classified by the F-Secure spam scanner.

1. Open the following page in the server's browser to check that Email and Server Security is able to connect to the internet: https://aspam.sp.f-secure.com/bdnc/config. The page should open and show the following JSON content:

The anti-spam scanner needs to connect to the detection center for each message that it scans. The product includes a small local database that is used for internal optimization, but that does not cover enough data to complete a scan. If the page does not open:

a) Check if you need a proxy to access the page in your browser. If so, you need to configure the anti-spam scanner to use the same proxy in Policy Manager.

b) Check that your firewall allows access to the following domains: • *.f-secure.com • *.fsapi.com

2. Check that Anti-Spam updates are downloaded.

a) Open the product's local user interface.

b) Select Settings Updates and check the list of updates under Update history.

3. If spam messages are not being quarantined, check the maximum email size under Email traffic scanning Spam control in the web console and increase it if it is set too low.

4. Check the quarantine rules. For example, if you have set the quarantine rules as follows: • If the spam detection level is between 1 and 5, the message is only marked as spam • If the spam detection level is between 6 and 8, the message is quarantined • If the spam detection level is 9, the message is dropped On receiving10 messages rated at level 4, 10 messages rated at level 6, and 10 messages rated at level 9, this means that a total of 30 messages are scanned, but only 10 are quarantined.

5. There could be wrong settings in internal_senders which results in wrong email direction handling (spam filter works only for incoming direction); for example: