So, I set requiresUniqueEmail = true on the ASPNetMembershipProvider, and everithing was right until I create my second portal on the same instance and realize that when I wanted to create a new user on the second portal with an email of a user of the first portal it runs the validation and tell me another user is using that email, but there is no user on the second portal... so I need to figure out if there is a way to tell the instance that checks unique emails per portal.....

Thanks

mmm... well.. I guess I will just set the requrieEmail thing to false, and make the validation myself... I was in love with dotnetnuke.. until this unusefull feature came out.. :(

yeah.. I know... the worst feature ever for me... but well it is more acceptable that you change your username because supposely someone took it already... but your email?? That was just illarious... Considering that my end users do not known and they dont have to know that my 2 portals or 3 portals or 4 portals are part of the same dotnetnuke instance...