Hello, I use NOD32 version 3.0.650.0 with the latest comdo fw. I have to allow, in comodo, for outlook to access tcp port 30606 on 127.0.0.1 for it to access ekrn.exe (by NOD32), for emails to go out. This is nice and OK. The problem is that I wish NOT to allow outlook to go out on any non-email ports, like HTTP, to avoid web threats and so, originating from email I receive. Now, with version 3 of NOD32, I can't do that since it is acting as a proxy, "outside" comodo, and I can't granularly make NOD32 NOT allowing outlook to go out in any non-email ports. Thus, NOD32 is creating a bypass to my fw, making it somehow useless... (unless it is a way to make us go for smart security... ). I tried adding a specific comodo rule, before the one for ekrn.exe, blocking the access of outlook to http ports, but, of course, it didn't help since outlook redirects, in advance, http traffic via port 30606 to ekrn.exe and not by outlook itself via port 80... Now, outlook.exe is only marked only as an email client and not web browser. But this doesn't help since the advanced option of "protocol filtering" has no sub-option to defer between email traffic and web traffic - they are bundled. I tried the middle option, "applications marked..." but it didn't help. It looks like eset should give here more granular settings, separating email traffic from web traffic. Please advise how can overcome this issue. Thanks.