NOD32

Hi Logan,

New to me. You could post the essence over here; after that, It'll be my pleasure to contact Eset/NOD32.

regards.

paul

 

Logan

Just had a look. "Low priority" eg of no importance to Eset as it seems. reading Palo's answer. Btw: we could have provided you with Palo's info weeks ago..Anyway: Becky users seem to have a problem here - without a solution. Sorry to hear so. IMHO the POP3 email scanner part from NOD32 isn't by far a reliable component at the moment by design. Probably/hopefully the upcomng version 2.0 will be vastly improved.

 

Hi Mickey,

It's a matter of design. The po3 scanner does "miss" numerous (compressed) files. Both JacK and my person have reported this on many occasions to Eset. Only in case the compressed files are actually activated, NOD32 will jump in. In the meanwhile, if only for "importing" reasons, the infected file is stored in an archived email client file - thus, in case anyone chooses to import archived email files/databases, the infected files will be imported as well.

Proof of the pudding: activating:
a) NOD32 pop3 scanner;
b) DrWeb anti-virus;
c) The Bat! email client;
d) DrWeb - The Bat! pop3 scanner .dll

Now, when receiving an infected compressed attachment, NOD32 pop3 scanner will not alert in any way. DrWeb detects the infected file at the spot, and handles it the way one has configured it (many options available). This leaving aside the config from DrWeb and/or DrWeb SpiderGuard.

stored is an issue here; see my comment about archived files mentioned above. What happens when for some reason one chooses to import archived email files using Becky?? - infected files will be imported IMHO...

As stated: a matter of design - and IMHO this could be handled far better - as might be demonstrated by now.

A matter of opinion. I for one am not a happy camper with the actual design.

I knew we would agree on at least one item in the end!

regards.

paul