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.

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

UID passed in and UID received are not equal #255

Open
duypham9895 opened this issue Jul 21, 2021 · 1 comment
Open

UID passed in and UID received are not equal #255

duypham9895 opened this issue Jul 21, 2021 · 1 comment

Comments

@duypham9895
Copy link

Screen Shot 2021-07-21 at 09 33 17

I was passed the range of UID 1:* then I received the range of UID 35:*. I met a lot of problems with them. Can anybody explain why, please. Thank you for your time & support.

@cuuupid
Copy link

cuuupid commented Aug 1, 2021

Most likely means UIDs 1-34 do not exist on the mailserver. UIDs are not continuous on the mailserver (this can cause certain bugs with mailservers, if you try to fetch a sequence of UIDs that no longer exist at all on the server it may never respond if it is configured poorly).

Please also note that * means the last known message and sequences are not strictly increasing. For example, if you fetch 68:* and the newest message on the mailserver is UID 67, this translates to 68:67 and will thus return the message with UID 67 even though it numerically precedes 68.

BTW - GMail has strict limits for IMAP operations. I highly recommend avoiding fetching 1:* or really anything above 500-1000 messages at a time or their server will misbehave. In our tests we found fetching blocks of 500 messages resulted in the most consistent behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants