I haven't been able to find this covered anywhere, but I would like to use both the spamcop list (which has been working pretty well) and a local URI blacklist in which to put my own domains that I have problems with. Since I find it hard to believe I am the only one wanting to do this, I can only assume I must have missed the how-to somewhere along the way. Can anyone lend a hand, or provide some links on how I can add in my own list?
On Wednesday, June 16, 2004, 12:12:39 PM, Jeff Taylor wrote:
I haven't been able to find this covered anywhere, but I would like to use both the spamcop list (which has been working pretty well) and a local URI blacklist in which to put my own domains that I have problems with. Since I find it hard to believe I am the only one wanting to do this, I can only assume I must have missed the how-to somewhere along the way. Can anyone lend a hand, or provide some links on how I can add in my own list?
Hi Jeff, You can create and serve a list for your local use simply by creating a zone file with a syntax like the existing SURBLs, but with your own zone name and "host names" where the host names are the domains (and IPs) to block on:
$TTL 28800 @ IN SOA YOUR_ORIGIN. YOUR_CONTACT. ( 1087415057 600 300 604800 28800 )
@ IN NS YOUR_NAMESERVERS_HERE.
YOUR_DOMAIN_TO_BLOCK IN A 127.0.0.2 IN TXT "YOUR TEXT MESSAGE HERE." REVERSED_IP_ADDRESS_TO_BLOCK IN A 127.0.0.2 IN TXT "YOUR TEXT MESSAGE HERE." [...]
Then serve the zone on your local name server and use the name of your own zone in your SA SURBL rules.
Jeff C.
Jeff Chan wrote:
You can create and serve a list for your local use simply by creating a zone file with a syntax like the existing SURBLs, but with your own zone name and "host names" where the host names are the domains (and IPs) to block on:
Something like MyDNS, or the MySQL patches for BIND would probably be very useful for this type of process.
David
Hmm ok. I was also thinking I might use Postfix's body checks and just drop the domains in there as well, as I'm guessing there's not much difference in performance between either test.
Also, what about simply adding the entries to the /etc/hosts file on the mailserver? Wouldn't that have the same effect as adding it to the local DNS?
Jeff Chan wrote:
Hi Jeff, You can create and serve a list for your local use simply by creating a zone file with a syntax like the existing SURBLs, but with your own zone name and "host names" where the host names are the domains (and IPs) to block on:
$TTL 28800 @ IN SOA YOUR_ORIGIN. YOUR_CONTACT. ( 1087415057 600 300 604800 28800 )
@ IN NS YOUR_NAMESERVERS_HERE.
YOUR_DOMAIN_TO_BLOCK IN A 127.0.0.2 IN TXT "YOUR TEXT MESSAGE HERE." REVERSED_IP_ADDRESS_TO_BLOCK IN A 127.0.0.2 IN TXT "YOUR TEXT MESSAGE HERE." [...]
Then serve the zone on your local name server and use the name of your own zone in your SA SURBL rules.
Jeff C.
Discuss mailing list Discuss@lists.surbl.org http://lists.surbl.org/mailman/listinfo/discuss
Jeff Taylor wrote:
Hmm ok. I was also thinking I might use Postfix's body checks and just drop the domains in there as well, as I'm guessing there's not much difference in performance between either test.
Also, what about simply adding the entries to the /etc/hosts file on the mailserver? Wouldn't that have the same effect as adding it to the local DNS?
Logical yes (not really - see bellow), but not performance. DNS servers have everything in memory ready to answer everything as fast as possible. hosts file is good, but not if you have some thosands of entries at the same time. Back to old internet times before hosts.
Also, this will have the secondary effect of disallowing you to see web pages on those sites. E.g., you you define at your hosts file : spammer.com, you can't no more access the URL http://spammer.com/index.html, as this will resolve to 127.0.0.2 (e.g.). Saw it ???
Joe
Jeff Chan wrote:
Hi Jeff, You can create and serve a list for your local use simply by creating a zone file with a syntax like the existing SURBLs, but with your own zone name and "host names" where the host names are the domains (and IPs) to block on:
$TTL 28800 @ IN SOA YOUR_ORIGIN. YOUR_CONTACT. ( 1087415057 600 300 604800 28800 )
@ IN NS YOUR_NAMESERVERS_HERE.
YOUR_DOMAIN_TO_BLOCK IN A 127.0.0.2 IN TXT "YOUR TEXT MESSAGE HERE." REVERSED_IP_ADDRESS_TO_BLOCK IN A 127.0.0.2 IN TXT "YOUR TEXT MESSAGE HERE." [...]
Then serve the zone on your local name server and use the name of your own zone in your SA SURBL rules.
Jeff C.
Discuss mailing list Discuss@lists.surbl.org http://lists.surbl.org/mailman/listinfo/discuss
Discuss mailing list Discuss@lists.surbl.org http://lists.surbl.org/mailman/listinfo/discuss
Jose-Marcio.Martins@ensmp.fr wrote:
this will have the secondary effect of disallowing you to see web pages on those sites. E.g., you you define at your hosts file : spammer.com, you can't no more access the URL http://spammer.com/index.html, as this will resolve to 127.0.0.2 (e.g.).
In theory he could define spammer.com.a.surbl.test 127.0.0.2 and use a.surbl.test like say sc.surbl.org minus TXT records.
I'm not sure about the performance effects on small systems, my /etc/hosts is rather small (some "doubleclick" entries).
Bye, Frank
-
David Coulson -
Frank Ellermann -
Jeff Chan -
Jeff Taylor -
Jose-Marcio.Martins＠ensmp.fr