Prompt

Amazon SES bounce handling

Technology / Developer Tools1 observationLast seen Nov 11, 2026

Latest observation

Nov 11, 2026OpenAI APIWeb search: off

Amazon SES bounce handling usually means detecting bounced emails from SES and processing them in your app so you can suppress invalid addresses, update user status, or alert admins.

How SES bounce handling works

When SES sends an email, some deliveries may fail. SES can send event notifications for:

  • Bounce — the recipient’s mail server rejected the message
  • Complaint — recipient marked it as spam
  • Delivery — message was successfully delivered
  • Reject — SES rejected the message before sending
  • Open/Click — if enabled

For bounce handling, you typically:

  1. Configure SES to publish events

    • Use SNS, CloudWatch, EventBridge, or Kinesis Firehose
    • Most common: SES → SNS → Lambda / HTTP endpoint
  2. Subscribe your app to bounce notifications

    • Parse the SNS message
    • Extract email address, bounce type, bounce reason, timestamp
  3. Update your suppression logic

    • Mark the email as bounced
    • Stop sending to that address
    • Optionally store bounce counts / reason

Typical bounce notification structure

A bounce event contains fields like:

  • notificationType: "Bounce"
  • bounceType: Permanent or Transient
  • bounceSubType: reason detail
  • bouncedRecipients: list of recipients
  • timestamp
  • feedbackId

Example fields:

{
  "notificationType": "Bounce",
  "bounce": {
    "bounceType": "Permanent",
    "bounceSubType": "General",
    "bouncedRecipients": [
      {
        "emailAddress": "user@example.com",
        "action": "failed",
        "status": "5.1.1",
        "diagnosticCode": "smtp; 550 5.1.1 user unknown"
      }
    ]
  }
}

Best practices

  • Treat permanent bounces as hard failures
    • Suppress immediately
  • Retry transient bounces carefully
    • Temporary issues may resolve
  • Deduplicate events
    • SES/SNS may redeliver notifications
  • Use a suppression list
    • Don’t keep sending to known bad addresses
  • Track complaints separately
    • Complaints are usually more serious than bounces

Common SES setup options

1) SNS notification

  • SES publishes bounce events to an SNS topic
  • Your Lambda subscribes to the topic
  • Good for real-time processing

2) Configuration set

  • Create a Configuration Set in SES
  • Add an event destination for bounce events
  • Apply the configuration set when sending mail

Example sending with a configuration set:

  • SES API / SMTP headers can include the configuration set name
  • Lets you choose which emails produce events

AWS Lambda processing flow

  1. SNS receives bounce event from SES
  2. SNS triggers Lambda
  3. Lambda parses JSON
  4. Lambda updates database / suppression list

Pseudo-logic:

if notificationType == "Bounce":
    for recipient in bouncedRecipients:
        mark_email_bounced(recipient["emailAddress"], bounceType, status)

Important note: SES suppression list

Amazon SES also has a account-level suppression list feature.
This can automatically suppress sending to addresses that previously bounced or complained.

You can:

  • Enable account-level suppression
  • Use your own suppression list
  • Or both

If you want, I can help with any of these next:

  • Set up SES bounce notifications step-by-step
  • Write a Lambda handler for SES bounce events
  • Show SNS + SES configuration
  • Give examples in Python, Node.js, or Java

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.