RE: [Declude.Virus] 4.2.20 Error in Log

2006-07-12 Thread Andy Schmidt
Do you have a second/external scanner defined. May be the internal scanner (AVG) deletes an attachment and then Declude complains that its gone when it tries to launch the secondary? Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Messag

[Declude.Virus] 4.2.20 Error in Log

2006-07-12 Thread Darrell \([EMAIL PROTECTED])
Since upgrading to 4.2.20 I started seeing the following error: 07/12/2006 00:34:41.812 q7bca020f6715.smd 1 [1 of 2 not deleted] files were deleted. You should not use an on-access virus scanner that scans the \IMail directory or sub-directories.07/12/2006 00:34:41.328 This only happens

[Declude.Virus] RE: Trying to install Declude 4.2.20

2006-07-12 Thread Andy Schmidt
Hi Dave, Okay, then Declude's error message is misleading. Here is what I had done: - I had defined McAfee as "scanner 2", assuming that the internal was going to be scanner 1. - Based on your explanation, the internal scanner is "scanner 0". So, in effect, I had defined a "scanner 2" without

RE: [Declude.Virus] Ambiguous Virus Scanner ID in log

2006-07-12 Thread David Barker
The External McAfee Scanner, if you run logs on DEBUG you will see that the AVG (Internal) Scanner reports as AVG. David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt Sent: Wednesday, July 12, 2006 5:38 PM To: declude.vir

[Declude.Virus] Ambiguous Virus Scanner ID in log

2006-07-12 Thread Andy Schmidt
Hi Dave, My log indicates: 07/12/2006 17:34:20.625 q6ad4014a0137.smd Vulnerability flags = 0 07/12/2006 17:34:21.593 q6ad4014a0137.smd Virus scanner 1 reports exit code of 0 Which one is considered "Virus scanner 1" - the INTERNAL (AVG) scanner that comes with Declude 4.2.20 - or my EXT

Re: [Declude.Virus] 4.2.3 Built-in scanner slight off topic reply

2006-07-12 Thread Nick Hayer
I just switched to 4x and noticed in the logs that scan times are recorded - here are some sample scan times against the same email - 2062ms Clamscan 468ms Mcafee scan.exe 171ms fprot These relative scan time proportional differences appear to remain the same against other emails. Switching

RE: [Declude.Virus] 4.2.3 Built-in scanner

2006-07-12 Thread John Shacklett
Sorry for the tardy response, I've been traveling. I used mcafee on my old system in combination with f-prot, and never had any problems there either. On my new box [new since May], I started out with a different program from eTrust because we're moving away from McAfee across the board, but I had