使用AWS SES API发送邮件成功但无法收件的问题求助

Hey there, let’s break down why your emails might be missing from inboxes even though sendTemplatedEmail and sendBulkTemplatedEmail are returning successful responses. That valid MessageId and RequestId in your output confirms SES accepted your request—so the issue lies in what happens after SES processes it. Here are the key steps to diagnose and fix this:

• First, check spam/junk folders
  This is the most common culprit. Even if SES sends the email successfully, recipient email providers (Gmail, Outlook, etc.) might flag it as spam based on content, sender reputation, or missing authentication. Have your recipients double-check their spam, junk, or "promotions" tabs.

• Confirm full domain and identity verification
  Since you’ve tried different domains, make sure each one is fully verified in SES:

  • Enable DKIM for your domain (SES Console > Identities > Select your domain > DKIM tab). This adds cryptographic signatures that prove you own the domain, which boosts deliverability.
  • Set up SPF records for your domain to authorize SES as a legitimate sender.
  • Add a DMARC record to tell providers how to handle unauthenticated emails from your domain.
    Also, ensure any custom "From" email addresses are either verified individually or covered by a verified domain.

• Check if your SES account is in sandbox mode
  New SES accounts start in sandbox mode, which restricts you to sending only to verified recipient email addresses (you have to add and verify each recipient in the SES Console). If you’re sending to non-verified addresses, SES will accept the API request but won’t deliver the email. To exit sandbox mode, you need to submit a request to AWS support.

• Review your email template for spam triggers
  Templates with certain red flags can get filtered:

  • Overuse of salesy language (e.g., "free", "guaranteed", "act now")
  • Too many hyperlinks or links to untrusted domains
  • Missing plain-text version of your email (SES requires both HTML and plain-text for better deliverability)
  • Images hosted on unauthenticated domains or with broken links
    You can test your template content with spam-check tools to identify issues.

• Check SES delivery logs
  The SES Console has detailed delivery logs that show exactly what happened to your email after SES accepted it:

  1. Go to SES Console > Monitoring > Logs
  2. Look for logs associated with your MessageId
  3. Check the eventType (e.g., Delivery, Bounce, Reject) and diagnosticCode for specific errors from the recipient’s email server. This will tell you if the email was bounced, rejected, or delayed.

• Verify recipient email validity
  SES doesn’t validate recipient addresses in real-time when you call the API. If the recipient’s email is invalid, inactive, or has a full inbox, SES will accept the request but the email will bounce. Check the bounce logs in SES to see if this is the case.

• Check SES suppression lists
  SES maintains a suppression list of email addresses that have bounced or complained in the past. If your recipient is on this list, SES will automatically stop delivering emails to them (even if your API call succeeds). You can view and manage the suppression list in the SES Console under Suppression Lists.

内容的提问来源于stack exchange，提问作者Simran