mkettler_sa at verizon
Feb 5, 2010, 4:51 AM
Post #2 of 3
(380 views)
Permalink
|
On 2/4/2010 5:35 AM, Kārlis Repsons wrote:
> People,
> in trying to set up Razor2 sitewide, I found some things, which were not so good about the wikipage [1]. As per me, it would be this way (and it works):
>
>
> I What was wrong
>
> 1. no need calling razor-client
> 2. no need to touch /etc/spamassassin, just /etc/spamassassin/.razor
> 3. cd .razor && chmod g+rw *
>
> (first two cause some small confusion, but the last one took me digging through logfiles)
>
> + better razorhome = /etc/mail/spamassassin/.razor
> not razorhome = /etc/mail/spamassassin/.razor/
> !
>
>
more to the point, razorhome is an obsolete option, I can find no
reference to it in the 3.3 code :-)
>
> Its not clear to me in what cases should "-C /etc/mail/spamassassin" be added to calling spamassassin. Maybe /etc/mail/spamassassin is in some default path?
> (as it works without "-C .." for me)
>
That clearly needs fixing.
-C should *NEVER* point to /etc/mail/spamassassin. *EVER*. No really.
This is a massive mistake popularized by a gross misunderstanding of
what this option does.
/etc/mail/spamassassin is the default for the --siteconfig path (ie:
where local.cf, init.pre and other files you edit should live). -C
specifies the default ruleset path (ie: files that are installed by SA
and/or sa-update, and you really should never be editing).
-C should only be used by true experts and/or developers who need to
maintain multiple base rulesets, because this option points to it. The
default here is /usr/share/spamassassin/, and then sa-update over-rides
to a directory under /var/lib/spamassassin.
It is important to note that using -C breaks sa-update, unless you
manually point -C to the directory it created, or copy the files
sa-update downloaded. At which point, why are you using it?
So, by specifying -C /etc/mail/spamassassin, you're forcing the default
ruleset path to be the same as the site config.
The folks making this mistake are also the ones who find they need to
copy /usr/share/spamassassin into /etc/mail/spamassassin. And then they
wonder why sa-update doesn't seem to be fixing their ruleset.
>
> [1] http://wiki.apache.org/spamassassin/RazorSiteWide
>
|
signature.asc
