Prompt
Amazon SES bounce handling
Latest observation
Nov 11, 2026
OpenAI 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:
-
Configure SES to publish events
- Use SNS, CloudWatch, EventBridge, or Kinesis Firehose
- Most common: SES → SNS → Lambda / HTTP endpoint
-
Subscribe your app to bounce notifications
- Parse the SNS message
- Extract email address, bounce type, bounce reason, timestamp
-
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:PermanentorTransientbounceSubType: reason detailbouncedRecipients: list of recipientstimestampfeedbackId
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
- SNS receives bounce event from SES
- SNS triggers Lambda
- Lambda parses JSON
- 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