I've been able to re-discover pyzor servers (and it always winds up with the same server) and get pyzor working for a couple hours before the "couldn't grok response '...TimeoutErrors'" begins again. I've disabled Pyzor and just written it off to my own ignorance. Basically once it starts not grokking, it successfully queries roughly 10% of the time. And I've increased the timeout beyond belief, too. Idunno. Disabled works for me, at this point.
> -----Original Message----- > From: Robert Leonard III [mailto:[EMAIL PROTECTED] > Sent: Friday, October 03, 2003 9:51 AM > To: [EMAIL PROTECTED] > Subject: Re: [SAtalk] Re: Pyzor in 2.60? > > > The solution was given to me yesterday... and it, as many > solutions are, was > easy.. if not obvious.. > > On Pyzors website they state that their servers IP address > have changed and > you need to run 'pyzor discover'... > > I did.. it re-discovered.. and it now works... > > :) > > > > > Here is what I see when I run spamassassin --lint -D > > > > > > debug: Pyzor is available: /usr/bin/pyzor > > > debug: entering helper-app run mode > > > debug: Pyzor: got response: 66.47.67.162:24441 TimeoutError: > > > debug: leaving helper-app run mode > > > debug: Pyzor: couldn't grok response "66.47.67.162:24441 > > > TimeoutError: " ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
