As of 22 October, we have changed the behaviour of message analyzing.

If a message contains known hosts, discard the message as already listed but reset “deleted”-dates and relist if necessary.

Messages are no longer discarded with a “already listed”. This behaviour was built to save data storage. Data storage is a problem, but we have to live with that even if some cases is automatically solved by our orphan-cleaner (DNSBL-46). So, for each message found as “already listed”, we are incrementing the hostcount. This means that, the more hits from a server the harder rules are applied on the host.

Source: DNSBL-54

It has been alive for a while, but since we’re starting on v5.0.3 today, here’s also the official release notes for DNSBL 5.0.2

Release Notes – Tornevall Networks DNSBL Project – Version EP-DNSBL-5.0.2

Bugs

• [DNSBL-27] – When extended information is active and deleted items are shown
• [DNSBL-47] – Undefined indexes in curl removal tests
• [DNSBL-51] – API removal allows multiple removals on delisted address and adds penalty if more than one request is sent

Task

• [DNSBL-26] – Removal tool via http
• [DNSBL-30] – Permanent deletion of local addresses
• [DNSBL-32] – Need navbar for DNSBL-web
• [DNSBL-36] – Removal penalties for returning hosts
• [DNSBL-37] – Penalty timer reset after 180 days
• [DNSBL-38] – Penalty timer should show up on delisting-homepage
• [DNSBL-39] – Release of PenaltyBL
• [DNSBL-44] – Purge host instead of delist in API