-
Notifications
You must be signed in to change notification settings - Fork 2
🪲 BUG-#67: Use UID EXPUNGE in MailBox.move fallback and narrow except #76
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
407ef8d
🪲 BUG-#67: Use UID EXPUNGE in MailBox.move fallback and narrow except
FernandoCelmer b122651
❤️ TEST-#67: Add MailBox.move fallback, UIDPLUS and error-propagation…
FernandoCelmer 48a196c
🪲 BUG-#67: Also catch IMAPError in MOVE fallback (NO/BAD response)
FernandoCelmer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
[Blocking]
Problem — narrowing the
exceptfromExceptiontoimaplib.IMAP4.errorskips the most common way servers signal "MOVE not supported": a taggedNO/BADresponse.Status.state(...)translates those intoemail_profile.core.errors.IMAPError, which is not a subclass ofimaplib.IMAP4.error. So when the server repliesNO [CANNOT] MOVE not supported,IMAPErrorpropagates out ofmove()and the COPY+STORE+UID EXPUNGE fallback never runs — a regression vs. the previous bareexcept Exception.Failure scenario — Dovecot (and many others) advertise capabilities through
CAPABILITY, not through raisingimaplibprotocol errors. Callingmailbox.move(uid, "Archive")on a server without RFC 6851 will:client.uid("MOVE", ...)returns("NO", [b"MOVE not supported"])Status.stateraisesIMAPError("Command failed")except imaplib.IMAP4.errordoes not match → caller seesIMAPError, message not moved.The existing test
test_falls_back_to_copy_uid_expungemasks this because it mocksside_effect=imaplib.IMAP4.error(...)— butStatus.statewould never raise that class in production.Fix — catch both exception classes (or, better, check capabilities up-front and skip the try entirely when MOVE is unsupported):
Add a regression test that simulates
("NO", [b"MOVE not supported"])returned fromuid()(no exception raised) and asserts the COPY/STORE/UID-EXPUNGE path runs.References — RFC 3501 §6.4 (untagged
NOfor unsupported commands), RFC 6851 §3 (MOVE capability advertised viaCAPABILITY; servers without it returnNO/BAD).