I help administer a site that has over 13,000 registered users.  When we first set up the site, we left the "requiresUniqueEmail" set to false so we could use dummy accounts for testing purposes.

Now that the site is mature and has a large user-base we'd like to cut down on the users that register a new account everytime they forget what their password is (and it happens a lot).  The problem is that we know there are a number of accounts with duplicate email addresses.  Although we try to manually address these duplicates, the number could still be anywhere from 100 accounts to 1000.

If we update web.config now and set requiresUniqueEmail="true", what type of issues are we looking at?  I have a test server I'm going to try this out on first, that has a copy of the live website database on it (duplicate accounts and all), but I wanted to get some feedback from the community first.  Has anyone else had experience with this? Were you able to make the change?

And what happens to the user accounts with duplicates?  Does the logic only get used when creating a new account?

Thanks for any help!

-Xavier

I tried this and it seems that when you log in as an existing user with a duplicate email it throws an error and does not let you log in. So I am working on a script to identify all duplicates and will decide how to handle it first, then flick the switch.. I really like the "Forgotten PW by email" - in 5 years of using DNN I had no idea that even existed - I think this setting should be TRUE on the default installations...

---

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

Thanks Alex, I added my 2cents..

---

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players