John,
There is a processing loop wherein all the scanners are called in
succession. It is independent of vulnerability checking. This directive
merely tells Declude to break out of the external virus scanner execution
loop. If you use this directive to exit the scanning loop on virus detection
and (1) you have 5 scanners listed in your cfg file and (2) a virus is
detected by the first scanner listed, then the effect is exactly the same in
processing as if you had a single scanner listed and a virus were detected
by that single scanner.
David Franco-Rocha
Declude Technical Support
----- Original Message -----
From: "John Tolmachoff (Lists)" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, May 27, 2005 2:50 AM
Subject: [Declude.Virus] EXITSCANONVIRUS
A question about this new feature.
Am I correct in thinking that as soon as a scanner reports a virus, the next
scanner(s) in line will not be called and the message will be processed
accordingly, and that it will not be affected by Declude first finding a
banned attachment before having it scanned by a scanner?
John T
eServices For You
---
This E-mail came from the Declude.Virus mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.Virus mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus". The archives can be found
at http://www.mail-archive.com.
