On 5/11/07, Daryl C. W. O'Shea <[EMAIL PROTECTED]> wrote:
> the "\d+_scores.cf" rules also can be a pain with sa-update which is a
> big part of the juggling.
Care to elaborate?
If you have a minimal configuration the mass-check scores will likely
bomb on your lint check. The names of the two plugins escape me, I
believe its a the uri scanning and dnsbl one. Which later in those
same files have ifplugin/endif lines wrapping similar rule scores.
*****
I was merely pointing out that the switch from pre-3.2 to 3.2 is just
stricter. In 3.1.8 you could can / run with an all in one local.cf and
no other file in /etc/mail/spamassassin and let sa-update or re/sare
script do their thing and they would march on.
The conversion issues from pre-3.2 to 3.2 such as the "no loaded
plugin implements 'check_main': cannot scan" and the "why are my
options being ignored" from users I would guess may indicate this. The
README snippet below and the lines in the /etc/mail/spamassassin
default files that reads may not be as clear or easily over looked.
Especially since I think the M:S:Conf does not mention this .cf/.pre
distinction.
# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
- /usr/share/spamassassin/*.cf:
Distributed configuration files, with all defaults. Do not modify
these, as they are overwritten when you upgrade.
- /etc/mail/spamassassin/*.cf:
Site config files, for system admins to create, modify, and
add local rules and scores to. Modifications here will be
appended to the config loaded from the above directory.
- /etc/mail/spamassassin/*.pre:
Plugin control files, installed from the distribution. These are
used to control what plugins are loaded. Modifications here will
be loaded before any configuration loaded from the above
directories.
You want to modify these files if you want to load additional
plugins, or inhibit loading a plugin that is enabled by default.
If the files exist in /etc/mail/spamassassin, they will not
be overwritten during future installs.
--
Gabriel Millerd
