Amazon SES mailer daemon delivery status notification (failure). An error occured while trying to deliver mail to following recipent. From Gmail to Gmail wia SES.

Question

Introduction:
As a AWS Cloud ESP (Email Service Provider), we send bulk emails, including transactional emails, on behalf of our clients. Recently, we have encountered two distinct types of email delivery failures, and while we have a solution for the first type, we are **seeking an effective solution for the second.**
**
1. Issue with Domain-Identified Emails (Solved):**

Error Message Example:

Error: An error occurred while trying to deliver the mail to the following recipients: test@ya&oo.co.in

Reporting-MTA: dns; a9-37.smtp-out.ama2onses.com

Action: failed

Diagnostic-Code: smtp; 552 1 Requested mail action aborted, mailbox not found

Status: 5.3.0

Understanding and Resolution:

These errors occur when the client’s domain lacks proper email authentication records (DKIM, SPF, and DMARC).

Resolution: We assist clients in configuring these DNS records for their domain to ensure successful email delivery.

**2. Issue with Public Email Providers (Unresolved):
**
Error Message Example:

From: mailer daemon address of A W S

Sent: Monday, July 15, 2024, 1:16 PM

To: companyxyz

Subject: Undeliverable: test subject line

Error Details:

An error occurred while trying to deliver the mail to the following recipients: test1234@gm#il.com

Problem Explanation:

In this scenario, the delivery failure is related to public email providers like Gmail or Outlook.

Unlike domain-specific failures, there is no diagnostic code, status, or detailed error message provided, making it difficult to identify the root cause.

Current Workaround:

We currently advise clients to use a new Gmail or Outlook address as a temporary fix, assuming it might be a reputation issue. However, this is not a reliable or scalable solution.

Request for Assistance:

We are seeking an effective method to identify and resolve email delivery failures for public email providers (Gmail, Outlook) without having to rely on creating new email addresses. Any guidance on obtaining diagnostic information or best practices to improve deliverability would be highly appreciated.

Kidd Ip · Answer

It may related to IP reputation and blacklisting, please also take care SES suppression list in AWS as well, moreover Email may rejected by rate limit as well but retry may solve itself.

Taz · Answer

Hey,

Hope you're keeping well.

For large mailbox providers like Gmail, silent rejections or vague bounce messages usually point to sender reputation or content filtering rather than DNS misconfiguration. Even if SPF, DKIM, and DMARC are correct, SES will be throttled or blocked if the sending domain, IP pool, or message content has low trust scores. Check your SES account’s reputation metrics in the **SES console > Reputation dashboard**, review bounce/complaint rates, and ensure you’re sending through a production account with a dedicated IP pool if high volume. It also helps to sign with a custom MAIL FROM domain and keep content compliant with Gmail’s bulk sender guidelines.

Thanks and regards,  
Taz

Amazon SES mailer daemon delivery status notification (failure). An error occured while trying to deliver mail to following recipent. From Gmail to Gmail wia SES.

Add your answer

Relevant content