RE: R: pyzor server address
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
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
R: pyzor server address
> I have a simple question... someone know a good pyzor server? > > Right now "pyzor discover" give me "66.250.40.33:24441" > and a "pyzor ping" give me " 66.250.40.33:24441 TimeoutError:" > > So I suppose this server is just dead... Actually, I already heard this question and is probably better addressed to the pyzor list. However, the fact is that the 66.250.40.33 seems to be a bit overwhelmed and just can't handle many of the requests it receives. A new server had been setup (82.94.255.100:24441). The problem is that the pyzor project actually doesn't provide any mean to replicate the data among the two servers. However, efforts in this matter are going to be spent and it may be that a replicating layer will be available within weeks. Actually, you have two options: a) manually change your server to 82.94.255.100:24441. If you choose this, expect to have less spam reports from Pyzor: much less people uses 82.91.255.100; 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 your mileage may vary. If you like, there is also a third option which uses both servers. The SA patch http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5148 is needed in order to adopt this. Regards, --- Giampaolo Tomassoni - IT Consultant Piazza VIII Aprile 1948, 4 I-53044 Chiusi (SI) - Italy Ph: +39-0578-21100 MAI inviare una e-mail a: NEVER send an e-mail to: [EMAIL PROTECTED] > > Thanks > > Francois Rousseau
pyzor server address
I have a simple question... someone know a good pyzor server?Right now "pyzor discover" give me "66.250.40.33:24441"and a "pyzor ping" give me " 66.250.40.33:24441 TimeoutError:"So I suppose this server is just dead...ThanksFrancois Rousseau
