Email address is not verified (AWS SES) - amazon-web-services

Question

I want to use Amazon's Simple Email Service to send emails.
I verified my domain as well as the email address I want to send from.
For both it says verified.
Now when I use the Send Test Email from the AWS Console to send a test email to myemail#outlook.com, I only get the error message:
Email address is not verified. The following identities failed the
check in region EU-WEST-1: myemail#outlook.com (Request ID:
9fb78de1-2673-11e6-bbbc-5f819fabe4f4)
Now it strikes me because it says myemail#outlook.com was not verified but I tried to send from admin#mydomain.example. The Send Test Email Dialog even forces you to use an email which already is registered.
How can this issue be resolved? Did I miss anything?

Answer 1

When your SES account is in "sandbox" mode, you can:
Only send from verified domains and email addressed, and
Only send to verified domains and email addresses
In order to send to anyone else, you must move your account out of sandbox mode by contacting AWS support and requesting it:
https://docs.aws.amazon.com/console/ses/sandbox

Answer 2

In my case I needed to verify the email again in the region where it failed. You can try to change your region in the top right then you have click again "Verify a New Email Address"

Answer 3

If the email is already verified and you're out of the SES Sandbox, check that you've the correct AWS region for the SMTP server. I was trying to connect to email-smtp.eu-west-1.amazonaws.com when my SMTP credential was for the email-smtp.us-east-1.amazonaws.com server.

Answer 4

#Matt Houser has already answered the questions but I am adding a screenshot from June, 2020 that explains what he said.

Answer 5

Make sure
You add your email to ses and get verified.
You enable the Production mode for your account.

Answer 6

Make sure
-You have submitted your case request to support customer and explain in what purposes confirm it for to 24 maybe they will ask you about some additional information about your application

Answer 7

I had this issue. I verified domain and email, even the DKIM settings was verified.
But still getting this message :
Email address is not verified. The following identities failed the check in region {aws_region}: {email}
I added SourceArn as parameter for sendEmail than get this message :
User `arn:aws:iam::{account_id}:user/{username}' is not authorized to perform `ses:SendEmail' on resource `arn:aws:ses:{aws_region:{account_id}:identity/{email}'
After 2 days I found out the I was using wrong IAM user !

Answer 8

Be aware the Verified Identities are actually case sensitive. I was wondering why I got such error, even though my email was verified and out of SandBox.

Answer 9

Problem
Confusion comes from the fact that your e-mail address shows as "Verified" in AWS SES -> Verified identities and still not working.
In fact, there are two verification:
DKIM one (which makes the field tick green and verified)
E-mail address verification
That means you must use the e-mail address which you have access to (mailbox) in order to click in the verification link.
Without clicking the link in the e-mail, your identity may be verified but you'll still see the error everywhere.
Simple solution using AWS WorkMail
I am using AWS WorkMail but I've created a new Group instead of another WorkMail account, then added my personal account to it, received a verification e-mail and managed to get: "noreply#..." working.

Answer 10

In my case, I wanted to email to the same verify email.
So, I verified my email by DKIM as #Greg Wozniak mentioned. I saw the field tick green and verified:
But I was still seeing:
Email address is not verified. The following identities failed the check in region...
The solution in my case was to add this function in the code:
def verify_email_identity():
ses_client = boto3.client("ses", region_name="us-east-1")
response = ses_client.verify_email_identity(
# Email address that will receive the email
# In my case the same email address
# that was verified on Amazon SES
EmailAddress="receipientemail#gmail.com"
)
print(response)
Taken from this webside
So, I received a new email to verify the recipient email address. After verify the recipient email address by clicking in the link sent by Amazon SES. I was able to send the email with this code:
client = boto3.client('ses',region_name="us-east-1")
# Try to send the email.
try:
#Provide the contents of the email.
response = client.send_email(
Destination={
'ToAddresses': [
receipientemail#gmail.com,
],
},
Message={
'Body': {
'Html': {
'Charset': "UTF-8",
'Data': "Test",
},
},
'Subject': {
'Charset': "UTF-8",
'Data': "Test",
},
},
Source=receipientemail#gmail.com,
)
# Display an error if something goes wrong.
except ClientError as e:
print(e.response['Error']['Message'])
else:
print("Email sent! Message ID:"),
print(response['MessageId'])

Answer 11

I had verified an email address, and then a few days later my domain. When the domain was fully verified (inc DKIM) I was still getting the 'Email address is not verified' error when trying to send emails to email addresses within my domain, that weren't my specific verified address.
I deleted my verified email address, and re-verified it, and it worked immediately. I could then send domain wide emails, whereas before - I could only send to and from the email I had previously verified.

Answer 12

I was having the same issue a couple minutes ago, although this time I'm working with the SDK in PHP.
I had to double check the SesClient instantiation code.
$SesClient = new SesClient([
'profile' => 'default',
'version' => '2010-12-01',
'region' => 'us-west-2',
]);
I discovered that the region in the instantiation code is us-west-2.
I went back to my console and discovered that SES account was sandboxed in us-east-2 (Ohio).
I implemented the change in the instantiation code like so
$SesClient = new SesClient([
'profile' => 'default',
'version' => '2010-12-01',
'region' => 'us-east-2',
]);
It's working now.

Answer 13

I had this issue and none of the above worked for me. My issue related specifically to sending via python using boro3. I eventually figured out that the system I was working on had a different set of aws credentials stored in the windows system than it did on the Linux subsystem on the same windows machine. The solution was to set both sets of aws credentials to match the appropriate aws account. I add this here just in case anyone has the same issue and, like me, couldn't find an answer.

Answer 14

For me the issue was that I was mismatching cases.
The verified email and the email sent have to match exactly.
test#gmail.com vs Test#gmail.com