- Newest
- Most votes
- Most comments
Hello, I would suggest you do the below checks
Log in to the Amazon SES Console and review your sending limits and quotas. https://docs.aws.amazon.com/ses/latest/dg/manage-sending-quotas.html
Check your email statistics for high bounce or complaint rates. https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-email-deliverability-dashboard-bounce-complaint.html
Verify your domain settings (SPF, DKIM, DMARC) in the SES console. https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dmarc.html
Review your email content for potential spam triggers and ensure your recipient list is clean.
Check the AWS Service Health Dashboard for any SES-related issues.
Set up SNS notifications to monitor bounces, complaints, and delivery statuses. https://aws.amazon.com/it/blogs/messaging-and-targeting/amazon-ses-set-up-notifications-for-bounces-and-complaints/
Test email sending with different content and recipients to identify any patterns.
could you please check this :- https://aws.amazon.com/it/blogs/messaging-and-targeting/three-places-where-your-email-could-get-delayed-when-sending-through-ses/
Contact AWS Support if the issue persists after performing the above steps.
You don't tell us if the delays are with all e-mail destinations or only a sub-set. We have become used to SMTP mail delivering immediately, so much so that we forget the protocol is actually store-and-forward (a message is received by a given MTA, and then re-queued for delivery by that MTA).
A transient network or other error at that point, will typically cause the message to be re-queued for later delivery by the MTA.
Verify if you are seeing this only for some destinations.
Relevant content
- asked a year ago
- asked a year ago
- asked 3 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