Bug 4769 - sa-learn produces errors
Summary: sa-learn produces errors
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Learner (show other bugs)
Version: 3.1.0
Hardware: PC Linux
: P5 major
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-25 04:09 UTC by Martin
Modified: 2006-08-12 19:52 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2006-01-25 04:09:54 UTC 
Sa-learn produces errors, the below was produced from an sa-learn --ham (--
spam produces similar results but usually with more of the same)...

Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 320.
Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 321.
Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 320.
Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 321.
Use of uninitialized value in pattern match (m//) 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 225.
Use of uninitialized value in pattern match (m//) 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 227.
Use of uninitialized value in concatenation (.) or string 
at /usr/lib/perl5/site_perl/5.8.7/Mail/SpamAssassin/Message/Metadata/Received.p
m line 228.

I also have problems with spamd crashing at random intervals, though I've not 
had the chance to look into the root of the problem as yet. I originally 
thought it was due to an over-zealous sized bayes db, but even with a clean 
new db it still crashes (since I upgraded to 3.1.0)
Comment 1 Theo Van Dinter 2006-08-02 01:56:38 UTC 
is this still occuring?
Comment 2 Theo Van Dinter 2006-08-13 02:52:04 UTC 
hearing nothing, closing as wfm.