On Fri, 2006-12-29 at 17:34 -0600, Noel Jones wrote:
Is there any way to track how long each portion of the scan takes for a
message? It would be handy to know for each message how long the virus
scan took, how long the rbl checks take, how long FuzzyOCR takes... etc.
Log level 2 (in
Bob wrote:
On Fri, 2006-12-29 at 17:34 -0600, Noel Jones wrote:
Is there any way to track how long each portion of the scan takes for a
message? It would be handy to know for each message how long the virus
scan took, how long the rbl checks take, how long FuzzyOCR takes... etc.
Log level
At 03:10 PM 1/2/2007, Bob Pierce wrote:
On Fri, 2006-12-29 at 17:34 -0600, Noel Jones wrote:
Is there any way to track how long each portion of the scan takes for a
message? It would be handy to know for each message how long the virus
scan took, how long the rbl checks take, how long
On Tue, 2007-01-02 at 14:24 -0700, Gary V wrote:
Which makes me wonder, is there a performance benefit to running clamd
instead of having spamassassin call clamscan?
There is a hugh difference. Get clamd running. Actually, it's amavisd-new
that calls virus scanners, not spamassassin.
I'm just looking at our scan times from our amavis scanners and
wondering if there might be some way to bring the average scan time
down.
We're currently averaging about 6 seconds per message on our scanners.
We're scanning about 600,000 messages per day
We're using:
ClamAV
Spamassassin
-DCC
At 04:41 PM 12/29/2006, Bob Pierce wrote:
I'm just looking at our scan times from our amavis scanners and
wondering if there might be some way to bring the average scan time
down.
We're currently averaging about 6 seconds per message on our scanners.
We're scanning about 600,000 messages per day
