| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ound (pythonGH-122233) - Encode header parts that contain newlines Per RFC 2047: > [...] these encoding schemes allow the > encoding of arbitrary octet values, mail readers that implement this > decoding should also ensure that display of the decoded data on the > recipient's terminal will not cause unwanted side-effects It seems that the "quoted-word" scheme is a valid way to include a newline character in a header value, just like we already allow undecodable bytes or control characters. They do need to be properly quoted when serialized to text, though. - Verify that email headers are well-formed This should fail for custom fold() implementations that aren't careful about newlines. Co-authored-by: Bas Bloemsaat <bas@bloemsaat.org> Co-authored-by: Serhiy Storchaka <storchaka@gmail.com> (cherry picked from commit 0976339)
|
Marking this for consideration as a release blocker. |
Sorry, something went wrong.
The fix for this issue was included in upstream release of 3.12.5. python/cpython#122599
The fix for this issue was included in upstream release of 3.12.5. python/cpython#122599
| Back | FazBrowse Home | New Git URL |
Per RFC 2047:
It seems that the "quoted-word" scheme is a valid way to include
a newline character in a header value, just like we already allow
undecodable bytes or control characters.
They do need to be properly quoted when serialized to text, though.
This should fail for custom fold() implementations that aren't careful
about newlines.
Co-authored-by: Bas Bloemsaat bas@bloemsaat.org
Co-authored-by: Serhiy Storchaka storchaka@gmail.com
(cherry picked from commit 0976339)
📚 Documentation preview 📚: https://cpython-previews--122599.org.readthedocs.build/