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