Hi Everyone, I have SpamAssassin up and running both in test and in production. In production, everything is fine. In test, not so much. I originally thought Test was broken just since the changes I made yesterday, but the deeper I look, it appears test has been broken all along.
Red Hat 2.4.20-24.8 SpamAssassin 2.61-1 qmail 1.03 I've never messed with SpamAssassin at all before yesterday. Yesterday I downloaded some .cf files into /etc/mail/spamassassin bigevil.cf pbw.cf 90_FVGT.cf nov2rules.cf I don't think the .cf files have anything to do with the problem, but I'm throwing this in there for completeness of the report. Then I restarted spamassassin service spamassassin restart Everything came up OK. That was yesterday, and everything seemed fine - I was in a hurry, and didn't have time to test; figuring I'd look at it this morning. Here is my qmailanalog file being sent to me in the middle of the night, from Test, just as always: Dec 23 04:02:33 mx3 qmail: 1072180953.039285 new msg 98420 Dec 23 04:02:33 mx3 qmail: 1072180953.039371 info msg 98420: bytes 6825 from <[EMAIL PROTECTED]> qp 16924 uid 0 Dec 23 04:02:33 mx3 qmail: 1072180953.530169 starting delivery 172: msg 98420 to local [EMAIL PROTECTED] Dec 23 04:02:33 mx3 qmail: 1072180953.530241 status: local 1/10 remote 0/110 Dec 23 04:02:33 mx3 spamd[12541]: connection from mx3 [127.0.0.1] at port 33304 Dec 23 04:02:33 mx3 spamd[16969]: info: setuid to alias succeeded Dec 23 04:02:33 mx3 spamd[16969]: processing message <[EMAIL PROTECTED]> for alias:100. Dec 23 04:02:33 mx3 spamd[16969]: clean message (0.3/5.0) for alias:100 in 0.0 seconds, 6947 bytes. Dec 23 04:02:34 mx3 qmail: 1072180954.124888 new msg 98456 Dec 23 04:02:34 mx3 qmail: 1072180954.124966 info msg 98456: bytes 6940 from <[EMAIL PROTECTED]> qp 16971 uid 100 Dec 23 04:02:34 mx3 qmail: 1072180954.212866 starting delivery 173: msg 98456 to remote [EMAIL PROTECTED] Dec 23 04:02:34 mx3 qmail: 1072180954.212895 status: local 1/10 remote 1/110 Dec 23 04:02:34 mx3 qmail: 1072180954.212915 delivery 172: success: procmail:_Couldn't_create_"/var/spool/mail/alias"/procmail:_Extraneous_filter-flag_ignored/forward:_qp_16971/did_0+0+2/ Dec 23 04:02:34 mx3 qmail: 1072180954.225858 status: local 0/10 remote 1/110 Dec 23 04:02:34 mx3 qmail: 1072180954.225916 end msg 98420 Dec 23 04:02:34 mx3 qmail: 1072180954.356004 delivery 173: success: 170.192.153.111_accepted_message./Remote_host_said:_250_2.6.0__<[EMAIL PROTECTED]>_Queued_mail_for_delivery/ Dec 23 04:02:34 mx3 qmail: 1072180954.378265 status: local 0/10 remote 0/110 Dec 23 04:02:34 mx3 qmail: 1072180954.378286 end msg 98456 You can see spamd doing its thing just fine, looking at the email that started locally - this is a scheduled send of my qmailanalog report; happens every morning. And then today, when I went back through all of my maillog's on the test box, spamd has never worked except for mail coming from the test box itself. Anything coming from outside is NOT analyzed at all by SpamAssassin. Which leads me to think this has to do with somehow SpamAssassin is only letting certain networks in? Here is an example from today, of an outside email, with spamassassin not working at all: Dec 23 12:38:39 mx3 smtpd: 1072211919.874232 tcpserver: status: 1/200 Dec 23 12:38:39 mx3 smtpd: 1072211919.874472 tcpserver: pid 19366 from 64.4.47.13 Dec 23 12:38:39 mx3 smtpd: 1072211919.875649 tcpserver: ok 19366 mx3.puget.com:204.61.33.68:25 bay9-f13.bay9.hotmail.com:64.4.47.13::4483 Dec 23 12:38:40 mx3 qmail: 1072211920.347026 new msg 98422 Dec 23 12:38:40 mx3 qmail: 1072211920.347099 info msg 98422: bytes 1370 from <[EMAIL PROTECTED]> qp 19367 uid 101 Dec 23 12:38:40 mx3 smtpd: 1072211920.376242 tcpserver: end 19366 status 0 Dec 23 12:38:40 mx3 smtpd: 1072211920.376279 tcpserver: status: 0/200 Dec 23 12:38:40 mx3 qmail: 1072211920.436881 starting delivery 174: msg 98422 to local [EMAIL PROTECTED] Dec 23 12:38:40 mx3 qmail: 1072211920.436924 status: local 1/10 remote 0/110 Dec 23 12:38:40 mx3 qmail: 1072211920.569436 new msg 98456 Dec 23 12:38:40 mx3 qmail: 1072211920.569503 info msg 98456: bytes 1472 from <[EMAIL PROTECTED]> qp 19370 uid 100 Dec 23 12:38:40 mx3 qmail: 1072211920.650945 starting delivery 175: msg 98456 to remote [EMAIL PROTECTED] Dec 23 12:38:40 mx3 qmail: 1072211920.650970 status: local 1/10 remote 1/110 Dec 23 12:38:40 mx3 qmail: 1072211920.650985 delivery 174: success: did_0+1+0/qp_19370/ Dec 23 12:38:40 mx3 qmail: 1072211920.663592 status: local 0/10 remote 1/110 Dec 23 12:38:40 mx3 qmail: 1072211920.663664 end msg 98422 Dec 23 12:38:40 mx3 qmail: 1072211920.780760 delivery 175: success: 170.192.153.111_accepted_message./Remote_host_said:_250_2.6.0__<[EMAIL PROTECTED]>_Queued_mail_for_delivery/ Dec 23 12:38:40 mx3 qmail: 1072211920.794184 status: local 0/10 remote 0/110 Dec 23 12:38:40 mx3 qmail: 1072211920.794202 end msg 98456 You'll notice that spamd isn't doing a damn thing! Yet it seems to be running just fine: [EMAIL PROTECTED] log]# ps -aux | grep spam root 781 0.0 0.9 26808 22976 ? S 13:49 0:01 /usr/bin/spamd -d [EMAIL PROTECTED] log]# On the other hand, here is one of my production system log files: Dec 23 17:00:27 mx1 spamd[6230]: connection from localhost.localdomain [127.0.0.1] at port 54131 Dec 23 17:00:27 mx1 spamd[19725]: info: setuid to alias succeeded Dec 23 17:00:27 mx1 spamd[19725]: processing message <[EMAIL PROTECTED]> for alias:100. Dec 23 17:00:27 mx1 qmail: 1072227627.390285 new msg 606457 Dec 23 17:00:27 mx1 qmail: 1072227627.390342 info msg 606457: bytes 2371 from <[EMAIL PROTECTED]> qp 19718 uid 101 Dec 23 17:00:27 mx1 smtpd: 1072227627.405295 tcpserver: end 19698 status 0 Dec 23 17:00:27 mx1 smtpd: 1072227627.405368 tcpserver: status: 5/200 Dec 23 17:00:27 mx1 spamd[19725]: clean message (1.8/5.0) for alias:100 in 0.0 seconds, 1284 bytes. Dec 23 17:00:27 mx1 smtpd: 1072227627.566307 tcpserver: end 19700 status 0 Dec 23 17:00:27 mx1 smtpd: 1072227627.566356 tcpserver: status: 4/200 Dec 23 17:00:27 mx1 smtpd: 1072227627.605627 tcpserver: status: 5/200 Dec 23 17:00:27 mx1 smtpd: 1072227627.605887 tcpserver: pid 19728 from 64.200.120.138 Dec 23 17:00:27 mx1 smtpd: 1072227627.689411 tcpserver: status: 6/200 Dec 23 17:00:27 mx1 smtpd: 1072227627.689545 tcpserver: pid 19729 from 69.6.28.118 Dec 23 17:00:27 mx1 smtpd: 1072227627.690650 tcpserver: ok 19729 mx1.puget.com:204.61.33.69:25 15.pnae.com:69.6.28.118::3964 Dec 23 17:00:27 mx1 smtpd: 1072227627.692693 rblsmtpd: 69.6.28.118 pid 19729: 451 http://www.spamhaus.org/SBL/sbl.lasso?query=SBL6636 Dec 23 17:00:27 mx1 qmail: 1072227627.803692 starting delivery 4437970: msg 606457 to local [EMAIL PROTECTED] Dec 23 17:00:27 mx1 qmail: 1072227627.803729 status: local 2/10 remote 0/110 Dec 23 17:00:27 mx1 spamd[6230]: connection from localhost.localdomain [127.0.0.1] at port 54132 Dec 23 17:00:27 mx1 spamd[19737]: info: setuid to alias succeeded Dec 23 17:00:27 mx1 spamd[19737]: processing message (unknown) for alias:100. Dec 23 17:00:27 mx1 qmail: 1072227627.912603 new msg 606291 Dec 23 17:00:27 mx1 qmail: 1072227627.912660 info msg 606291: bytes 6017 from <[EMAIL PROTECTED]> qp 19716 uid 101 Dec 23 17:00:28 mx1 smtpd: 1072227628.018372 tcpserver: end 19702 status 0 Dec 23 17:00:28 mx1 smtpd: 1072227628.018437 tcpserver: status: 5/200 Dec 23 17:00:28 mx1 spamd[19737]: clean message (-4.9/5.0) for alias:100 in 1.0 seconds, 2509 bytes. Dec 23 17:00:28 mx1 qmail: 1072227628.687734 delivery 4437969: success: procmail:_Extraneous_filter-flag_ignored/forward:_qp_19727/did_0+0+2/ Dec 23 17:00:28 mx1 qmail: 1072227628.731749 status: local 1/10 remote 0/110 Dec 23 17:00:28 mx1 qmail: 1072227628.731805 starting delivery 4437971: msg 606291 to local [EMAIL PROTECTED] Dec 23 17:00:28 mx1 qmail: 1072227628.731816 status: local 2/10 remote 0/110 Dec 23 17:00:28 mx1 qmail: 1072227628.731826 end msg 606297 Dec 23 17:00:28 mx1 smtpd: 1072227628.827503 tcpserver: status: 6/200 Dec 23 17:00:28 mx1 smtpd: 1072227628.827719 tcpserver: pid 19740 from 216.9.176.93 Dec 23 17:00:28 mx1 smtpd: 1072227628.831425 tcpserver: ok 19740 mx1.puget.com:204.61.33.69:25 mail.feathersushi.com:216.9.176.93::35270 Dec 23 17:00:28 mx1 smtpd: 1072227628.832560 rblsmtpd: 216.9.176.93 pid 19740: 451 http://www.spamhaus.org/SBL/sbl.lasso?query=SBL10331 Dec 23 17:00:28 mx1 spamd[6230]: connection from localhost.localdomain [127.0.0.1] at port 54133 Dec 23 17:00:28 mx1 spamd[19748]: info: setuid to alias succeeded Dec 23 17:00:28 mx1 spamd[19748]: processing message <[EMAIL PROTECTED]> for alias:100. Dec 23 17:00:28 mx1 qmail: 1072227628.975392 new msg 606474 Dec 23 17:00:28 mx1 qmail: 1072227628.975446 info msg 606474: bytes 1263 from <[EMAIL PROTECTED]> qp 19727 uid 100 Dec 23 17:00:28 mx1 smtpd: 1072227628.981870 tcpserver: status: 7/200 Dec 23 17:00:28 mx1 smtpd: 1072227628.982045 tcpserver: pid 19749 from 69.6.29.154 Dec 23 17:00:28 mx1 smtpd: 1072227628.983174 tcpserver: ok 19749 mx1.puget.com:204.61.33.69:25 :69.6.29.154::64654 Dec 23 17:00:28 mx1 smtpd: 1072227628.985106 rblsmtpd: 69.6.29.154 pid 19749: 451 http://www.spamhaus.org/SBL/sbl.lasso?query=SBL6636 Dec 23 17:00:29 mx1 spamd[19748]: identified spam (16.8/5.0) for alias:100 in 1.0 seconds, 6156 bytes. Dec 23 17:00:29 mx1 smtpd: 1072227629.320534 tcpserver: end 19749 status 0 And this is what is loaded on the same system: [EMAIL PROTECTED] log]# ps -aux | grep spam root 6230 0.1 1.8 24212 19344 ? S Dec18 7:33 /usr/bin/spamd -d alias 22195 0.0 0.0 1968 536 ? S 17:10 0:00 /usr/bin/spamc -f alias 22196 0.0 2.0 25564 20916 ? D 17:10 0:00 /usr/bin/spamd -d [EMAIL PROTECTED] log]# Both systems have the following identical file: [EMAIL PROTECTED] spamassassin]# cat local.cf # This is the right place to customize your installation of SpamAssassin. # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # tweaked. # ########################################################################### # #rewrite_subject 0 #report_safe 1 required_hits 5.0 whitelist_from [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] spamassassin]# I have googled and searched the archives, and can't find anything to tell me why my production systems are scanning inbound mail, and my test system isn't. Can someone please tell me: a) why SpamAssassin is working for local mail, but not external mail b) what I should do to fix it? Many thanks, Jesse Wendel Seattle ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
