gh-99533: Fix issue where email.generator.Generator ignores policy when using multipart/signed#100204
gh-99533: Fix issue where email.generator.Generator ignores policy when using multipart/signed#100204jackpendley wants to merge 4 commits intopython:mainfrom
Conversation
…issue python#99533 where EmailMessage behaves differently when being set to multipart/signed mimetype
…part_signed would resolve issue python#99533
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
✅ Deploy Preview for python-cpython-preview canceled.
|
|
All commit authors signed the Contributor License Agreement. |
|
Have things been fixed so that unmodified headers are never refolded? If that has been done, then this works. However, if it is still the case that long headers get refolded when rendering an existing (not a new) message, then this will break re-rendering existing signed messages, which was the point of the original fix. The correct fix, obviously, is to never refold header lines that have not been modified since the message was deserialized, which is what I should have done originally (hindsight is wonderful :) |
|
The following commit authors need to sign the Contributor License Agreement: |
|
This PR is stale because it has been open for 30 days with no activity. |
3 participants
Provides fix for Issue #99533
The requested fix in the original issue report was implemented.
Removed _handle_multipart_signed from generator.py altogether so the headers folding no longer changes when accessing the whole message at once
multipart/signed→ ruins signing #99533