[saeedh]

Thanks for the replies pattycake & x9x6. I should have been a bit more specific. The forum gets about 20k+ impressions a day and enough user registrations that administration can't keep up with for a sake of tracking. Tracking is still useless for an individual of the sort, and maybe a little history would help:

- He was banned
- He made another account and banned and the process repeated a couple of times
- He understood that people figure out who he is easily so got impatient and opened a new forum of his own and got users to go etc, which I didn't care
- The idea of his didn't work out as the major female user base didn't bother going over
- He's returned and keeps making new accounts.

The guy knows the technical side of matters enough to deal with the aspects like cookies for tracking and so on and I don't care to get in any arms races. Some of the complaints are rather scary so I would like to just be rid of most of the problem by banning a large demographic which I don't care for.

The ban would be ideal (thus depending on hostname) or otherwise a more preferable method of being able to define the register.php to do a hostname lookup of those registering before running table queries and place the user of question in a specific bin. That way I can go ahead and be better off too. This is concerning a freak that I wouldn't be surprised to know is searching google to find ways to keep doing what he's doing. I'd like to take the technical steps before the few abuse departments respond and I'm resorted to take further action in terms of ensuring service providers or where ever he gets access to the service from enforces their TOS clauses concerning online harassment and so on.

I can code but I'd have assumed that there would already be a chunk of code that would not make me read through the vb db structure and code for the registration process to make the hack. (But thanks pattycake for the IB tidbit, it may come in handy)