Confused as to your problem actually, could you be more specific as to what you are scanning with, and what you are scanning, i.e., A Linux Partition, AND/OR, a Windows Partition, with âAvast xxxâ.
Thankyou.
What i find strange is that with this definitions VPS: 130723-0 the linux client doesnât find the virus while the windows client with the same VPS finds it.
Today with VPS 130723-1 also the avast4server finds the virus but what is strange is the dicrepancy between the 2 versions.
Strange as you say.
I guess itâs possible that avast for widows made the detection originally using a non-signature-based technique.
That detection was confirmed, and so the signature has now been added?
overblood, as mag suggests, the Windows Virus may now be in the Linux â.vbsâ (although they both should be same - Linux and Windows) : We have seen in the past slow downs in the Avast4Linux server, updating the .vbs, which may also be a factor.
mag:
"...I guess it's possible that avast for widows made the detection originally using a non-signature-based technique."
I suspect the Windows scanner uses heuristic techniques, etc., whereas i'm not sure as to the methods of detection of the avast4server scanner, simply the .vbs I believe.
Also, a Linux scanner wonât scan protected (root) files, as is the nature of Linux permissions.
Is the Email owned by a âuserâ, or â/â may be something worth checking ?
If you are having further problems, I suggest contacting Avast.co, as Avast4Server is a paid for and licensed product.