fix(activesync): skip missing messages in Find results#46
Open
TDannhauer wants to merge 1 commit into
Open
Conversation
Fetch each hit before encoding and ignore Horde_Exception_NotFound so a deleted or stale search result no longer aborts the entire Find response with HTTP 500.
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
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.
Skip missing messages in Find results
Summary
Prevents a single unavailable mailbox hit from failing the entire EAS 16.0 Find response with HTTP 500.
Problem
Find searches IMAP and then fetches each hit via
itemOperationsFetchMailbox()to build preview properties (Subject, From, Preview, etc.). If one message is no longer available when fetched — deleted, moved, or present only in a stale search cache entry —getMessage()throwsHorde_Exception_NotFound(Nicht gefunden). That exception propagated out of_encodeResult()and aborted the whole Find response, even when other hits were valid.Observed in production: two ESET messages encoded successfully; a third stale UID caused HTTP 500 and a truncated WBXML buffer.
Solution
Find:ResultWBXML element.Horde_Exception_NotFound, log at info level, and skip that hit._encodeResult(); only successfully encoded hits count towardFind:Range.Find:Totalstill reflects the IMAP search count;Find:Rangereflects the number of results actually returned.Files changed
lib/Horde/ActiveSync/Request/Find.phpTest plan
Find: message … no longer available, skipping result.Find:Rangematches the number of encoded results when some hits are skippedSuggested commit message
Author
Torben Dannhauer torben@dannhauer.de