On Sun, Dec 28, 2003 at 05:56:01PM -0500, Chris Tracy wrote: > > Hello, > > I am having a weird problem with spamassassin missing messages > > completely. Spamd logs that it accepted the mail to syslog but it does > > not add any headers. This has been happening a lot lately (20x a day or > > so) and I am unsure if it is an error in my setup or a problem with > > spamassassin. SA works fine for 99% of my messages it is only a small > > percent that slip through. I am wondering if anyone else has experienced > > this problem before and if there is a way to get more information from > > sa/postfix/procmail about what is going wrong. > > Interesting. I have been having similar problems since upgrading to > 2.61... I'm using qmail and FreeBSD, but I'm calling procmail with a > recipe similar to yours, except that I'm running spamd on one central > server which services a couple heavily-used mail servers. > > The machine running spamd catches ~100k spam messages per day for over > 700 users: > > # gzcat /var/log/maillog.0.gz | grep "Dec 27" | grep "identified spam" | wc -l > 104004 > > And about ~8k clean messages per day for those same users: > > # gzcat /var/log/maillog.0.gz | grep "Dec 27" | grep "clean message" | wc -l > 7848 > > Since upgrading, I've noticed that I am now getting some spam messages > in my INBOX that have no spamassassin headers. > > I get about 1300 spams a day, and I'm seeing maybe 10 messages per day > that have no spamassassin headers whatsoever, so the percentage is > rather small here as well (about 1%...) > > I'm still debugging to see what I can find out... Did you try turning > on spamd's debugging flag to see if anything else shows up in the > logs? (Unfortunately, turning that on on my server results in > terrible performance degradation, as there are an average of 29 spamd > processes running on average at any given point in time...)
I recently had this problem due to a number of "issues" on my personal mail server. The dual PPro 200 MHz setup was averaging 28.blah seconds per message. I added some statistics to my daily reporting script to tell me the maximum scanning time and how many messages exceeded that maximum. http://www.lambertfam.org/~lambert/SpamAssassin/spamassassin.stats It seemed somewhat obvious that my system just wasn't cutting it. About one message in ten was exceeding the 30 second timeout in spamc. So I upgraded the hardware but still had several messages slipping through. I was getting some Perl sig 6s in the logs so I rebuilt *every* port on which the p5-Mail-SpamAssassin port depends. That also happened to upgrade my SpamAssassin from 2.60 to 2.61. That got rid of the sig 6s and got my mail back under control. The sig 6s where causing bayes lock file to be left laying around which added a 10 second timeout to every message. I twigged to that when my 1.6GHz Athlon started averaging 10 seconds per message. None of my 4 day job spamd servers have had sig 6 issues with identical software configurations, and a lot more e-mail. -- Scott Lambert KC5MLE Unix SysAdmin [EMAIL PROTECTED] ------------------------------------------------------- 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_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
