Every now and then a spam slips through with no header markups. I finally tracked some of these down and found that spamd took so long to finish that spamc finally timed out. (In this case, 742 seconds.)
I'm not sure what causes this. I'm running 2.60, and I thought that very slow RBLs were handled so as to avoid this. The machine wasn't particularly busy, but resource contention is always possible, especially if there is a burst of spam. I once suggested a header be added to show a timeout, and was told that it was beyond the scope of the spamc logic. How about just a log message? Something to help distinguish between a legit false negative and a resource problem. -- Jack Gostl [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
