DNSBL Chile, created in 2011, appears to be a Chilean homegrown effort to tackle spamblocking from a local perspective. As they explain on their website: "Existing DNSBL services aim to block spam based on the type and origin affecting certain types of user. Chilean spam is generally ignored by these DNSBLs, mainly because of the language barrier. This raises the need for a specific DNSBL for Chile, which is able to investigate cases of spam in South-American Spanish."
The DNSBL zone is just "dnsblchile.org" and they report a few different types of responses: 127.0.0.2 and 127.0.0.3 for "verified spam sources," 127.0.0.5 for "verified scam sources," and 127.0.0.10 and 127.0.0.11 for DUL/PBL-like dynamic/"should not be running an MTA" entries.
I don't know much about this list in particular but it's always nice to see somebody attempt to address a previously segment or region's spam problem. If you have any thoughts or details around this list, don't hesitate to drop me a line.
(Crappy translation above courtesy of my high school Spanish + a little help from Google Translate.)
All about DNSBLs, aka blocklists/blacklists // Since 2001 // Published by Al Iverson
| Thanks for visiting! Remember that nowadays, (most) blocklists don't usually govern deliverability and inbox placement on their own. Want to learn more about email marketing best practices, email technology, and deliverability troubleshooting? Then you'll want to check out my other site, Spam Resource. |
Status of APEWS: ????
Long-standing (though not very accurate) blocking list APEWS seemed to be down for the count. Their website at www.apews.org has been down since March 15th, according to David Ritz.
My recommendation to mail administrators is to stop using APEWS. But then again, was anybody using APEWS recently, anyway?
For history's sake, here's a link to the article I published long ago, explaining what to do if you find yourself listed by APEWS.
APEWS was previously down for three weeks in August, 2010.
Update: APEWS appears to have returned somewhere around May 1st, 2013.
It goes down, it comes back up, it goes down again, it comes back up again. At this point I think we'll just call it a status of "?????"
My recommendation to mail administrators is to stop using APEWS. But then again, was anybody using APEWS recently, anyway?
For history's sake, here's a link to the article I published long ago, explaining what to do if you find yourself listed by APEWS.
APEWS was previously down for three weeks in August, 2010.
Update: APEWS appears to have returned somewhere around May 1st, 2013.
It goes down, it comes back up, it goes down again, it comes back up again. At this point I think we'll just call it a status of "?????"
Status of spamtrap.trblspam.com: DEAD
The DNSBL spamtrap.trblspam.com appears to have gone offline as of April 2, 2013. It appears to have been created in early 2011 by somebody known as "Tom from TRBL," whom I observed participating in various email discussion lists. I've emailed Tom and will update this page if I receive any further details.
I recommend removing spamtrap.trblspam.com from any blocklist checking you're doing. Any time a list is shut down, there's a chance that they will end up putting in a wildcard DNS record, which ends up effectively "listing the world" and causing problems for any receiving sites who still have that DNSBL configured in their mail server configuration.
(Thanks to Martijn Grooten for the heads up.)
I recommend removing spamtrap.trblspam.com from any blocklist checking you're doing. Any time a list is shut down, there's a chance that they will end up putting in a wildcard DNS record, which ends up effectively "listing the world" and causing problems for any receiving sites who still have that DNSBL configured in their mail server configuration.
(Thanks to Martijn Grooten for the heads up.)
Subscribe to:
Posts (Atom)