When Will TypePad Sort Out *Their* Spam Problem? - Part 2
I posted an article on Monday about the problems I'm having with spam attacks on my blog and what Typepad are doing, or rather are not doing, to solve the problem. I hadn't planned on posting a follow-up to the post but seeing as nobody from Typepad has read the post (or at least they haven't commented) and after what has happened overnight I think I need to post a follow-up.
Overnight I was attacked by a comment spammer using the same IP addressto spam me about 50 times over a period of 5 hours. Now I doubt I'm the only TypePad subscriber being spammed by the spammer (although I could be wrong) so why haven't TypePad got a system in place to recognise when a spam attack is in progress. Whilst this is just a major inconvenience and thankfully they don't happen regularly, what happened next really annoyed me.
Late last night I reported a few spammers to TypePad including this one...
TypePad responded at 23:57 BST telling me that they had been banned globally, presumably using the approach I mentioned on Monday (a combination of factors including "URL, email address, and content submitted with the comment").
At 02:11 BST, 2 hours after the previous spams, I received this spam...
Notice anything similar? Yep, the spammer who was banned globally is still allowed to spam TypePad blogs using the same IP address and email address.
In my latest ticket I've mentioned that this person has been able to continue spamming and it will be interesting to see what their reply is.