John wrote:
Stephen Gran wrote:
On Thu, Jan 20, 2005 at 12:37:05PM -0500, John said:
Hello all,
I have searched the archives, FAQ, and docs, but was unable to find any info I could use. If I have missed it please feel free to RTFM (hopefully with a link) me.
I have a public email/web/dns server, although it does these functions very well, if I add email scanning (spamassassin) to the process, it tends to bring the machine to it's knees. I solved this problem by moving the actual spam scanning to another machine. I figured that because clamd can be run as a daemon, I should be able to do the same with virus scanning, by now, I'm sure, you can figure out it is not working.
I'm running exim4-daemon-heavy with exiscan on Debian(sarge). The error I get is:
malware acl condition: clamd: ClamAV returned /var/spool/exim4/scan/[message-id]: Access denied. ERROR
I suspect clamd on the remote server is looking on it's own file system and not finding the file. Can I pass the file to be scanned via the network? What am I doing wrong? Or am I missing the point entirely, and clamd will not work via network.
clamd itself works via the network. However, the exiscan code makes a
connection to the named clamd process, and issues a 'SCAN /var/spool/exim4/scan/$meesage_id/' request. So the remote server
does indeed try to scan it's own file system.
The only way around this, AFAICT, is to network mount the scan/ directory onto the remote machine, if you must do it this way. However, I have found clam to be a very lightweight process, even on fairly heavily loaded machines, and so running it locally with exim would be my advice.
HTH,
> Stephen (& Tomasz), > > Thanks for the quick responses. I'm trying running clamd on the public > server (milter does not seem to be available for exim4) and now I'm > getting a 'bad file descriptor' error??? > > Sorry to be a pain... > John > Sorry for the top post in previous message.
I've fixed this problem, it seems that debconf is not attempting to config clamd upon installation, after running:
dpkg-reconfigure clamav-daemon
and making sure clamav is added to Debian-exim group, all is well.
Again, sorry for the top post and thank you for the quick responses... John
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
