Can't get clamd working???
Rick Cooper
rcooper at dwford.com
Wed Jun 6 04:51:14 IST 2007
> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf
> Of Gerry Doris
> Sent: Tuesday, June 05, 2007 8:40 PM
> To: mailscanner at lists.mailscanner.info
> Subject: Can't get clamd working???
>
> I've been playing with the newest beta release and am having problems
> getting clamd working. When I do a MailScanner --lint I get
> the following:
>
> MailScanner --lint
> Read 764 hostnames from the phishing whitelist
> Config: calling custom init function SQLBlacklist
> Config: calling custom init function MailWatchLogging
> Config: calling custom init function SQLWhitelist
> Checking version numbers...
> Version number in MailScanner.conf (4.61.2) is correct.
>
> Checking for SpamAssassin errors (if you use it)...
> Using SpamAssassin results cache
> Connected to SpamAssassin cache database
> SpamAssassin reported no errors.
> Using locktype = posix
> Creating hardcoded struct_flock subroutine for linux (Linux-type)
> MailScanner.conf says "Virus Scanners = clamd trend f-prot
> bitdefender"
> Found these virus scanners installed: bitdefender, f-prot,
> clamavmodule,
> trend
>
>
What exactly isn't working? I have no idea how MailScanner performs it's
lint test, but mine outputs the following:
Creating hardcoded struct_flock subroutine for linux (Linux-type)
MailScanner.conf says "Virus Scanners = panda f-prot clamd"
Found these virus scanners installed: bitdefender, clamavmodule, f-prot,
panda, sophossavi
Note clamd is not one of the installed scanners and it works fine. It also
says:
Could not use Custom Function code MailScanner::CustomConfig::InitWrapper,
it could not be "eval"ed. And that all works properly as well.
You will have to ask Julian how he lints a virus scanner that doesn't
require a wrapper script, I thought setting clamd the same as clamavmodule (
/bin/false /tmp) would do it but he set it as /bin/false /usr/local...
Setting it to /tmp doesn't seem to work either.
When you test does it not work? If not what does the log say?
If running MailScanner in debug mode what do the current parameters say?
Rick
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the MailScanner
mailing list