Problem setting up ClamAV and SpamAsassin, configuration has no effect

Support Spam & Virus Protection
3

I had the same issue. I believe I got SpamAssassin working but not ClamAV.
See Below the responce I got. I will watch to see your outcome. I gave up and went back to running a server on CentOS but would love to run Axigen in Docker if I could get the same results.

Nov '19

Hello,

Our advice is to use a dedicated container for SpamAssassin (for example this one ) and configure Axigen to connect to it*. Same approach should work for ClamAV as well.

HTH,
Ioan

  • in axigen.cfg update the address for “AV:Spamassassin” from the default value ( inet://127.0.0.1:783 ) to the one specific for your installation (like below), restart Axigen and enable Spamassassin built-in external application filter from WebAdmin > Security & Filtering > Antivirus & AntiSpam > Supported Applications (igrnore that you may get ‘could not connect’ status for this particular configuration)
  {
         name = "AV:SpamAssassin"
         address = "inet://172.17.0.1:783"
         protocolFile = "/var/opt/axigen/filters/spamassassin.afsl"
         idleTimeout = 300
         actionOnMatch = pass
         maxConnections = 10
         maxMessageSize = 10240
  }

P.S. could you link me to the Docker Hub versions of Spamassassin and ClamAV you are running? Thanks!