pyzor functionality

[Scott Silva]

Stephen Swaney spake the following on 11/15/2006 9:19 AM:
>> -----Original Message-----
>> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-
>> bounces at lists.mailscanner.info] On Behalf Of Scott Silva
>> Sent: Wednesday, November 15, 2006 12:04 PM
>> To: mailscanner at lists.mailscanner.info
>> Subject: Re: pyzor functionality
>>
>> Martin Hepworth spake the following on 11/15/2006 8:17 AM:
>>> David Lee wrote:
>>>> On Wed, 15 Nov 2006, Martin Hepworth wrote:
>>>>
>>>>> Erik van der Leun wrote:
>>>>>> Hi,
>>>>>>
>>>>>> On several servers, PYZOR seems to work every now and then...
>>>>>> I can't seem to find a reason why... no errormessages when checking
>>>>>> with
>>>>>> --lint
>>>>>>
>>>>>> To be honest, I don't have much of a clue...
>>>>>>
>>>>>> What would be a good way of testing whether the online request gets a
>>>>>> proper answer?
>>>>>> [...]
>>>>>> # spamassassin --lint -D 2>&1 | grep -i pyzor
>>>>>> [16257] dbg: config: read file /usr/share/spamassassin/25_pyzor.cf
>>>>>> [16257] dbg: plugin: loading Mail::SpamAssassin::Plugin::Pyzor from
>>>>>> @INC
>>>>>> [16257] dbg: pyzor: network tests on, attempting Pyzor
>>>>>> [16257] dbg: plugin: registered
>>>>>> Mail::SpamAssassin::Plugin::Pyzor=HASH(0x158ffe00)
>>>>>> [16257] dbg: plugin: registering glue method for check_pyzor
>>>>>> (Mail::SpamAssassin::Plugin::Pyzor=HASH(0x158ffe00))
>>>>>> [16257] dbg: pyzor: pyzor is available: /usr/bin/pyzor
>>>>>> [16257] dbg: pyzor: opening pipe: /usr/bin/pyzor check <
>>>>>> /tmp/.spamassassin16257UZ6Czhtmp
>>>>>> [16257] dbg: pyzor: killed stale helper [16322]
>>>>>> [16257] dbg: pyzor: [16322] terminated: exit=0x000f
>>>>>> [16257] dbg: pyzor: check timed out after 5 seconds
>>>>>>
>>>>> Erik
>>>>>
>>>>> I'd echo what Steve S just said. remove it from your configs.
>>>> But pyzor is a useful item in the spam/ham discrimination battle, and
>>>> nice
>>>> to keep if reasonably possible.
>>>>
>>>> A few weeks ago there was a thread here on the MailScanner list which
>>>> suggested that the default pyzor server was in some sort of long-term
>>>> trouble, but that someone else was maintaining another pyzor server.
>>>> See:
>>>>
>>>> http://lists.mailscanner.info/pipermail/mailscanner/2006-
>> September/065292.html
>>>>
>>>> So before removing pyzor, it might be worth trying that alternative
>>>> server.  You probably have a ".pyzor" directory (possible in root's
>> home
>>>> directory) containing a file "servers", itself containing the old
>> IP:port
>>>> as "66.250.40.33:24441".  The new one seems to be
>> "82.94.255.100:24441".
>>>> (The issue of local trust of, and reliance upon, such remote services
>>>> (whether pyzor, Razor, DCC, the various RBLs etc.) is another
>> matter...)
>>> David
>>>
>>> cool, I'll that a go....
>>>
>> I just have the following in cron.daily;
>> <code>
>> #!/bin/bash
>> pyzor discover
>> echo 82.94.255.100:24441 >>/.pyzor/servers
>> </code>
>>
>> --
> 
> I can confirm:
> 
> 82.94.255.100:24441 seems to be responding right now
> 
> `echo 82.94.255.100:24441 >> /root/.pyzor/servers` corrects the host that
> Pyzor uses
> 
> Running `Pyzor discover` writes the bad data ""66.250.40.33:24441" to
> .pyzor/servers "66.250.40.33:24441" :(
> 
> Steve
> 
> Stephen Swaney
> Fort Systems Ltd.
> stephen.swaney at fsl.com
> www.fsl.com
> 
I have not had a lot of problems with the default server, but added the second
address as a fallback. I didn't look at the pyzor code to see if it would hurt
anything, but I had noticed that the pyzor hits have been decreasing before I
added this. Maybe I will run for a while with just the other server. Razor and
DCC are responsible for far more tagging than pyzor ever was.

-- 

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!