> The default value for --server is 127.0.0.1 so there's no need to add
> --server=localhost.
I have now documented this in the clamav-milter(8) manual page, and committed it to
CVS,
along with an overview of the ability of clamav-milter to talk to more than one clamd
server.
-Nigel
--
Nigel
>new:
>CLAMAV_FLAGS=" -lo --quarantine-dir=/var/spool/clamav --max-children=10
>--force-scan --quiet --dont-log-clean --server=localhost
>local:/var/run/clamav/clamav-milter.sock"
The default value for --server is 127.0.0.1 so there's no need to add
--server=localhost.
-Nigel
--
Nigel Horne.
Steven Stern wrote:
On second thought, maybe I should have a chance to look at incoming messages
rather than bouncing them with a 550. I've removed the -b from the
clamav-milter startup. I've replaced it with --quarantine=/var/spool/clamav.
Is this what's necessary to quarantine messages in /var/
On second thought, maybe I should have a chance to look at incoming messages
rather than bouncing them with a 550. I've removed the -b from the
clamav-milter startup. I've replaced it with --quarantine=/var/spool/clamav.
Is this what's necessary to quarantine messages in /var/spool/clamav?
old:
C
