Re-check approved comments for spam
Let’s face it, spam happens. While we’ve made a lot of improvements to our Akismet integration to catch future spam from sullying your comments with links to cheap prescription drugs, it’s possible that some spam might have slipped through in the past.
Don’t worry, we’ve got you covered.
There’s a nifty new option in your moderation page to re-check all of your approved comments for spam with the click of a button.
Just click on the “Re-check For Spam” button and we’ll do the heavy lifting for you, and run all of the comments on your site through Akismet again.
Think of all of the time that will save you. While we do that, you can take some time away from your computer and slow things down. Go relax with a beverage and rest your eyes for a bit. You can read an old-fashioned newspaper (you know, the kind that you can tear), or catch-up with a long-lost friend – after all, IntenseDebate is all about connecting people. 😉
When you get back, head over to your moderation page again. If we’ve found any spam, there will be a notification waiting for you. If there isn’t one, then your site is spam free.
Keep in mind that the more comments you have, the longer it will take for us to re-check them all. If you return to your moderation page while we’re still checking, then the “Re-check For Spam” button will be greyed-out and inactive.
You can learn more about the rest of our moderation tools at support.intensedebate.com/moderation and read our past posts on our moderation options here.
Posted by Michael Koenig in features
5 Comments
RSS feed for comments on this post. TrackBack URI
Sorry, the comment form is closed at this time.
Oh God, why did I click that button? It has already marked more than 500 comments as spam and as I've looked at them none of them looks like spam to me. Bugger.
Sorry to hear that Rafael. We're investigating and I'll let you know hat we find.
Sorry for the delay. Is it possible that those comments were comments that were originally flagged by Akismet? We haven't been able to reproduce this or dig up anything in the code that would have caused this.
Apologies for the hassle!
Maybe, but I can't say for sure.