Fix for Sendgrid SMTP-ID bug #10
Merged
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
added 2 commits
May 12, 2016 16:47
In cases where the same recipient is defined twice, Sendgrid is sending unique messages with the same recipient SMTP ID. This causes Gmail to discard the extras, even if they have unique content (due to different merge vars or etc.). This is a workaround for the issue until Sendgrid decides what, if anything, they'd like to do on their end to resolve this.
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.
In cases where the same recipient is defined twice, Sendgrid is sending
unique messages with the same recipient SMTP ID. This causes Gmail to
discard the extras, even if they have unique content (due to different
merge vars or etc.). This is a workaround for the issue until Sendgrid
decides what, if anything, they'd like to do on their end to resolve
this.