Mailscanner warnings

[Glenn Steen]

On 19/02/2008, Ugo Bellavance <ugob at lubik.ca> wrote:
> AlxFrag wrote:
> > Glenn Steen wrote:
> >> On 15/02/2008, Martin.Hepworth <martinh at solidstatelogic.com> wrote:
> >>
> >>> Also
> >>>
> >>>  The clamd facility is only really stable at 4.62 or later and didn't exist before 4.61..
> >>>
> >>>
> >> Not to mention that no facility of MailScanner would ever run trhe
> >> clamd _command_ ... Not whatsoever.
> >>
> >> What seems to have happened here is that someone has followed a
> >> bothced instruction on enabling clamdscan support by futzing the
> >> clamav-* wrapper scripts. This of course hasn't worked, since clamd is
> >> the server part, not the client.
> >> This would explain the bogus log entries on both hosts.
> >>
> >> What Alex should do is to follow the spirit of the wiki article
> >> http://wiki.mailscanner.info/doku.php?id=documentation:anti_virus:clamav:switch_to_rpm_clamd
> >> to get things going on the newer install (4.66.5 was it?), and upgrade
> >> the other one to a version later than 4.62.something (just as you say
> >> Martin), and do the same there.
> >> Only other really viable option would be to run clamavmodule on the old one.
> >>
> >> Cheers
> >>
> > Good morning,
> >
> > I've followed your advice and these described in
> > http://wiki.mailscanner.info/doku.php?id=documentation:anti_virus:clamav:switch_to_rpm_clamd.
> > I've also modified the clamav-wrapper file to its original form.
> >
> > Now, no warnings are displayed. The problem is that clamscan is running
> > that needs too much CPU.
> > How can i switch to clamdscan?
>
> - make sure you're running a version of MS that supports clamd
> - make appropriate changes in MailScanner.conf
> - restart MailScanner
>
> Ugo
>
If the version is too old for clamd (4.62.something...?), then use clamavmodule.

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se