<p>I'm not sure that I agree with your analysis.  At a minimum maybe it's a <a href="http://feedback.craftcms.com/forums/285221-feature-requests" rel="nofollow">feature request</a> with a config setting to change the behavior.</p>

<p>But if you're really concerned about the behavior, you can currently set the <a href="https://craftcms.com/docs/config-settings#purgePendingUsersDuration" rel="nofollow">purgePendingUsersDuration</a> config setting to something like 24 hours so they don't hang around very long.</p>

CC BY-SA 3.0
2016-06-29T18:31:56.073Z
Yeah, I figured it was kind of specific to my particular need. Didn't know about `purgePendingUsersDuration`, which will definitely help though. If I need to go further, I'll file a feature request.
Tim Kelty
CC BY-SA 3.0
2016-06-29T17:29:13.700Z
2016-06-29T17:29:13.700Z
Brad Bell
<p><code>craft()-&gt;users-&gt;saveUser</code> seems to check email for uniqueness across ALL users, not just verified ones.</p>

<p>It seems like it should only check against verified ones to me.</p>

<p>Example:</p>

<ul>
<li>boob@gmail.com registers (only he fat fingered and it was supposed to be bob@gmail.com). Bob never gets his verification email, but that's his fault. Boob gets one, doesn't know what it is and ignores it.</li>
<li>Later, the real boob@gmail.com now tries to register, but he can't because boob@gmail.com is sitting there unverified, squatting on that email.</li>
</ul>

<p>At this point you could have an option to resend the activation code, however once boob@gmail.com get that and verifies it, his account will now be the account that the other guy actually signed up for, so if you're doing stuff with accounts, it might have data associated with it you don't want.</p>

<users><emails><registration>
Unverified emails blocking user registration
# Unverified emails blocking user registration

(Asked by: username_0 on 2016-06-29)

`craft()->users->saveUser` seems to check email for uniqueness across ALL users, not just verified ones.

It seems like it should only check against verified ones to me.

Example:

* boob@gmail.com registers (only he fat fingered and it was supposed to be bob@gmail.com). Bob never gets his verification email, but that's his fault. Boob gets one, doesn't know what it is and ignores it.
* Later, the real boob@gmail.com now tries to register, but he can't because boob@gmail.com is sitting there unverified, squatting on that email.

At this point you could have an option to resend the activation code, however once boob@gmail.com get that and verifies it, his account will now be the account that the other guy actually signed up for, so if you're doing stuff with accounts, it might have data associated with it you don't want.

**Tags:** users, emails, registration

---

## 1 answers

### Answer by username_1 on 2016-06-29. Score: 3 | Accepted answer

I'm not sure that I agree with your analysis. At a minimum maybe it's a [feature request](http://feedback.craftcms.com/forums/285221-feature-requests) with a config setting to change the behavior.

But if you're really concerned about the behavior, you can currently set the [purgePendingUsersDuration](https://craftcms.com/docs/config-settings#purgePendingUsersDuration) config setting to something like 24 hours so they don't hang around very long.

> **Comments:**
> **username_0**: Yeah, I figured it was kind of specific to my particular need. Didn't know about `purgePendingUsersDuration`, which will definitely help though. If I need to go further, I'll file a feature request.  

---

