Bug 2355 - Non-spam causes error message
Summary: Non-spam causes error message
Status: RESOLVED DUPLICATE of bug 2206
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.60
Hardware: Other Linux
: P5 minor
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-25 06:06 UTC by Gerhard Blab
Modified: 2003-08-24 23:09 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Blab 2003-08-25 06:06:35 UTC
checking a non-spam message causes spamassassin and spamd to give the following 
error message on the commandline / shell that spamd/spamassassin was started 
from:

Can't use an undefined value as an ARRAY reference at 
/usr/local/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 303, <GEN3> 
line 45.
Can't use an undefined value as an ARRAY reference at 
/usr/local/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 303, <GEN5> 
line 83.
Can't use an undefined value as an ARRAY reference at 
/usr/local/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 303, <GEN4> 
line 162.
Can't use an undefined value as an ARRAY reference at 
/usr/local/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 303, <GEN6> 
line 45.
Can't use an undefined value as an ARRAY reference at 
/usr/local/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 303, <GEN7> 
line 162.
Can't use an undefined value as an ARRAY reference at 
/usr/local/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 303, <GEN8> 
line 83.

the <GENX>, line YYY is omitted if the "spamassassin -t < sample-nonspam.txt" is 
 issued
if the message is classified as spam, no error is generated. 

I am using spamd/spamc; filtering works as usual, so this is a mere annoyance, 
as all mail is being classified and delivered as expected.
Comment 1 Theo Van Dinter 2003-08-25 07:09:56 UTC
this was fixed for 2.60rc2.

*** This bug has been marked as a duplicate of 2206 ***