Dedupe enhance x-ms-exchange-parent-message-id vs Message-ID - #542
Open
magikyyz wants to merge 1 commit into
Open
Dedupe enhance x-ms-exchange-parent-message-id vs Message-ID#542magikyyz wants to merge 1 commit into
magikyyz wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Well, is it always the case that Exchange change the message-id to a new one and signals the change with a new x-ms-exchange-parent-message-id header? |
Sorry, something went wrong.
Copy link
Copy Markdown
Author
|
Always. In the environment triggering this, mailbox gets original copy (message-id) from one host and a copy via Exchange. Exchange may be doing a redirect(?) causing the oddness. Link describes other observing same quirk. |
Sorry, something went wrong.
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.
Identical emails but sourced from alternate hosts (nicehost vs exchange) will not match and negate use of --delete2duplicates.
Example
nicehost
exchange
Change to sub header_construct allows X-MS-Exchange-Parent-Message-Id and Message-ID to match when both headers are used for comparing (--useheader Message-Id --useheader X-MS-Exchange-Parent-Message-Id)