Many ISPs, including mine, are having major problems with comment spam straining their servers. I can report that two simple fixes have blocked a HUGE fraction of my MT 2.6x comment spam: closed comments on all posts more than a month old, using the close comments plugin, and I rewrote my comment templates to require users to preview comments once before posting. Combined with my usual MT-Blackllist list, the results are dramatic. Not 100% blockage, but at least 97% of the stuff that used to get through isn't. And much of what remains is weird spam — links to non-existent web sites … which I presume are being groomed for sale once they get high googleranks. (And lots of these are in the .de TLD for some odd reason.)
A Personal Blog
by Michael Froomkin
Laurie Silvers & Mitchell Rubenstein Distinguished Professor of Law
University of Miami School of Law
My Publications | e-mail
All opinions on this blog are those of the author(s) and not their employer(s) unelss otherwise specified.
Who Reads Discourse.net?
Readers describe themselves.
Please join in.Reader Map
Recent Comments
- And the Winner Is Boring – Discourse.netDiscourse.net on Yet Another Florida Voting Disaster
- Guilletmogomezvillafan on Brad DeLong Writes a Letter About a Suspected War Criminal on His Campus
- how long does payomatic transition take to adifferent bank - prohowquestion on Why Does It Take Two Days for an E-Payment to Move Between Two Big US Banks?
- Michael Froomkin on Thank You Gov. Ron DeSantis!
- Thomas Locke on Thank You Gov. Ron DeSantis!
Subscribe to Blog via Email
One other thing to consider: rename your comments script to mt-comment.cgi. You have to make some changes in a few forms, but spammers looking for “mt-comments.cgi” won’t find it.