|
From: John H. <joh...@pl...> - 2006-06-27 18:13:34
|
On Tue, 2006-06-27 at 11:43 -0600, John E Hein wrote:
> Bill McCormick wrote at 11:02 -0500 on Jun 27, 2006:
> > >Okay, after looking through the SA source... 3.1.1 uses a 5 seconds
> > >timeout by default. 2.63 uses 10. I'm going to try bumping up the 5
> > >second timeout to see how it affects my hit percentage. Other than
> > >the timeout, the pyzor_lookup code looks similar on the surface.
> > >
> > Where/How do you set the time out?
>
> man Mail::SpamAssassin::Plugin::Pyzor
>
> But in retrospect, I don't think this will help. SA just invokes
> 'pyzor check' and sets a timeout around that. Since pyzor has its own
> notion of a timeout, waiting longer than pyzor's timeout (plus a
> little overhead for forking) isn't going to buy you anything.
>
> It looks like pyzor's timeout is 5 seconds:
>
You might want to try creating in your ~/.pyzor directory a 'config'
file. In that file put this:
[client]
ServersFile = servers
Timeout = 5
There is, as far as I can tell, a '[server]' section too which can take
a timeout (I suspect used for reporting rather than checking). However,
depending on your setup, you need to make sure you create the file in
the directory of the user that SA uses to run the 'pyzor check' command.
Note, I haven't checked any of this, other than by using 'pyzor ping'.
It works for that. (I don't have SA set up on this PC to use pyzor.)
John.
--
---------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: Joh...@pl... Fax: +44 (0)1752 233839
|