How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally replaces the EPEL version of ClamAV required by Warden. To Fix:

Remove the Imunify360 ClamAV

rpm -e --nodeps clamav clamav-data clamav-filesystem clamav-lib clamav-update clamav-server

Exclude their ClamAV packages from Yum

Add the line exclude=clam* to the [imunify360] repo section in the file /etc/yum.repos.d/imunify360.repo or /etc/yum.repos.d/cloudlinux-imunify360.repo (if they exist). After it should look something like this (do not use our example as it will vary from system to system):

[imunify360]
name=EL-7 - Imunify360
baseurl=https://repo.imunify360.cloudlinux.com/defense360/el/7/updates/x86_64/
username=defense360
password=XXX
enabled=1
gpgcheck=1
gpgkey=https://repo.imunify360.cloudlinux.com/defense360/RPM-GPG-KEY-CloudLinux
exclude=clam*

In Warden go to Settings -> Application setup and go though the Warden Setup Wizard again to re-run the product installer (applying the default settings to the Antivirus pages) to re-apply the correct settings that were replaced by the Immunify360 ClamAV.

If you still have trouble don't hesitate to open a ticket to have a support technician fix this for you.

  • cloudlinux, imunify360
  • 1 کاربر این را مفید یافتند
آیا این پاسخ به شما کمک کرد؟

مقالات مربوطه

How can I fix any statistics generation problems?

Missing the Warden Crontab Entry There is a crontab entry that will update Warden statistics...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...

How can I fix the error: milter-reject: DATA 451 4.7.1 Service unavailable - try again later?

Reject log In the Warden reject log you see the message: Service unavailable - try again later....