Nod32 3.0 und sTunnel problem

[Tommy]

Hi Folks,
now as i have NOD v3 installed i have a problem with stunnel and checking emails which btw. worked perfect in 2.7

Situation:
MUI->sTunnel->Gmail
GMAIL acount is accessed via stunnel. The local port which is configured in the email client is 42 (stunnel is listening on port 42).
Problem:
NOD32 is not checking anymore the traffic between sTunnel and the email client, even port 42 is configured in NOD32 POP3 configuration.

What do i make wrong?

[Thankful]

Make sure 'append tag messages to received and read email' set to
'To all email' as follows:

[Tommy]

I tried this already for checking. No markings of incoming messages. So any more ideas?

Two more question.

How would you classify following application regarding setup in NOD v3? Webbrowser or email apllication?
- Freepops (i think accesses hotmail via web)
- PopPeeper (i think accesses via web)

Are there some special settings nececarry if i am behind a Wifi Linksys Router?

[Tommy]

Any ideas regarding scanning stunnel local traffic my dear developers from ESET? ;D

[Tommy]

Seems i talk to my self as there is no reaction from ESET. That's poor, sorry.
Back to Nod 2.7?

[grifdog]

I too am having trouble with email tags with version 3, so have gone back to 2.7 which scans the email and tags it too.

[b00ze]

I found out that nod v3.0.556.0 does not scan my emails if i connect to stunnel via 127.0.0.1/localhost ... when i change the adress to my local ip (in my case its 192.168.1.100) nodv3 scans all mails as it should.

dont forget to set stunnel to listen on your local ip

thats the part of my stunnel config:
; Service-level configuration
[pop3s]
accept = 192.168.1.100:110
connect = pop3.blablabla.de:995

hope that helps