[5.2] Added reply_to field for SparkPost API request within SparkpostTransport #13410
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
Signed-off-by: Byron Smith <byronsmith@30db80bfe262>
Signed-off-by: Byron Smith <byronsmith@users.noreply.github.com>
byronsmith
force-pushed
the
feature/sparkpost-transport-replyto
branch
from
8a4d104 to
62d4fc7
Compare
GrahamCampbell
changed the title
|
What about the other drivers please? |
|
Happy to contribute to the Mailgun transport, but mandrill is no longer a free service, and I don't have a EC2 instance for SES. I therefore wouldn't be comfortable implementing code I cannot test. With that in mind, where does that leave me in terms of having this SparkPost improvement merged? |
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.
Added reply_to field for SparkPost API request within SparkpostTransport
Signed-off-by: Byron Smith byronsmith/framework@30db80bfe262