-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign up flow blocked for some email addresses #1135
Comments
Not recent, no, but multiple signups from the same email have been heavily limited for the best part of a year now. |
@tomhughes do you have any recommendations? The reason we use aliases is to stay on top of the feedback our mappers receive by ensuring it goes to one inbox. E.g. If we gave a range of emails, could they be put on an allowlist? |
Well if it was on a meta domain then I could whitelist it as we did for mapbuilder but I can't really whitelist gmail. What I need is either an email domain or an IP address range that is reasonably specific that I can then whitelist. |
Ok thank you. I'll look into it and reply back. |
@tomhughes if you are able to add @meta.com to an allow list, that would be much appreciated. We'll make sure all new organization editing accounts are created on this domain. We'll use the account to track any feedback that the community is providing. Thank you! |
You're going to be using a single account with plus addressing on meta.com is that correct? |
Yes, that's correct @tomhughes |
That should be allow listed now. |
Much appreciated. Thank you @tomhughes! |
As I'm sure you know, Meta has paid editors that map in OSM. We have a consistent username and email format we use to keep track of these accounts e.g. username: xyzxxx and email: [email protected]. Our team has been encountering errors on sign up recently when they try to create these accounts.
Is there a recent change that is causing these signups to be blocked? Is this an vandalism initiative? We can adjust accordingly, but wanted to confirm.
Thank you!
The text was updated successfully, but these errors were encountered: