http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5574
------- Additional Comments From [EMAIL PROTECTED] 2007-07-26 02:20 ------- a mail on the users list has something that may be related: 'Am trying to upgrade to the new 3.2.2 and everything looked OK during make/test/install but during operation, I'm getting these errors: Jul 25 13:46:53 boxen spamd[25710]: dcc: check failed: util: setuid 0 to 501 failed! at /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/Util.pm line 1343. [some normal spamassassin status messages] Jul 25 13:46:53 boxen spamd[25710]: spamd: accidental fork: 25710 != 21988 at /usr/bin/spamd line 1628. Jul 25 13:46:53 boxen spamd[21988]: dcc: check failed: failed to read header [some normal spamassassin status messages] Jul 25 13:47:00 boxen spamc[25709]: failed sanity check, 1654 bytes claimed, 3385 bytes seen The resulting messages do not have any X-Spam headers. I reverted back to 3.2.1 and all of these error messages went away. This is on a CentOS 4.5 machine running sendmail-8.13.1-3.2.el4, perl v5.8.5, and dcc-1.3.58.' (In reply to comment #11) > Perl 5.8.0 was released 5 years ago (July 18, 2002). The last two Debian > releases have perl 5.8 (and we all know Debian releases are about as frequent > as > ice ages). Perhaps it is about time to start dropping 5.6 support? I'd prefer not to do this -- there are still BSD platforms running 5.6.1, iirc, and it's not that much trouble to support. (I maintain a perl561 install on my laptop, and there's a buildbot too.) Also, there have been reports of setuid-related problems on perl 5.8.1 and 5.8.5 (see above), so it may not be limited to 5.6.1 anyway... > (I'm not > saying we gratuitously dump our perl 5.6 compatibility, we just umm... stop > fixing perl 5.6 bugs?) then we become perl 5.6.1 incompatible, we can no longer state that we're compatible with 5.6.1, therefore we're no longer supporting it. ;) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
