Re: Is pyzor active?

[John E H. <jh...@ti...>]

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:

sh -xc 'time pyzor -d check < some_email'
+ time pyzor -d check
calculated digest: dac867e642c5abc187f4cdd7cebc86d2d959fda9
sending: 'User: anonymous\nTime: 1151427741\nSig: b0373e9cfd8b57db9f8e74af370038609a0bd92e\n\nOp: check\nOp-Digest: dac867e642c5abc187f4cdd7cebc86d2d959fda9\nThread: 45631\nPV: 2.0\n\n'
66.250.40.33:24441      TimeoutError: 
        5.13 real         0.07 user         0.01 sys


I don't see a way to adjust that in the docs, but it's probably easy
to change in the source code.  From my timing tests, however, I don't
think it will help.  It looks like the success cases always happen in
less than 1 second.

So now I am back to not knowing why SA 3.1.1 seems to hit PYZOR_CHECK
far less than SA 2.63.