TY, but the result is same. claimav is enabled but not blocking none of test files. (and not marking in Object filed)Try running this for ssh as root
Code:cd /usr/local/directadmin/custombuild ./build set_fastest ./build update ./build set clamav yes ./build set clamav_exim yes ./build clamav ./build eximconf
So what happens now if you send a test inbound?Fri 2022-02-18 05:13:14 EST; 6h ago
mail are delivered to mailbox with virus attached and no waring insered in object.So what happens now if you send a test inbound?
Did you update freshclam?
Code:freshclam
Did you restart exim as well?
Code:systemctl restart exim
2022-02-19 14:53:20 1nLQAo-0002C1-5z malware acl condition: clamd : unable to send file body to socket (127.0.0.1): Broken pipe
In our case it's not clamav.conf but /etc/clamd.conf which can be changed. Use maybe 100M and don't forget to restart clamd, then try again.To solve this, open your clamav.conf file (/etc/clamav.conf or find your location) and change value for StreamMaxLength according to your needs. Default value is 25M.
ty for testing,You're right. I have clamav running doesn't do anything with it either.
That is odd. However it's known that Clamav is not the best virusscanner around, it does not detect everything.