- Newest
- Most votes
- Most comments
I have received an answer from SES support that overriding the Feedback-ID is currently not possible. I interpret it in a way that SES needs their Feedback-ID to be able to calculate their own Complaint metrics. I was told that there is an open change request with the internal SES team to enable us to set our own Feedback-ID, but there is no ETA. But our inquiries might increase the prio.
That's terrible news. GMails new Spam standards kick in in less than a week, and the number 1 tool they recommend using to manage the problem is the Feeback Loop tool via the Feedback-ID. So the worlds largest email platform (SES) cannot work with the worlds largest mailbox provider (Gmail) so we can analyze our spam complaints more effectively?
AWS has just made a change: https://aws.amazon.com/about-aws/whats-new/2024/06/amazon-ses-custom-values-feedback-header/
Today, Amazon Simple Email Service (SES) released a new feature to give customers control over parts of the auto-generated Feedback-ID header in messages sent through SES. This feature provides additional details to help customers identify deliverability trends. Customers can use products like PostMaster Tools by Gmail to see complaint rates by identifiers of their choice, such as sender identity or campaign ID. This makes it easier to track deliverability performance associated with independent workloads and campaigns, and accelerates troubleshooting when diagnosing complaint rates.
Previously, SES automatically generated a Feedback-ID header when sending emails on behalf of SES customers. This Feedback-ID helps customers track their deliverability performance, such as complaint rates, at the AWS account level. Now SES includes up to two custom values in the Feedback-ID header, which customers can pass to SES during sending. Customers specify message tag values for either “ses:feedback-id-a” or “ses:feedback-id-b” (or both), and SES automatically includes these values as the first and second fields in the Feedback-ID header (respectively). This gives even more granularity when viewing deliverability metrics in tools such as PostMaster Tools by Gmail.
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Yes we are having the same exact problem!
I have also created an AWS support ticket about this and pointed them here.