Problem with ASL and MailScanner using ClamAV

[jbourque]

I'm having a problem when updating ASL it updates CLAMAV but then breaks Configserver MailScanner which prevents emails from being delivered. I have to force an update in mailscanner to change the path of clamav in order to get things working again.

How can I make clamav work for both Mailscanner and ASL?

Thanks
Joe

[scott]

What path do you have to change? They shouldnt be using anything other than a socket or a port.

[jbourque]

Where can I change the port number in ASL?

So once I force upgrade for clamav for mail scanner I get the following error logs

/etc/cron.hourly/freshclam:

connect(): No such file or directory

[scott]

We dont change the port number in clamav, it just uses the defaults. Sounds like the other application might have though. Running: asl -s -f should fix it

[jbourque]

Yes but if I change it it breaks my mail scanner and all email is not delivered

[scott]

What would be helpful is to know what this other application does to the configs on the system. We use package management (rpms) which would protect the configurations and binaries from being modified if another software package uses package management. We call this the "Good Neighbour" effect. It sounds like what your using is not using package management, so that layer of configuration management isnt in place. What you're losing from our side is the ability to detect malicious software uploaded over HTTP/HTTPS or written to the filesystem. Thats a pretty significant problem there, so I'd like to help you and this other vendor keep that from becoming a bigger issue.

[callum-JH]

I'm sure the config server mailscanner changes the clams socket to /tmp/clamd instead of /tmp/clamd.socket

Maybe the update changed the clamd socket?

[scott]

If that is what they are doing, I recommend reaching out to them about it. Every other branch of clamav uses .socket or .sock for socket files. Its a pretty common standard these days.