Solution
SpamAssassin configuration
In order to prepend a tag to the subject of spam messages with a tag of your choice, you first need to configure SpamAssassin and set the desired tag. Depending on the SpamAssassin solution used you need to edit one of the following files:
- For SpamAssassin Bundled:
/etc/opt/axigen/spamassassin/conf/local.cf - For system SpamAssassin:
/etc/spamassassin/local.cf
or
/etc/mail/spamassassin/local.cf
In one of the files above you will need to add or uncomment the following configuration option:
rewrite_header Subject [SPAM]
AXIGEN configuration
In the AXIGEN configuration file /var/opt/axigen/run/axigen.cfg you need to add one of the following blocks depending on the SpamAssassin solution used.
NOTE: Before editing, you should make a backup of your current AXIGEN configuration file.
- For SpamAssassin Bundled, place the following block under "socketFilters = (" line:
{
name = "AV:SpamAssassinBundled-bin"
address = "inet://127.0.0.1:1987"
protocolFile = "/var/opt/axigen/filters/spamassassin-bin.afsl"
idleTimeout = 60
actionOnMatch = pass
maxConnections = 10
}
- For system SpamAssassin, place the following block under "socketFilters = (" line:
{
name = "AV:SpamAssassin-bin"
address = "inet://127.0.0.1:783"
protocolFile = "/var/opt/axigen/filters/spamassassin-bin.afsl"
idleTimeout = 60
actionOnMatch = pass
maxConnections = 10
}
After adding one of the blocks above, save the configuration file, and reload/restart the AXIGEN service for the changes to take effect. Login to Webadmin interface, go to Security & Filtering menu, AntiVirus and AntiSpam context, and instead of your current active filter you need to enable the one ending in "-bin":
- If you use SpamAssassin you need to enable SpamAssassin-bin
- If you use SpamAssassinBundled you need to enable SpamAssassinBundled-bin
NOTE: While using the "-bin" filter and AFSL, the AntiSpam Thresholds will no longer be effective.