All I know is that I installed simscan and chose clamav as the viral
scanner. The error message that shows as follows:
odin clamav # clamscan
LibClamAV Warning: ********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.  ***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/faq.html ***
LibClamAV Warning: ********************************************************
LibClamAV Warning: ********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.  ***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/faq.html ***
LibClamAV Warning: ********************************************************
/var/log/clamav/freshclam.log: OK
/var/log/clamav/clam-update.log: OK
which is from clamscan NOT freshclam is read by simscan as an error when
using custom smtp rejection compiled in. Not answering your question as why
these things happen. Just stating that they just happen.

----- Original Message ----- 
From: "Rick Macdougall" <[EMAIL PROTECTED]>
To: <vchkpw@inter7.com>
Sent: Thursday, June 30, 2005 3:03 PM
Subject: Re: [vchkpw] mail relay problems ...


> Chris Godwin wrote:
>
> >problems with qmailrocks-- vpopmail mail quota system is broken because
of
> >no maildir++ patch and few patches that enable chkuser and others,
> >qmailscannerqueue is a freakin mem hog. Uses qscanqueue or simscan. If
you
> >use simscan, clamav's out of date warning will cause a hard smtp error on
> >the client end, you must not enable custom smtp rejection messages.
> >
> >
> >
> Uhhh, why would the out of date warning (that comes from freshclam)
> cause a hard smtp error on the client end ?
>
> I use it on a lot of machines and I've never had that problem.
>
> Regards,
>
> Rick
>
>


Reply via email to