-
Notifications
You must be signed in to change notification settings - Fork 234
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
Users not created #55
Comments
Please disregard the second error, it was on our end :) |
I'm having the same error. CloudWatch reports:
any thoughts? |
For what it's worth -- I just tested signing up an email from an SES verified domain, and it looks like the registration worked. So it seems the problem is that somewhere along the way only emails from SES verified domains are acceptable... Has this script always worked like this? I'm a first time user |
So... as it turns out the particular AWS SES account I'm using is still in the SES "sandbox," which I forgot about. @sg0894074 perhaps this is our problem? http://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html |
Yes, that seems to be my problem too. I was not aware of this limitation by default. Thanks! From: aggied [mailto:[email protected]] So... as it turns out the particular AWS SES account I'm using is still in the SES "sandbox," which I forgot about. @sg0894074https://github.com/sg0894074 perhaps this is our problem? http://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html — |
After installing, no users were able to sign up.
Page displays 'user Not created', when looking at the CloudWatch logs for the LambdAuthCreateUser function, I found this error:
2016-10-05T18:15:38.131Z b72f1452-8b27-11e6-a0ef-3f70cb5b1481
{ "errorMessage": "Error in sendVerificationEmail: MessageRejected: Email address is not verified. The following identities failed the check in region US-WEST-2: [email protected]"}
Recipients of the verification email, that is the end users, should not have to be registered on SES for it to send them email.
When trying with a registered account, it worked the first time, then the second one I got this other error:
2016-10-05T18:19:17.803Z 3a41c422-8b28-11e6-969a-41fcce75977a
{"errorMessage": "Error in sendVerificationEmail: InvalidParameterValue: Domain ends with dot"}
This user had the same domain as I did and had entered its address correctly
The text was updated successfully, but these errors were encountered: