Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mail app: BAD UID FETCH: Invalid arguments. #131

Closed
icgood opened this issue Apr 24, 2022 · 0 comments · Fixed by #132
Closed

Mail app: BAD UID FETCH: Invalid arguments. #131

icgood opened this issue Apr 24, 2022 · 0 comments · Fixed by #132

Comments

@icgood
Copy link
Owner

icgood commented Apr 24, 2022

Observed in logs using macOS Mail app:

DEBUG:pymap.imap:076ba983f9e04785823144c89371ef66 -->| 8.1049 UID FETCH 265 (BODY.PEEK[1]<208.78> BODY.PEEK[2]<2027.77>)
DEBUG:pymap.imap:076ba983f9e04785823144c89371ef66 <--| 8.1049 BAD UID FETCH: Invalid arguments.
icgood added a commit that referenced this issue May 7, 2022
@icgood
Fix the incorrect fetch partial parsing
3cf851e 
Fix #131

The original implementation interpreted the partial fetch arguments as
a start and end octet, but the RFC states they are a start octet and a
length. This also causes incorrect parsing failures because there was a
check that the first number was less than the second number, which does
not make sense with corrected assumptions.
@icgood icgood mentioned this issue May 7, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix the incorrect fetch partial parsing icgood/pymap
1 participant
@icgood