Sophos SAVI problems

[Daniel Kleinsinger]

I applied the patch and the error message changed to:
Apr 26 23:11:07 nts-2 MailScanner[13286]: Virus and Content Scanning:
Starting
Apr 26 23:11:07 nts-2 MailScanner[13286]: FATAL: Encountered code that
does not meet configured acceptable stability
Apr 26 23:11:07 nts-2 MailScanner[13286]: FATAL: *Please go and READ*
http://www.sng.ecs.soton.ac.uk/mailscanner/install/codestatus.shtml as
it will tell you what to do.

So I then changed Minimum Code Status from supported to beta and,
surprise surprise, it started working.  I then reverted to the unpatched
SweepViruses.pm, leaving MCS at beta, and the old error came back.  So
it would seem that the new code fixed some problem with identifying new
IDEs.  Thanks for fixing it so quickly.

Daniel

Julian Field wrote:

> It watches the modification dates of the Sophos ide directory and the
> Sophos lib directory. I have just added some more error-checking to the
> code that does all this, so it should log slightly better what is
> going on.
>
> Try applying this patch to
> /usr/lib/MailScanner/MailScanner/SweepViruses.pm:
>
> ---- PATCH STARTS ----
> --- SweepViruses.pm.orig        2003-04-26 11:00:01.000000000 +0100
> +++ SweepViruses.pm     2003-04-26 11:00:49.000000000 +0100
> @@ -291,6 +291,9 @@
>
>    my $SAVIidedir = MailScanner::Config::Value('sophoside');
>    $SAVIidedir = '/usr/local/Sophos/ide' unless $SAVIidedir;
> +  my $SAVIlibdir = MailScanner::Config::Value('sophoslib');
> +  $SAVIlibdir = '/usr/local/Sophos/lib' unless $SAVIlibdir;
> +
>    $ENV{'SAV_IDE'} = $SAVIidedir;
>    $SAVI = new SAVI();
>    MailScanner::Log::DieLog("SophosSAVI ERROR:: initializing savi: %s
> (%s)",
> @@ -342,10 +345,14 @@
>    # Store the last modified time of the SAVI lib directory, so we can
> check
>    # for major upgrades
>    my(@statresults);
> -  @statresults = stat(MailScanner::Config::Value('sophoside'));
> -  $SAVIidedirmtime = $statresults[9];
> -  @statresults = stat(MailScanner::Config::Value('sophoslib'));
> -  $SAVIlibdirmtime = $statresults[9];
> +  @statresults = stat($SAVIidedir);
> +  $SAVIidedirmtime = $statresults[9] or
> +    MailScanner::Log::WarnLog("Failed to read mtime of IDE dir
> %s",$SAVIidedir);
> +  @statresults = stat($SAVIlibdir);
> +  $SAVIlibdirmtime = $statresults[9] or
> +    MailScanner::Log::WarnLog("Failed to read mtime of lib dir
> %s",$SAVIlibdir);
> +  MailScanner::Log::InfoLog("Watching modification date of %s and %s",
> +                            $SAVIidedir, $SAVIlibdir);
>  }
>
>  # Are there new Sophos IDE files?
> ---- PATCH ENDS ----
>
> Let us know what it says.
>
>
>> Apr 25 17:52:03 nts-2 MailScanner[4739]: MailScanner E-Mail Virus
>> Scanner version 4.14-9 starting...
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: SophosSAVI 3.68 (engine
>> 2.14) recognizing 80979 viruses
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: SophosSAVI using 15 IDE files
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: Using locktype = flock
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: New Batch: Scanning 2
>> messages, 13643 bytes
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: Sophos update detected,
>> resetting SAVI library
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: Sophos SAVI library has been
>> updated, killing this child
>> Apr 25 17:52:05 nts-2 MailScanner[4739]: MailScanner child dying of
>> old age
>