Use of uninitialized value error ?

[Simon Byrnand <si...@igrin.co.nz>]

Hi Everyone,

Upgraded from 2.64 to 3.0.3 today + a few of the SARE rulesets, and I'm
noticing a spamd warning message in the log files occasionally that was
not occuring on the test server I evaluated 3.0.3 on:

May  9 21:41:39 mail spamd[30290]: Use of uninitialized value in
substitution (s///) at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssa
ssin/PerMsgStatus.pm line 983.
May  9 21:41:39 mail spamd[30290]: Use of uninitialized value in
substitution (s///) at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssa
ssin/PerMsgStatus.pm line 907.
May  9 21:41:39 mail spamd[30290]: Use of uninitialized value in quotemeta
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMs
gStatus.pm line 912.
May  9 21:41:39 mail spamd[30290]: Use of uninitialized value in
concatenation (.) or string at /usr/lib/perl5/site_perl/5.8.0/Mail/
SpamAssassin/PerMsgStatus.pm line 912.

The extra rulesets I have installed are:

70_sare_adult.cf
70_sare_bayes_poison_nxm.cf
70_sare_header0.cf
70_sare_html0.cf
70_sare_uri.cf
72_sare_bml_post25x.cf
99_sare_fraud_post25x.cf
antidrug.cf
bogus-virus-warnings.cf

Is this a known problem with SA 3.0.3 or is it something wrong with one of
these extra rulesets ? Does anyone know or have any idea how to diagnose
this problem ?

It doesn't seem to be causing any problems, but I'm uncomfortable about
errors like these...

Regards,
Simon

Re: Use of uninitialized value error ?

[Robert Menschel <Ro...@Menschel.net>]

Hello Simon,

Monday, May 9, 2005, 2:46:15 AM, you wrote:

SB> Hi Everyone,

SB> Upgraded from 2.64 to 3.0.3 today + a few of the SARE rulesets, and I'm
SB> noticing a spamd warning message in the log files occasionally that was
SB> not occuring on the test server I evaluated 3.0.3 on:

SB> May  9 21:41:39 mail spamd[30290]: Use of uninitialized value in
SB> substitution (s///) at
SB> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssa
SB> ssin/PerMsgStatus.pm line 983.

SB> The extra rulesets I have installed are:
SB> 70_sare_adult.cf
SB> 70_sare_bayes_poison_nxm.cf
SB> 70_sare_header0.cf
SB> 70_sare_html0.cf
SB> 70_sare_uri.cf
SB> 72_sare_bml_post25x.cf
SB> 99_sare_fraud_post25x.cf
SB> antidrug.cf
SB> bogus-virus-warnings.cf

Drop antidrug.cf -- it's been incorporated into 3.0.x; the others are
OK.

SB> Is this a known problem with SA 3.0.3 or is it something wrong with one of
SB> these extra rulesets ? Does anyone know or have any idea how to diagnose
SB> this problem ?

I don't know enough about the internals of SA to know if it's the same
problem or not, but at least similar problems have been reported with
3.0.x.  You scan scan bugzilla for uninitialized value and
PerMsgStatus.pm in the comments areas, and probably find it.

Bob Menschel