• As noted in another place here on the boards, comment spam of blogs has started gaining speed these last few days (like here). I thought it’d be a good idea to have a place to report IP addresses and the likes so that we can combat this thing in some way.

Viewing 11 replies - 1 through 11 (of 11 total)
  • My blog got spammed. I think it happened today. I was so taken aback, I simply deleted the comment without investigating further. I’m not sure an IP address approach is that worthwhile. The referer stats I have via my Tiki Wiki sometimes show no IP address or domain name where there should be one, just a date and the number of visits. I am thinking if this happens again I’ll have to turn commenting off.
    As a feature suggestion, it would be extremely useful to be able to select/filter a view of posts that have comments. Right now I have to manually scan the screens or go into phpMyAdmin and run a query.
    Now, the funny thing is about this comment spam, I don’t allow HTML tags in the comment field, but the comment looked as though it was coded (the comments looked like hyperlinks). I tested the exclusion of HTML in comments myself, and they are excluded, so I’m not sure what to make of this attack.
    David Mattison (http://www.davidmattison.ca/wordpress)

    I’m curious to know how to implement the various blacklist.txt these sites mention. In other words, how do I actually incorporate blacklists into my site? (PHP neophyte here.)

    I found another comment spam from, I’m sure, the same individual or bot at IP address 61.181.5.40. The comment was left on September 2, 2003 at 8:53 am in a short post dated August 28, 2003. I’ve deleted the comment. The comment field includes an encoded mailto: URL and an HTTP: URL, both of which should be impossible according to my settings since no HTML is allowed. The URL field was used to also include a URL to the site itself.
    According to http://www.zoneedit.com/whois.html?zone=61.181.5.40 this IP address is part of a block registered to the “CHINANET Tianjin province network”, Beijing, China.
    Talk about your international incident!
    It’s critical that WordPress work out or provide some third-party solution ASAP, or I predict not only WordPress but every other blog that has open commenting systems will come crashing down as this problem escalates.

    If you had a webhoster who gave you the ability to block IP ranges, this wouldn’t be an issue.
    I’m not going to spam my web hosting company but I have dont this for many people in the past.

    Feedster has a place to report comment spam:
    http://feedster.com/commentspam.php

    The Feedster link right above your post has an IP blacklist… Feedster has a simple URL API for reporting spam comments too. It would be really easy to add this as a link to the comments list.

    I think a simple solution would be to hold comments in an ‘unapproved’ state until approved either through a simple password-protected hyperlink from an email, or via the admin screen.
    -Garth
    (www.garth.org – been spammed four times by 12.231.63.199)

    @garth: this is what my hack will allow.
    Bye, Mike (found his first spam today in his blog, coming from 61.181.5.38)

    asfsfd

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Blog spammer’ is closed to new replies.