Problem with upgrade to 2.64

["R. Steven Rainwater" <sr...@ncc.com>]

I just upgraded from 2.63 to 2.64 and I'm getting a lot of weird error
messages in my logs now. I'm using the Theo Van Dinter source RPM
version of Spamassassin linked from the official site. I'm running
spamassasin under Red Hat Linux 9. We use the spamd daemon integrated
with sendmail using smtp-vilter. 

I did the upgrade by building binary RPMs from the src RPM like so:

 rpmbuild --rebuild spamassassin-2.64-1.src.rpm

And then upgraded the old binaries like so:

 rpm -Uvh *.i386.rpm

The install proceeded without any errors.

This is the same process I used to originally install 2.63 on the server
some time ago and it has run without any problem since then. I upgraded
because we've been on the receiving end of some sort of DoS attack that
seems to target Spamassasin. I noticed the upgrade claimed to fix an
unspecified DoS problem, so here I am.

The startup options we use are "-d -c -a -m10 -H -u mail"

The exact errors we're getting over and over in the logs are:

Use of uninitialized value in length at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
1339, <GEN141> line 98.

Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
1342, <GEN141> line 98.

Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
1343, <GEN141> line 98.

Use of uninitialized value in length at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 457,
<GEN141> line 98.

Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 460,
<GEN141> line 98.

Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 461,
<GEN141> line 98.

Can anyone tell me how to fix this problem?

-Steve

Re: Problem with upgrade to 2.64

["R. Steven Rainwater" <sr...@ncc.com>]

On Fri, 2004-08-27 at 15:04, Theo Van Dinter wrote:
> If you're getting a lot of these (really?) you can put:
> 
>     $value ||= '';
> 
> around Bayes.pm line 452 and PerMsgStatus line 1335 (after
> the key,value = split line ...)

Thanks! That seems to have worked. No more error messages now.

-Steve

Re: Problem with upgrade to 2.64

["R. Steven Rainwater" <sr...@ncc.com>]

On Fri, 2004-08-27 at 15:04, Theo Van Dinter wrote:
> Those three are caused by invalid headers in the message.

What sort of invalid header would cause that?

> If you're getting a lot of these (really?) you can put:
>     $value ||= '';

Yep, 100% of the emails processed since I did the 2.63->2.64 upgrade
have generated these errors. (and that's a lot of emails)

-Steve

Re: Problem with upgrade to 2.64

[Theo Van Dinter <fe...@kluge.net>]

On Fri, Aug 27, 2004 at 02:46:23PM -0500, R. Steven Rainwater wrote:
> Use of uninitialized value in length at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
> 1339, <GEN141> line 98.
> 1342, <GEN141> line 98.
> 1343, <GEN141> line 98.

Those three are caused by invalid headers in the message.

> Use of uninitialized value in length at
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 457,
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 460,
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Bayes.pm line 461,

Same issue.

> Can anyone tell me how to fix this problem?

If you're getting a lot of these (really?) you can put:

    $value ||= '';

around Bayes.pm line 452 and PerMsgStatus line 1335 (after the key,value =
split line ...)

FWIW, 3.0.0 doesn't have this issue.

-- 
Randomly Generated Tagline:
"The Beatles used more hair products then Jesus."   - Rusty McGee