[5.8] Storing Mailgun Message-ID in the headers after sending #28994
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… the message has been sent
driesvints
approved these changes
Jul 1, 2019
|
@CyrilMazur great PR. I remember wanting something similar when working with Mandril a year ago. Can definitely see this being used. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 stores the message ID from Mailgun into the
X-Mailgun-Message-IDheader so that sendPerformed() can reference it. The same behaviour already exists for SparkPost (#18594) and SES (#16366).My personal use case is that it allows me to track individual emails (for open, click and spam complaint events) when I receive webhooks from Mailgun / SparkPost / SES.