# Interpreting Amazon SES event data from Amazon SNS
Amazon SES publishes email sending events to Amazon Simple Notification Service (Amazon SNS) as JSON records. Amazon SNS then delivers notifications to the endpoints that are subscribed to the Amazon SNS topic associated with the event destination. For information about setting up topics and subscriptions in Amazon SNS, see [Getting Started](https://docs.aws.amazon.com/sns/latest/dg/GettingStarted.html) in the *Amazon Simple Notification Service Developer Guide*.
For a description of the record contents and for example records, see the following sections.
+ [Event record contents](event-publishing-retrieving-sns-contents.md)
+ [Event record examples](event-publishing-retrieving-sns-examples.md)
# Contents of event data that Amazon SES publishes to Amazon SNS
Amazon SES publishes email sending event records to Amazon Simple Notification Service in JSON format.
You can find example records for all of these notification types in [Examples of event data that Amazon SES publishes to Amazon SNS](event-publishing-retrieving-sns-examples.md).
**Topics**
+ [Top-level JSON object](#event-publishing-retrieving-sns-contents-top-level-json-object)
+ [Mail object](#event-publishing-retrieving-sns-contents-mail-object)
+ [Bounce object](#event-publishing-retrieving-sns-contents-bounce-object)
+ [Complaint object](#event-publishing-retrieving-sns-contents-complaint-object)
+ [Delivery object](#event-publishing-retrieving-sns-contents-delivery-object)
+ [Send object](#event-publishing-retrieving-sns-contents-send-object)
+ [Reject object](#event-publishing-retrieving-sns-contents-reject-object)
+ [Open object](#event-publishing-retrieving-sns-contents-open-object)
+ [Click object](#event-publishing-retrieving-sns-contents-click-object)
+ [Rendering Failure object](#event-publishing-retrieving-sns-contents-failure-object)
+ [DeliveryDelay object](#event-publishing-retrieving-sns-contents-delivery-delay-object)
+ [Subscription object](#event-publishing-retrieving-sns-contents-subscription-object)
## Top-level JSON object
The top-level JSON object in an email sending event record contains the following fields. The event type determines which other objects are present.
| Field Name | Description |
| --- | --- |
| `eventType` | A string that describes the type of event. Possible values: `Bounce`, `Complaint`, `Delivery`, `Send`, `Reject`, `Open`, `Click`, `Rendering Failure`, `DeliveryDelay`, or `Subscription`. If you did not [set up event publishing](monitor-sending-using-event-publishing-setup.md) this field is named `notificationType`. |
| `mail` | A JSON object that contains information about the email that produced the event. |
| `bounce` | This field is only present if `eventType` is `Bounce`. It contains information about the bounce. |
| `complaint` | This field is only present if `eventType` is `Complaint`. It contains information about the complaint. |
| `delivery` | This field is only present if `eventType` is `Delivery`. It contains information about the delivery. |
| `send` | This field is only present if `eventType` is `Send`. |
| `reject` | This field is only present if `eventType` is `Reject`. It contains information about the rejection. |
| `open` | This field is only present if `eventType` is `Open`. It contains information about the open event. |
| `click` | This field is only present if `eventType` is `Click`. It contains information about the click event. |
| `failure` | This field is only present if `eventType` is `Rendering Failure`. It contains information about the rendering failure event. |
| `deliveryDelay` | This field is only present if `eventType` is `DeliveryDelay`. It contains information about the delayed delivery of an email. |
| `subscription` | This field is only present if `eventType` is `Subscription`. It contains information about the subscription preferences. |
## Mail object
Each email sending event record contains information about the original email in the `mail` object. The JSON object that contains information about a `mail` object has the following fields.
| Field Name | Description |
| --- | --- |
| `timestamp` | The date and time, in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*), when the message was sent. |
| `messageId` | A unique ID that Amazon SES assigned to the message. Amazon SES returned this value to you when you sent the message. This message ID was assigned by Amazon SES. You can find the message ID of the original email in the `headers` and `commonHeaders` fields of the `mail` object. |
| `source` | The email address that the message was sent from (the envelope MAIL FROM address). |
| `sourceArn` | The Amazon Resource Name (ARN) of the identity that was used to send the email. In the case of sending authorization, the `sourceArn` is the ARN of the identity that the identity owner authorized the delegate sender to use to send the email. For more information about sending authorization, see [Email authentication methodsUsing sending authorization](sending-authorization.md). |
| `sendingAccountId` | The AWS account ID of the account that was used to send the email. In the case of sending authorization, the `sendingAccountId` is the delegate sender's account ID. |
| `destination` | A list of email addresses that were recipients of the original mail. |
| `headersTruncated` | A string that specifies whether the headers are truncated in the notification, which occurs if the headers are larger than 10 KB. Possible values are `true` and `false`. |
| `headers` | A list of the email's original headers. Each header in the list has a `name` field and a `value` field. Any message ID within the `headers` field is from the original message that you passed to Amazon SES. The message ID that Amazon SES subsequently assigned to the message is in the `messageId` field of the `mail` object. |
| `commonHeaders` | A mapping of the email's original, commonly used headers. Any message ID within the `commonHeaders` field is the message ID that Amazon SES subsequently assigned to the message in the `messageId` field of the `mail` object. |
| `tags` | A list of tags associated with the email. |
## Bounce object
The JSON object that contains information about a `Bounce` event has the following fields.
| Field Name | Description |
| --- | --- |
| `bounceType` | The type of bounce, as determined by Amazon SES. |
| `bounceSubType` | The subtype of the bounce, as determined by Amazon SES. |
| `bouncedRecipients` | A list that contains information about the recipients of the original mail that bounced. |
| `timestamp` | The date and time, in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*), when the ISP sent the bounce notification. |
| `feedbackId` | A unique ID for the bounce. |
| `reportingMTA` | The value of the `Reporting-MTA` field from the DSN. This is the value of the Message Transfer Authority (MTA) that attempted to perform the delivery, relay, or gateway operation described in the DSN. This field only appears if a delivery status notification (DSN) was attached to the bounce. |
### Bounced recipients
A bounce event may pertain to a single recipient or to multiple recipients. The `bouncedRecipients` field holds a list of objects—one object per recipient whose email address produced a bounce—and contains the following field.
| Field Name | Description |
| --- | --- |
| `emailAddress` | The email address of the recipient. If a DSN is available, this is the value of the `Final-Recipient` field from the DSN. |
Optionally, if a DSN is attached to the bounce, the following fields may also be present.
| Field Name | Description |
| --- | --- |
| `action` | The value of the `Action` field from the DSN. This indicates the action performed by the reporting MTA as a result of its attempt to deliver the message to this recipient. |
| `status` | The value of the `Status` field from the DSN. This is the per-recipient transport-independent status code that indicates the delivery status of the message. |
| `diagnosticCode` | The status code issued by the reporting MTA. This is the value of the `Diagnostic-Code` field from the DSN. This field may be absent in the DSN (and therefore also absent in the JSON). |
### Bounce types
Each bounce event is of one of the types shown in the following table.
The event publishing system only publishes hard bounces and soft bounces that are no longer retried by Amazon SES. When you receive bounces marked `Permanent`, you should remove the corresponding email addresses from your mailing list; you will not be able to send to them in the future. `Transient` bounces are sent to you when a message has soft bounced several times, and Amazon SES has stopped trying to re-deliver it. You may be able to successfully resend to an address that initially resulted in a `Transient` bounce in the future.
| bounceType | bounceSubType | Description |
| --- | --- | --- |
| `Undetermined` | `Undetermined` | Amazon SES was unable to determine a specific bounce reason. |
| `Permanent` | `General` | Amazon SES received a general hard bounce. If you receive this type of bounce, you should remove the recipient's email address from your mailing list. |
| `Permanent` | `NoEmail` | Amazon SES received a permanent hard bounce because the target email address does not exist. If you receive this type of bounce, you should remove the recipient's email address from your mailing list. |
| `Permanent` | `Suppressed` | Amazon SES has suppressed sending to this address because it has a recent history of bouncing as an invalid address. To override the global suppression list, see [Using the Amazon SES account-level suppression list](sending-email-suppression-list.md). |
| Permanent | OnAccountSuppressionList | Amazon SES has suppressed sending to this address because it is on the [account-level suppression list](sending-email-suppression-list.md). This does not count toward your bounce rate metric. |
| `Transient` | `General` | Amazon SES received a general bounce. You may be able to successfully send to this recipient in the future. |
| `Transient` | `MailboxFull` | Amazon SES received a mailbox full bounce. You may be able to successfully send to this recipient in the future. |
| `Transient` | `MessageTooLarge` | Amazon SES received a message too large bounce. You may be able to successfully send to this recipient if you reduce the size of the message. |
| `Transient` | `CustomTimeoutExceeded` | Amazon SES was not able to successfully deliver the email within the time specified by the email sender. *(The bounce message will specify the reason for any possible delivery attempt failures within the defined TTL.)* |
| `Transient` | `ContentRejected` | Amazon SES received a content rejected bounce. You may be able to successfully send to this recipient if you change the content of the message. |
| `Transient` | `AttachmentRejected` | Amazon SES received an attachment rejected bounce. You may be able to successfully send to this recipient if you remove or change the attachment. |
## Complaint object
The JSON object that contains information about a `Complaint` event has the following fields.
| Field Name | Description |
| --- | --- |
| `complainedRecipients` | A list that contains information about recipients that may have submitted the complaint. |
| `timestamp` | The date and time, in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*), when the ISP sent the complaint notification. |
| `feedbackId` | A unique ID for the complaint. |
| `complaintSubType` | The subtype of the complaint, as determined by Amazon SES. |
Further, if a feedback report is attached to the complaint, the following fields may be present.
| Field Name | Description |
| --- | --- |
| `userAgent` | The value of the `User-Agent` field from the feedback report. This indicates the name and version of the system that generated the report. |
| `complaintFeedbackType` | The value of the `Feedback-Type` field from the feedback report received from the ISP. This contains the type of feedback. |
| `arrivalDate` | The value of the `Arrival-Date` or `Received-Date` field from the feedback report in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*). This field may be absent in the report (and therefore also absent in the JSON). |
### Complained recipients
The `complainedRecipients` field contains a list of recipients that may have submitted the complaint.
**Important**
Most ISPs redact the email addresses of recipients who submit complaints. For this reason, the `complainedRecipients` field includes a list of everyone who was sent the email whose address is on the domain that issued the complaint notification.
JSON objects in this list contain the following field.
| Field Name | Description |
| --- | --- |
| `emailAddress` | The email address of the recipient. |
### Complaint types
You may see the following complaint types in the `complaintFeedbackType` field as assigned by the reporting ISP, according to the [Internet Assigned Numbers Authority website](https://www.iana.org/assignments/marf-parameters/marf-parameters.xml#marf-parameters-2):
| Field Name | Description |
| --- | --- |
| `abuse` | Indicates unsolicited email or some other kind of email abuse. |
| `auth-failure` | Email authentication failure report. |
| `fraud` | Indicates some kind of fraud or phishing activity. |
| `not-spam` | Indicates that the entity providing the report does not consider the message to be spam. This may be used to correct a message that was incorrectly tagged or categorized as spam. |
| `other` | Indicates any other feedback that does not fit into other registered types. |
| `virus` | Reports that a virus is found in the originating message. |
### Complaint subtypes
The value of the `complaintSubType` field can either be null or `OnAccountSuppressionList`. If the value is `OnAccountSuppressionList`, Amazon SES accepted the message, but didn't attempt to send it because it was on the [account-level suppression list](sending-email-suppression-list.md).
## Delivery object
The JSON object that contains information about a `Delivery` event has the following fields.
| Field Name | Description |
| --- | --- |
| `timestamp` | The date and time when Amazon SES delivered the email to the recipient's mail server, in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*). |
| `processingTimeMillis` | The time in milliseconds between when Amazon SES accepted the request from the sender to when Amazon SES passed the message to the recipient's mail server. |
| `recipients` | A list of intended recipients that the delivery event applies to. |
| `smtpResponse` | The SMTP response message of the remote ISP that accepted the email from Amazon SES. This message will vary by email, by receiving mail server, and by receiving ISP. |
| `reportingMTA` | The host name of the Amazon SES mail server that sent the mail. |
| `remoteMtaIp` | The IP address of the MTA to which Amazon SES delivered the email. |
## Send object
The JSON object that contains information about a `send` event is always empty.
## Reject object
The JSON object that contains information about a `Reject` event has the following fields.
| Field Name | Description |
| --- | --- |
| `reason` | The reason the email was rejected. The only possible value is `Bad content`, which means that Amazon SES detected that the email contained a virus. When a message is rejected, Amazon SES stops processing it, and doesn't attempt to deliver it to the recipient's mail server. |
## Open object
The JSON object that contains information about a `Open` event has the following fields.
| Field Name | Description |
| --- | --- |
| `ipAddress` | The recipient's IP address. |
| `timestamp` | The date and time when the open event occurred in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*). |
| `userAgent` | The user agent of the device or email client that the recipient used to open the email. |
## Click object
The JSON object that contains information about a `Click` event has the following fields.
| Field Name | Description |
| --- | --- |
| `ipAddress` | The recipient's IP address. |
| `timestamp` | The date and time when the click event occurred in ISO8601 format (*YYYY-MM-DDThh:mm:ss.sZ*). |
| `userAgent` | The user agent of the client that the recipient used to click a link in the email. |
| `link` | The URL of the link that the recipient clicked. |
| `linkTags` | A list of tags that were added to the link using the `ses:tags` attribute. For more information about adding tags to links in your emails, see [Q5. Can I tag links with unique identifiers?](faqs-metrics.md#sending-metric-faqs-clicks-q5) in the [Amazon SES email sending metrics FAQs](faqs-metrics.md). |
## Rendering Failure object
The JSON object that contains information about a `Rendering Failure` event has the following fields.
| Field Name | Description |
| --- | --- |
| `templateName` | The name of the template used to send the email. |
| `errorMessage` | A message that provides more information about the rendering failure. |
## DeliveryDelay object
The JSON object that contains information about a `DeliveryDelay` event has the following fields.
| Field Name | Description |
| --- | --- |
| `delayType` | The type of delay. Possible values are: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/ses/latest/dg/event-publishing-retrieving-sns-contents.html) |
| `delayedRecipients` | An object that contains information about the recipient of the email. |
| `expirationTime` | The date and time when Amazon SES will stop trying to deliver the message. This value is shown in ISO 8601 format. |
| `reportingMTA` | The IP address of the Message Transfer Agent (MTA) that reported the delay. |
| `timestamp` | The date and time when the delay occurred, shown in ISO 8601 format. |
### Delayed recipients
The `delayedRecipients` object contains the following values.
| Field Name | Description |
| --- | --- |
| `emailAddress` | The email address that resulted in the delivery of the message being delayed. |
| `status` | The SMTP status code associated with the delivery delay. |
| `diagnosticCode` | The diagnostic code provided by the receiving Message Transfer Agent (MTA). |
## Subscription object
The JSON object that contains information about a `Subscription` event has the following fields.
| Field Name | Description |
| --- | --- |
| `contactList` | The name of the list the contact is on. |
| `timestamp` | The date and time, in ISO8601 format *(YYYY-MM-DDThh:mm:ss.sZ)*, when the ISP sent the subscription notification. |
| `source` | The email address that the message was sent from (the envelope MAIL FROM address). |
| `newTopicPreferences` | A JSON data-structure (map) which specifies the subscription status of all the topics in the contact list indicating the status after a change (contact subscribed or unsubscribed). |
| `oldTopicPreferences` | A JSON data-structure (map) which specifies the subscription status of all the topics in the contact list indicating the status before the change (contact subscribed or unsubscribed). |
### New/old topic preferences
The `newTopicPreferences` and `oldTopicPreferences` objects contain the following values.
| Field Name | Description |
| --- | --- |
| `unsubscribeAll` | Specifies if the contact unsubscribed from all the topics in the contact list. |
| `topicSubscriptionStatus` | Specifies the subscription status of the topic in the `topicName` field indicating whether it is currently subscribed to receive notifications from SES for the specified event type. Possible values are **OptIn** (subscribed) or **OptOut** (unsubscribed) in the `subscriptionStatus` field. |
| `topicDefaultSubscriptionStatus` | Specifies the default subscription status of the topic in the `topicName` field determining whether new topics added to the event destination will be subscribed or unsubscribed by default. Possible values are **OptIn** (subscribed by default) or **OptOut** (unsubscribed by default) in the `subscriptionStatus` field. |
# Examples of event data that Amazon SES publishes to Amazon SNS
This section provides examples of the types of email sending event records that Amazon SES publishes to Amazon SNS.
**Topics**
+ [Bounce record](#event-publishing-retrieving-sns-bounce)
+ [Complaint record](#event-publishing-retrieving-sns-complaint)
+ [Delivery record](#event-publishing-retrieving-sns-delivery)
+ [Send record](#event-publishing-retrieving-sns-send)
+ [Reject record](#event-publishing-retrieving-sns-reject)
+ [Open record](#event-publishing-retrieving-sns-open)
+ [Click record](#event-publishing-retrieving-sns-click)
+ [Rendering Failure record](#event-publishing-retrieving-sns-failure)
+ [DeliveryDelay record](#event-publishing-retrieving-sns-delayed-delivery)
+ [Subscription record](#event-publishing-retrieving-sns-subscription)
**Note**
In the following examples where a `tag` field is utilized, it is using event publishing through a configuration set for which SES supports the publishing of tags for all event types. If using feedback notifications directly on the identity, SES does not publish tags. Read about adding tags when [creating a configuration set](creating-configuration-sets.md) or [modifying a configuration set](managing-configuration-sets.md#console-detail-configuration-sets).
## Bounce record
The following is an example of a `Bounce` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType":"Bounce",
3. "bounce":{
4. "bounceType":"Permanent",
5. "bounceSubType":"General",
6. "bouncedRecipients":[
7. {
8. "emailAddress":"recipient@example.com",
9. "action":"failed",
10. "status":"5.1.1",
11. "diagnosticCode":"smtp; 550 5.1.1 user unknown"
12. }
13. ],
14. "timestamp":"2017-08-05T00:41:02.669Z",
15. "feedbackId":"01000157c44f053b-61b59c11-9236-11e6-8f96-7be8aexample-000000",
16. "reportingMTA":"dsn; mta.example.com"
17. },
18. "mail":{
19. "timestamp":"2017-08-05T00:40:02.012Z",
20. "source":"Sender Name ",
21. "sourceArn":"arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
22. "sendingAccountId":"123456789012",
23. "messageId":"EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
24. "destination":[
25. "recipient@example.com"
26. ],
27. "headersTruncated":false,
28. "headers":[
29. {
30. "name":"From",
31. "value":"Sender Name "
32. },
33. {
34. "name":"To",
35. "value":"recipient@example.com"
36. },
37. {
38. "name":"Subject",
39. "value":"Message sent from Amazon SES"
40. },
41. {
42. "name":"MIME-Version",
43. "value":"1.0"
44. },
45. {
46. "name":"Content-Type",
47. "value":"multipart/alternative; boundary=\"----=_Part_7307378_1629847660.1516840721503\""
48. }
49. ],
50. "commonHeaders":{
51. "from":[
52. "Sender Name "
53. ],
54. "to":[
55. "recipient@example.com"
56. ],
57. "messageId":"EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
58. "subject":"Message sent from Amazon SES"
59. },
60. "tags":{
61. "ses:configuration-set":[
62. "ConfigSet"
63. ],
64. "ses:source-ip":[
65. "192.0.2.0"
66. ],
67. "ses:from-domain":[
68. "example.com"
69. ],
70. "ses:caller-identity":[
71. "ses_user"
72. ]
73. }
74. }
75. }
```
## Complaint record
The following is an example of a `Complaint` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType":"Complaint",
3. "complaint": {
4. "complainedRecipients":[
5. {
6. "emailAddress":"recipient@example.com"
7. }
8. ],
9. "timestamp":"2017-08-05T00:41:02.669Z",
10. "feedbackId":"01000157c44f053b-61b59c11-9236-11e6-8f96-7be8aexample-000000",
11. "userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36",
12. "complaintFeedbackType":"abuse",
13. "arrivalDate":"2017-08-05T00:41:02.669Z"
14. },
15. "mail":{
16. "timestamp":"2017-08-05T00:40:01.123Z",
17. "source":"Sender Name ",
18. "sourceArn":"arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
19. "sendingAccountId":"123456789012",
20. "messageId":"EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
21. "destination":[
22. "recipient@example.com"
23. ],
24. "headersTruncated":false,
25. "headers":[
26. {
27. "name":"From",
28. "value":"Sender Name "
29. },
30. {
31. "name":"To",
32. "value":"recipient@example.com"
33. },
34. {
35. "name":"Subject",
36. "value":"Message sent from Amazon SES"
37. },
38. {
39. "name":"MIME-Version","value":"1.0"
40. },
41. {
42. "name":"Content-Type",
43. "value":"multipart/alternative; boundary=\"----=_Part_7298998_679725522.1516840859643\""
44. }
45. ],
46. "commonHeaders":{
47. "from":[
48. "Sender Name "
49. ],
50. "to":[
51. "recipient@example.com"
52. ],
53. "messageId":"EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
54. "subject":"Message sent from Amazon SES"
55. },
56. "tags":{
57. "ses:configuration-set":[
58. "ConfigSet"
59. ],
60. "ses:source-ip":[
61. "192.0.2.0"
62. ],
63. "ses:from-domain":[
64. "example.com"
65. ],
66. "ses:caller-identity":[
67. "ses_user"
68. ]
69. }
70. }
71. }
```
## Delivery record
The following is an example of a `Delivery` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType": "Delivery",
3. "mail": {
4. "timestamp": "2016-10-19T23:20:52.240Z",
5. "source": "sender@example.com",
6. "sourceArn": "arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
7. "sendingAccountId": "123456789012",
8. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
9. "destination": [
10. "recipient@example.com"
11. ],
12. "headersTruncated": false,
13. "headers": [
14. {
15. "name": "From",
16. "value": "sender@example.com"
17. },
18. {
19. "name": "To",
20. "value": "recipient@example.com"
21. },
22. {
23. "name": "Subject",
24. "value": "Message sent from Amazon SES"
25. },
26. {
27. "name": "MIME-Version",
28. "value": "1.0"
29. },
30. {
31. "name": "Content-Type",
32. "value": "text/html; charset=UTF-8"
33. },
34. {
35. "name": "Content-Transfer-Encoding",
36. "value": "7bit"
37. }
38. ],
39. "commonHeaders": {
40. "from": [
41. "sender@example.com"
42. ],
43. "to": [
44. "recipient@example.com"
45. ],
46. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
47. "subject": "Message sent from Amazon SES"
48. },
49. "tags": {
50. "ses:configuration-set": [
51. "ConfigSet"
52. ],
53. "ses:source-ip": [
54. "192.0.2.0"
55. ],
56. "ses:from-domain": [
57. "example.com"
58. ],
59. "ses:caller-identity": [
60. "ses_user"
61. ],
62. "ses:outgoing-ip": [
63. "192.0.2.0"
64. ],
65. "myCustomTag1": [
66. "myCustomTagValue1"
67. ],
68. "myCustomTag2": [
69. "myCustomTagValue2"
70. ]
71. }
72. },
73. "delivery": {
74. "timestamp": "2016-10-19T23:21:04.133Z",
75. "processingTimeMillis": 11893,
76. "recipients": [
77. "recipient@example.com"
78. ],
79. "smtpResponse": "250 2.6.0 Message received",
80. "remoteMtaIp": "123.456.789.012",
81. "reportingMTA": "mta.example.com"
82. }
83. }
```
## Send record
The following is an example of a `Send` event record that Amazon SES publishes to Amazon SNS. Some fields are not always present. For example, with a templated email, the subject is rendered later and included in subsequent events.
```
1. {
2. "eventType": "Send",
3. "mail": {
4. "timestamp": "2016-10-14T05:02:16.645Z",
5. "source": "sender@example.com",
6. "sourceArn": "arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
7. "sendingAccountId": "123456789012",
8. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
9. "destination": [
10. "recipient@example.com"
11. ],
12. "headersTruncated": false,
13. "headers": [
14. {
15. "name": "From",
16. "value": "sender@example.com"
17. },
18. {
19. "name": "To",
20. "value": "recipient@example.com"
21. },
22. {
23. "name": "Subject",
24. "value": "Message sent from Amazon SES"
25. },
26. {
27. "name": "MIME-Version",
28. "value": "1.0"
29. },
30. {
31. "name": "Content-Type",
32. "value": "multipart/mixed; boundary=\"----=_Part_0_716996660.1476421336341\""
33. },
34. {
35. "name": "X-SES-MESSAGE-TAGS",
36. "value": "myCustomTag1=myCustomTagValue1, myCustomTag2=myCustomTagValue2"
37. }
38. ],
39. "commonHeaders": {
40. "from": [
41. "sender@example.com"
42. ],
43. "to": [
44. "recipient@example.com"
45. ],
46. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
47. "subject": "Message sent from Amazon SES"
48. },
49. "tags": {
50. "ses:configuration-set": [
51. "ConfigSet"
52. ],
53. "ses:source-ip": [
54. "192.0.2.0"
55. ],
56. "ses:from-domain": [
57. "example.com"
58. ],
59. "ses:caller-identity": [
60. "ses_user"
61. ],
62. "myCustomTag1": [
63. "myCustomTagValue1"
64. ],
65. "myCustomTag2": [
66. "myCustomTagValue2"
67. ]
68. }
69. },
70. "send": {}
71. }
```
## Reject record
The following is an example of a `Reject` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType": "Reject",
3. "mail": {
4. "timestamp": "2016-10-14T17:38:15.211Z",
5. "source": "sender@example.com",
6. "sourceArn": "arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
7. "sendingAccountId": "123456789012",
8. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
9. "destination": [
10. "sender@example.com"
11. ],
12. "headersTruncated": false,
13. "headers": [
14. {
15. "name": "From",
16. "value": "sender@example.com"
17. },
18. {
19. "name": "To",
20. "value": "recipient@example.com"
21. },
22. {
23. "name": "Subject",
24. "value": "Message sent from Amazon SES"
25. },
26. {
27. "name": "MIME-Version",
28. "value": "1.0"
29. },
30. {
31. "name": "Content-Type",
32. "value": "multipart/mixed; boundary=\"qMm9M+Fa2AknHoGS\""
33. },
34. {
35. "name": "X-SES-MESSAGE-TAGS",
36. "value": "myCustomTag1=myCustomTagValue1, myCustomTag2=myCustomTagValue2"
37. }
38. ],
39. "commonHeaders": {
40. "from": [
41. "sender@example.com"
42. ],
43. "to": [
44. "recipient@example.com"
45. ],
46. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
47. "subject": "Message sent from Amazon SES"
48. },
49. "tags": {
50. "ses:configuration-set": [
51. "ConfigSet"
52. ],
53. "ses:source-ip": [
54. "192.0.2.0"
55. ],
56. "ses:from-domain": [
57. "example.com"
58. ],
59. "ses:caller-identity": [
60. "ses_user"
61. ],
62. "myCustomTag1": [
63. "myCustomTagValue1"
64. ],
65. "myCustomTag2": [
66. "myCustomTagValue2"
67. ]
68. }
69. },
70. "reject": {
71. "reason": "Bad content"
72. }
73. }
```
## Open record
The following is an example of an `Open` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType": "Open",
3. "mail": {
4. "commonHeaders": {
5. "from": [
6. "sender@example.com"
7. ],
8. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
9. "subject": "Message sent from Amazon SES",
10. "to": [
11. "recipient@example.com"
12. ]
13. },
14. "destination": [
15. "recipient@example.com"
16. ],
17. "headers": [
18. {
19. "name": "X-SES-CONFIGURATION-SET",
20. "value": "ConfigSet"
21. },
22. {
23. "name":"X-SES-MESSAGE-TAGS",
24. "value":"myCustomTag1=myCustomValue1, myCustomTag2=myCustomValue2"
25. },
26. {
27. "name": "From",
28. "value": "sender@example.com"
29. },
30. {
31. "name": "To",
32. "value": "recipient@example.com"
33. },
34. {
35. "name": "Subject",
36. "value": "Message sent from Amazon SES"
37. },
38. {
39. "name": "MIME-Version",
40. "value": "1.0"
41. },
42. {
43. "name": "Content-Type",
44. "value": "multipart/alternative; boundary=\"XBoundary\""
45. }
46. ],
47. "headersTruncated": false,
48. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
49. "sendingAccountId": "123456789012",
50. "source": "sender@example.com",
51. "tags": {
52. "myCustomTag1":[
53. "myCustomValue1"
54. ],
55. "myCustomTag2":[
56. "myCustomValue2"
57. ],
58. "ses:caller-identity": [
59. "IAM_user_or_role_name"
60. ],
61. "ses:configuration-set": [
62. "ConfigSet"
63. ],
64. "ses:from-domain": [
65. "example.com"
66. ],
67. "ses:source-ip": [
68. "192.0.2.0"
69. ]
70. },
71. "timestamp": "2017-08-09T21:59:49.927Z"
72. },
73. "open": {
74. "ipAddress": "192.0.2.1",
75. "timestamp": "2017-08-09T22:00:19.652Z",
76. "userAgent": "Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_3 like Mac OS X) AppleWebKit/603.3.8 (KHTML, like Gecko) Mobile/14G60"
77. }
78. }
```
## Click record
The following is an example of a `Click` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType": "Click",
3. "click": {
4. "ipAddress": "192.0.2.1",
5. "link": "http://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-smtp.html",
6. "linkTags": {
7. "samplekey0": [
8. "samplevalue0"
9. ],
10. "samplekey1": [
11. "samplevalue1"
12. ]
13. },
14. "timestamp": "2017-08-09T23:51:25.570Z",
15. "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36"
16. },
17. "mail": {
18. "commonHeaders": {
19. "from": [
20. "sender@example.com"
21. ],
22. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
23. "subject": "Message sent from Amazon SES",
24. "to": [
25. "recipient@example.com"
26. ]
27. },
28. "destination": [
29. "recipient@example.com"
30. ],
31. "headers": [
32. {
33. "name": "X-SES-CONFIGURATION-SET",
34. "value": "ConfigSet"
35. },
36. {
37. "name":"X-SES-MESSAGE-TAGS",
38. "value":"myCustomTag1=myCustomValue1, myCustomTag2=myCustomValue2"
39. },
40. {
41. "name": "From",
42. "value": "sender@example.com"
43. },
44. {
45. "name": "To",
46. "value": "recipient@example.com"
47. },
48. {
49. "name": "Subject",
50. "value": "Message sent from Amazon SES"
51. },
52. {
53. "name": "MIME-Version",
54. "value": "1.0"
55. },
56. {
57. "name": "Content-Type",
58. "value": "multipart/alternative; boundary=\"XBoundary\""
59. },
60. {
61. "name": "Message-ID",
62. "value": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000"
63. }
64. ],
65. "headersTruncated": false,
66. "messageId": "EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
67. "sendingAccountId": "123456789012",
68. "source": "sender@example.com",
69. "tags": {
70. "myCustomTag1":[
71. "myCustomValue1"
72. ],
73. "myCustomTag2":[
74. "myCustomValue2"
75. ],
76. "ses:caller-identity": [
77. "ses_user"
78. ],
79. "ses:configuration-set": [
80. "ConfigSet"
81. ],
82. "ses:from-domain": [
83. "example.com"
84. ],
85. "ses:source-ip": [
86. "192.0.2.0"
87. ]
88. },
89. "timestamp": "2017-08-09T23:50:05.795Z"
90. }
91. }
```
## Rendering Failure record
The following is an example of a `Rendering Failure` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType":"Rendering Failure",
3. "mail":{
4. "timestamp":"2018-01-22T18:43:06.197Z",
5. "source":"sender@example.com",
6. "sourceArn":"arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
7. "sendingAccountId":"123456789012",
8. "messageId":"EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
9. "destination":[
10. "recipient@example.com"
11. ],
12. "headersTruncated":false,
13. "tags":{
14. "ses:configuration-set":[
15. "ConfigSet"
16. ]
17. }
18. },
19. "failure":{
20. "errorMessage":"Attribute 'attributeName' is not present in the rendering data.",
21. "templateName":"MyTemplate"
22. }
23. }
```
## DeliveryDelay record
The following is an example of a `DeliveryDelay` event record that Amazon SES publishes to Amazon SNS.
```
1. {
2. "eventType": "DeliveryDelay",
3. "mail":{
4. "timestamp":"2020-06-16T00:15:40.641Z",
5. "source":"sender@example.com",
6. "sourceArn":"arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
7. "sendingAccountId":"123456789012",
8. "messageId":"EXAMPLE7c191be45-e9aedb9a-02f9-4d12-a87d-dd0099a07f8a-000000",
9. "destination":[
10. "recipient@example.com"
11. ],
12. "headersTruncated":false,
13. "tags":{
14. "ses:configuration-set":[
15. "ConfigSet"
16. ]
17. }
18. },
19. "deliveryDelay": {
20. "timestamp": "2020-06-16T00:25:40.095Z",
21. "delayType": "TransientCommunicationFailure",
22. "expirationTime": "2020-06-16T00:25:40.914Z",
23. "delayedRecipients": [{
24. "emailAddress": "recipient@example.com",
25. "status": "4.4.1",
26. "diagnosticCode": "smtp; 421 4.4.1 Unable to connect to remote host"
27. }]
28. }
29. }
```
## Subscription record
The following is an example of a `Subscription` event record that Amazon SES publishes to Firehose.
```
1. {
2. "eventType": "Subscription",
3. "mail": {
4. "timestamp": "2022-01-12T01:00:14.340Z",
5. "source": "sender@example.com",
6. "sourceArn": "arn:aws:ses:us-east-1:123456789012:identity/sender@example.com",
7. "sendingAccountId": "123456789012",
8. "messageId": "EXAMPLEe4bccb684-777bc8de-afa7-4970-92b0-f515137b1497-000000",
9. "destination": ["recipient@example.com"],
10. "headersTruncated": false,
11. "headers": [
12. {
13. "name": "From",
14. "value": "sender@example.com"
15. },
16. {
17. "name": "To",
18. "value": "recipient@example.com"
19. },
20. {
21. "name": "Subject",
22. "value": "Message sent from Amazon SES"
23. },
24. {
25. "name": "MIME-Version",
26. "value": "1.0"
27. },
28. {
29. "name": "Content-Type",
30. "value": "text/html; charset=UTF-8"
31. },
32. {
33. "name": "Content-Transfer-Encoding",
34. "value": "7bit"
35. }
36. ],
37. "commonHeaders": {
38. "from": ["sender@example.com"],
39. "to": ["recipient@example.com"],
40. "messageId": "EXAMPLEe4bccb684-777bc8de-afa7-4970-92b0-f515137b1497-000000",
41. "subject": "Message sent from Amazon SES"
42. },
43. "tags": {
44. "ses:operation": ["SendEmail"],
45. "ses:configuration-set": ["ConfigSet"],
46. "ses:source-ip": ["192.0.2.0"],
47. "ses:from-domain": ["example.com"],
48. "ses:caller-identity": ["ses_user"],
49. "myCustomTag1": ["myCustomValue1"],
50. "myCustomTag2": ["myCustomValue2"]
51. }
52. },
53. "subscription": {
54. "contactList": "ContactListName",
55. "timestamp": "2022-01-12T01:00:17.910Z",
56. "source": "UnsubscribeHeader",
57. "newTopicPreferences": {
58. "unsubscribeAll": true,
59. "topicSubscriptionStatus": [
60. {
61. "topicName": "ExampleTopicName",
62. "subscriptionStatus": "OptOut"
63. }
64. ]
65. },
66. "oldTopicPreferences": {
67. "unsubscribeAll": false,
68. "topicSubscriptionStatus": [
69. {
70. "topicName": "ExampleTopicName",
71. "subscriptionStatus": "OptOut"
72. }
73. ]
74. }
75. }
76. }
```