IMAP "semi-asynchronous" backwards search in batches #7825
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.
IMAP searches can take a very long time if you have a large inbox. In my inbox it is common that the HTTP timeout occurs before the search has finished. This feature is intended to resolve this problem and would greatly enhance user experience, in my opinion.
If you turn on "backwards" search, the IMAP search command will use an RFC 3501 message sequence range to search the n most recent messages in the folder. Once the web client receives a reply, it will send a search request for the next n emails in the folder. I have hardcoded n to 500 for body and full text searches and 5000 for other searches.
Open issues:
Backwards search with threads listing is still buggy. The threads implementation looks complicated and I have run out of time to study it.