>>>>> "Bob" == Bob Eby <[EMAIL PROTECTED]> writes:
Bob> Instead, I'm going to follow Mr. Roberts' advice and try out a base Bob> system with spamd and greylisting. In the mean time, while such a Bob> system is keeping my few users afloat, I'll see if I can come up with Bob> something more tailored to our situation. If you have a spare IP address or two, you can also consider low-MX and high-MX traps. I've been using a high-MX trap for two years, and it eliminates about half of my spam. I just recently learned about low-MX traps, and am anxious to try that as well. Basically, you need to turn off the mailer on your A record, and point your lowest MX value at that same IP. Spammers will try to deliver here, and fail. Legitimate mailers will roll over to... Have a mid-range MX pointing at your actual mailer on a *different* IP. Ideally, this should be the same machine, so that you get consistent results with the following... Have a hi-range MX pointing at a different IP *with a mailer listening*. This mailer should return 450 for all mail, but also block that IP for an hour or so from reaching either your actual mailer IP or your hi-range MX ip again (temporary blacklist using PF, preferably on a separate ingres machine if you can). These "lightning rods" attract the spammers, while allowing normal RFC-compliant mail to get through. Like I said, I've been VERY happy with my high-MX trap for over two years. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
