Pyzor issue - error from Mailscanner but not from SA or Pyzor run directly

[Glenn Steen]

On 3 August 2010 19:34, Alex Crow <alex at nanogherkin.com> wrote:
> On 31/07/10 15:46, Alex Crow wrote:
>>
>> Hi all,
>>
>> I'm having this issue in MailScanner - when Pyzor check are run from
>> within ms, I get an error in the logs:
>>
>> 15:37:52 Jul 31 15:37:52.686 [13270] dbg: pyzor: pyzor is available:
>> /usr/bin/pyzor
>> 15:37:52 Jul 31 15:37:52.686 [13270] dbg: dns: entering helper-app run
>> mode
>> 15:37:52 Jul 31 15:37:52.686 [13270] dbg: pyzor: opening pipe:
>> /usr/bin/pyzor -d check < /tmp/.spamassassin13270K6yw83tmp
>> 15:37:52 Jul 31 15:37:52.690 [13272] dbg: util: setuid: ruid=89 euid=89
>> 15:37:52 Jul 31 15:37:52.693 [13270] info: pyzor: [13272] error: exit 6
>> 15:37:52 Jul 31 15:37:52.693 [13270] dbg: dns: leaving helper-app run mode
>> 15:37:52 Jul 31 15:37:52.694 [13270] dbg: pyzor: check failed: no response
>>
>> However, if I run as the postfix user (the one configured in
>> MailScanner.conf)
>>
>> spamassassin -D < /tmp/.spamassassin9936b1QieYtmp
>>
>> I get pyzor working:
>>
>> Jul 31 15:45:05.186 [13308] dbg: pyzor: pyzor is available: /usr/bin/pyzor
>> Jul 31 15:45:05.186 [13308] dbg: dns: entering helper-app run mode
>> Jul 31 15:45:05.187 [13308] dbg: pyzor: opening pipe: /usr/bin/pyzor -d
>> check < /tmp/.spamassassin13308yrAHtDtmp
>> Jul 31 15:45:05.189 [13311] dbg: util: setuid: ruid=89 euid=89
>> Jul 31 15:45:05.242 [13308] dbg: pyzor: [13311] finished successfully
>> Jul 31 15:45:05.242 [13308] dbg: pyzor: got response: sending: 'User:
>> anonymous\nTime: 1280587505\nSig:
>> 47f0553e50650e0309d871f46cdc5dde598c3b1d\n\nOp: check\nOp-Digest:
>> 2108c5b03e2f3f526b3158395a05899745cde179\nThread: 9258\nPV:
>> 2.0\n\n'\nreceived: 'Thread: 9258\nCount: 5301\nWL-Count: 0\nCode:
>> 200\nDiag: OK\nPV: 2.0\n\n'\npublic.pyzor.org:24441 (200, 'OK') 5301 0
>> Jul 31 15:45:05.243 [13308] dbg: dns: leaving helper-app run mode
>> Jul 31 15:45:05.243 [13308] dbg: pyzor: failure to parse response
>> "sending: 'User: anonymous\nTime: 1280587505\nSig:
>> 47f0553e50650e0309d871f46cdc5dde598c3b1d\n\nOp: check\nOp-Digest:
>> 2108c5b03e2f3f526b3158395a05899745cde179\nThread: 9258\nPV: 2.0\n\n'"
>> Jul 31 15:45:05.243 [13308] dbg: pyzor: failure to parse response
>> "received: 'Thread: 9258\nCount: 5301\nWL-Count: 0\nCode: 200\nDiag: OK\nPV:
>> 2.0\n\n'"
>> Jul 31 15:45:05.243 [13308] dbg: pyzor: listed: COUNT=5301/5 WHITELIST=0
>> Jul 31 15:45:05.244 [13308] dbg: rules: ran eval rule PYZOR_CHECK ======>
>> got hit (1)
>>
>> I am running Centos 5.5 x64 with the latest ClamAV/SA easy-install package
>> from the MailScanner site installed.
>>
>> Any help gratefully received.
>>
>> Thanks
>>
>> Alex
>
> All,
>
> Are there any more details I need to provide for this?
>
> TBH I seems like a command parsing issue as with my first test with real
> messages (copied from another MS server's queue) the error was still in the
> logs but Pyzor scores were recorded (verified in MailWatch).
>
> Cheers
>
> Alex
>
Did you do your pyzor tests as the user postfix is running as? Probably not;).

Do "su - postfix -s /bin/bash" and then redo the SA test from there...
It'll likely fail.
My guess is that your postfix user cannot get at the correct pyzor
config (amoung other things), so fixing that config/permission issue
will likely make things hum along a bit better:)

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se