[9.x] Set SES MessageId to the sent message ID #41328
Closed
Conversation
This file contains hidden or 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
Member
|
Would this be a breaking change for existing applications? Why or why not? |
Contributor
Author
|
After you asked me, I dug deeper and realized that this behavior is actually wrong, because the generated ID has already sent in the message headers. I'll try to find another approach to attach the returned ID. Sorry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR sets the given SES message ID as the
SentMessage's message ID.As mentioned in #40696, the addition of Message ID's to the headers of the just-sent message was removed because Symfony is generating one. But the actual SES message ID may be needed, in my case, to manage the status of the sent e-mail, that may be afterwards sent by the SES service, referencing the previously given ID.