RES: [Spambayes] Unable to bind different addresses to port 110?

[Paulo Sakamoto]

Tony,

If I enter by hand, pop3proxy won't load.
I need to use different addresses for the same port because my pop client
only works with port 110...

Thanks,

Paulo 

> > Here is what the 1.0a2 web interface says:
> [...]
> > POP3 proxy running on 10.1.1.55:110, 10.1.1.56:110,
> > 10.1.1.57:110, proxying to pop.XXX.com:110, pop3.YYY.com:110, 
> > pop.ZZZ.com:110.
> > 
> > But I couldn't enter the same configuration in the 1.0a4, it
> > gives the error message below.
> 
> So you're putting "pop.XXX.com:110, pop3.YYY.com:110, 
> pop.ZZZ.com:110" into the servers field and "10.1.1.55:110, 
> 10.1.1.56:110, 10.1.1.57:110" into the ports field?  This 
> won't work because the ports field expects just that - ports, 
> i.e. "110,111,112".
> 
> Richie, is the pop3proxy meant to be able to accept servers 
> and addresses for the 'port' to proxy on?  If so we need to 
> change the 'nice name', allowed value and description of the 
> option, plus possibly the code that checks the ports (in ProxyUI.py).
> 
> Paulo: if pop3proxy does work like this (which I suppose it 
> must if this is what you had for a2, unless something has 
> changed), then you should be able to just enter these details 
> into your config file by hand, if you change the "PORT" in 
> Options.py in the "pop3proxy" section in the "listen_ports" 
> option to "SERVER".  Alternatively you could proxy on 
> separate ports, rather than separate ip's.
> 
> =Tony Meyer
>