-
-
Notifications
You must be signed in to change notification settings - Fork 33k
gh-78319: add UTF8 marker per RFC #9436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@gordonmessmer tests are failing (see |
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
36fd655
to
41c490e
Compare
I'll look at it again, yes. I'm getting odd results from updated tests, so some additional work is still needed... |
c116b76
to
633ad44
Compare
Tests look like they're passing, but trying this on a live IMAP server fails, because the server actually receives:
... when Sam suggested that it should receive:
But that's probably a larger bug in the imaplib module, and not directly related to this change. |
I've asked Sam to chime in. The RFC calls those arguments optional. Based on its behavior, it seems that Courier expects them to be specified as NIL when they are not provided, rather than left out entirely. |
I added a commit for consideration. Transforming None to "NIL" is RFC-compliant (which is consistent with the intent of this PR). Tests pass, and this works with Courier IMAP. |
Please let me know if there's anything I can do to help move this forward. |
This PR is stale because it has been open for 30 days with no activity. |
This PR is stale because it has been open for 30 days with no activity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. 👍
Thanks @gordonmessmer for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
Make UTF8 support for the IMAP APPEND command RFC 6855 compliant. (cherry picked from commit 408154d) Co-authored-by: Gordon Messmer <[email protected]>
Make UTF8 support for the IMAP APPEND command RFC 6855 compliant. (cherry picked from commit 408154d) Co-authored-by: Gordon Messmer <[email protected]>
GH-139406 is a backport of this pull request to the 3.14 branch. |
GH-139407 is a backport of this pull request to the 3.13 branch. |
…-139407) gh-78319: Fix implementation of IMAP APPEND UTF8 (GH-9436) Make UTF8 support for the IMAP APPEND command RFC 6855 compliant. (cherry picked from commit 408154d) Co-authored-by: Gordon Messmer <[email protected]>
|
…-139406) Make UTF8 support for the IMAP APPEND command RFC 6855 compliant. (cherry picked from commit 408154d) Co-authored-by: Gordon Messmer <[email protected]>
This change implements RFC 6855 UTF8 APPEND per guidance from Sam Varshavchik:
https://bugs.python.org/issue34138
https://bugs.python.org/issue34138