RE: Pyzor server not responding

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

>> pyzor --homedir /etc/mail/spamassassin/ ping
>>  82.165.246.93:24441     (200, "OK")
>>  217.160.253.84:24441    (200, "OK")

>> Tobias Stefan Richter, on 2004-11-10, wrote:

>> Is there a good reason the new server (82.165.246.93) answering requests
>> to 217.160.253.84 isn"t officially announced (via "pyzor discover" or at
>> least mailing list)?

> Currently the server is on a multihomed host; I"ll see what I can do about
> having it bind to the advertised address.
> --
> Frank


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.