Email and Server Security- Scanning 'message' by WithSecure Spam Scanner was unsuccessful

Issue:

Email and Server Security, the following message keeps occurring:
Scanning 'message' by WithSecure Spam Scanner was unsuccessful. Scan result: Scan error: -1073741808
The message can be found in various logs, including the following:
- email-scan.log
- transportAgent.log

Resolution:

The error "WithSecure Spam Scanner was unsuccessful" typically indicates network connectivity issues preventing the anti-spam engine from connecting to the detection center at https://aspam.fsapi.com/.

Resolution:

Test Connectivity to the Detection Center:
- Open the following URL in a browser to test connectivity:
  https://aspam.fsapi.com/bdnc/config
- If the connection is successful, the page will display JSON data similar to:
```
{"benchmarkInterval":3600,"benchmark":1,"servers":["aspam.fsapi.com"],"statsInterval":1800,"enforceSSL":true,"benchmarkThreshold":5,"disableThreshold":10}
```
Proxy Configuration:
- If a proxy is used to access the above URL in a browser, ensure the anti-spam engine is configured to use the same proxy.
- This can be configured via the Policy Manager Console.
Firewall Settings:
- If the connection fails, verify that your firewall allows traffic to the following domains:
  - *.f-secure.com
  - *.fsapi.com
Email Size Configuration:
- Ensure the email size does not exceed the configured file size limit, as this can result in error code -1073741808.
- To modify the file size limit:
  - Open Policy Manager.
  - Navigate to Settings > MS Exchange > SPAM Control.
  - Adjust the file size limit as needed.
Verify Anti-Spam Updates:
- Ensure that the anti-spam updates are downloaded and up to date.
- To check:
  a) Open the product's local user interface.
  b) Go to Settings > Updates and review the list of updates under Update History.

Article no: 000035299