A user, bvdrie72, reports that after migrating to SSO, 9 email addresses are failing with the error “Validation failed: Primary email is not allowed.” Despite the emails being valid and not existing in Discourse, they are being blocked. Stephen suggests investigating commonalities in the email addresses, such as length or characters. bvdrie72 notes no clear pattern, with most being Gmail accounts and using alphanumeric characters. codinghorror advises checking the “Screened Emails” list in Admin, Logs. bvdrie72 confirms the issue was resolved by approving the emails in the screened list, resolving the SSO error.
We recently moved all users to SSO via our primary site. Out of 50k+ users, all but 9 seem to work fine.
The 9 remaining emails get this error:
Validation failed: Primary email is not allowed.
The email addresses do not exist in discourse and they are valid emails
We are running 2.3.9
Any reason to believe these will suddenly work in 2.4 or 2.5?
Is there anything common to the email addresses? Their length? Any symbols? Unicode characters?
If we can identify why they’re being rejected it should be possible to answer whether the rejection criteria in 2.3.9 has changed since.
Sorry, I had notifications turned off for some reason.
There is nothing consistent or unique about the email addresses.
Check your blocked emails in Admin, Logs, Screened Emails. And remember emails that are too close to the blocked emails (such as superdave versus superdave1) will also be blocked.
I don’t think I would have ever found it but they were in the screened emails list.
I approved them and now it works great.