Bug 5109 - port scan causes spamd to log noise to syslog
Summary: port scan causes spamd to log noise to syslog
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: Future
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-25 22:39 UTC by Daryl C. W. O'Shea
Modified: 2021-04-12 12:16 UTC (History)
1 user (show)


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 Daryl C. W. O'Shea 2006-09-25 22:39:28 UTC 
A port scan with nmap triggers this junk to be logged, spamd continues along
happily:

Sep 25 18:38:23 bob spamd[12406]: Use of uninitialized value in subroutine entry
at /usr/lib/perl5/5.8.8/i386-linux-thread-multi/Socket.pm line 370.
Sep 25 18:38:23 bob spamd[12406]: Bad arg length for Socket::unpack_sockaddr_in,
length is 0, should be 16 at
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/Socket.pm line 370.
Sep 25 18:38:23 bob spamd[12406]: spamd: error: Bad arg length for
Socket::unpack_sockaddr_in, length is 0, should be 16 at
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/Socket.pm line 370.
Sep 25 18:38:23 bob spamd[12406]:  , continuing at /usr/bin/spamd line 924.
Comment 1 Theo Van Dinter 2006-11-30 20:11:27 UTC 
fwiw, the errors are from Socket.pm, so I don't think there's much we can do
about it.
Comment 2 Henrik Krohns 2021-04-12 12:16:09 UTC 
Doesn't seem to be a problem anymore.