On Fri, 22 Apr 2016 13:42:28 +0200 İhsan Doğan wrote: > On Friday, 22 Apr 2016 13:03 +0200, Reindl Harald wrote: > > > > I've installed Spamassassin 3.4.1 on FreeBSD 10.3 together with > > > Pyzor 0.7.0 and Razor 2.84. I'm using Spamassassin through > > > amavisd-new. > > > > > > When executed manually, both, Razor and Pyzor are fine: > > > > > > $ pyzor --homedir /some/dir ping > > > public.pyzor.org:24441 (200, 'OK') > > > > anmd spamassassin is running as the same user and has permissions > > to the homedir with it#s configuration? > > My first thought was also, that it could be a permissions issue. > I've double checked that and the amavisd-new user has read/write > access to this directory
SA didn't even start a pyzor process, so it can't be a runtime pyzor error. In the version that worked, you had: dbg: pyzor: network tests on, attempting Pyzor dbg: pyzor: pyzor is available: /opt/csw/bin/pyzor dbg: pyzor: ... in the version that didn't, the only debug is dbg: pyzor: network tests on, attempting Pyzor This doesn't suggest that pyzor is missing because then you'd expect an alternate debug line saying so, it suggests that check_pyzor() isn't being called. Check your rules to see if PYZOR_CHECK has been redefined or scored at 0.
