RE: [Declude.Virus] ZEROHOUR, scanner order

2009-06-08 Thread David Barker
Commtouch Zerohour identifies virus’ based on traffic patterns rather than signatures this is why it is not associated with a name. There is only one option currently for Commtouch – in the global.cfg ZEROHOUR x Where x is the weight assigned if ZEROHOUR is triggered. In the Declude

RE: [Declude.Virus] ZEROHOUR, scanner order

2009-06-08 Thread Andy Schmidt
...@declude.com] On Behalf Of David Barker Sent: Monday, June 08, 2009 10:34 AM To: declude.virus@declude.com Subject: RE: [Declude.Virus] ZEROHOUR, scanner order Commtouch Zerohour identifies virus' based on traffic patterns rather than signatures this is why it is not associated with a name

RE: [Declude.Virus] ZEROHOUR, scanner order

2009-06-08 Thread David Barker
Subject: RE: [Declude.Virus] ZEROHOUR, scanner order Hi David: Thanks. The Global.cfg configures the Declude.Junkmail - but you said it was implemented as Declude.Virus. So any configuration would go into the Virus.cfg file. It seems to me as if it's implemented in some fashion in both ends

RE: [Declude.Virus] ZEROHOUR, scanner order

2009-06-08 Thread Andy Schmidt
: RE: [Declude.Virus] ZEROHOUR, scanner order Andy, It is implemented in the Declude virus but because the spam function overlaps into junkmail and the spam weighting system is in junkmail the weight is specified in the global.cfg - as you can see it is more as a directive than a test

RE: [Declude.Virus] ZEROHOUR, scanner order

2009-06-08 Thread David Barker
Of Andy Schmidt Sent: Monday, June 08, 2009 11:28 AM To: declude.virus@declude.com Subject: RE: [Declude.Virus] ZEROHOUR, scanner order Fair enough! Looks like a good service in general - hopefully, the implementation can be cleaned up at some point. Thanks, Andy From: supp