-
Notifications
You must be signed in to change notification settings - Fork 330
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
Not receiving verification email #2775
Comments
Same problem here. Doublechecked it is not in spam. Tried both with a gmail address and another provider (gandi). None work. |
Same here. Also tried resend - confirm that the web page is sending a POST to https://galaxy.ansible.com/api/v1/emails/verification/ containing a JSON like so and is getting 200 success
|
I have the same problem |
Same here. Multiple attempts and checked but no email received. |
Same. :( |
Same here. |
Same here |
Same issue. confirmed with mail admin they are not seeing anything hit our mail servers/spam filters. |
Same here |
Same here. Will anyone look into this? |
Same here... |
This issue has been pinged in the Ansible core meeting which brought it to the attention of the Galaxy team which is investigating. TBH somehow it seems it was missed. I don't think it was clear that this blocked use of Galaxy by contributors in various important ways. Hopefully there will be some progress. |
Thanks for the update, @mikedlr! |
@mikedlr Thanks for the update. And yes, it's important for contributors. |
@mikedlr thank you for the update :) Is there a way to delete old namesspaces also? |
Email is now working, thanks for the patience on this. |
Bug Report
SUMMARY
Have been trying to verify the email but not receiving the email.
STEPS TO REPRODUCE
Go to profile and click resend verification. Not email receiving including spam box.
EXPECTED RESULTS
Should get a verification email.
ACTUAL RESULTS
Nothing happened. There is a popup box that says "Sending Verification We've sent your verification code to to [email protected]"
There is also a typo in the notification message. A double "to".
The text was updated successfully, but these errors were encountered: