Re: Pyzor server not responding

[Gary V. <li...@jo...>]

> echo "217.160.253.84:24441" > /root/.pyzor/servers
> echo "82.165.246.93:24441" >> /root/.pyzor/servers

> pyzor ping
> 217.160.253.84:24441    TimeoutError:
> 82.165.246.93:24441     (200, 'OK')

> pyzor ping
> 217.160.253.84:24441    (200, 'OK')
> 82.165.246.93:24441     (200, 'OK')


> This definitely needs to be fixed. I ran 'pyzor discover' the other
> day and Pyzor stopped working. I thought it was a problem with
> SpamAssassin and amavisd-new (there was a bug in 3.0.0). You
> may never get a response from 217.160.253.84 unless you first
> initiate a session with 82.165.246.93. Most properly set up packet
> filters will not allow a session from a host unless it is first
> ESTABLISHED. No one who uses Pyzor should have to spend the time
> like I have trying to figure this out.

If this is the same server, why not simply replace
217.160.253.84:24441 with 82.165.246.93:24441 in
http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x

Using 82.165.246.93:24441 appears to work.

Or set it back to 66.250.40.33:24441 until the issue is resolved.