Then I configured amavis on another VM so that it has to contact CLamav through TCP connection to the VM where Clamav is installed. But the error is the same.
I am not aware that an Amavis-to-ClamAV content stream includes file paths. So if the error message of the remote ClamAV contains an amavis spool path, your debug-setup is probably not what you intended.
Try an "strace -f -e trace=file --failed-only -p $local_clamav_pid" instead.
_______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
