Simon Avery wrote:
> Sometime yesterday, without me knowingly changing anything (maybe an
> apt-get upgrade), SA started throwing the following warnings on nearly
> every message. It still seems to be working okay and spam is being
> correctly ID'd, but the logfile's now full of these.
>
> I've tried copying a fresh copy of this file over, checking it in an
> editor (all looks fine), commenting out the block mentioned (It then
> starts throwing errors on another section of the same .pm) removing SA
> entirely and reinstalling. The disk seems healthy. Google doesn't seem
> to help me much other than show others have had the same problem, but
> no solutions.
>
> Has anyone any ideas on why this has gone kaflooey and how to fix?
>
> Debian etch, SpamAssassin version 3.2.0 running on Perl version 5.8.8
> SA from source.
>
Ok, you don't have any .deb SpamAssassin packages installed, do you?
Otherwise an apt-get could blow away some or all of the source installed
SpamAssassin and really screw things up.
<snip>
> May 29 22:38:17 office spamd[28630]: rules: failed to run header
> tests, skipping some: syntax error at (eval 331) line 11, near ";
> May 29 22:38:17 office spamd[28630]: }"
> May 29 22:38:17 office spamd[28630]: Use of uninitialized value in
> concatenation (.) or string at
> /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2669, <GEN12>
> line 302.
Something doesn't appear to be right there. SA 3.2.0's PerMsgStatus.pm
doesn't have a line 2669.
$wc -l PerMsgStatus.pm
2602 PerMsgStatus.pm
Check around and see if you wound up with two copies of the SpamAssassin
libraries. I'd suggest doing a find or locate on PerMsgStatus.pm, and
compare all the ones anywhere in /usr/ to make sure they're the same as
the one in your 3.2.0 source build.
>
>
>
