Mailing List Archive: pyzor and failure to parse response

pyzor and failure to parse response

Nov 20, 2022, 8:58 AM

Post #1 of 3 (225 views)

Hi,
I'm using the latest SA from trunk and trying to get pyzor working. It runs
correctly to check a message from the command-line, but SA apparently fails
to properly parse the output?

Nov 20 11:55:13.213 [2531397] dbg: pyzor: network tests on, attempting Pyzor
Nov 20 11:55:15.756 [2531397] dbg: pyzor: adjusting rule PYZOR_CHECK
priority to -100
Nov 20 11:55:21.963 [2531397] dbg: pyzor: pyzor is available: /usr/bin/pyzor
Nov 20 11:55:21.968 [2531521] dbg: pyzor: child process 2531521 forked
Nov 20 11:55:21.970 [2531521] dbg: pyzor: opening pipe: /usr/bin/pyzor
--homedir /var/spool/amavisd/.pyzor --debug --log-file
/var/spool/amavisd/.pyzor/pyzor.log check
</tmp/.spamassassin2531397BVp8kXtmp
Nov 20 11:55:22.233 [2531521] dbg: pyzor: [2531522] finished: exit 1
Nov 20 11:55:22.480 [2531397] dbg: pyzor: child process 2531521 finished,
reading results
Nov 20 11:55:22.481 [2531397] dbg: pyzor: got response: 2022-11-20
11:55:22,070 (2531522) DEBUG sending: 'Op: check\\nOp-Digest:
d4b0fd297cb1bf9332b0bcba8dd026bfd58d7067\\nThread: 41907\\nPV: 2.1\\nUser:
anonymous\\nTime: 1668963322\\nSig:
86e3776ffd084e69ef20025588864b26a851882f\\n\\n'
Nov 20 11:55:22.481 [2531397] info: pyzor: failure to parse response
"2022-11-20 11:55:22,070 (2531522) DEBUG sending: 'Op: check\\nOp-Digest:
d4b0fd297cb1bf9332b0bcba8dd026bfd58d7067\\nThread: 41907\\nPV: 2.1\\nUser:
anonymous\\nTime: 1668963322\\nSig:
86e3776ffd084e69ef20025588864b26a851882f\\n\\n'"
Nov 20 11:55:22.481 [2531397] dbg: pyzor: got response: 2022-11-20
11:55:22,221 (2531522) DEBUG received: b'Code: 200\\nDiag: OK\\nPV:
2.1\\nThread: 41907\\nCount: 0\\nWL-Count:0\\n\\n'/('154.61.86.89', 24441)
Nov 20 11:55:22.481 [2531397] info: pyzor: failure to parse response
"2022-11-20 11:55:22,221 (2531522) DEBUG received: b'Code: 200\\nDiag:
OK\\nPV: 2.1\\nThread: 41907\\nCount:0\\nWL-Count:
0\\n\\n'/('154.61.86.89', 24441)"
Nov 20 11:55:22.481 [2531397] dbg: pyzor: got response:
public.pyzor.org:24441\t(200, 'OK')\t0\t0
Nov 20 11:55:22.481 [2531397] dbg: pyzor: result: COUNT=0/5
WELCOMELIST=0/10/0.0

$ pyzor --version
/usr/bin/pyzor 1.1.1

$ spamassassin --version
SpamAssassin version 4.0.0-r1904221
running on Perl version 5.36.0

Re: pyzor and failure to parse response [ In reply to ]

hege at hege

Nov 20, 2022, 9:54 AM

Post #2 of 3 (225 views)

Permalink

On Sun, Nov 20, 2022 at 11:58:31AM -0500, Alex wrote:
> Hi,
> I'm using the latest SA from trunk and trying to get pyzor working. It runs
> correctly to check a message from the command-line, but SA apparently fails to
> properly parse the output?
>
> Nov 20 11:55:21.970 [2531521] dbg: pyzor: opening pipe: /usr/bin/pyzor
> --homedir /var/spool/amavisd/.pyzor --debug --log-file /var/spool/amavisd
> /.pyzor/pyzor.log check </tmp/.spamassassin2531397BVp8kXtmp

Your --debug parameter is messing up the output, remove it from
pyzor_options.

Re: pyzor and failure to parse response [ In reply to ]

mysqlstudent at gmail

Nov 20, 2022, 10:00 AM

Post #3 of 3 (225 views)

Permalink

On Sun, Nov 20, 2022 at 12:54 PM Henrik K <hege@hege.li> wrote:

> On Sun, Nov 20, 2022 at 11:58:31AM -0500, Alex wrote:
> > Hi,
> > I'm using the latest SA from trunk and trying to get pyzor working. It
> runs
> > correctly to check a message from the command-line, but SA apparently
> fails to
> > properly parse the output?
> >
> > Nov 20 11:55:21.970 [2531521] dbg: pyzor: opening pipe: /usr/bin/pyzor
> > --homedir /var/spool/amavisd/.pyzor --debug --log-file /var/spool/amavisd
> > /.pyzor/pyzor.log check </tmp/.spamassassin2531397BVp8kXtmp
>
> Your --debug parameter is messing up the output, remove it from
> pyzor_options.
>

Ah yes, of course, thanks.