[3.8] bpo-37482: Fix email address name with encoded words and specia…#15380
Merged
ned-deily merged 1 commit intopython:3.8from Aug 29, 2019
bsiem:backport-df0c21f-3.8
Merged
[3.8] bpo-37482: Fix email address name with encoded words and specia…#15380ned-deily merged 1 commit intopython:3.8from bsiem:backport-df0c21f-3.8
ned-deily merged 1 commit intopython:3.8from
bsiem:backport-df0c21f-3.8
Conversation
…l chars (GH-14561) Special characters in email address header display names are normally put within double quotes. However, encoded words (=?charset?x?...?=) are not allowed withing double quotes. When the header contains a word with special characters and another word that must be encoded, the first one must also be encoded. In the next example, the display name in the From header is quoted and therefore the comma is allowed; in the To header, the comma is not within quotes and not encoded, which is not allowed and therefore rejected by some mail servers. From: "Foo Bar, France" <foo@example.com> To: Foo Bar, =?utf-8?q?Espa=C3=B1a?= <foo@example.com> https://bugs.python.org/issue37482 (cherry picked from commit df0c21f) Co-authored-by: bsiem <52461103+bsiem@users.noreply.github.com>
epicfaace
approved these changes
Aug 24, 2019
Member
|
It looks like this backport had to be restarted and did not get merged like the 3.7 backport did. With the 3.8.0b4 cutoff approaching, I'm going to manually push merge it for 3.8. |
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
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.
…l chars (GH-14561)
Special characters in email address header display names are normally
put within double quotes. However, encoded words (=?charset?x?...?=) are
not allowed withing double quotes. When the header contains a word with
special characters and another word that must be encoded, the first one
must also be encoded.
In the next example, the display name in the From header is quoted and
therefore the comma is allowed; in the To header, the comma is not
within quotes and not encoded, which is not allowed and therefore
rejected by some mail servers.
From: "Foo Bar, France" foo@example.com
To: Foo Bar, =?utf-8?q?Espa=C3=B1a?= foo@example.com
https://bugs.python.org/issue37482
(cherry picked from commit df0c21f)
Co-authored-by: bsiem 52461103+bsiem@users.noreply.github.com
https://bugs.python.org/issue37482