This is a necessary byproduct of the fact that there's only ONE email, even though there are multiple recipients. It would be impossible for SA, which is merely a filter, to do anything more sophisticated than what it does now. It can't magically indicate "ok, when you deliver this Joe, do this, but when you give Sue her copy of it, behave differently".
The only way to prevent this behavior is to run SA independently per-user at the mailbox level. At this point each user has his/her own separate copy of the email.
And if you're using it, disable your AWL before you run into that common sitewide problem. That's got similar issues when used site-wide in combination with ALL_SPAM_TO'ed users. (hint: if the spammer mails an ALL_SPAM_TO'ed user first on a site with site-wide AWL, he now has a major whitelisting when emailing any other user in your network).
At 12:43 AM 1/14/2003 -0600, Brad Jackson wrote:
Hi all,
Running SA 2.50 on BSDI 4.x, Perl 5.8.0, delivering to local mailbox files via Postfix + Procmail. Everything works as advertised -- kudos to the SA coders!! :-) :-)
I have one minor problem. Using a site-wide config, I have some entries in my local.cf which specify users who have requested SA be 'turned off' by adding an all_spam_to entry for them (there's just no explaining it to the dullards ... {sigh}). This works properly; mail directed to those users gets scored a heavy negative, and is delivered marked as non-spam.
The problem arises when inbound spam has multiple addressees in the 'To:' header, and one of those addressees has an all_spam_to entry. Regardless of which recipient is receiving the current copy of the message, SA marks the mail as non-spam because the USER_IN_ALL_SPAM_TO rule was matched :-(
Is there a known fix or workaround for this? Am I just being stupid? (Wouldn't be the first time!)
I'd appreciate off-list copies of any replies.
Thanks,
Brad Jackson
Net Admin
I-1 Internet Group, Inc.
"i1" + at-sign + "i-1.net"
PS: Personal email stats for today: Received 114 emails of which 110 were correctly ID'd as Spam, 3 were legit emails correctly marked as non-spam, and one Spam slipped through (due to the issue mentioned above). That's damn near perfect. I'm a *happy* admin!
------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
