Michael C. Toren on 2 Jun 2006 21:05:16 -0000 |
On Fri, Jun 02, 2006 at 03:33:21PM -0400, Andrew Libby wrote: > If I recall correctly, one approach was to have a third MX that > basically trashes everything as a spam subversion measure. There > may be more to the configuration than that, but I don't recall. > > Anyone heard of this, know more about this? Randal Schwartz does something like this, which he outlined on the qpsmtpd list at one point (http://www.nntp.perl.org/group/perl.qpsmtpd/4756). He configured two virtual IPs on the same mail server, and MX records for his domain which point to these addresses: [mct@ellesmere ~]$ mx stonehenge.com stonehenge.com mail is handled by 5 blue.stonehenge.com. stonehenge.com mail is handled by 666 spamtrap.stonehenge.com. If a client connects to the primary MX, mail is accepted and delivered as you would expect. If a client connects instead to the secondary MX, the client's IP address is blacklisted for an hour. Pretty cool. -mct ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|