I would still rather use a managable file that lists users.
Would anyone out there know how to make procmail check a list for a username?
On Wed, 2004-02-11 at 09:28, Bob Apthorpe wrote:
Hi,
On Wed, 11 Feb 2004 09:09:48 -0500 Wess Bechard <[EMAIL PROTECTED]> wrote:
> Currently I have spamassassin running globally via spamd with procmail.
>
> Is it possible to specify which users can use spamassassin, and which
> cannot? I wish to change from spamd to calling spamassassin per user.
Using spamassassin instead of spamc/spamd will incur a substantial
performance hit.
You could probably do something with procmail and $LOGNAME where you
pass mail through spamc if $LOGNAME is in a list of allowed spamassassin
users. I doubt that running spamassassin vs spamc/spamd is going to
solve this problem.
> I would really like to allow a certain group to use spamassassin, and
> have spamassassin not see the other email addresses.
Are there certain users you don't trust to use SpamAssassin or are there
accounts that you don't want to filter (e.g. role accounts)? If it's the
latter, consider using the all_spam_to directives in your global config
file. From 'perldoc Mail::SpamAssassin::Conf':
----
whitelist_to [EMAIL PROTECTED]
If the given address appears as a recipient in the
message headers (Resent-To, To, Cc, obvious envelope
recipient, etc.) the mail will be whitelisted. Useful
if you're deploying SpamAssassin system-wide, and
don't want some users to have their mail filtered.
Same format as "whitelist_from".
There are three levels of To-whitelisting,
"whitelist_to", "more_spam_to" and "all_spam_to".
Users in the first level may still get some spammish
mails blocked, but users in "all_spam_to" should never
get mail blocked.
more_spam_to [EMAIL PROTECTED]
See above.
all_spam_to [EMAIL PROTECTED]
See above.
----
hth,
-- Bob
|
Wess Bechard Technical Support eliquidMEDIA International Inc. [EMAIL PROTECTED] 519.973.1930 -1.800.561.7525 |
