Milter starts with messages: Mon May 25 20:02:17 2020 -> +++ Started at Mon May 25 20:02:17 2020 Mon May 25 20:02:17 2020 -> Local socket unix:/var/run/clamav/clamd.sock added to the pool (slot 1) Mon May 25 20:02:18 2020 -> Probe for slot 1 returned: success $ ls -l /var/run/clamav total 2 -rw-rw-r-- 1 clamav clamav 6 May 25 20:02 clamav-milter.pid -rw-rw-r-- 1 clamav clamav 6 May 25 20:00 clamd.pid srw-rw-rw- 1 clamav clamav 0 May 25 20:00 clamd.sock srwxrwxrwx 1 clamav clamav 0 May 25 20:02 clmilter.sock In Exim configuration: acl_smtp_data = acl_check_data av_scanner = clamd:/var/run/clamav/clmilter.sock acl_check_data: deny malware = * message = This message contains a virus ($malware_name). In Exim logging: 2020-05-25 20:10:18 1jdGcE-0004o2-Dq malware acl condition: clamd /var/run/clamav/clmilter.sock : unable to read from socket (EOF)
(In reply to Igor Konov from comment #0) I think this is configuration issue of exim. So you should first consult exim support such as mailing list.
(In reply to Igor Konov from comment #0) Exim does not support the milter protocol. Use av_scanner = clamd:/var/run/clamav/clamd.sock
(In reply to Igor Konov from comment #0) Have you tried the advice in comment #2?