Pyzor check fails with SpamAssassin 3.2.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SpamAssassin |
Fix Released
|
Critical
|
|||
spamassassin (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: spamassassin
Since the newest update to 3.2.2 in Gutsy the Pyzor check in SpamAssassin doesn't correctly run anymore. This is a portion of my mail.info which shows the problem:
Sep 28 10:50:15 localhost spamd[17388]: spamd: got connection over /var/run/spamd.sock
Sep 28 10:50:15 localhost spamd[17388]: spamd: setuid to Debian-exim succeeded
Sep 28 10:50:15 localhost spamd[17388]: spamd: processing message <01c801ac$
Sep 28 10:50:18 localhost spamd[18126]: pyzor: check failed: util: setuid 0 to 112 failed! at /usr/share/
Sep 28 10:50:24 localhost spamd[17388]: spamd: identified spam (12.8/5.0) for Debian-exim:112 in 8.9 seconds, 4550 bytes.
Sep 28 10:50:24 localhost spamd[17388]: spamd: result: Y 12 - BAYES_50,
Sep 28 10:50:24 localhost spamd[17379]: prefork: child states: II
It looks like that failure does not influence any other tests, so luckily most Spam is still identified correctly but some (especially short ones) aren't correctly identified due to this bug.
Googling for the problem revealed http://
http://
Changed in spamassassin: | |
status: | Unknown → Fix Released |
Changed in spamassassin: | |
status: | Fix Released → Unknown |
Changed in spamassassin: | |
status: | Unknown → Fix Released |
Changed in spamassassin: | |
importance: | Unknown → Critical |
yeah, 3.2.3 is strongly recommended -- 3.2.1 and 3.2.2 both have pretty serious bugs.