- Newest
- Most votes
- Most comments
SES is a relay agent which takes the email from your API then filter it as per standards and accept it if all good. Then it setup connection with recipient MTA and handover the email to recipient MTA. Once SES got SMTP 250 OK from recipient MTA we donot have any visibility how recipient MTA process the email.
There could be below mentioned possible reason behind delay:
-
If recipient MTA is not able to accept new connections then SES will keep retrying. If you want notification for each retry then you can configure the same by referring https://aws.amazon.com/about-aws/whats-new/2020/06/amazon-ses-can-now-send-notifications-when-the-delivery-of-an-email-is-delayed/
-
Recipient MTA accepts the email and then keeps that in buffer before landing it in recipients inbox.
-
Recipient MTA facing some throttling hence not processing the emails at given time.
-
Rare but possible if recipient MTA has SES IP addresses in filtering hence you may facing throttle issues.
In order to resolve this please open support case with AWS and share below mentioned:
- From email address, To email address, Time stamp and Message ID from logs if possible.
By having this information SES team will analyze the internal logs in order to find root cause and that's how they will help you to resolve this issue.
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hi
I've chosen not sign up for support, since in my experience I only get links to be able to read and find out the answer myself. (Which I kind of understand, but I can find this information myself, so no need to pay for it.) So I can't open a support case. =(
Since yesterday I've enabled SES in another region and from the initial tests it seems to work better than eu-west-1.
Also, I have tried emailing different recipients and the issue is the same. So my guess is that it's not due to recipient MTA.