You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Al.Aeefyu" <ae...@gmail.com> on 2004/06/25 09:12:23 UTC
Pyzor /w SA not working anymore?
Hi there
I am running a postfix/amavisd-new/SA on FreeBSD-4.9 machine. All
components are built from the FreeBSD ports tree:
postfix 2.1.1
amavisd-new-20030616-p9
spamassassin 2.63_2
razor_agents 2.40
dcc-dccd-1.2.48
pyzor 0.4.0.3
SA has been working very well in our setup, and although its not 100%
(which it never claims to be), it catches most of the nuisances.
However, during one of our routine checks, we discovered that recently
no spams scores are contributed by Pyzor. I have no records when this
actually happens, though i vaguely recall Pyzor used to work with our
SA installation before.
I have use_pyzor 1 in local.conf, and ran "pyzor discover" repeatedly
(~/.pyzor/servers are confirmed to be updated)
We even modified our firewall to explicitly allow any UDP from the
pyzor server with same negative results
running spamassassin -P -t -D < /tmp/spam.txt:
.....
debug: Pyzor is available: /usr/local/bin/pyzor
debug: entering helper-app run mode
debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
debug: leaving helper-app run mode
debug: Pyzor: couldn't grok response "66.250.40.33:24441 TimeoutError: "
......
Same error everytime.
What gives? The Pyzor mailing lists doesnt seem to be helpful so far,
nor does googling. Is this an isolated incident, or is Pyzor not
working with SA 2.63 everywhere else?
thanks for any replies/suggestions
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by "Al.Aeefyu" <ae...@gmail.com>.
> > I doubt it since it appears that pyzor is doing everything it needs to do
> > (calculating the digest, defining the user and sig, attempting to deliver
> > the payload to the pyzor server),
> but either cannot deliver the payload or
> > cannot receive the response back. Sure sounds like a network issue to me.
OK. Basically i cant get Pyzor working on my setup. No matter what I
do, (even turning of my firewall), I get:
[1455][vscan@beta: siteadm]$ pyzor -d check < /tmp/spam.txt
calculated digest: c5329bdd61f2d8c11dafce62232ce3ff9ab05a58
sending: 'User: anonymous\nTime: 1089010532\nSig:
dd53b82fd445b98965dece74982b415722d87132\n\nOp: check\nOp-Digest:
c5329bdd61f2d8c11dafce62232ce3ff9ab05a58\nThread: 48324\nPV: 2.0\n\n'
66.250.40.33:24441 TimeoutError:
The only networking components I havent gone through is the perimeter
routers, to which I've no access, and requests to the administrators
have thus far met with silence.
sighs.
Guess I have to live without pyzor checks for now
Thanks all.
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by "Al.Aeefyu" <ae...@gmail.com>.
On Mon, 28 Jun 2004 09:13:20 -0700, Bill Landry <bi...@pointshare.com> wrote:
> I doubt it since it appears that pyzor is doing everything it needs to do
> (calculating the digest, defining the user and sig, attempting to deliver
> the payload to the pyzor server),
OK. Didnt know this was a sign Pyzor working proper (although I should
have known by common sense .. sighs)
but either cannot deliver the payload or
> cannot receive the response back. Sure sounds like a network issue to me.
>
At this point I agree with you. Yes, re-installing was a waste of
time. I am back to square one. Will go through the networks and report
here my findings - wether +ve or -ve
Thanks all
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by Bill Landry <bi...@pointshare.com>.
----- Original Message -----
From: "Al.Aeefyu" <ae...@gmail.com>
> [1716][vscan@host: amavis]$ pyzor -d --homedir /var/amavis/.pyzor
> check < /tmp/spam.txt
> calculated digest: c5329bdd61f2d8c11dafce62232ce3ff9ab05a58
> sending: 'User: anonymous\nTime: 1088414211\nSig:
> 3333d7a8faaea530b03b77e3e90550b30f6a82c9\n\nOp: check\nOp-Digest:
> c5329bdd61f2d8c11dafce62232ce3ff9ab05a58\nThread: 57015\nPV: 2.0\n\n'
> 66.250.40.33:24441 TimeoutError:
>
> OK. Officially am convinced there is something wrong with my local
> pyzor installation rather than any network-related problems
I doubt it since it appears that pyzor is doing everything it needs to do
(calculating the digest, defining the user and sig, attempting to deliver
the payload to the pyzor server), but either cannot deliver the payload or
cannot receive the response back. Sure sounds like a network issue to me.
> Will try to re-install python and pyzor tonight.
Okay, but sounds like a waste of time, especially since you have already
tried that before and still gotten the same result. I would start looking
into network issue, starting with the perimeter router and working my way
back to the server.
Just my 2 cents... Good luck!
Bill
Re: Pyzor /w SA not working anymore?
Posted by "Al.Aeefyu" <ae...@gmail.com>.
On Mon, 28 Jun 2004 01:51:12 -0700, Bill Landry <bi...@pointshare.com> wrote:
> What do you get from:
> pyzor ping
[1705][vscan@host: amavis]$ pyzor ping
66.250.40.33:24441 TimeoutError:
> pyzor -d check < /tmp/spam.txt
[1716][vscan@host: amavis]$ pyzor -d --homedir /var/amavis/.pyzor
check < /tmp/spam.txt
calculated digest: c5329bdd61f2d8c11dafce62232ce3ff9ab05a58
sending: 'User: anonymous\nTime: 1088414211\nSig:
3333d7a8faaea530b03b77e3e90550b30f6a82c9\n\nOp: check\nOp-Digest:
c5329bdd61f2d8c11dafce62232ce3ff9ab05a58\nThread: 57015\nPV: 2.0\n\n'
66.250.40.33:24441 TimeoutError:
OK. Officially am convinced there is something wrong with my local
pyzor installation rather than any network-related problems
Will try to re-install python and pyzor tonight.
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by Bill Landry <bi...@pointshare.com>.
----- Original Message -----
From: "Al.Aeefyu" <ae...@gmail.com>
> $sa_local_tests_only is set to 0. This is confirmed because other
> checks such as Razor and DCC is working A-OK
>
> > amavisd debug-sa
> running spamassassin -P -t -D < /tmp/spam.txt:
> .....
> debug: Pyzor is available: /usr/local/bin/pyzor
> debug: entering helper-app run mode
> debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
> debug: leaving helper-app run mode
> debug: Pyzor: couldn't grok response "66.250.40.33:24441 TimeoutError: "
>
> This is where SA-Pyzor is failing. Apparently it is met with a timeout
> Error from the Pyzor servers (with or without firewall enabled).Have
> repeatedly ran "pyzor discover". On that note, if i run "pyzor check",
> the command is ran indefinitely without getting any results.
What do you get from:
pyzor ping
I get: 66.250.40.33:24441 (200, 'OK')
And what do you get from:
pyzor -d check < /tmp/spam.txt
Here is what I get back:
calculated digest: 8cb3bcf6b607614b8addac079dec9edf97d518c4
sending: 'User: anonymous\nTime: 1088411995\nSig:
8b445b5d7e660139f3c877761f98942839051b6f\n\nOp: check\nOp-Digest:
8cb3bcf6b607614b8addac079dec9edf97d518c4\nThread: 42779\nPV: 2.0\n\n'
received: 'Thread: 42779\nCount: 0\nWL-Count: 0\nCode: 200\nDiag: OK\nPV:
2.0\n\n'
66.250.40.33:24441 (200, 'OK') 0 0
You might want to take a look at:
https://sourceforge.net/docman/display_doc.php?docid=11885&group_id=50000#using-accounts
to see if there is any information that might help you debug your problem.
Good luck!
Bill
Re: Pyzor /w SA not working anymore?
Posted by Loren Wilton <lw...@earthlink.net>.
> debug: Pyzor: couldn't grok response "66.250.40.33:24441 TimeoutError: "
>
> This is where SA-Pyzor is failing. Apparently it is met with a timeout
> Error from the Pyzor servers (with or without firewall enabled).Have
I'm suspicious here. Mind you, I know absolutely nothing about Pyzor, so
may be talking through my hat. But that response looks to me like it GOT a
response of "66.250.40.33:24441", and then was either expecting more data,
or didn't like the data it got.
Two possibiliities occur to me if the above guess is correct. 1) you may
have a locally corrupted version of Pyzor that can't understand a valid
response from the server. I would consider wiping Pyzor and reinstalling,
if this is possible. 2) perhaps there has been a Pyzor update, and the
server is now sending a new data format, and you have an old Pyzor that
can't recognize the new data, so gets confused. Again, wiping Pyzor and
pulling down the latest version may solve the problem.
Perhaps the problem isn't Pyzor directly, but either some library or some
lookup path on your system that may have changed. Again, I know nothing
about Pyzor. But I've noticed people having problems with SA installs and
other installs on an upgrade where part of the stuff starts looking at an
old version of Perl and another part is looking at a newer version. Perhaps
something like this is also possible with Pyzor?
If none of the above makes any sense in relation to Pyzor, just ignore me,
I'm just shooting in the dark here.
Loren
Re: Pyzor /w SA not working anymore?
Posted by Bill Landry <bi...@pointshare.com>.
----- Original Message -----
From: "Al.Aeefyu" <ae...@gmail.com>
> running spamassassin -P -t -D < /tmp/spam.txt:
> .....
> debug: Pyzor is available: /usr/local/bin/pyzor
> debug: entering helper-app run mode
> debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
> debug: leaving helper-app run mode
> debug: Pyzor: couldn't grok response "66.250.40.33:24441 TimeoutError: "
>
> This is where SA-Pyzor is failing. Apparently it is met with a timeout
> Error from the Pyzor servers (with or without firewall enabled).Have
> repeatedly ran "pyzor discover". On that note, if i run "pyzor check",
> the command is ran indefinitely without getting any results.
As a follow-up, it sure appears like something is blocking the connection to
the pyzor server or is blocking the response coming back from the server,
like a firewall or router filter. If I unplug my network cable and run my
test spam message through SA, I receive the same error you are seeing:
debug: Pyzor is available: /usr/bin/pyzor
debug: entering helper-app run mode
debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
debug: leaving helper-app run mode
debug: Pyzor: couldn't grok response "66.250.40.33:24441
TimeoutError: "
Anyway, I would check the firewall or router to see if you can see the
packets leaving your network, and if so, whether you see the return traffic
being blocked.
Again, good luck!
Bill
Re: Pyzor /w SA not working anymore?
Posted by "Al.Aeefyu" <ae...@gmail.com>.
On Mon, 28 Jun 2004 00:59:41 -0700, Bill Landry <bi...@pointshare.com> wrote:
> $sa_local_tests_only = 0; # (default: false)
>
> Make sure you have the "sa_local_tests_only" option above set to 0 or
$sa_local_tests_only is set to 0. This is confirmed because other
checks such as Razor and DCC is working A-OK
> amavisd debug-sa
running spamassassin -P -t -D < /tmp/spam.txt:
.....
debug: Pyzor is available: /usr/local/bin/pyzor
debug: entering helper-app run mode
debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
debug: leaving helper-app run mode
debug: Pyzor: couldn't grok response "66.250.40.33:24441 TimeoutError: "
This is where SA-Pyzor is failing. Apparently it is met with a timeout
Error from the Pyzor servers (with or without firewall enabled).Have
repeatedly ran "pyzor discover". On that note, if i run "pyzor check",
the command is ran indefinitely without getting any results.
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by Bill Landry <bi...@pointshare.com>.
----- Original Message -----
From: "Al.Aeefyu" <ae...@gmail.com>
> > I must have missed your original posting, so I don't know what issue you
are
> > having. I am running the exact same configuration you show above on
RedHat
> > 9 on several machines, and pyzor is working just fine for me.
>
> I am running a postfix/amavisd-new/SA on FreeBSD-4.9 machine. All
> components are built from the FreeBSD ports tree:
>
> postfix 2.1.1, amavisd-new-20030616-p9, spamassassin 2.63_2,
> razor_agents 2.40, dcc-dccd-1.2.48, pyzor 0.4.0.3
>
> ..... snipped ...
>
> However, during one of our routine checks, we discovered that recently
> no spams scores are contributed by Pyzor. I have no records when this
> actually happens, though i vaguely recall Pyzor used to work with our
> SA installation before.
>
> I have use_pyzor 1 in local.conf, and ran "pyzor discover" repeatedly
> (~/.pyzor/servers are confirmed to be updated)
>
> We even modified our firewall to explicitly allow any UDP from the
> pyzor server with same negative results
>
> running spamassassin -P -t -D < /tmp/spam.txt:
> .....
> debug: Pyzor is available: /usr/local/bin/pyzor
> debug: entering helper-app run mode
> debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
> debug: leaving helper-app run mode
> debug: Pyzor: couldn't grok response "66.250.40.33:24441
TimeoutError: "
Check your SA settings in your amavisd.conf file. You will find the SA
settings in Section VII:
# SpamAssassin settings
# $sa_local_tests_only is passed to Mail::SpamAssassin::new as a value
# of the option local_tests_only. See Mail::SpamAssassin man page.
# If set to 1, SA tests are restricted to local tests only, i.e. no tests
# that require internet access will be performed.
#
$sa_local_tests_only = 0; # (default: false)
Make sure you have the "sa_local_tests_only" option above set to 0 or
amavisd will override your SA local.cf settings and not run any non-local
tests like pyzor. If everything looks okay in your amavisd.conf file, then
try starting amavisd-new in debug mode and see what it reports for pyzor:
amavisd debug-sa
This will write all amavisd start-up info to the screen, as well as all
logging info, so do a ctrl-c to stop amavisd after all start-up scripts have
run so you can see what amavisd reported about pyzor.
Bill
Re: Pyzor /w SA not working anymore?
Posted by "Al.Aeefyu" <ae...@gmail.com>.
On Sun, 27 Jun 2004 20:48:59 -0700, Bill Landry <bi...@pointshare.com> wrote:
> From: "Al.Aeefyu" <ae...@gmail.com>
> > Did that, as it was the only suggestion obtained on this list.
> > Sighs - still not working.
> > I guess I have to wait for anyone else, using my particular setup -
> > postfix:amavisd-new:SA:pyzor to acknowledge he/she doesnt have the
> > particular problem
>
> I must have missed your original posting, so I don't know what issue you are
> having. I am running the exact same configuration you show above on RedHat
> 9 on several machines, and pyzor is working just fine for me.
I am running a postfix/amavisd-new/SA on FreeBSD-4.9 machine. All
components are built from the FreeBSD ports tree:
postfix 2.1.1, amavisd-new-20030616-p9, spamassassin 2.63_2,
razor_agents 2.40, dcc-dccd-1.2.48, pyzor 0.4.0.3
..... snipped ...
However, during one of our routine checks, we discovered that recently
no spams scores are contributed by Pyzor. I have no records when this
actually happens, though i vaguely recall Pyzor used to work with our
SA installation before.
I have use_pyzor 1 in local.conf, and ran "pyzor discover" repeatedly
(~/.pyzor/servers are confirmed to be updated)
We even modified our firewall to explicitly allow any UDP from the
pyzor server with same negative results
running spamassassin -P -t -D < /tmp/spam.txt:
.....
debug: Pyzor is available: /usr/local/bin/pyzor
debug: entering helper-app run mode
debug: Pyzor: got response: 66.250.40.33:24441 TimeoutError:
debug: leaving helper-app run mode
debug: Pyzor: couldn't grok response "66.250.40.33:24441 TimeoutError: "
Bill,
you have any ideas what I might have missed?
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by Bill Landry <bi...@pointshare.com>.
----- Original Message -----
From: "Al.Aeefyu" <ae...@gmail.com>
> > Unfortunately the only solid suggestions I have are for things you've
> > already done (pyzor discover, check the firewall, etc.) File
permissions,
> > maybe? Or have you upgraded Python recently? (Reinstalling Pyzor may
help.)
>
> Did that, as it was the only suggestion obtained on this list.
> Sighs - still not working.
> I guess I have to wait for anyone else, using my particular setup -
> postfix:amavisd-new:SA:pyzor to acknowledge he/she doesnt have the
> particular problem
I must have missed your original posting, so I don't know what issue you are
having. I am running the exact same configuration you show above on RedHat
9 on several machines, and pyzor is working just fine for me.
Bill
Re: Pyzor /w SA not working anymore?
Posted by "Al.Aeefyu" <ae...@gmail.com>.
On Fri, 25 Jun 2004 09:07:42 -0700, Kelson Vibber <ke...@speed.net> wrote:
> At 12:12 AM 6/25/2004, Al.Aeefyu wrote:
> Unfortunately the only solid suggestions I have are for things you've
> already done (pyzor discover, check the firewall, etc.) File permissions,
> maybe? Or have you upgraded Python recently? (Reinstalling Pyzor may help.)
Did that, as it was the only suggestion obtained on this list.
Sighs - still not working.
I guess I have to wait for anyone else, using my particular setup -
postfix:amavisd-new:SA:pyzor to acknowledge he/she doesnt have the
particular problem
Thanks, Vibber
--
-------------------
aeefyu
-------------------
Re: Pyzor /w SA not working anymore?
Posted by Kelson Vibber <ke...@speed.net>.
At 12:12 AM 6/25/2004, Al.Aeefyu wrote:
>What gives? The Pyzor mailing lists doesnt seem to be helpful so far
Yeah, it's *very* low traffic, though Frank usually responds fairly quickly
when someone asks him a question.
>nor does googling. Is this an isolated incident, or is Pyzor not
>working with SA 2.63 everywhere else?
Our latest Pyzor hit was just a few minutes ago, so it doesn't seem to be a
global problem. (Mimedefang/Spamassassin/Pyzor on Red Hat 7.3).
Unfortunately the only solid suggestions I have are for things you've
already done (pyzor discover, check the firewall, etc.) File permissions,
maybe? Or have you upgraded Python recently? (Reinstalling Pyzor may help.)
Kelson Vibber
SpeedGate Communications <www.speed.net>