>My boss is twisting off today because he got 350 messages marked [SPAM] >over the weekend. His Reaction is to "Bounce em all, Let the isps sort >it out."
And then when a spammer sends tons of e-mail to your site forged as, say, [EMAIL PROTECTED], you stand a good chance IBM may end up blocking all email from your site, at least for a while. Also, check the terms of service with your ISP. I suppose it is possible they might consider such a configuration as abusive, and could use it as grounds to terminate your service. Plenty of people are savvy enough to report spam to the ISP of the sender. (In this case, you would in effect be that sender.) What you want to do, IMO, is run SpamAssassin during the SMTP session, such as with http://duncanthrax.net/exiscan-acl/. Then reject messages with a very high score, but simply label and deliver messages for a lower spam score. For example, reject mail scoring 15 or higher, mark and deliver if 5 or over, and classify as ham if the score is below 5. Other MTAs provide other ways of doing this as well. -- John C. Ring, Jr. [EMAIL PROTECTED] Network Engineer Union Switch & Signal Inc. "If all mankind minus one, were of one opinion, & only one person of the contrary opinion, mankind would be no more justified in silencing that one person, than he, if he had the power, would be justified in silencing mankind" -- John Stuart Mill
