Bug 3909 - SPAMD keeps stopping on my SMTP gateway
Summary: SPAMD keeps stopping on my SMTP gateway
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.0.0
Hardware: PC Linux
: P5 critical
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords: triage
Depends on:
Blocks:
 
Reported: 2004-10-19 08:43 UTC by Chris
Modified: 2005-06-14 15:06 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 Chris 2004-10-19 08:43:43 UTC 
Redhat Fedora Core 2
Spamassassin 3.0.0
using Postfix to call spamc/spamd combo

Here are the errors in my maillog:

Oct 18 15:49:23 wall postfix/pipe[24001]: 915EDB4B1: 
to=<webmaster@castellan.net>, relay=spamassassin, delay=617, status=sent 
(mt1.castellan.net)
Oct 18 15:49:27 wall spamd[22763]: identified spam (19.4/5.0) for nobody:99 in 
607.1 seconds, 2755 bytes.
Oct 18 15:49:28 wall spamd[22763]: result: Y 19 - 
BIZ_TLD,DNS_FROM_AHBL_RHSBL,FORGED_HOTMAIL_RCVD,HELO_DYNAMIC_DIALIN,HTML_FONT_BI
G,HTML_MESSAGE,HTML_TAG_EXI$
Oct 18 15:49:30 wall spamd[22762]: Use of uninitialized value in subroutine 
entry at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/Socket.pm line 373, 
<GEN157$
Oct 18 15:49:30 wall spamd[22762]: Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Metadata/Received.p$
Oct 18 15:49:31 wall spamd[22762]: Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Metadata/Received.p$
Oct 18 15:49:31 wall spamd[22762]: Use of uninitialized value in subroutine 
entry at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/Socket.pm line 373, 
<GEN157$
Oct 18 15:49:32 wall spamd[22762]: Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Metadata/Received.p$
Oct 18 15:49:32 wall spamd[22762]: Use of uninitialized value in hash element 
at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Metadata/Received.p$
Oct 18 15:49:32 wall spamd[22762]: Use of uninitialized value in pattern match 
(m//) at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Metadata/Rec$
Oct 18 15:49:33 wall spamd[22762]: Use of uninitialized value in pattern match 
(m//) at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Metadata/Rec$
Oct 18 15:49:33 wall spamd[22762]: Use of uninitialized value in concatenation 
(.) or string at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Message/Meta$
Oct 18 15:49:34 wall spamd[22762]: Use of uninitialized value in subroutine 
entry at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/Socket.pm line 373, 
<GEN157$
Oct 18 15:49:36 wall last message repeated 9 times
Oct 18 15:49:36 wall spamd[22762]: Failed to run DNS_FROM_AHBL_RHSBL RBL 
SpamAssassin test, skipping:__(Bad arg length for Socket::pack_sockaddr_in, 
length i$
Oct 18 15:49:37 wall spamd[22762]: Use of uninitialized value in subroutine 
entry at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/Socket.pm line 373, 
<GEN157$
Oct 18 15:49:37 wall spamd[22762]: Use of uninitialized value in subroutine 
entry at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/Socket.pm line 373, 
<GEN157$
Oct 18 15:49:41 wall postfix/smtpd[24071]: connect from unknown[211.110.148.34]
Oct 18 15:49:43 wall postfix/smtpd[24071]: 1E35AB4B1: client=unknown
[211.110.148.34]
Comment 1 era eriksson 2005-02-23 04:26:33 UTC 
The log lines appear to be truncated at $ so the actual line numbers of the
errors etc are mostly missing. If this is still happening, perhaps you could
attach a log file snippet instead of an error-prone copy/paste
Comment 2 Daniel Quinlan 2005-05-04 22:45:30 UTC 
Can you please test the current nightly build of SpamAssassin and see if
this is still happening to you?

http://cvs.apache.org/snapshots/spamassassin/
Comment 3 Justin Mason 2005-06-14 23:06:04 UTC 
closing due to lack of feedback.

if this is still occurring in either 3.0.4 or 3.1.0, feel free to reopen.