# Consequences of not validating email addresses

**URL:** <https://meta.discourse.org/t/consequences-of-not-validating-email-addresses/40132>\
**Category:** Product Support\
**Created:** [25.Февраль.2016 00:04:10 UTC](https://meta.discourse.org/t/consequences-of-not-validating-email-addresses/40132 "2016-02-25T00:04:10Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [25.Февраль.2016 00:04:11 UTC](https://meta.discourse.org/t/consequences-of-not-validating-email-addresses/40132/1 "2016-02-25T00:04:11Z")

</div>

I’m using Discourse with SSO. The guidelines say:

> [@Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso)](https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045/1):
>
> ⚠ Discourse uses emails to map external users to Discourse users, and assumes that external emails are secure. IF YOU DO NOT VALIDATE EMAIL ADDRESSES BEFORE SENDING THEM TO DISCOURSE, YOUR SITE WILL BE EXTREMELY VULNERABLE!
> 
> Alternatively, if you insist on sending unvalidated emails BE SURE to set require\_activation=true, this will force all emails to be validated by Discourse.

I’m tempted to 🔥 open the gates of hell 🔥 and not send `require_activation=true` although I’m not validating addresses. There are good reasons why I cannot force email address validation in my SSO provider, and I’d really like my users to have a fully set-up Discourse account with a single click.

What terrible consequences will this have?

- Users can sign up with a developer email address and become admins.  
**Solution:** All developer addresses are taken already.
- I make spam sign-ups easier.  
**Solution:** Registration on the parent site is only open for a limited amout of time and to a limited set of people.
- If I ever disable SSO, password recovery mails go to the wrong address.  
**Solution:** I will never disable SSO. Instead, the Discourse instance will be 💣 when it is no longer needed.
- Users can sign up with addresses they do not own and spam the owner of the address.  
**Workaround:** Not a new problem, they can already do that on the parent site. It has never been a problem.
- Users can sign up with incorrect addresses accidentally and miss important emails.  
**Workaround:** Missing emails from the parent site is probably the bigger problem for these users 😉

I know that I’m leaving the safe, established path if I go ahead. Still, does anyone see a significant problem with this?

---

_[View the full topic](https://meta.discourse.org/t/consequences-of-not-validating-email-addresses/40132)._
