RE: [SAtalk] Stop Checking When Score Reached

[Paul Fries]

Doug,   I inquired about this as well a few weeks ago.   The reason it was discontinued is because that switch causes SA to be a “red herring” in some cases. There are some negative scoring tests that do not get processed if the message reaches the threshold too soon.   I believe there was talk of fixing this option. Perhaps by running all of the negative scoring tests first.   -Paul   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Doug Eubanks Sent: Tuesday, December 31, 2002 11:45 AM To: [EMAIL PROTECTED] Subject: [SAtalk] Stop Checking When Score Reached   I have been using SPAMC/SPAMD for 5 or 6 weeks now (2.50-CVS).  I just updated the src from the new CVS and rebuilt the package.  When I tried to start the SPAMD service it politely informed me that -S was no longer a valid switch.  Isn't that the switch that told SPAMD to stop checking when it reached the specified score?  Our server is now running complete checks and logging this in the log file.     identified spam (17.8/6.0) for SOMEUSER:99 in 11.0 seconds, 1276 bytes.   This would be fine except we are using SpamAssassin on a roundrobin server that handles >150,000 messages/day and the extra checking is eating up more CPU than we need.  I searched the documentation to see if this had been changed to a different switch, but I can't find it in the Changes or man files.   Can someone help me out and point me into the direction I need to go to get it where it wont continue processing when it reaches the user specified score?   If you take a moment to reply, please carbon copy the message to my personal address as well so that I will not have to wait for the digest to be generated to get a reply.   Thanks Everyone! [EMAIL PROTECTED]