If you're seeing ALL_TRUSTED in all of your email headers, that has
nothing to do with Bayes.  It's a different setting in
spam.assassin.prefs.conf.  When it doesn't know which IP(s) to count as
"trusted", all are trusted.  Add in a line or two in the form of:

trusted_networks 127.0.0.1 #trust everything coming from the local computer
trusted_networks 192.168.1. #trust everything coming from 192.168.50.*

Once you've explicitely defined your trusted networks, it will stop adding
this in for all other networks.

Renee

>
>
>
> Matt Kettler-3 wrote:
>>
>> squintr wrote:
>>> I'm seeing this in every message that goes through SpamAssassin:
>>>
>>> Score Matching Rule Description
>>> cached not
>>>  score=1.451
>>> 2 required
>>> -1.80 ALL_TRUSTED
>>> -2.60 BAYES_00
>>>
>>> This is often causing spam that should have a relatively high score to
>>> not
>>> get caught.
>>>
>>> I've turned bayes off in my mailscanner.conf file -- am I supposed to
>>> go
>>> somewhere else to turn it off?
>>>
>> Erm, you can't turn bayes off in your MailScanner.conf file. That's a
>> Mailscanner config file that SA does not, and can not interpret.
>>
>> Do you main /etc/mail/spamassassin/Mailscanner.cf?
>>
>> That said, a few things:
>>
>> 1) you need to reload your MailScanner processes for changes made to any
>> of your SA .cf files to take effect. If you run a redhat-like distro,
>> just do "service MailScanner reload". This will shutdown and restart all
>> the MailScanner processes without disturbing the sendmail processes.
>> Otherwise you'll have to wait until MailScanner kills and relaunches all
>> of its children on its own, which might take a few hours.
>>
>> 2) If you ever have external mail match ALL_TRUSTED, you need to declare
>> a trusted_networks setting manually.
>> See http://wiki.apache.org/spamassassin/TrustPath
>>
>
> Thanks!  I'm still fairly new to this.  I removed the comment before
> "use_bayes 0"  in /etc/MailScanner/spam.assassin.prefs.conf  so I don't
> see
> any references to BAYES in the spam reports.  I now see autolearn=disabled
>
> I wonder how much impact this is going to have with spam detection.
>
> So this basically does nothing?
>
> /etc/MailScanner/MailScanner.conf
> # If you are using the Bayesian statistics engine on a busy server,
> # you may well need to force a Bayesian database rebuild and expiry
> # at regular intervals. This is measures in seconds.
> # 1 day = 86400 seconds.
> # To disable this feature set this to 0.
> # Note: If you enable this feature, set "bayes_auto_expire 0" in
> #       spam.assasssin.prefs.conf which you will find in the same
> #       directory as this file.
> Rebuild Bayes Every = 0
>
>
>
>
> --
> View this message in context:
> http://www.nabble.com/I%27ve-turned-off-BAYES-but..-tf2949647.html#a8262307
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply via email to