V2 and Popfile

[kenw]

When I try to change the port that I want v2 listen on, 9999, it adds port 110 by default.
Using Agent.
Error in Agent, can't log on to 127.0.0.1:9999:110:username

OK, read the Becky thread.

Killed one of the best spam filtering tools !!!!!!!!!!!!!!!!

[LowWaterMark]

Sorry Ken, I'm not sure I understand.

The Becky thread (link) (http://www.wilderssecurity.com/showthread.php?t=10214) notes that NOD32 v2 no longer uses a proxy to scan email and that you should return your email client back to pop email from your email server directly and use port 110, not a localhost proxy port... So, you don't need to use port 9999 for this.

What do you mean by this?

>> Killed one of the best spam filtering tools !!!!!!!!!!!!!!!!

I'm sure all of this can all be set up to work properly.

[kenw]

It's just the way the port chain is set up.
Email >110 >NOD32> 9999 >Popfile(or K9) 123 >Agent

So Popfile is a proxy and can't be used

[Clive T]

Right, I had a struggle with this setup, too. I've now got it all working by setting NOD, POPfile and TheBat to ALL point to port 111. POPfile insisted on using this port and I couldn't move it away from it.

For some reason 110 breaks the chain -- don't know why.

Regards

Clive T

[marti]

Why not turn off IMON? I ran for close to 3 years with an AV that didn't have an email scanner and I was never infected. When I started using NOD (last Fall) I never bothered to load IMON. (With my current configuration, I probably couldn't use it anyway, bacause I have POP3 ports of 110 for some and 995 for others.)

[jan]

Hi all,

if you use a direct connection from your e-mail client to the mail server - the port 110 is normally used. If there is a kind of "proxy" - spamfilter, or something else in between - it's needed to fill in the Incomong mail port number that the "proxy" requires to the e-mail client.

Cheers,

jan

[kenw]

-{ Quote: " quoting: Clive T link=board=39;threadid=10265;start=0#msg66638 date=1055571294]
Right, I had a struggle with this setup, too. I've now got it all working by setting NOD, POPfile and TheBat to ALL point to port 111. POPfile insisted on using this port and I couldn't move it away from it.

For some reason 110 breaks the chain -- don't know why.

Regards

Clive T
" }-

What are your exact settings ? Popfile won't stay on 111. keeps changing to 123
Agent pop3,comcast.net:111:username
Agent pop server pop3.comcast.net

[Clive T]

>>What are your exact settings ? Popfile won't stay on 111. keeps changing to 123

Try changing your email prog's POP settings and NOD to port 123 then.

I don't know why you've got port 111 in your pop settings. POPfile's setup guide says to enter popserver:username. That works for me.

Good luck