This repository was archived by the owner on Jan 30, 2020. It is now read-only.
Fix mail sender #11
Merged
Fix mail sender #11
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
This allows to extend and change data given to that specific test in the future. This also ensures that the test signature reflects what it needs for better understanding.
denis-sokolov
force-pushed
the
fix-mail-sender
branch
from
f1f3b65 to
b89b367
Compare
|
@denis-sokolov Thanks for this PR; however, you did modify the test behavior and as such the conditions from the previous test also need to continue in being tested. |
|
Thank you for your note. |
|
💡 |
weierophinney
added a commit
that referenced
this pull request
Sep 9, 2015
weierophinney
added a commit
that referenced
this pull request
Sep 9, 2015
glensc
pushed a commit
to eventum/zend-mail
that referenced
this pull request
Feb 15, 2016
This commit backports changes from the 2.5 series for the 2.4.8 LTS release. These include the following: - [zendframework#11](zendframework#11) ensures that the sender can be a mailbox name, or an email specifying a host that omits the TLD. - [zendframework#21](zendframework#21) provides a patch to allow addresses in the form `Name address@domain.tld` (without angle brackets surrounding the actual email addres). - [zendframework#24](zendframework#24) fixes parsing of mail messagse that contain an initial blank line (prior to any headers), a situation observed in particular with GMail. - [zendframework#26](zendframework#26) fixes the `ContentType` header to properly handle parameters with encoded values.
weierophinney
added a commit
to zendframework/zendframework
that referenced
this pull request
Dec 20, 2016
This commit backports changes from the 2.5 series for the 2.4.8 LTS release. These include the following: - [#11](zendframework/zend-mail#11) ensures that the sender can be a mailbox name, or an email specifying a host that omits the TLD. - [#21](zendframework/zend-mail#21) provides a patch to allow addresses in the form `Name address@domain.tld` (without angle brackets surrounding the actual email addres). - [#24](zendframework/zend-mail#24) fixes parsing of mail messagse that contain an initial blank line (prior to any headers), a situation observed in particular with GMail. - [#26](zendframework/zend-mail#26) fixes the `ContentType` header to properly handle parameters with encoded values.
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.
If I'm not mistaken, in RFC 5322 3.6.2. states
sender = "Sender:" mailbox CRLF, and 3.4.mailbox = name-addr / addr-spec, whereaddr-spec = local-part "@" domain.More specifically, I got an email sent from Gmail with
Sender: foo@bar.