On Fri, May 30, 2003 at 11:21:05AM -0400, Maciek J. Maciak wrote:
> Here's the output from the above cmd, can you shed some light on why its 
> trying to use /root/.spamassassin directory and files ? should i be 

That's where the user preferences for root live.

> pointing it to a different location for systemwide rules?

They look ok to me.  /usr/share/spamassassin is where the default rules
go, /etc/mail/spamassassin is for your site-wide config.

> What are the different score sets used for, just debug ?

RTFM (perldoc Mail::SpamAssassin::Conf), look up "score". :)   (the short
short version is that the different scoresets are used when different
pieces of SA are enabled to get a more accurate score.)


The debug run looks good.

> The site rules file - /etc/mail/spamassassin/local.cf,  i can add any 
> lines similiar to the .cf files in /usr/share/spamassassin, anything 
> from whitrelists to header and body checks, and it will be read after 
> the default rules, correct ?

Yes.

> The following  is part of my 10_misc.cf,
> The file which i will create : /etc/mail/spamassassin/auto-whitelist, 
> what format/syntax should it be, a db file or just a text file 
> containing lines like these :
> whitelist_from_rcvd   [EMAIL PROTECTED]                  domainA.com

Well, there's the auto-whitelist, and there are manual whitelists
(whitelist_from, etc.)  They're completely different.

> Is this the proper way how to make sytemwide whitelists active ?
> # use this for a system-wide whitelist:
> # uncommented thefollowing 2 lines and created directory, not file - 
> 5_27_2003
> auto_whitelist_path        /etc/mail/spamassassin/auto-whitelist
> auto_whitelist_file_mode   0666

No.  Just add whitelist_* entries to local.cf.  There's a section in
the README about the auto-whitelist:

SpamAssassin includes automatic whitelisting; The current iteration is
considerably more complex than the original version.  The way it works is
by tracking for each sender address the average score of messages so far
seen from there.  Then, it combines this long-term average score for the
sender with the score for the particular message being evaluated, after
all other rules have been applied.

its purpose is primarily to keep spammy looking messages from someone
who tends to not send you spam from being caught by adjusting their
score downward a little bit automatically.

if you want to allow domain.foo though, you'd just add to a config file:

whitelist_from [EMAIL PROTECTED]

although whitelist_from_rcvd is better, but the details are in the docs.

-- 
Randomly Generated Tagline:
"Oh Yes!  It's X-Agent.  Faster than ... a regular sheep.  More powerful
 than ... a regular sheep.  Able to leap a regular sheep in a single bound!
 Yes!!  He's X-Agent: sheep with the power of an ox!"
         - Sheep in the Big City, "Hoof I Got a Surprise For Ewe"

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to