You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Sujit Choudhury <S....@westminster.ac.uk> on 2006/12/06 11:56:26 UTC
Confused with sa-update
I have run sa-update. The rules used to be in /usr/share/spamassassin &
SARE rules + local.cf in /etc/mail/spamassassin directory.
However spamassassin -D --lint now shows the following:
[28874] dbg: config: using "/etc/mail/spamassassin" for site rules pre
files
[28874] dbg: config: using "/var/lib/spamassassin/3.001007" for sys
rules pre fi les [28874] dbg: config: read file
/var/lib/spamassassin/3.001007/updates_spamassass
in_org.pre
[28874] dbg: config: using "/var/lib/spamassassin/3.001007" for default
rules di r [28874] dbg: config: read file
/var/lib/spamassassin/3.001007/updates_spamassass
There is no mention of rules in /usr/share/spamassassin.
I wonder whether I have a made a mistake.
Please help!!
- Sujit
Re: Confused with sa-update
Posted by Chris Purves <ch...@northfolk.ca>.
Sujit Choudhury wrote:
> I have run sa-update. The rules used to be in /usr/share/spamassassin &
> SARE rules + local.cf in /etc/mail/spamassassin directory.
>
> However spamassassin -D --lint now shows the following:
> [28874] dbg: config: using "/etc/mail/spamassassin" for site rules pre
> files
>
> [28874] dbg: config: using "/var/lib/spamassassin/3.001007" for sys
> rules pre fi les [28874] dbg: config: read file
> /var/lib/spamassassin/3.001007/updates_spamassass
> in_org.pre
> [28874] dbg: config: using "/var/lib/spamassassin/3.001007" for default
> rules di r [28874] dbg: config: read file
> /var/lib/spamassassin/3.001007/updates_spamassass
>
> There is no mention of rules in /usr/share/spamassassin.
>
> I wonder whether I have a made a mistake.
>
There's no mistake. From the wiki
http://wiki.apache.org/spamassassin/RuleUpdates
NOTE: Once the /var/lib/spamassassin/<spamassassin version> directory
exists, spamassassin expects to find all rules underneath that
directory, so make sure that the first time you run sa-update it
completes successfully (see below for information about running in debug
mode).
--
Chris