It seems in a recent update, new signup with same email including a + to represent a new email isnt allowed. my system is highly dependent on it. how to enable it again? for example if I have already signup with email@gmail.com, I cant signup with email+1@gmail.com btw I am testing this with rest api [image] also, I dont have this option checked: [image]

[image] hosna: yes I can see the normalized email is blocked. In this case we almost definitely block subaddresses of blocked addresses regardless of the setting as an anti-griefing measure since the normalisation option is not the default. [image] hosna: where should I check “Only show overridden” in settings. But now I suspect we don’t need to worry about that.

I believe that’s the normalize emails admin setting: :+1: [image] Edit: I did not see that edit before I posted. :slight_smile:

[image] JammyDodger: I believe that’s the normalize emails admin setting: :+1: yes it is already disabled for me

I can’t duplicate this on try.discourse.org. Can you sign up from the normal UI with this email? Also, can you double check the +1 email wasn’t already used for a signup?

yes normal UI is ok. rest api is not ok.

I did exactly the same and could not duplicate the problem on the latest code running live - it behaved as expected with the normalize emails setting disabled: [image] Can you show the output of these from the rails console: [1] pry(main)> SiteSetting.normalize_emails [2] pry(main)> User.find_by_email('YOURUSERNAME@gmail.com').username [3] pry(main)> User.find_by_email('YOURUSERNAME+1@gmail.com').username Also, what version of Discourse are you on? I might also double check you’re hitting your production site and not your test one (or vice versa).

[image] Michael Brown: Also, what version of Discourse are you on? I updated right now [image] Michael Brown: Can you show the output of these from the rails console: here it is [image]

What do these translate to? [image] (and can you copy/paste them here) I should have asked this first :man_facepalming:

[image] “Primary email مجاز نیست.” it is a translation for user.email.blocked

hmmm it seems the normalized email is blocked. :thinking: I mean if email@gmail.com is blocked, then email+1@gmail.com is blocked too. it is wierd to me when I have not normalized email option selected.

That’s why I should have asked first instead of assuming it was “already taken” :rofl: What are your overridden settings in the email and user categories? Have you blocked that email address, or, say, the Gmail domain?

New signup with old email including + doesnt work in rest API

Product Support

JammyDodger June 7, 2023, 8:47pm 2

I believe that’s the normalize emails admin setting:

Edit: I did not see that edit before I posted.

Topic		Replies	Views
Text after + in an email address being disregarded in uniqueness check Product Support email , signup	3	200	March 26, 2025
Suggestion: Wildcard Block Email Address Feature	32	5112	December 7, 2021
Enabling e-mail normalization by default Announcements	3	473	September 27, 2025
Registration-spammed forum with aliased email addresses despite "normalize_emails" enabled Product Support spam	3	367	December 21, 2024
Issue with Signing up - primary email has already been taken Product Support email , invites	1	322	May 13, 2024

New signup with old email including + doesnt work in rest API

Related topics