Re: pyzor: check failed: internal error, python traceback seen in response
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-0ubuntu2 ancient, buggy, EOL version for both issues, you should ask help on ubuntu. I have no idea whether 10.04 is supported still (is that LTS version?) but ubuntu should take care about such issues if it's supported (well, that's what support means) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. REALITY.SYS corrupted. Press any key to reboot Universe.
Re: pyzor: check failed: internal error, python traceback seen in response
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'm sure that bugs have been fixed, and new ones introduced, in later versions of both packages. All I really want is to find some diagnostic output. When I run Pyzor from the command line on the same emails it returns without an error. -Steve Bergman
Re: pyzor: check failed: internal error, python traceback seen in response
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 Spamassassin. I guess I'm not sure why such buggy software would ever have been released as gold in the first place. -Steve
Re: pyzor: check failed: internal error, python traceback seen in response
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
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 - how do you interface spamassassin with your MTA/MUA amavisd, procmail, some milter, etc.. running under what user etc
pyzor: check failed: internal error, python traceback seen in response
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 adding '-d' to the pyzor options, I haven't been able to actually look at a traceback. Could anyone direct me to how to find an actual traceback? On a related note, we have postfix aliases. Should I be explicitly giving a --homedir for pyzor? I'm not sure what that servers file is about. Setting a --homedir doesn't seem to fix the problem. I'm running Ubuntu 10.04 on the server, with the Ubuntu provided packages. spamassassin 3.3.1-1 pyzor 1:0.5.0-0ubuntu2 Thank you for any enlightenment on this. Steve Bergman
Re: pyzor: check failed: internal error, python traceback seen in response
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 make it through to the recipient. Despite adding '-d' to the pyzor options, I haven't been able to actually look at a traceback. Could anyone direct me to how to find an actual traceback? On a related note, we have postfix aliases. Should I be explicitly giving a --homedir for pyzor? I'm not sure what that servers file is about. Setting a --homedir doesn't seem to fix the problem. I'm running Ubuntu 10.04 on the server, with the Ubuntu provided packages. spamassassin 3.3.1-1 time to update... pyzor 1:0.5.0-0ubuntu2 ancient, buggy, EOL version All the docs on: http://www.pyzor.org/en/latest/ There's been lots of small bugs fixes imprevement lately. As you don't mention what gue you use with SA it's hard to guess where your Pyzor config files should be.
pyzor: check failed: internal error, python traceback seen in response
Howdy, I'm running SA on a RHEL 6.5 machine.
Using spamassassin-3.3.1-3.el6.x86_64, pyzor-0.5.0-3.el6.noarch,
spamass-milter-0.3.2-3.el6.x86_64 and milter-greylist-4.5.7-1.el6.x86_64
(if that matters).
The relevant parts of my sendmail.mc are:
INPUT_MAIL_FILTER(`spamassassin',
`S=unix:/var/run/spamass-milter/spamass-milter.sock, F=,
T=C:15m;S:4m;R:4m;E:10m')dnl
define(`confMILTER_MACROS_CONNECT',`t, b, j, _, {daemon_name},
{if_name},{if_addr}')dnl
INPUT_MAIL_FILTER(`greylist',`S=local:/var/run/milter-greylist/milter-greylist.sock')dnl
define(`confMILTER_MACROS_HELO', `{verify}, {cert_subject}')dnl
define(`confMILTER_MACROS_ENVFROM', `i, {auth_authen}')dnl
define(`confMILTER_MACROS_ENVRCPT', `b, r, v, Z, {greylist}')dnl
define(`confINPUT_MAIL_FILTERS', `spamassassin, greylist')
I set spamassassin to run as user spam:
[root@ns2 ~]# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTIONS=-u spam -d -c -m5 -H
I also set spamass-milter to run as spam:
[root@ns2 ]# grep RUN_AS_USER /etc/rc.d/init.d/spamass-milter
RUN_AS_USER=spam
...
I am seeing this in /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
