recently i had an idea on how to control spam, here's
a rundown...
what if i add a secondary mx record and point it to
any of my servers, not the primary mail server, just
any server that's not running an mta for the outside
world, then DROP packets on that server. won't that
slow down spammers? a proper mta would just retry with
an another mx and everyone's happy.
apparently i'm not the only one who thought of this,
here's a document discussing the idea. he's calling it
Nolisting "Poor Man's Greylisting" hehehe:
http://www.joreybump.com/code/howto/nolisting.html
the difference is the document recommends using
"REJECT --reject-with tcp-reset" instead of DROP,
which plays nicer with legit mtas, and actually having
this as the primary mail server.
any ideas, comments, past experiences?
although what i think is sooner or later spammers will
catch on, and just direct the spam to a single ip. but
this is still worth a shot, and pretty easy to do so i
might as well do it.
another variation to this idea is to actually have an
mta but always give out a 450 error, some sort of a
permanent greylisting. and of course you'd have
greylisting on your primary server, so this should
take some load of the main server and hopefully slow
down spammers ...
ideas, comments?
____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Jolug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups-beta.google.com/group/Jolug?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
