RE: 10_default_prefs.cf file in 3.2.x branch

> No, it doesn't... Your local.cf gets parsed *AFTER* this file, so your
> local.cf overides 10_default_prefs.cf.
>
> Note: for this to work 10_default_prefs.cf MUST NOT be in your
> /etc/mail/spamassassin. It belongs in /usr/share/spamassassin, as do ALL
> the rulefiles that come with SA. Only your site-specific customizations
> should be in /etc/mail/spamassassin.

snip
> My bigger question is, why not just let the SA installer install all
> this stuff? Why are you mucking about hand-installing the rules in the
> first place?

Matt,

I haven't moved anything no or ever.

Ummmm I am just dealing with having the hit report in my headers and I don't want it there. I want it off.

I turned it on at one time and then I turned it off in local.cf

Ive upgraded from 3.1.7 to 3.1.8 to 3.2.1 and in 3.2.1 I am seeing the rules hit report in my headers and I haven't figured out why when it is not on by default (near as I can tell) and I have the configs for that commented out since 3.1.8

Dunno

• rh