SES Send Mail Issue

0

My SES account was moved from sandbox to production some time ago. Unfortunately, that production machine has since been shut down and deleted while I re-develop the system. So, I'm sending emails from the development machine (dev.qwikfoto.com). However, all emails I send now (from the development machine) to unverified addresses draw the following error,

"Expected response code "250" but got code "554", with message "554 Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: (email address)".

When I requested the account be moved to Production, I specified the Web URL as "www.qwikfoto.com". Does this have any bearing on the problem? Also, why is it using the region US-EAST-1 instead of ap-southeast-2?

3 Answers
1

Hello, Sorry to hear about the issues you are experienceing in sending emails with SES.

The 554 error code you're receiving suggests that the email address you're attempting to send emails with has not been verified, at least in US-EAST-1. Here is a link with more description to the corresponding error code - Amazon SES SMTP issues.

Amazon SES is a regional service, so ensure you have created and verified the email address identity you wish to use in the region you want the SES service to operate from. Here are links to creating, verifying and troubleshooting an email address identity.

To your question, "When I requested the account be moved to Production, I specified the Web URL as "www.qwikfoto.com". Does this have any bearing on the problem?"

  • The information you provide when requesting production access is used to verify your use case for email deliverability and help prevent fraud and abuse. Here is an an additional note regarding production access request for Amazon SES. I noticed the Website URL you provided was inaccessible (at least for me).

If your email address identity has already been verified and your received approval for production use from AWS, I would double-check which region both were approved for:

  1. Log into the AWS console
  2. Select US-EAST-1 region
  3. Navigate to the Amazon SES service console
  4. On the Account Dashboard page, toggle between US-EAST-1 and AP-SOUTHEAST-2 to see if there is a yellow banner at the top informing you that you're in the Sandbox environment for that region. This will help verify which region you have production access in
  5. Next, go to Verified Identities (under Configuration dropdown) on the leftside panel
  6. Toggle between US-EAST-1 and AP-SOUTHEAST-2 to see if there are any discrepancies on where your email address identity is verified

This should be a good starting point to troubleshoot.

AWS
answered 7 months ago
  • I don’t have production access to region US-east-1. So, I have request production access to every region in the world? Nowhere did it say that.

0

@Paul - "I don’t have production access to region US-east-1. So, I have request production access to every region in the world? Nowhere did it say that."

Amazon SES is not global (every region), rather it's a regional service. So verified identities and production access is limited to the region in which your email address identity was verified and where you requested production access from. Because you stated that you received a "554 Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: (email address)", yet you ask why not AP-SOUTHEAST-2, the guidance in my prior answer should help validate which region you have both your email address identity verified and production access approved.

Both your verified identities and production access need to be in the same region.

AWS
answered 7 months ago
0

The domain identity "qwikfoto.com" is verified for regions ap-southeast-2 and us-east-1 as is my email identity. I think my SES setup is ok. When I try sending test emails using AWS Cloud Shell, I can happily send emails to anyone without any problems. When I use the Laravel SES Mailable interface, I get the "554 Message rejected" error. I'm using the same credentials for both and the same domain identity "qwikfoto.com". The config settings look ok. What else haven't I considered? BTW, I shutdown www.qwikfoto.com some time ago. I'm currently developing on dev.qwikfoto.com.

Cheers,

Paul
answered 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions