pyzor-users — general discussion of Pyzor and Pyzor-related topics

RE: Pyzor errors with SA 3.1

[Matthias G. I. <mg...@vt...>]

My current pyzor fails with the reported symptoms.

I downloaded the proposed patch from http://www.engelken.net/download/pyzor.patch

Upon running the patch with patch -p0 < pyzor.patch, I get the message that 
patch detected a reverse patch. Should the patches still be applied as reverse 
patches?

Matthias
-- 
**************************************************************************
* Matthias G. Imhof, Ph.D.                         phone: (540) 231 6004 *
* 4044 Derring Hall (0420)                         fax:   (540) 231 3386 *
* Virginia Tech                                        email: mg...@vt... *
* Blacksburg, VA 24061                  http://www.geol.vt.edu/profs/mgi *
* There is no dark side of the moon really. Matter of fact it's all dark *
**************************************************************************

Re: Pyzor errors with SA 3.1

[Chris <cpo...@ea...>]

On Thursday 06 October 2005 08:07 am, Dallas L. Engelken wrote:

> > Not having installed a patch before, I'm doing something
> > wrong.  I downloaded the patch, copied it over to my
> > /usr/lib/python2.3/site-packages/pyzor opened a root console
> > and typed patch -p0 which did absolutely nothing that I could
> > see.  I'm sure its simple, so what did I do wrong?
>
> # cp pyzor.patch /usr/lib/python2.3/site-packages/pyzor
> # cd /usr/lib/python2.3/site-packages/pyzor
> # patch -p0 < pyzor.path
>
> d
>
Thanks Dalla, the < makes a big difference.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
19:20:05 up 26 days, 7:32, 2 users, load average: 0.82, 0.48, 0.29
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk

RE: Pyzor errors with SA 3.1

[Dallas L. E. <da...@nm...>]

> -----Original Message-----
> From: pyz...@li...=20
> [mailto:pyz...@li...] On Behalf Of Chris
> Sent: Wednesday, October 05, 2005 7:17 PM
> To: pyz...@li...
> Subject: Re: Pyzor errors with SA 3.1
>=20
> On Wednesday 05 October 2005 11:45 am, Dallas L. Engelken wrote:
>=20
> > > > Is this a pyzor error or an SA error?  I've not seen it in=20
> > > > previous versions of SA.  I have Pyzor 0.4.0 installed as an RPM
> > >
> > > from Mandrake.
> > >
> > > It's a Pyzor error that's happened all along, but SA just started=20
> > > logging it.  (Basically when Pyzor hits a message it can't handle=20
> > > and throws an exception, SA used to ignore it.
> > > Now SA logs it.)
> > >
> > > IIRC there's a patch floating around - you should be able=20
> to find it=20
> > > in the the SA list archives.
> >
> > From http://bugzilla.spamassassin.org/show_bug.cgi?id=3D4580
> >
> > To make it simple, I have combined those 3 patches into 1...
> > http://www.engelken.net/download/pyzor.patch
> >
> > Just cd to your python2.x/site-packages/pyzor dir, and=20
> patch -p0 on it.
> > Example code from a shell script that installs pyzor...
> >
> >          # patch pyzor
> >          if [ -e "/usr/lib/python2.3/site-packages/pyzor" ]; then
> >             cd /usr/lib/python2.3/site-packages/pyzor
> >             patch -p0 < $DIR/patches/pyzor.patch 2>&1 >/dev/null
> >          fi
> >
> > D
> Not having installed a patch before, I'm doing something=20
> wrong.  I downloaded the patch, copied it over to my=20
> /usr/lib/python2.3/site-packages/pyzor opened a root console=20
> and typed patch -p0 which did absolutely nothing that I could=20
> see.  I'm sure its simple, so what did I do wrong?
>=20

# cp pyzor.patch /usr/lib/python2.3/site-packages/pyzor
# cd /usr/lib/python2.3/site-packages/pyzor=20
# patch -p0 < pyzor.path

d

Re: Pyzor errors with SA 3.1

[Chris <cpo...@ea...>]

On Wednesday 05 October 2005 11:45 am, Dallas L. Engelken wrote:

