Release Notes – WP_DNSBL – Version 2.0.7
- [DNSBLWP-60] – False positives shown with fraudbl
The prior weekend our mail server was moved to a completely new place, so we also decided to shut down the old mailserver.
However, the old server contained important files that handled the blacklist functions (methods that automatically updates and changes the zone data in the zone tornevall.org). As this service has been shut down, an update for the DNSBL API has been deployed since we have been unable to rewrite zone data since then.
This also means that all removals from the removal interface should be instant if everything goes as planned (tests has been successful) – and not hourly.
Just remember that even if removals are instant, your blacklisted IP may still be present in caches around the workd, and won’t be updated instantly.
This also includes 2.0.3 and 2.0.4 as they only contained minor fixes
Minor fix for open/closed comments on delisting page
Translation update (text domain fixed)
Text and translation
Currently there’s a few steps left before we can release the new portal system (as shown via the test site at https://www.tornevall.com) and the new portal configurator (Test site located at https://auth.tornevall.com). The old platform for handling DNS Blacklists became deprecated as the development of NetCURL (https://www.netcurl.org) have been highly upgraded to fit other (ecommerce) needs. The behaviour of netcurl is backward compatible, but the DNS blacklist and portal software really needed a facelift anyway.
I’ve been looking for a platform that I can handle easier than the self built, and got stuck into a million of alternatives. However, the forum platform is still there, since there are too many posts and history behind. So those parts can’t be replaced (yet). Besides, if everything goes well, there might be no need of doing so.
So what’s left before a release? Actually, TorneAPI (3.0) is ready to go live and the applications built in the API is also very dynamic. As I proceed more things will be added to it and currently, the big focus is the DNS Blacklist, FraudBL and NETFILTER.
FraudBL is, since june 22, an active resolver. Tornevall Networks has in active for tests and currently we’ve seen a positive result of the activation. More information about bitmasking will in short get updated at http://docs.tornevall.net/x/AoA_/. In short, we will also activate the new default database for dnsbl.tornevall.org.
You can still contact firstname.lastname@example.org for blacklisting support.
For three years ago (june 2013) we decided to remove the substructure opm.tornevall.org, from the DNSBL. Statistics, however, shows that opm are still in use. And in fact traffic seems to increase, from those resolvers. They are therefore reinstated, even if there will be double entries of each blacklisted host.
Our honeypot have also begun to catch e-mail on a new level. Messages containing traces of phishing and fraud will be flagged differently from the regular lookups. This refactoring and migrating to the new system are not finished yet, so bit-flags are not considered yet. However, our new domain for phishing – FraudBL – may be useful here.
And do not forget: As long as the migration is not finished, we will continue remove your blacklisted hosts manually, with as high SLA as possible. In that case, we still use the support address email@example.com
To be continued…