Bug#335424: pyzor: Pyzor problem still exists as of 2008-MAR-26

[Greg Folkert <greg@uno.gregfolkert.net>]

Package: pyzor
Version: 1:0.4.0+cvs20030201-8
Followup-For: Bug #335424


This original error is still occuring.

I get this message:

Mar 25 18:03:30 uno spamd[2931]: pyzor: check failed: internal error

and many variants of it (only the PID changes) per day.

I get it in mail.log, mail.warn, mail.info, syslog.

Pyzor seems to fail very well.

I have setup additional sitewide stuff using the howtos on spamassassin's wiki 
(changes made for use with Debian), but it just makes no difference.

I'd really like to use pyzor with everything, but this is a blocker.

Let me know anything else you need, and i'll try to get it here.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages pyzor depends on:
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-gdbm                   2.4.4-3    GNU dbm database support for Pytho
ii  python-support                0.7.7      automated rebuilding support for P

pyzor recommends no packages.

-- no debconf information