SpamAssassin Diagnostics

Support Spam & Virus Protection
2

Hello,

By default, the Axigen service does not preserve any changes that SpamAssassin may do to the email message - the filter is executed only to obatain SpamAssassin’s spam score, which is then used to compute the value of X-AxigenSpam-Level.
This is needed in order for the AntiSpam thresholds to work in a consistent manner with different AntiSpam filter applications.

You may alter this behavior by specifying a different protocol file for the SpamAssassin filter - we provide the “spamassassin-bin.afsl” protocol file specifically for this purpose (when using this file Axigen will preserve SpamAssassin’s changes/added headers, instead of computing X-AxigenSpam-Level).

The required steps are:

  1. Create a backup copy of the current /var/opt/axigen/run/axigen.cfg file
  2. open the /var/opt/axigen/run/axigen.cfg file in a text editor and locate the following section:
    {
    name = "AV:SpamAssassin"
    address = "inet://127.0.0.1:783"
    protocolFile = "afsl/spamassassin.afsl"
    idleTimeout = 300
    actionOnMatch = pass
    maxConnections = 10
    maxMessageSize = 10240
    }
  3. change the protocolFile parameter into:
    protocolFile = "afsl/spamassassin-bin.afsl"
  4. save the changes to the axigen.cfg file
  5. signal Axigen to reload configuration or simply restart the Axigen service

From this point, Axigen will no longer compute X-AxigenSpam-Level as a result of SpamAssassin integration, but instead it will preserve all changes done to the message by SpamAssassin. To add the X-Spam-Report header you need to configure SpamAssassin appropriately, i.e. by adding the following parameter to it’s local.cf file:
add_header all Report _REPORT_

Note: since the X-AxigenSpam-Levelheader will no longer be added, this means that the AntiSpam threshold actions found in Security & Filtering → AntiVirus & AntiSpam → AntiSpam Configuration will no longer have any effect.

Best regards,
Adrian