fix(imap): prevent null HIGHESTMODSEQ after initial sync#12788
Merged
ChristophWurst merged 1 commit intomainfrom Apr 22, 2026
Merged
fix(imap): prevent null HIGHESTMODSEQ after initial sync#12788ChristophWurst merged 1 commit intomainfrom
ChristophWurst merged 1 commit intomainfrom
Conversation
kesselb
approved these changes
Apr 22, 2026
Signed-off-by: Christoph Wurst <1374172+ChristophWurst@users.noreply.github.com>
ChristophWurst
force-pushed
the
fix/imap/highestmodseq-after-initial-sync
branch
from
d3f4c2d to
7980d9e
Compare
Member
Author
|
/backport ot stable5.7 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This brings back #6880 which was lost in #8968.
Having no HIGHESTMODSEQ after initial sync means that the server will report all emails as changed.
Note: accounts that were synced initially but ran into OOM at the first partial sync will stay in a OOM loop because the sync token with null was persisted before. This needs a separate fix.