> > > Is this a pyzor error or an SA error?  I've not seen it in previous
> > > versions of SA.  I have Pyzor 0.4.0 installed as an RPM
> >
> > from Mandrake.
> >
> > It's a Pyzor error that's happened all along, but SA just
> > started logging it.  (Basically when Pyzor hits a message it
> > can't handle and throws an exception, SA used to ignore it.
> > Now SA logs it.)
> >
> > IIRC there's a patch floating around - you should be able to
> > find it in the the SA list archives.
>
> From http://bugzilla.spamassassin.org/show_bug.cgi?id=4580
>
> To make it simple, I have combined those 3 patches into 1...
> http://www.engelken.net/download/pyzor.patch
>
> Just cd to your python2.x/site-packages/pyzor dir, and patch -p0 on it.
> Example code from a shell script that installs pyzor...
>
>          # patch pyzor
>          if [ -e "/usr/lib/python2.3/site-packages/pyzor" ]; then
>             cd /usr/lib/python2.3/site-packages/pyzor
>             patch -p0 < $DIR/patches/pyzor.patch 2>&1 >/dev/null
>          fi
>
> D
Not having installed a patch before, I'm doing something wrong.  I 
downloaded the patch, copied it over to 
my /usr/lib/python2.3/site-packages/pyzor opened a root console and typed 
patch -p0 which did absolutely nothing that I could see.  I'm sure its 
simple, so what did I do wrong?

-- 
Chris
Registered Linux User 283774 http://counter.li.org
19:13:26 up 25 days, 7:26, 1 user, load average: 0.75, 0.84, 0.76
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk

RE: Pyzor errors with SA 3.1

[Dallas L. E. <da...@nm...>]

> -----Original Message-----
> From: pyz...@li...=20
> [mailto:pyz...@li...] On Behalf Of Kelson
> Sent: Wednesday, October 05, 2005 11:35 AM
> To: pyz...@li...
> Subject: Re: Pyzor errors with SA 3.1
>=20
> Chris wrote:
> > I upgraded to SA 3.1 last weekend, since then I've been=20
> seeing this in=20
> > my
> > syslog:
> >=20
> > Oct  3 22:30:40 cpollock spamd[29599]: internal error Oct =20
> 3 22:30:40=20
> > cpollock spamd[29599]: pyzor: check failed: internal error
> >=20
> > Is this a pyzor error or an SA error?  I've not seen it in previous=20
> > versions of SA.  I have Pyzor 0.4.0 installed as an RPM=20
> from Mandrake.
>=20
> It's a Pyzor error that's happened all along, but SA just=20
> started logging it.  (Basically when Pyzor hits a message it=20
> can't handle and throws an exception, SA used to ignore it. =20
> Now SA logs it.)
>=20
> IIRC there's a patch floating around - you should be able to=20
> find it in the the SA list archives.
>=20

From http://bugzilla.spamassassin.org/show_bug.cgi?id=3D4580

To make it simple, I have combined those 3 patches into 1...
http://www.engelken.net/download/pyzor.patch

Just cd to your python2.x/site-packages/pyzor dir, and patch -p0 on it.
Example code from a shell script that installs pyzor...

         # patch pyzor
         if [ -e "/usr/lib/python2.3/site-packages/pyzor" ]; then
            cd /usr/lib/python2.3/site-packages/pyzor
            patch -p0 < $DIR/patches/pyzor.patch 2>&1 >/dev/null
         fi

D

Re: Pyzor errors with SA 3.1

[Kelson <ke...@sp...>]

Chris wrote:
> I upgraded to SA 3.1 last weekend, since then I've been seeing this in my 
> syslog:
> 
> Oct  3 22:30:40 cpollock spamd[29599]: internal error 
> Oct  3 22:30:40 cpollock spamd[29599]: pyzor: check failed: internal error 
> 
> Is this a pyzor error or an SA error?  I've not seen it in previous versions 
> of SA.  I have Pyzor 0.4.0 installed as an RPM from Mandrake.

It's a Pyzor error that's happened all along, but SA just started
logging it.  (Basically when Pyzor hits a message it can't handle and
throws an exception, SA used to ignore it.  Now SA logs it.)

