Ok, one of the first replies to this thread pointed to: Have you checked out http://wiki.apache.org/spamassassin/UsingSpamAssassin ("Spam getting through?")?
Which I have looked at and saw the following there: Edit your spamd start-up script, or start-up options file (depending on which OS you're running, these may be different). There should be a -L or --local switch in that file. Remove it to enable network tests. I have commented out this line in the spamd file and done a restart. So this may have already helped some? Mike Loren Wilton wrote: > > Assuming you also restarted amvis so it will see the change, you should > now > be getting some more headers in your mail messages. You should see > headers > similar to the following in a typical non-spam mail: > > X-Spam-Virus: No > X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on > morticia.wizardess.wiz > X-Spam-Level: > X-Spam-Status: No, score=-95.6 required=4.6 > tests=BAYES_50,DK_POLICY_SIGNSOME, > FM_NO_STYLE,HELO_EQ_DSL,HOST_EQ_DSL,HTML_10_20,HTML_FONT_BIG, > HTML_MESSAGE,SPF_PASS,USER_IN_WHITELIST autolearn=disabled > version=3.1.4 > > From the above you can see which tests hit on the mail. By implication you > can see what tests are running, and possibly which rules you have loded on > the system. You can also detect some configuration errors that can lead > to > spam leaking through. > > When you see some of these for a spam that leaks through, post the full > thing including the headers and body. I have a hunch you may not be > running > network tests, and either aren't running Bayes or it is mistrained. It is > possible you have a problem with the trust path, since that is a common > misconfiguration. We will be able to tell that from the headers. > > Loren > > > -- View this message in context: http://www.nabble.com/OS-X-Server-spam-still-getting-through-%3A-%28-tf2206629.html#a6115926 Sent from the SpamAssassin - Users forum at Nabble.com.
