Axigen Community Forum

  • If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Problems with Axigen + ClamAV

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    Problems with Axigen + ClamAV

    Greetings Community,

    I have been trying to get Axigen (v10.2.1) working with ClamAV (v0.100.1.3). I have followed the guide posted on these forums here (See post #13 for Centos 7):
    https://www.axigen.com/forum/forum/s...ith-axigen?t=1

    ClamAV is properly setup on my mailserver, and it updates properly with freshclam. It scans successfully and identifies viruses from the command line. etc. However, when I go into Axigen and enable it, it causes all mail delivery to stop, the logs show this error message:

    PROCESSING:00207CF6: Error connecting to socket filter: ClamAV(/var/run/clamav/clamd.ctl) reason: No such file or directory

    Can anyone point me in the right direction? How do I troubleshoot this?



    ps : can someone explain why I have two ClamAVs listed in the Axigen GUI: I have ClamAV (Type=Built-in External), then I have ClamAV-local (type: User External).


    #2
    Hello,

    Please know that we have tested the ClamAV installation on CentOS 7 by using the steps from the guide available at the link:

    https://ismailyenigul.wordpress.com/...v-on-centos-7/

    To make clamd listen on port 3310 we uncommented the lines below:

    TCPSocket 3310
    TCPAddr 127.0.0.1

    in the configuration file.

    After the service started, we added the clamscan system user to the axigen system group so that clamd can access the queue files to scan them then restarted the service. At this point ClamAV was displayed as available in Webadmin -> Security & Filtering -> AntiVirus & AntiSpam -> Supported Applications. Then we enabled it, sent a test message and confirmed that it was scanned.

    Please find attached to this message the file clamav_centos7.txt containing the commands used. Our suggestion is to try the same steps.

    Regarding the two ClamAV filters listed in the Webadmin interface, the difference between them is how Axigen tries to communicate with ClamAV, respectively one filter uses a local socket while the other uses a TCP socket. After performing the steps described above you should enable only the "ClamAV" filter, not "ClamAV-local"

    Thank you.
    Attached Files
    Paul

    Comment

    Working...
    X