Even while I’ve been off and on this blog for the past few days (more off than on, it seems at times), I’ve been pleased by the relative dearth of comment and trackback spam that’s made it through. Indeed, aside from nine trackbacks that sneaked past last night (and are now blocked in several ways), things have stayed pretty clean here.
That said, MT Blacklist has been very hard at work. A number of items were forced-moderation (which means you never saw them, and I could quietly delete them when I got to it). Many others were just plain gunned down when they tried cross the wire — including several hundred from that guy who does broad pr0n attacks (the subdomain blocking worked great, and I’ve put the other two subdomains I missed into the blacklist, so they won’t get through again). (And, indeed, I can see in the log his bots are still out there trying it. Zap!)
Since September, when I installed MT3 and MT-BL2, the thing has blocked 4,320 comment and trackback spams, and sent to moderation another 456 (of which only a dozen or so were legit posts). To me, that’s a huge benefit, and praise be unto Jay Allen for this incredibly powerful and useful product.
(And, by the way, the master blacklist is beginning to be updated again. Huzzah! And it’s timely enough that the spammer I mentioned above would have been blocked today one my blacklist was auto-updated.)
All that said, there’s a critical MT-Blacklist bug (in v.2, the MT3x version) that’s been reported: under undefined but evidently rare circumstances, deleting a blog in an installation set up with MT-BL will delete a second blog in that installation. Eep! Jay’s on top of it, so just pass the word. (Deleting blogs is not a common thing, but I’ve been considering archiving and deleting some of the older blogs here, just on GPs, and am glad that I didn’t …)
And, in keeping with that, before you go doing major blog maintenance like that, it’s a good idea to back up your blogs. All of them. In fact, it’s a good idea to just plain ol’ do so on a regular basis.