IIRC there's a patch floating around - you should be able to find it in
the the SA list archives.

-- 
Kelson Vibber
SpeedGate Communications <www.speed.net>

Timeout

[<And...@ke...>]

hi there,

since weeks (months) i get the following error

debug: Pyzor: got response: 217.160.253.84:24441 TimeoutError:
debug: leaving helper-app run mode
debug: Pyzor: couldn't grok response "217.160.253.84:24441 TimeoutError: =
"

pyzor discover running every day via cron

how to solv ? this timeout takes about 5 sec for every scand mail

greetings
andy

--free your mind, use open source
http://www.mono-project.com

ASCII ribbon campaign ( )
 - against HTML email  X
             & vCards / \ =20

Pyzor errors with SA 3.1

[Chris <cpo...@ea...>]

I upgraded to SA 3.1 last weekend, since then I've been seeing this in my=20
syslog:

Oct =A03 22:30:40 cpollock spamd[29599]: internal error=20
Oct =A03 22:30:40 cpollock spamd[29599]: pyzor: check failed: internal erro=
r=20

Is this a pyzor error or an SA error?  I've not seen it in previous version=
s=20
of SA.  I have Pyzor 0.4.0 installed as an RPM from Mandrake.

=2D-=20
Chris
Registered Linux User 283774 http://counter.li.org
17:09:30 up 24 days, 5:22, 2 users, load average: 0.40, 0.29, 0.22
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk

Re: Socket.error: (13, 'Permission denied') errors

[Frank T. <ft...@ne...>]

Drew Marshall, on 2005-09-27, wrote:

> Thanks for your help. This *shouldn't* be the case but I won't discount 
> anything at this stage. Which UDP port(s) does Pyzor use/ should I 
> allow?

Outbound Pyzor will use whatever the system allocates.  According to 
udp(7) on Linux:

...the socket layer will automatically assign a free local port out of the
    range defined by net.ipv4.ip_local_port_range and bind the socket to
    INADDR_ANY.

-- 
Frank

Re: Socket.error: (13, 'Permission denied') errors

[Drew M. <dr...@th...>]

On Tue, September 27, 2005 06:39, Frank Tobin wrote:
> Drew Marshall, on 2005-09-25, wrote:
>
>>   self.socket.sendto(mac_msg_str, 0, address)
>> socket.error: (13, 'Permission denied')
>>
>> Now clearly the last line is significant. I have run this as root so
>> it's not (Or shouldn't be) a permissions problem with files or
>> directories and as root I shouldn't have issues with binding to low
>> numbered ports, which was one suggestion from Google.
>
> Interesting.  Given you're getting an EACCES error (13 is EACCES on Lin=
ux,
> and I'm assuming it's likewise on FreeBSD), my best guess is that you h=
ave
> a firewall setup which might be disallowing pyzor to use a UDP port to
> send messages.

Frank

Thanks for your help. This *shouldn't* be the case but I won't discount
anything at this stage. Which UDP port(s) does Pyzor use/ should I allow?

Regards

Drew


--=20
In line with our policy, this message has=20
been scanned for viruses and dangerous=20
content by MailScanner, and is believed to be clean.
www.themarshalls.co.uk/policy

Re: Socket.error: (13, 'Permission denied') errors

[Frank T. <ft...@ne...>]

Drew Marshall, on 2005-09-25, wrote:

>   self.socket.sendto(mac_msg_str, 0, address)
> socket.error: (13, 'Permission denied')
>
> Now clearly the last line is significant. I have run this as root so 
> it's not (Or shouldn't be) a permissions problem with files or 
> directories and as root I shouldn't have issues with binding to low 
> numbered ports, which was one suggestion from Google.

Interesting.  Given you're getting an EACCES error (13 is EACCES on Linux, 
and I'm assuming it's likewise on FreeBSD), my best guess is that you have 
a firewall setup which might be disallowing pyzor to use a UDP port to 
send messages.

-- 
Frank

Socket.error: (13, 'Permission denied') errors

[Drew M. <dr...@th...>]

Hi all

