Apparently this does not prevent Spamassassin from properly interpret pyzor results. The depreciation warnings are not completely addressed though. When using the workaround suggested in the bug report (add -Wignore::DeprecationWarning) I get this clean debug output :
$ spamassassin -D pyzor <spam.eml > /dev/null Oct 12 14:12:01.871 [11753] dbg: pyzor: network tests on, attempting Pyzor Oct 12 14:12:04.645 [11753] dbg: pyzor: pyzor is available: /usr/bin/pyzor Oct 12 14:12:04.645 [11753] dbg: pyzor: opening pipe: /usr/bin/pyzor check < /tmp/.spamassassin11753rQcVjLtmp Oct 12 14:12:04.828 [11753] dbg: pyzor: [11754] finished successfully Oct 12 14:12:04.828 [11753] dbg: pyzor: got response: public.pyzor.org:24441 (200, 'OK') 818 0 Oct 12 14:12:04.829 [11753] dbg: pyzor: listed: COUNT=818/5 WHITELIST=0 This is only a workaround though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/394775 Title: Pyzor DeprecatedWarning causes spamassassin to fail to parse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/394775/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
