Tim B wrote: > This way regardless of the reason, if X-SPAM-STATUS header is > missing, we will assume spamc had some kind of problem, and then we > will use the good ol' stand by command line spamassassin.
On a heavily loaded server, this is downright *suicidal*. spamd/spamc are used to reduce system load incurred by having to load Perl and parse all of the configuration files for each message. With a high mail volume, this can mean ~3x or more mail volume can be processed on the same hardware without causing problems. With your method of making sure mail gets scanned, mail will slowly build up in the queue until the server runs out of disk space, the MTA can't process the queue because it's too big, or SA's memory usage triggers the Linux kernel OOM process killer. (Exactly which happens first depends on the MTA and how much physical memory you have.) On a private server with only a few accounts, this is not an issue. -kgd -- "Sendmail administration is not black magic. There are legitimate technical reasons why it requires the sacrificing of a live chicken." - Unknown ------------------------------------------------------- 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
