On Sat, 2012-10-06 at 15:27 +0200, Tom Hendrikx wrote: > > Oct 6 11:11:52.056 [10904] dbg: pyzor: opening pipe: /bin/pyzor > --homedir /home/mark/.pyzor check < /tmp/.spamassassin10904BmyCb9tmp > Oct 6 11:11:52.344 [10904] dbg: pyzor: [10906] finished: exit 1 > > Seems trivial to reproduce the part where spamassassin sees the > problem: just run the piped command yourself.
OK - I don't know what the output means though!... ============================8<======================================= $ pyzor -d --homedir /home/mark/.pyzor check < spam1.txt sending: 'User: anonymous\nTime: 1349530888\nSig: 011dffafd6c01568e1ebdc453bf9feae2bb000e9\n\nOp: check\nOp-Digest: 6da5a18b2eda6b5db73a8747932e84436d653cd5\nThread: 31045\nPV: 2.0\n\n' received: 'Code: 200\nDiag: OK\nPV: 2.1\nThread: 31045\nCount: 0\nWL-Count: 0\n\n' public.pyzor.org:24441 (200, 'OK') 0 0 ============================8<======================================= > > 'man pyzor' might give you more details on enabling debug output for > the above when the command does not emit anything useful by itself. > $ man pyzor No manual entry for pyzor Am I worrying unnecessarily? I don't know for certain that "exit 1" means that it failed. Does it just mean that Pyzor did not "hit" on this particular message? Thanks for the help so far... Mark
signature.asc
Description: This is a digitally signed message part
