Reaching milestones for SpamAssassin and DNS editor

There are several side projects going on right now. One of the completed “milestones” is the SpamAssassin configurator that was finalized today. For a few hours ago, we’ve started to work on a DNS editor, that makes it possible to update entries into two of our master DNS-servers. This is another milestone as much of the changes today are being made manually with regular zone files. We’ll still go that way, but in a near future, it will be possible to update records live. This work might speed up our DNS Blacklist a bit, which might give us a chance to live update both the primary master server and the second backup without hourly reloading. The DNS API was besides of this not even planned – it was “just a test” to see if it was possible and suddenly, there was an almost complete interface for it in the API.

Any plugins?

Yes, there was recently a minor release of the DNSBL WordPress-plugin also (not a milestone), but the release was too small to set up a whole post for it. But here goes, 2.0.6 gave us one minor update, as we had problems with blacklisted users requesting for delisting in the delisting-page comment fields. Those fields are less checked than the support mailbox, so the patch was based on removing comment abilities in the removal page as an option in the admin configuration.

  • [DNSBLWP-49] – comments_open has a problem that might open for comments again, if other plugins has it disabled

DNSBL for WordPress 2.0.5/2.0.6 CHANGELOG

This also includes 2.0.3 and 2.0.4 as they only contained minor fixes

2.0.6

Minor fix for open/closed comments on delisting page

2.0.5

  • [DNSBLWP-42] – duplicate () in link (readme.txt)
  • [DNSBLWP-47] – Ability to disable comments on removal page
  • [DNSBLWP-48] – Make notice on “comments disabled”-page, that admins are blacklisted (if they are)

2.0.4

Translation update (text domain fixed)

2.0.3

Text and translation