Send Amazon SES events back to your suppression list

Subscribe your workspace to the Amazon SNS topic for your SES notifications. Bounces and complaints update your suppression list.

Get started free Delivery feedback

Fig. 1Amazon SES → Verifier

1.1 Amazon SES

Amazon SESSNS notifications

1.2 Delivery endpoint

Token in the URL
SNS message signature
Allowed topic ARNs

1.3 Recorded as

Delivery → deliveredHistory
Bounce → bouncedSuppressed
Complaint → complainedSuppressed

POST /v1/inbound/providers/ses/{endpoint}/{token}

Source: Amazon SNS notifications
Verification: SNS signature and topic ARN
Suppressed: Bounces, complaints
Setup: One private URL

§ 1

Why it matters

Delivery problems stay inside Amazon SES

When an event is only recorded in the email platform, the address comes back with the next import.

Close the loop between Amazon SES and your list checks.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Bounce notifications stay in an SNS topic.With Verifier: Each SNS message is checked for its signature and topic ARN.
Without: Imports from other tools bring the same addresses back.With Verifier: Bounces and complaints join one suppression list.
Without: Suppression lists differ from tool to tool.With Verifier: Every event shows in the address history.

§ 2

How it works

A private URL for each endpoint

Amazon SES sends bounce and complaint notifications to an SNS topic. Verifier checks the SNS signature and accepts only the topic ARNs that you set.

2.1In Amazon SNS, create a topic, and copy its topic ARN.
2.2In Verifier, open Outcomes, and add an Amazon SES endpoint with that topic ARN. Copy its private URL.
2.3In Amazon SNS, add an HTTPS subscription to the URL. Verifier confirms the subscription.
2.4In Amazon SES, open your verified identity, then Notifications. Send bounce and complaint feedback to the topic.

Fig. 3One bounce from Amazon SES

Sent by Amazon SES

{  "Type": "Notification",  "TopicArn": "arn:aws:sns:us-east-1:123456789012:ses-events",  "MessageId": "f3c1a2b4-...",  "Message": "{\"notificationType\":\"Bounce\",\"mail\":{\"destination\":[\"[email protected]\"]}}",  "Signature": "EXAMPLEpH+..."}

Verifier · POST /v1/inbound/providers/ses/{endpoint}/{token}

{  "provider": "ses",  "accepted": 1,  "duplicates": 0,  "rejected": 0}

GET /v1/suppressions/[email protected]

{  "suppressed": true,  "reason": "bounce",  "source": "ses"}

SNS signature and your topic ARN · fields trimmed

§ 3

What you get

What you get.

3.1One suppression listSuppressions from Amazon SES sit next to invalid results and manual entries.
3.2Event historySee the delivery events for each address in its history.

Table 3 · Event mapping

Event from the platform	Recorded as
Delivery	delivered
Bounce	bounced
Complaint	complained

§ 4

In practice

Typical uses.

Case 4.1
Stop repeat problems
A suppressed address goes to the drop file when you clean your next list.
Case 4.2
More than one sending tool
A Amazon SES bounce also stops the address in lists from your CRM and other tools.

Other integrations.

All integrations

Questions

Before you start.

Which events are recorded?

The event mapping on this page shows what is recorded. Bounces and complaints go on the suppression list.

Do I need to confirm the SNS subscription?

No. Verifier checks the signature of the confirmation message from Amazon SNS and confirms the subscription.

Delivery problems stay inside Amazon SES

When an event is only recorded in the email platform, the address comes back with the next import.

Close the loop between Amazon SES and your list checks.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Bounce notifications stay in an SNS topic.With Verifier: Each SNS message is checked for its signature and topic ARN.
Without: Imports from other tools bring the same addresses back.With Verifier: Bounces and complaints join one suppression list.
Without: Suppression lists differ from tool to tool.With Verifier: Every event shows in the address history.

A private URL for each endpoint

Amazon SES sends bounce and complaint notifications to an SNS topic. Verifier checks the SNS signature and accepts only the topic ARNs that you set.

2.1In Amazon SNS, create a topic, and copy its topic ARN.
2.2In Verifier, open Outcomes, and add an Amazon SES endpoint with that topic ARN. Copy its private URL.
2.3In Amazon SNS, add an HTTPS subscription to the URL. Verifier confirms the subscription.
2.4In Amazon SES, open your verified identity, then Notifications. Send bounce and complaint feedback to the topic.

Fig. 3One bounce from Amazon SES

Sent by Amazon SES

{  "Type": "Notification",  "TopicArn": "arn:aws:sns:us-east-1:123456789012:ses-events",  "MessageId": "f3c1a2b4-...",  "Message": "{\"notificationType\":\"Bounce\",\"mail\":{\"destination\":[\"[email protected]\"]}}",  "Signature": "EXAMPLEpH+..."}

Verifier · POST /v1/inbound/providers/ses/{endpoint}/{token}

{  "provider": "ses",  "accepted": 1,  "duplicates": 0,  "rejected": 0}

GET /v1/suppressions/[email protected]

{  "suppressed": true,  "reason": "bounce",  "source": "ses"}

SNS signature and your topic ARN · fields trimmed

Event from the platform

Recorded as

Delivery

delivered

Bounce

bounced

Complaint

complained

From a raw listto a safe send.

Send Amazon SES events back to your suppression list

Delivery problems stay inside Amazon SES

A private URL for each endpoint

What you get.

Typical uses.

Other integrations.

Before you start.

From a raw listto a safe send.

Send Amazon SES events back to your suppression list

Delivery problems stay inside Amazon SES

A private URL for each endpoint

What you get.

Typical uses.

Other integrations.

Before you start.