i want to understand something please

[Matt Kettler]

<x-flowed>
At 05:12 PM 8/29/2004, Idan Plotnik wrote:
>xmlns:ns0="urn:schemas-microsoft-com:office:smarttags">
>Hello,
>
>1. If I configure in my MailScanner.conf:
>Using SA = yes
>And I configure score = 7
>And in the local.cf I configure:
>required_hits           7.5
>
>what is count between them?

As someone else said, the option in MailScanner.conf is the one that will
matter. Mailscanner calls spamassassin, but it only pays attention to the
resulting score and does it's own message tagging.

the required_hits in local.cf will affect any test-runs you might do using
the command-line spamassassin, but it won't affect mail processed through
MailScanner.

>2. I saw some people copy the SA rules to /etc/mail/spamassassin and some
>not, they just using the original rules in /usr/shard/spamassassin
>What is the different between those two locations ?

There are actually three locations


/usr/share/spamassassin/*.cf - intended for the default rules that come
with spamassassin. This directory will get wiped out and replaced during SA
upgrades.

/etc/mail/spamassassin/*.cf  - intended for your site-wide customizations
and over-rides of the defaults. Not touched by the upgrade process.

MailScanner/spam.assassin.prefs.conf -  replaces the normal
"~/.spamassassin/user_prefs" file in SA, and allows you a place to
customize SA settings only when SA is invoked by MailScanner. Note: some
"administrative" settings won't be honored by SA here for security reasons.


>And what really count ?

All of them count..  They are parsed in order of most general to most
specific, starting with /usr/share, then /etc/, and the prefs are parsed
last. If there's a conflict SpamAssassin takes a 'last one parsed wins'
type approach.

This way, site-custom settings in /etc/mail/spamassassin/ can over-ride the
defaults in /usr/share.

Similarly the user-specific preferences can over-ride the site custom
settings in /etc/mail/spamassassin.

See man Mail::SpamAssassin::Conf for more details, but be aware that in
MailScanner spam.assassin.prefs.conf is equivalent to user_prefs, but
always acts as if allow_user_rules is set.

Also be aware that SA's subject_tag, add_header, required_hits, and other
message marking/encapsulation options don't matter, as MailScanner makes
it's own.

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).
</x-flowed>