Home > Software design >  AWS SES SMTP- error 554 after switching to new server (and IP). NOT IN sandbox mode
AWS SES SMTP- error 554 after switching to new server (and IP). NOT IN sandbox mode

Time:10-11

I'm having an issue with AWS SES after switching to a new server. I've been using the service (SES) for a few years and everything was fine - I'm not in a sandbox mode. But just recently I switched to a new server and problems began. I'm getting these types of errors when I'm trying to send a new email:

An error occurred while trying to deliver the mail to the following recipients:
[email protected]


Reporting-MTA: dns; a7-18.smtp-out.eu-west-1.amazonses.com

Action: failed
Final-Recipient: rfc822; [email protected]
Diagnostic-Code: smtp; 554 4.4.7 Message expired: unable to deliver in 840 minutes. 
<450 4.1.8 <01020183adb179f8-ecc0a1d6-ce0f-42bc-a892-2ec5582748ce-000000@support.mydomain.com>:

Sender address rejected: Domain not found>
Status: 4.4.7

My SES account has DKIM verification & custom email verification. Do I need to do everything all over again in order to fix the issue?

Previously my domain & the server were located on the same shared hosting. But recently the hosting provider hiked up my bills x4 and I decided to switch. Still, my domain is based on the first shared hosting, but my server is located on another hosting provider. I only changed the nameservers to point to the new hosting provider.

CodePudding user response:

Thank you all for helping me. I think I manage to find the solution, which of course was very simple: When I changed the nameservers of my domain name I didn't move all the DNS records to the new hosting, because I thought that the old DNS records will be used. After a day or two Amazon revoked my DKIM status and send me an email stating that there are no DNS records to be found.

So I copied the DNS records to the new server and my status was returned. Now I'm sending emails again, so far (around 12-15 hours) without any problems.

  • Related