Thanks Paul (sic), Kris & Andrew, It hadn't occurred to me to use a "faked" clamd.conf -- I guess I thought that the '-c' option was just for keeping the real clamd.conf at a non-standard place.
What I had tentatively decided to do was to change the real clamd.conf to specify the remote port (on localhost) since I wouldn't be running clamd locally at all, and then use xinetd to "redirect" that local port to the remote clamd. This suggested approach, with an explicit "faked" clamd.conf -- renamed clamdscan.conf for clarity -- is far more elegant (and more efficient)! Thanks again, Paul Kosinski -------------------------------------- On Mon, 22 Sep 2025 14:46:11 +0100 Paul Netpresto via clamav-users <[email protected]> wrote: > Hi > > This should work > > clamdscan -c /path/to/clamdscan.conf /email.file > > clamdscan.conf contents > > TCPSocket 3310 > > TCPAddr remote clamd IP address _______________________________________________ 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