Just installed Pyzor and have stumbled over this problem that I hope  
some one can help with.

It all installed nicely but it just won't run. Pyzor discover works  
fine but if i run pyzor ping I get:

# pyzor -d ping
sending: 'User: anonymous\nTime: 1127684961\nSig:  
a8b2e41ed95b1ccd8678a9e2598ff6b06d80639e\n\nOp: ping\nThread: 42906 
\nPV: 2.0\n\n'
Traceback (most recent call last):
   File "/usr/local/bin/pyzor", line 4, in ?
     pyzor.client.run()
   File "/usr/local/lib/python2.4/site-packages/pyzor/client.py",  
line 934, in run
     ExecCall().run()
   File "/usr/local/lib/python2.4/site-packages/pyzor/client.py",  
line 188, in run
     if not apply(dispatch, (self, args)):
   File "/usr/local/lib/python2.4/site-packages/pyzor/client.py",  
line 219, in ping
     runner.run(server, (server,))
   File "/usr/local/lib/python2.4/site-packages/pyzor/client.py",  
line 725, in run
     response = apply(self.routine, varargs, kwargs)
   File "/usr/local/lib/python2.4/site-packages/pyzor/client.py",  
line 38, in ping
     self.send(msg, address)
   File "/usr/local/lib/python2.4/site-packages/pyzor/client.py",  
line 77, in send
     self.socket.sendto(mac_msg_str, 0, address)
socket.error: (13, 'Permission denied')

Now clearly the last line is significant. I have run this as root so  
it's not (Or shouldn't be) a permissions problem with files or  
directories and as root I shouldn't have issues with binding to low  
numbered ports, which was one suggestion from Google.

Any ideas any one?

For the record:

FreeBSD 5.4 with python 2.4 and the latest pyzor all installed from  
ports.

TIA

Drew


-- 
In line with our policy, this message has 
been scanned for viruses and dangerous 
content by MailScanner, and is believed to be clean.
www.themarshalls.co.uk/policy

Re: No pyzor server ?

[Ingo P. <in...@it...>]

On Tue, 13 Sep 2005, Ed Kasky wrote:

