more/all_spam_to

[Jack Briody]

The more_spam_to and all_spam_to seemed to work fine on our site. But I
added the directives in the SA .cf file itself, ours is at
/usr/share/spamassassin/60_whitelist.cf

Any reason why, if SA is only being used in conjunction with mail
scanner, not to use these .cf files as opposed to the root user file?

Jack

>>> mkettler at EVI-INC.COM 07/12/02 02:11PM >>>
Which SA config file did you add your "more_spam_to" directives? Be
aware
that without a bit of extra work spamassassin is always called as user
root
by mailscanner so /home/username/.spamassassin/user_prefs is not the
proper
place. /etc/mail/mailscanner is a good spot, or
/root/.spamassassin/user_prefs.

These seem to work fine for me, but make sure that mailscanner isn't
doing
RBL checks, let SA do them. Otherwise the more_spam_to will apply to
SA
scoring, but it could still be tagged by mailscanner doing a RBL
check.

At 03:39 PM 7/12/2002 -0300, David Lancaster wrote:
>Julian et all,
>
>Question:
>I'm using MailScanner and Spamassassin to scan incoming mail, flag it,
and
>pass it off to a server for delivery. Most of our users will be
extermely
>happy to be able to filter their spam out.
>
>Figuring that some users will (for whatever reason) be disgruntled by
the
>addition of {SPAM??} to the subject, I'm looking for a way to
>"opt-out" certain users.  SA has a "more_spam_to and
>all_spam_to" directive, but those don't seem to work when SA is being
>called by MailScanner.
>
>Am I missing a simple way to configure this? (I can't just setup user
>accounts and procmail scripts, too many users...) Could MailScanner
obey
>SA's more/all_spam_to directives?  Is this (or adding a recipient
>whitelist) an option that could be added simply?
>
>TIA,
>D.
>
>
>===========================================================
>David Lancaster
>ITS ESS