[8.x] Change to X-Message-ID in Mailgun and Ses Transport #34567
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a more usable X-Message-ID header to a sent message containing the response id from the third-party.
The X-Message-ID can be retrieved and used to keep track of upcoming triggered web-hook events from the same third-party.
Fully backwards compatible, however the existing headers could be removed in the next major version. These are: