Fix SMTP sender verification after WordPress changes #16
+2
−0
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
ribvid
changed the title
WordPress changeset 61010 removed the third parameter (false) from setFrom() in wp_mail(), which now causes the Sender header to be automatically set. This can cause sender verification failures with some SMTP servers. This fix explicitly sets Sender property to match From address. Fixes roots#15
ribvid
force-pushed
the
fix/sender-header
branch
from
98d0531 to
5459db2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
WordPress changeset 61010 removed the third parameter (false) from setFrom() in wp_mail(), which now causes the Sender header to be automatically set. This can cause sender verification failures with some SMTP servers.
This fix explicitly sets Sender property to match From address.
Fixes #15