Troubleshooting the Core Antispam Engine

To ensure that the Core Antispam Engine functions properly, the exceptions listed under Configuring installed on-access virus scanners must be set. If problems still occur, check the following points one after the other:

• Are there up-to-date definitions on the Gateway Role system? The path is C:\ProgramData\Net at Work Mail Gateway\Core Antispam Engine\antimalware\1\.
• If the definitions are up to date, it may be useful to activate the engine logging. To do this, add the following lines to the file C:\ProgramData\Net at Work Mail Gateway\Core Antispam Engine\bdamserver.conf:

The logs created in this way in the directory C:\ProgramData\Net at Work Mail Gateway\Core Antispam Engine\Logs can then be sent together with the message tracks of affected emails to your reseller or directly to NoSpamProxy support for clarification.

See

Core Antispam Engine Filter