This repository has been archived by the owner on Jan 8, 2020. It is now read-only.
Mail transfer encoding binary #6112
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
| $string = $header->toString(); | ||
|
|
||
| $this->assertContains("Content-Transfer-Encoding: quoted-printable", $string); | ||
| } |
There was a problem hiding this comment.
Why did you remove this test case?
There was a problem hiding this comment.
Actually, on review, I can see that other test cases already cover this behavior.
weierophinney
added a commit
that referenced
this pull request
Apr 14, 2014
Mail transfer encoding binary
weierophinney
added a commit
that referenced
this pull request
Apr 14, 2014
weierophinney
added a commit
to zendframework/zend-mail
that referenced
this pull request
May 14, 2015
…transfer-encoding-binary Mail transfer encoding binary
weierophinney
added a commit
to zendframework/zend-mail
that referenced
this pull request
May 14, 2015
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I can't see a reason why ContentTransferEncoding would disallow
binary.Real emails get sent with this encoding and it seems to just work if we allow it.