We're running Xeams as a spam firewall in front of our MS exchange box.

Everything is fine except I can't get ClamD to work.

ClamD installed as a daemon, the "Integration with ClamAV" in "Server Configuration" in the Xeams frontend reports "Success! Connection to ClamAV was successful. It also detected a test virus." and a detection for eicar event gets written in the ClamD log. But Xeams never passes any emails to ClamD to be checked, Eicar test emails get though.

I've tried running ClamD on the same box as Xeams and on a different box and running Xeams and ClamD on Windows and on Linux. Always with the same result.

There are no applicable events in the Xeams log, unless I turn off ClamD, then it writes;

480 ERROR util.ClamAVClient - Exception caught acquiring main socket to CLAMD on /192.168.1.7 on port 3310: Connection timed out: connect

Unable to connect to CLAMD. All addresses failed. Giving up.

Unable to connect to CLAMD. All addresses failed.

Seems like potentially a great product but without virus checking of incoming emails I'm struggling.

I am having the same issue and no one answers.  That is the problem with open source

I had the same issue when configuring clamAV on a cent-os.

I finaly gave up and installed my clamav on an ubuntu server 16-04. After a dpkg-reconfigure and editing the clamav.conf file all was working fine.

I had to add extra virus databases to up the detection rate. Good luck ;-)

On CentOS 7 SeLinux is more strict than ever before. I had to add configurations to clamd itself to limit the TCP ports it would use and to Selinux to allow those ports. Once I had all that right clamd scanning is working for me.