RE: R: pyzor server address

[Giampaolo Tomassoni]

From: Chris Purves [mailto:[EMAIL PROTECTED]
> Giampaolo Tomassoni wrote:
> > 
> >  b) leave the servers file as is, lower the pyzor's timeout and 
> increase the maximum retries:
> > I've been told that many short-time attempts are better 
> that a single, long-lasting,
> > one. So, in your local.cf, try using something like:
> > 
> > use_pyzor 1
> > pyzor_timeout 3
> > pyzor_max 10
> > 
> 
> pyzor_max is the number of reports on the pyzor server required to get a 
> positive match, not number of retries.  It seems to be poorly named.

Oh, my! That's why it was so difficult to me to see a pyzor score...

Thanks Chris. I was probably misleaded by a Hein's post in the pyzor list: he 
asserted that "few retries with a shorter timeout are more effective than a 
single longer timeout".

I probably presumed that there had to be a retry max count in the pyzor conf 
and didn't even read the perldoc...

Thanks again,

giampaolo


> 
> -- 
> Chris
> 

Re: R: pyzor server address

[Chris Purves]

Giampaolo Tomassoni wrote:


 b) leave the servers file as is, lower the pyzor's timeout and increase the 
maximum retries:
I've been told that many short-time attempts are better that a single, 
long-lasting,
one. So, in your local.cf, try using something like:

use_pyzor 1
pyzor_timeout 3
pyzor_max 10



pyzor_max is the number of reports on the pyzor server required to get a 
positive match, not number of retries.  It seems to be poorly named.


--
Chris