Bug 2547 - Spurious perl warnings in maillog
Summary: Spurious perl warnings in maillog
Status: RESOLVED DUPLICATE of bug 2504
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.60
Hardware: PC Linux
: P2 minor
Target Milestone: 2.61
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-04 13:19 UTC by James A. Cleland
Modified: 2003-10-07 10:20 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 James A. Cleland 2003-10-04 13:19:19 UTC 
Spamd emits various amounts of the following warning in the maillog. This does 
not appear to effect filtering and the program behaves normally. It was brought 
to my attention that the Content-length: header which is used to initialize the 
offending variable, is not a required header. Perhaps this is causing the 
problem?
Comment 1 James A. Cleland 2003-10-04 13:20:47 UTC 
Oops, forgot the log messages:

Sep 30 16:21:24 ria spamd[3631]: Use of uninitialized value in numeric eq (==) 
at /usr/local/bin/spamd line 707, <GEN1251> line 5. Sep 30 
16:21:24 ria spamd[3631]: Use of uninitialized value in numeric eq (==) 
at /usr/local/bin/spamd line 707, <GEN1251> line 6. Sep 30 
16:21:24 ria spamd[3631]: Use of uninitialized value in numeric eq (==) 
at /usr/local/bin/spamd line 707, <GEN1251> line 7. Sep 30 
16:21:24 ria spamd[3631]: Use of uninitialized value in numeric eq (==) 
at /usr/local/bin/spamd line 707, <GEN1251> line 8. S
Comment 2 Malte S. Stretz 2003-10-05 03:13:35 UTC 
How do you feed the mail to spamd? I guess via qsmtpd (or what its called) 
which uses an older version of the spamd protocol?
Comment 3 Keith Ivey 2003-10-06 15:26:13 UTC 
This is the same as 2504, where I've posted a fix.
Comment 4 James A. Cleland 2003-10-07 18:20:31 UTC 
Agreed. Thanks for the response, the fix eliminated the warnings. I recommend 
that this one be closed and I'm marking it as a duplicate.

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