bpo-39757: Use IDNA to encode domain part in email address #18667
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
CLA was signed this morning, also is it possible to mark this one to be backported in 3.8 and 3.7 ? |
While b64/qp can be used to encode most non-ascii headers, the domain part of an email address must conform IDNA ([rfc5890], [rfc5891]) thus be encoded using the punycode algorithm ([rfc3492]). [SMTPUTF8](rfc6531) is no exception. [rfc5890]: https://tools.ietf.org/html/rfc5890 [rfc5891]: https://tools.ietf.org/html/rfc5891 [rfc3492]: https://tools.ietf.org/html/rfc3492 [rfc6531]: https://tools.ietf.org/html/rfc6531#section-3.2
d79eb72 to
dccf01a
Compare
|
Duplicate of https://bugs.python.org/issue11783 |
While b64/qp can be used to encode most non-ascii headers, the domain
part of an email address must conform IDNA (rfc5890, rfc5891) thus
be encoded using the punycode algorithm (rfc3492).
https://bugs.python.org/issue39757