Re: pyzor: check failed: internal error, python traceback seen in response

2014-07-01 Thread Axb
On 07/01/2014 02:57 PM, Steve Bergman wrote: On 06/30/2014 02:15 PM, Axb wrote: As you don't mention what gue you use with SA it's hard to guess where your Pyzor config files should be. I guess I'm not quite sure what gue I am using with SA. Where would I find that? phatfingers meant "glue"

Re: pyzor: check failed: internal error, python traceback seen in response

2014-07-01 Thread Steve Bergman
On 06/30/2014 02:15 PM, Axb wrote: As you don't mention what gue you use with SA it's hard to guess where your Pyzor config files should be. I guess I'm not quite sure what gue I am using with SA. Where would I find that?

Re: pyzor: check failed: internal error, python traceback seen in response

2014-07-01 Thread Steve Bergman
pyzor 1:0.5.0-0ubuntu2 ancient, buggy, EOL version Interestingly, pyzor 0.7.0 (the latest stable version) gives the same error. And SA is not preserving the diagnostic output from it for the admin to view, even with debuging turned on in both packages. Looks like the bugs are in Spamassas

Re: pyzor: check failed: internal error, python traceback seen in response

2014-07-01 Thread Steve Bergman
Hmmm... My original question was "where's the traceback". Not whether this or that project chooses to abandon its stable releases. Ubuntu 10.04 LTS Server is supported until May 2015. And similar time-frame releases of SA and Pyzor are supported until 2020 in RHEL/Scientific Linux/Centos. I'

Re: pyzor: check failed: internal error, python traceback seen in response

2014-07-01 Thread Matus UHLAR - fantomas
On 06/30/2014 08:58 PM, Steve Bergman wrote: I'm getting: "pyzor: check failed: internal error, python traceback seen in response" I'm running Ubuntu 10.04 on the server, with the Ubuntu provided packages. On 30.06.14 21:15, Axb wrote: time to update... pyzor 1:0.5.0

Re: pyzor: check failed: internal error, python traceback seen in response

2014-06-30 Thread Axb
On 06/30/2014 08:58 PM, Steve Bergman wrote: Hi, I'm getting: "pyzor: check failed: internal error, python traceback seen in response" on many Spamassassin generated calls to pyzor. In the case of good emails, at least, the senders report getting a bounce, but the emails mak

pyzor: check failed: internal error, python traceback seen in response

2014-06-30 Thread Steve Bergman
Hi, I'm getting: "pyzor: check failed: internal error, python traceback seen in response" on many Spamassassin generated calls to pyzor. In the case of good emails, at least, the senders report getting a bounce, but the emails make it through to the recipient. Despite add

pyzor: check failed: internal error, python traceback seen in response

2014-03-05 Thread Thomas Cameron
var/log/maillog every time I start up SpamAssassin: Mar 5 23:26:34 ns2 spamd[9065]: pyzor: check failed: internal error, python traceback seen in response I've done pyzor -discover as the spam user, and pyzor ping reports everything is OK. What am I doing wrong? Everything is, as far as I can tell, running as "spam." Why am I getting an error in pyzor when SA starts up? Anyone know? Thomas