> On Tue, 13 Sep 2005, Ingo Preiml wrote:
>
>> On Tue, 5 Jul 2005, Ed Kasky wrote:
>>
>>> > # pyzor ping
>>> > 66.250.40.33:24441      TimeoutError:
>>> > [root[# pyzor discover
>>> > downloading servers from 
>>> http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
>>> > [root]# pyzor ping
>>> > 66.250.40.33:24441      TimeoutError:
>>> > [root]#
>>> >
>>> > What is wrong ?
>>> > Looks like this has been the case since June 23rd.
>>>
>>> Looks good from this end:
>>> $ pyzor ping
>>> 66.250.40.33:24441      (200, "OK")
>>>
>>> Maybe a firewall issue?
>>
>>
>> But tracepath 66.250.40.33/24441 did not succeed with the following
>> output:
>>
>> 15:  Quatro_Systems.demarc.cogentco.com (66.250.4.54)     asymm 20 
>> 116.956ms
>> 16:  no reply
>> 17:  no reply
>> ---- snip -----
>>
>> Is this a firewall problem on my local network or on 66.250.4.54? Am 
>> I doing
>> something wrong?
>
>
> Hard to say not knowing your setup.  Is there a firewall installed and 
> if so if all outbound traffic is not trusted, have you allowed inbound 
> traffic on 24441?
>
> Also, can you do a successful "pyzor ping"???
>
Oh dear, I am sorry to tell you that I had made a mistake. I have two 
mailserver (a productive server and a test system) that are in different 
networks. The test system is in a subnet with very restricted access to 
the internet and the productive server is located in our DMZ. I had no 
access from my test system and so I supposed (without checking :( )the 
productive server has no access too... But as I tried pyzor ping on my 
productive one, it says:
66.250.40.33:24441      (200, 'OK')

So everything works fine for me, only the test system has no access, but 
that is not very important.

Sorry and thanks for the quick reply.
Ingo Preiml

Re: Re: No pyzor server ?

[Ed K. <ed...@yo...>]

On Tue, 13 Sep 2005, Ingo Preiml wrote:

> On Tue, 5 Jul 2005, Ed Kasky wrote:
>
>> > # pyzor ping
>> > 66.250.40.33:24441      TimeoutError:
>> > [root[# pyzor discover
>> > downloading servers from 
>> http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
>> > [root]# pyzor ping
>> > 66.250.40.33:24441      TimeoutError:
>> > [root]#
>> >
>> > What is wrong ?
>> > Looks like this has been the case since June 23rd.
>> 
>> Looks good from this end:
>> $ pyzor ping
>> 66.250.40.33:24441      (200, "OK")
>> 
>> Maybe a firewall issue?
>
> But tracepath 66.250.40.33/24441 did not succeed with the following
> output:
>
> 15:  Quatro_Systems.demarc.cogentco.com (66.250.4.54)     asymm 20 116.956ms
> 16:  no reply
> 17:  no reply
> ---- snip -----
>
> Is this a firewall problem on my local network or on 66.250.4.54? Am I doing
> something wrong?

Hard to say not knowing your setup.  Is there a firewall installed and if 
so if all outbound traffic is not trusted, have you allowed inbound 
traffic on 24441?

Also, can you do a successful "pyzor ping"???

Ed

. . . . . . . . . . . . . . .
Randomly generated quote:
"I am certain that He (God) does not play dice."
  -- Albert Einstein

Re: Re: No pyzor server ?

[Ingo P. <in...@it...>]

On Tue, 5 Jul 2005, Ed Kasky wrote:

> > # pyzor ping
> > 66.250.40.33:24441      TimeoutError:
> > [root[# pyzor discover
> > downloading servers from http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
> > [root]# pyzor ping
> > 66.250.40.33:24441      TimeoutError:
> > [root]#
> >
> > What is wrong ?
> > Looks like this has been the case since June 23rd.
> 
> Looks good from this end:
> $ pyzor ping
> 66.250.40.33:24441      (200, "OK")
> 
> Maybe a firewall issue?

I also encountered problems when contacting 66.250.40.33:24441. 
I was able to ping/tracepath 66.250.40.33 with the following result:

 1:  r-176-1.net.uni-klu.ac.at (143.205.176.1)              5.568ms
 2:  143.205.170.3 (143.205.170.3)                          2.092ms
 3:  Klu.ACO.net (193.171.18.17)                            3.035ms
 4:  Linz.ACO.net (193.171.12.201)                          9.495ms
 5:  Wien21.ACO.net (193.171.12.193)                       12.028ms
 6:  vix2.core01.vie01.atlas.cogentco.com (193.203.0.113) asymm  7  13.050ms
 7:  p1-0.core01.muc01.atlas.cogentco.com (130.117.1.242) asymm  8  17.800ms
 8:  p14-0.core01.fra03.atlas.cogentco.com (130.117.1.198) asymm  9  23.667ms
 9:  p15-0.core02.par02.atlas.cogentco.com (130.117.0.18) asymm 10  33.373ms
10:  p12-0.core01.par01.atlas.cogentco.com (130.117.1.230) asymm 11  33.777ms
11:  p14-0.core02.dca01.atlas.cogentco.com (66.28.4.206)  asymm 12 113.908ms
12:  p15-0.core01.dca01.atlas.cogentco.com (66.28.4.21)   asymm 13 113.794ms
13:  p4-0.core01.phl01.atlas.cogentco.com (66.28.4.18)    asymm 14 117.202ms
14:  g49.ba01.b003003-2.phl01.atlas.cogentco.com (66.250.8.10) asymm 15 118.241ms
15:  Quatro_Systems.demarc.cogentco.com (66.250.4.54)     asymm 20 114.307ms
16:  clapton.quatro.com (66.250.40.33)                    asymm 17 118.382ms reached
     Resume: pmtu 1500 hops 16 back 17

But tracepath 66.250.40.33/24441 did not succeed with the following
output:

 1:  r-176-1.net.uni-klu.ac.at (143.205.176.1)              1.542ms
 2:  143.205.170.3 (143.205.170.3)                          1.801ms
 3:  Klu.ACO.net (193.171.18.17)                            2.825ms
 4:  Linz.ACO.net (193.171.12.201)                          8.854ms
 5:  Wien21.ACO.net (193.171.12.193)                       23.726ms
 6:  vix2.core01.vie01.atlas.cogentco.com (193.203.0.113) asymm  7  13.696ms
 7:  p1-0.core01.muc01.atlas.cogentco.com (130.117.1.242) asymm  8  17.741ms
 8:  p14-0.core01.fra03.atlas.cogentco.com (130.117.1.198) asymm  9  23.139ms
 9:  p15-0.core02.par02.atlas.cogentco.com (130.117.0.18) asymm 10  33.235ms
10:  p12-0.core01.par01.atlas.cogentco.com (130.117.1.230) asymm 11  33.980ms
11:  p14-0.core02.dca01.atlas.cogentco.com (66.28.4.206)  asymm 12 113.570ms
12:  p15-0.core01.dca01.atlas.cogentco.com (66.28.4.21)   asymm 13 147.783ms
13:  p4-0.core01.phl01.atlas.cogentco.com (66.28.4.18)    asymm 14 120.653ms
14:  g49.ba01.b003003-2.phl01.atlas.cogentco.com (66.250.8.10) asymm 15 124.670ms
15:  Quatro_Systems.demarc.cogentco.com (66.250.4.54)     asymm 20 116.956ms
16:  no reply
17:  no reply
---- snip -----

Is this a firewall problem on my local network or on 66.250.4.54? Am I doing
something wrong?

Regards 
Ingo Preiml

Re: Project still active?

[Frank T. <ft...@ne...>]

Mark Davies, on 2005-08-15, wrote:

> Is this project still active?  I set it up on my mail server, but it's 
> not picking up any incoming spam...

There could be many reasons for this.  Perhaps the spam you are subjected 
to is already filtered to the point that Pyzor doesn't pick up anything 
else.

> it returns:
>
> 66.250.40.33:24441      (200, 'OK')

That is the customary response (200 is 'success').

-- 
Frank

Project still active?

[Mark D. <ma...@cu...>]

Hi guys,

Is this project still active?  I set it up on my mail server, but it's
not picking up any incoming spam...


It is using 66.250.40.33:24441 as a server, and when I do a

pyzor report --mbox < ./mail/OldSPAM

it returns:

66.250.40.33:24441      (200, 'OK')
66.250.40.33:24441      (200, 'OK')
66.250.40.33:24441      (200, 'OK')


Any suggestions?


Mark Davies.

How it works

[Patrick R. <rut...@gm...>]

I'm researching spam solutions. I was checking out the test list on
apache spamassassin ( http://spamassassin.apache.org/tests_3_0_x.html
). I noticed that there was a "phyzor" test. Does this test against
your own phyzor server that you have to set up and maintain. Or is
there a big phyzor server somewhere that contains a huge blacklist?

Re: No pyzor server ?

[Ed K. <ed...@es...>]

On Tue, 5 Jul 2005, Lars Holmstrom wrote:

> # pyzor ping
> 66.250.40.33:24441      TimeoutError:
> [root[# pyzor discover
> downloading servers from http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
> [root]# pyzor ping
> 66.250.40.33:24441      TimeoutError:
> [root]#
>
> What is wrong ?
> Looks like this has been the case since June 23rd.

Looks good from this end:
$ pyzor ping
66.250.40.33:24441      (200, 'OK')

Maybe a firewall issue?

Ed
. . . . . . . . . . . . . . .
Randomly generated quote:
Life is not measured by the number of breaths we take,
but by the moments that take our breath away.
-George Carlin

No pyzor server ?

[Lars H. <lar...@fl...>]

# pyzor ping
66.250.40.33:24441      TimeoutError:
[root[# pyzor discover
downloading servers from =
http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
[root]# pyzor ping
66.250.40.33:24441      TimeoutError:
[root]#

What is wrong ?
Looks like this has been the case since June 23rd.

/Lars

Re: pyzor crashing on new install FreeBSD 5.4

[Frank T. <ft...@ne...>]

William F. Dudley Jr., on 2005-06-18, wrote:

> I'm trying to get a fresh install FreeBSD 5.4 system to do all my normal 
> spam filtering (using a FreeBSD 4.11 system right now), and pyzor is 
> crashing when I procmail tries to pipe mail through it.
>
> pyzor discover seems to work fine.

Is it just the the one mail message, or each?  Pyzor doesn't handle some 
mal-formatted messages well.

-- 
Frank

pyzor crashing on new install FreeBSD 5.4

[William F. D. Jr. <bi...@du...>]

I'm trying to get a fresh install FreeBSD 5.4 system to do all my
normal spam filtering (using a FreeBSD 4.11 system right now), and
pyzor is crashing when I procmail tries to pipe mail through it.

pyzor discover seems to work fine.

I looked in the mailing list archives and found that somebody else
had this problem but there was never an answer to his query.

Any ideas?  I don't know python so I'm afraid this error message is
worthless to me.

Thanks,

Please reply to me as well as to the list since I may have fallen off
the list subscription.

Bill Dudley

--- Logging /usr/home/dud/Mail/procmail.log for dud, Traceback (most recent call last):
  File "/usr/local/bin/pyzor", line 4, in ?
    pyzor.client.run()
  File "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 934, in run
    ExecCall().run()
  File "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 188, in run
    if not apply(dispatch, (self, args)):
  File "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 264, in check
    response = runner.run(server, (digest, server))
  File "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 725, in run
    response = apply(self.routine, varargs, kwargs)
  File "/usr/local/lib/python2.4/site-packages/pyzor/client.py", line 57, in check
    msg = CheckRequest(digest)
  File "/usr/local/lib/python2.4/site-packages/pyzor/__init__.py", line 381, in __init__
    typecheck(digest, str)
  File "/usr/local/lib/python2.4/site-packages/pyzor/__init__.py", line 494, in typecheck
    raise TypeError
TypeError
  Folder: /var/mail/dud                                                       2

Server back up

[Ed K. <ed...@es...>]

And just like that ;-)

$ date && pyzor ping
Wed May 25 16:56:48 PDT 2005
66.250.40.33:24441      (200, 'OK')

Ed Kasky
~~~~~~~~~
Randomly Generated Quote (92 of 477):
"If a free society cannot help the many who are poor, it cannot save
the few who are rich."   --John F. Kennedy, Inaugural address, 1961

RE: Pyzor errors

[Ugo B. <ug...@ca...>]

Ed Kasky wrote:
> At 12:13 PM Wednesday, 5/25/2005, Ugo Bellavance wrote -=3D>
>> Hi,
>>=20
>>         I get these errors when running pyzor through SA (debug
>> mode).=20
>>=20
>> debug: Pyzor is available: /usr/bin/pyzor
>> debug: entering helper-app run mode
>> debug: setuid: helper proc 7357: ruid=3D0 euid=3D0
>> 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: "=20
>>=20
>> I get those on all my servers and a few other mail server admins I
>> know told me they have them as well.
>>=20
>> Any idea of what is going on?
>=20
> Appears the server is down:
>=20
> $ pyzor ping
> 66.250.40.33:24441      TimeoutError:
>=20

Thanks, but there is only one pyzor server? Does anyone know how to run
a pyzor server, the requirements, etc. and if it could help avoiding
this kind of situation?

Thanks,

Ugo

Re: Pyzor errors

[Ed K. <ed...@es...>]

At 12:13 PM Wednesday, 5/25/2005, Ugo Bellavance wrote -=>
>Hi,
>
>         I get these errors when running pyzor through SA (debug mode).
>
>debug: Pyzor is available: /usr/bin/pyzor
>debug: entering helper-app run mode
>debug: setuid: helper proc 7357: ruid=0 euid=0
>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: "
>
>I get those on all my servers and a few other mail server admins I know
>told me they have them as well.
>
>Any idea of what is going on?

Appears the server is down:

$ pyzor ping
66.250.40.33:24441      TimeoutError:


Ed Kasky
~~~~~~~~~
Randomly Generated Quote (122 of 477):
"It must be a peace without victory.... Only a peace between equals
can last."   --Woodroe Wilson