On Mon, 28 Apr 2014, Jon Rowlan wrote:
>Clamdscan works fine at the command line, its just that I am struggling
>to get the clam scan of any kind working via the socket.
Did you configure MIMEdefang somehow to use that socket?
This is my /etc/mail/mimedefang.pl.conf on a debian server:
--------- 8< ---------------------------------------------------
# Mimedefang configuration file
# This file is a perl file which gets 'require'd from mimedefang # You
can set the virus-scanner paths etc.
# See mimedefang.pl
$Features{'Path:QUARANTINEDIR'} = '/var/spool/MD-Quarantine';
$Features{'Virus:CLAMAV'} = '/usr/bin/clamscan';
$Features{'Virus:CLAMD'} = 1; $ClamdSock = '/var/run/clamav/clamd.ctl';
# DO NOT delete the next line, or Perl will complain.
1;
--------- 8< ---------------------------------------------------
Debian modified /usr/bin/mimedefang.pl to 'require' this file.
I have just discovered that I do not have clamscan on my server but
clamdscan appears to work from the command line.
So I think that means that I have a correctly configured daemonised clam
install and clamdscan will using the socket I presume?
Thanks Kees,
jON
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
