You can use the whitelist_to, more_spam_to, and all_spam_to configuration options, but it won't cause SpamAssassin not to process the mail, just not to tag it as spam (to varying degrees). Another downside is that, if a mail comes in to a whitelisted user and a non-whitelisted user, it'll most likely slip through to the non-whitelisted user as well.

Doug Ledbetter wrote:

Hello all,

I've been doing research in preparation for installing SpamAssassin on my company's server in such a way that individual users can choose to turn it on or off. From what I've seen, it appears that I will need to install ProcMail and configure it individually for users so that only some users get their email processed with SpamAssassin. Is this correct or is there any simpler way to do this?

It's absolutely necessary that SpamAssassin NOT process mail for some users, so I can't do a site-wide MTA integration.

Here's my setup:

        - qmail
        - VPopMail v5.2.1

thanks,
-dougl


____________________________________________________________


Doug Ledbetter -- Hagen Software, Inc.
[EMAIL PROTECTED]
My PGP Public Key: http://dougledbetter.org/public_key.html



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01


_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk



This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.

Reply via email to