David, this log excerpt seems to indicate that my AVG hasn't been
working since May 1st 2009. Is this correct?
C:\IMail\Spoolgrep -c smd Scanned: Error in virus scanner vir.log
vir0401.log:0
vir0402.log:0
vir0403.log:0
vir0404.log:0
vir0405.log:0
vir0406.log:0
vir0407.log:0
vir0408.log:0
Can I replace the decludeproc.exe or is a upgrade install needed?
-Original Message-
From: supp...@declude.com [mailto:supp...@declude.com] On Behalf Of David
Barker
Sent: Monday, June 01, 2009 2:38 PM
To: declude.junkm...@declude.com; declude.virus@declude.com
Subject: [Declude.Virus]
4.6.35 AVG not scanning - FIX
David, this log excerpt seems to indicate that my AVG hasn't been working
since May 1st 2009. Is this correct?
C:\IMail\Spoolgrep -c smd Scanned: Error in virus scanner vir.log
vir0401.log:0
vir0402.log:0
vir0403.log:0
vir0404.log:0
vir0405.log:0
vir0406.log:0
You can just replace the decludeproc if you were previously running anything
later than 4.4.24
From: supp...@declude.com [mailto:supp...@declude.com] On Behalf Of Scott
Fisher
Sent: Monday, June 01, 2009 4:35 PM
To: declude.virus@declude.com
Subject: RE: [Declude.Virus] Upgrade 4.6.35 AVG
:00 PM
To: declude.virus@declude.com
Subject: RE: [Declude.Virus] Upgrade 4.6.35 AVG not scanning - FIX
Not for everyone, but certainly for your server that would be true if
that is what your logs indicate.
From: supp...@declude.com [mailto:supp...@declude.com] On Behalf Of
Colbeck, Andrew
: RE: [Declude.Virus] Upgrade 4.6.35 AVG not scanning - FIX
Aha! That was a fishy circumstance. Those errors were red herrings raised by
my other virus scanner, not the AVG scanner.
If anybody is interested, this is what the log lines looked like at the last
time that AVG triggered
