One one of my dasBlog sites that was built before Akismet was supported, I accientally allowed for pingbacks to be tracked.
Ping backs are supposed to happen between blogs whenver you link to another blog article.
It’s really a great idea! If you are reading a blog post, you might see a list of 4 ping backs at the end. These URLs are the locations of other blog articles that reference the article you are reading, so you might want to check some of those out to get those authors poing of view on whatever topic is being discussed.
But, of course, spammers ruin it for everyone.
Yesterday I got 18,000 pingbacks from sites selling prescription drugs in a matter of a hour or 2.
So I turned off ping backs, but that left me with a ton of spam to clean up.
Lucky for me, someone else has already run into this, and built a tool for stripping it out!
Really nice! The only problem I found was that it didn’t report issues with my config file (I had a bad character in there). Actually, it WOULD report them, but would immediately begin processing the files (with no patterns to match against) so you couldn’t tell that it was reporting it.
So if you run into a problem with this tool, try putting in a bad content path. This was throw an exception and you will have time to read any debug info in the command terminal indicating if there was a problem with your config file earlier in the process.
After I fixed this issue, it worked great!