I see. The order is really directory order and not so much as file
order. All .cf files within each of the directories are read.
Not quite. The files are read from each directory in the order of the file
names, which is why many of the names start with numbers. Obviously
99anything.cf is
Raymond Wan wrote:
Not pertaining to Debian (I think)... I was wondering in what
order are SA's settings read in. Is this correct:
1) /etc/spamassassin/init.pre
2) /etc/spamassassin/local.cf
3) /usr/share/spamassassin/*.cf
4) ~/.spamassassin/user_prefs
Not quite. I believe
On Tue, Aug 22, 2006 at 07:11:25PM +0900, Raymond Wan wrote:
Not pertaining to Debian (I think)... I was wondering in what
order are SA's settings read in. Is this correct:
1) /etc/spamassassin/init.pre
2) /etc/spamassassin/local.cf
3) /usr/share/spamassassin/*.cf
4)
Hi Theo,
On Tue, 22 Aug 2006, Theo Van Dinter wrote:
1) /etc/spamassassin/init.pre
2) /etc/spamassassin/local.cf
3) /usr/share/spamassassin/*.cf
4) ~/.spamassassin/user_prefs
You could just read the spamassassin documentation which talks about all of
this. :)
But to answer your
On Wed, Aug 23, 2006 at 12:27:44AM +0900, Raymond Wan wrote:
No, they aren't backups of init.pre, they're pre files that got added in
3.1.0
and 3.1.2.
Oh? You mean they're cummulative? When you upgrade to a new
version, the new init.pre doesn't include the old ones?
Yes and no.
Raymond Wan wrote:
Hi Theo,
On Tue, 22 Aug 2006, Theo Van Dinter wrote:
score UPPERCASE_25_50 0
score UPPERCASE_50_75 0
score UPPERCASE_75_100 0
score OBSCURED_EMAIL 0
which I honestly don't know what it means... :)
Those rules are being
Hi Bowie,
On Tue, 22 Aug 2006, Bowie Bailey wrote:
Raymond Wan wrote:
1) /etc/spamassassin/*.pre
2a) /var/lib/spamassassin/3.001003/updates_spamassassin_org/*.cf
(if the directory exists)
2b) /usr/share/spamassassin/*.cf
(if the previous directory doesn't exist)
3)
From: Raymond Wan [EMAIL PROTECTED]
Hi Bowie,
On Tue, 22 Aug 2006, Bowie Bailey wrote:
Raymond Wan wrote:
1) /etc/spamassassin/*.pre
2a) /var/lib/spamassassin/3.001003/updates_spamassassin_org/*.cf
(if the directory exists)
2b) /usr/share/spamassassin/*.cf
(if the previous directory
Hi jdow,
On Tue, 22 Aug 2006, jdow wrote:
Never change /etc/share/spamassassin or the /var/lib/spamassassin
directories. Always change /etc/spamassassin/ or
/etc/mail/spamassassin
as appropriate for your install. You can override values set
earlier
with new ones. That change should probably
