You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
If you are using a SES Configuration Set (by setting the custom mail header X-SES-CONFIGURATION-SET), the bounce event generated by SES is slightly different than if you configure bounce management globally. In fact, the difference is just a JSON key. It is eventType instead of notificationType.
We are using the X-SES-CONFIGURATION-SET header. As such, it seems like we need to support both.
The simplest solution seems to be copying eventType to notificationType if notificationType is not set.
The text was updated successfully, but these errors were encountered:
I have recently observed notifications are sent with the key
eventType
instead ofnotificationType
. The SES docs still state to expectnotificationType
per https://docs.aws.amazon.com/ses/latest/DeveloperGuide/notification-contents.htmlHowever, I've found other issues related to the problem:
An interesting comment at mautic/mautic#8903 (comment):
We are using the
X-SES-CONFIGURATION-SET
header. As such, it seems like we need to support both.The simplest solution seems to be copying
eventType
tonotificationType
ifnotificationType
is not set.The text was updated successfully, but these errors were encountered: