SendGrid Adapter Reply-To parameter updates #487
Merged
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 adds support for the "native"
Reply-To
header string (in addition to the already supported customreply-to
header string).Additionally, it also adds full support for SendGrids
reply_to
parameter format with both the requiredemail
field and optionalname
field.I split these two additions into 2 separate commits for easier review and editing. If there is no desire to add full support for the
name
field, I can gladly drop that commit and just send across theReply-To
commit.To me, at a minimum, the
Reply-To
format of the header string should be allowed as this is the standard name for the header in SMTP spec and is referenced directly in the top levelBamboo.Email
docs on theput_header/3
function.