Unless your MTA inserts header which tell who the actual recipient is, SA has no way of knowing and must rely on what is available in the headers. This makes the all_spam_to configuration a bit of a kludge because it's not completely effective, but it's the best that SA itself can do given what access it has to the message.
I'm not sure about spamass-milter, but some of the tools which call SA can be configured to do a true and absolute whitelisting based on the actual envelope recipient. I'm pretty sure I've read claims by amavisd-new and procmail setups that people have done these kinds of setups, and I know that mailscanner can do it too.
At 10:57 PM 6/8/03 -0500, Kim Jones wrote:
I am currently running spamassassin through spamass-milter in Sendmail. Working pretty good with the following exceptions. I have several users listed to not have spam blocked using all_spam_to. If a message is forwarded to them thus they are not apart of the TO, their spam will be blocked. Any suggestions appreciated.
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
