On Tue, 05 Jul 2005 21:27:23 PDT, Justin Mason said:
BTW, someone (possibly Randal L. Schwartz) came up with a neat related trick to the above -- set up an interface alias on *the same machine* as the primary MX, list that as the last MX in the list, and (assuming that the software side of the primary MX is reliable) you're then assured that any SMTP traffic that arrives on that IP's port 25 is spam, since when the primary MX's hardware goes down, this MX will, too.
(Damn, left out a paragraph somehow) And in fact, given that most link hiccups *are* transitory, the chances are *good* that if our attempts at the first MX fail, the link will be back before we finish running through the MX's - at which point we find ourselves talking to a spamtrap.
At 1:27 AM -0400 2005-07-06, Valdis.Kletnieks@vt.edu wrote:
And in fact, given that most link hiccups *are* transitory, the chances are *good* that if our attempts at the first MX fail, the link will be back before we finish running through the MX's - at which point we find ourselves talking to a spamtrap.
Which is why I prefer to set up a tarpit as my high-MX spamtrap, but not make it do anything permanent or even long-lasting. If you're a legitimate sender talking to my tarpit, it'll take you a while to discover that you can't make it through, and you should be able to successfully retransmit at a later time. If you're a spammer, it'll take you a while to discover you can't make it through, but then you probably won't try again. -- Brad Knowles, <brad@stop.mail-abuse.org> "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See <http://www.sage.org/> for more info.
participants (2)
-
Brad Knowles -
Valdis.Kletnieks＠vt.edu