I have all users in our portal set to be verified, but recently we've had an influx of bogus new user registrations.  Is it possible to A) Not allow another user to register another name, if there email address is already attached to another account, and B) Lookup the IP address to which a user registered from, so that if a given ip is causing problems, I can filter them from the server?

TIA

I think the authorization codes are given sequentially for each new person who registers.  So if a user, uses his real e-mail address to register he just has to look at the authorization code then register a user with a fake address and use the next authorization code.

DNN either should give random authorization codes and/or deny registrations from e-mails that get a bounce-back.