Re: [SAtalk] Order of precedence in rule sets?

[mairhtin]

Matt,

Thank you for explaining that so clearly for me. DUH! :) I should read more, but <insert lame excuse here>.

So, then my problem is, I have users with differing sets of "thresholds" that they want to use. I have one client who gets all sorts of odd emails from the suppliers he uses in the Far East, most of which have been marked as spam by SA. But he wants them. The only thing I could think of was to whitelist_to him with a -200 or so score.

Is there a more elegant solution to providing my differing client's expectaions? One might like a threshold of 5, another a threshold of 10. Another wants their OWN whitelist_to and blacklist_from, which I would not want to have any effect on my other users.

Any ideas?

Mairhtin




On Mon, 08 Dec 2003 13:06:38 -0500, Matt Kettler wrote:

>At 12:21 PM 12/8/2003, mairhtin wrote:
>>I have an oddity occuring. In my site-wide (local.cf) rules, I have some
>>custom rules, but none concerning dell.com . I want
>>one user to always get any mail from dell.com, but if other users get mail
>>from that domain (or one spoofed to look like it) I
>>want the general rules and learning to send it to the spam folder.
>>
>>I put a whitelist_from [EMAIL PROTECTED] in my special user's
>>/home/____/.spamassassin/user_prefs file, but I'm wondering if it
>>gets trapped before it goes to his directory, will it still be
>>whitelisted? In other words, if some rule or learned method says
>>that "[EMAIL PROTECTED]" (spoofed address) is spam, will he still
>>get it because it's addressed to him and his rules
>>say to whitelist anything from [EMAIL PROTECTED] ?????
>
>I think you're grossly misunderstanding how the whole user_prefs system works.
>
>SA does not EVER read user_prefs based on who the message is addressed to.
>After all, how does it know the addressee has an account on the server?
>Most of my user's don't have accounts at all, as the mailserver that runs
>SA is just a front-end relay to an internal server.
>
>Instead user_prefs is read based on the user ID that invokes the process
>(unless over-ridden with a -u parameter). This means that for most
>site-wide server setups, there's only one user_prefs ever read.. Usually
>this is root, mail, spamd, nobody, or some similar system account. It
>doesn't matter who it's addressed to, user_prefs is loaded from the home
>directory of the current user. If you specify -u, spamd does a setuid to
>that user prior to accessing ~/.spamassassin, and thus get's that user's
>home directory.
>
>Since SA only ever reads one user_prefs file per message, any other
>user_prefs files on the system are irrelevant. However, which user_prefs
>file is being read might not be what you think it is.
>
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
>Free Linux Tutorials. Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>_______________________________________________
>Spamassassin-talk mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/spamassassin-talk