Email deliverability issues with Amazon SES can arise from numerous factors relating to authentication, reputation, content, list management, sending practices, and technical configurations. Authentication problems with SPF, DKIM, and DMARC can lead to emails being flagged as spam. Poor IP reputation, due to shared IPs, lack of IP warming, or sudden volume increases, negatively impacts deliverability. Problematic content, such as spam trigger words or links to websites with poor reputations, also contributes to deliverability issues. Furthermore, sending to invalid addresses, unengaged subscribers, or failing to honor unsubscribe requests harms sender reputation. Technical configurations, such as missing or misconfigured rDNS records, and exceeding sending limits, can also cause problems. Amazon SES's global suppression list can block emails to addresses that have previously bounced or complained. Finally, temporary issues, such as problems with the receiving server, may also be responsible.
11 marketer opinions
Several factors can contribute to email deliverability issues when using Amazon SES. These include authentication problems (SPF, DKIM, DMARC), poor IP reputation (due to shared IPs or lack of IP warming), spam trigger words in email content, URLs to websites with bad reputations, sending to unengaged subscribers, abrupt increases in sending volume, exceeding sending limits, not honoring unsubscribe requests, and failing to set up feedback loops. Checking reputation, bounce rates, complaint rates, and suppressions are also essential.
Marketer view
Email marketer from Gmass explains that exceeding the sending limits imposed by Amazon SES can lead to deliverability problems. Monitor your sending limits and adjust your sending volume accordingly.
19 Nov 2021 - Gmass
Marketer view
Marketer from Email Geeks asks about the custom return-path and DKIM signing and if the SES reputation dashboard is showing any issues with bounces and complaints.
2 Feb 2025 - Email Geeks
3 expert opinions
Email delivery issues with Amazon SES can stem from several factors. Amazon SES maintains a global suppression list of email addresses that have previously bounced or complained; if an address is on this list, delivery will fail regardless of sender reputation. Additionally, a sudden spike in email volume from a new SES account can trigger spam filters and harm deliverability, making IP warming crucial. Finally, temporary issues like the recipient server's technical difficulties or DNS problems can also prevent email delivery.
Expert view
Expert from Word to the Wise explains that temporary issues can arise due to the receiving server experiencing technical difficulties. A DNS issue at the recipients end can affect if they get the email, or a technical issue between hops along the way can occur.
1 Sep 2024 - Word to the Wise
Expert view
Expert from Spam Resource explains that Amazon SES has a global suppression list which includes email addresses that have previously bounced or complained. If a recipient is on this list, your emails will not be delivered, regardless of your sender reputation. This can occur because of a previous sender marking the email as spam.
23 Oct 2021 - Spam Resource
4 technical articles
Email deliverability issues with Amazon SES can stem from sending emails to invalid addresses, resulting in bounces. High bounce and complaint rates negatively impact sender reputation. A missing or misconfigured reverse DNS (rDNS) record can also cause deliverability problems, as some email providers use rDNS to verify sending server legitimacy.
Technical article
Documentation from Amazon Web Services explains that high bounce rates can negatively impact your sender reputation, leading to deliverability issues. Hard bounces, in particular, should be addressed promptly by removing the invalid email addresses from your sending list. Amazon SES provides mechanisms for automatically handling bounces, such as using Amazon Simple Notification Service (SNS) to receive bounce notifications.
23 Oct 2022 - Amazon Web Services
Technical article
Documentation from DigitalOcean explains that not having a reverse DNS (rDNS) record set up for your sending IP address can cause deliverability issues. Some email providers use rDNS to verify the legitimacy of the sending server. The reverse DNS must also match the domain name used in your email.
4 Jun 2022 - DigitalOcean
Are there email sending issues with AWS?
Does a DMARC policy of 'none' negatively impact email reputation?
How can I manage Feedback-ID headers when using Amazon SES to send emails, especially with Gmail's upcoming sender requirements?
How do I show 'signed by' my domain when using Amazon SES or Mailchimp?
How do I troubleshoot email bounce messages?
How do Iterable shared infrastructure and Amazon SES handle SPF alignment and DMARC compliance?