[2.7] bpo-33336: Legalize MOVE command (GH-6569)#8370
[2.7] bpo-33336: Legalize MOVE command (GH-6569)#8370mcepl wants to merge 3 commits intopython:2.7from mcepl:33336_legalize_move_command_py27
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. When your account is ready, please add a comment in this pull request Thanks again for your contribution, we look forward to reviewing it! |
|
This is wrong, I have already signed CLA (see the master PR). |
|
I close this PR. I prefer to use miss-inlgton bot to generate backports PR to get "(cherry picked from commit XXX)" in the commit message. |
When running
I get an error "Unknown IMAP4 UID command: MOVE". The problem is that
imaplibcontains a list Commands of the permitted IMAP commands, and MOVE is not included, even though it is perfectly legal (and quite widely supported) command according to RFC-6851.@vstinner , @warsaw
https://bugs.python.org/issue33336