send: don't block replies on third-party parent deliveries - #39
Merged
Conversation
A received parent's recipient rows for other domains carry fmsgd's local sentinel response codes (-2 recorded from an exchange — another host's delivery; -1 no response, retryable). The reply pre-flight treated any recorded code as a failed delivery, so replying-all to a received multi-domain message was always refused with 409 even though the originating host had delivered the parent everywhere. Summarise the sentinels distinctly: -2 marks the domain as another host's delivery (allowed — the wire's parent-not-found rejection stays the arbiter) and -1 as pending. Only genuinely recorded delivery failures by this host still block. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
A received parent's recipient rows for other domains carry fmsgd's local sentinel response codes (-2 recorded from an exchange — another host's delivery; -1 no response, retryable). The reply pre-flight treated any recorded code as a failed delivery, so replying-all to a received multi-domain message was always refused with 409 even though the originating host had delivered the parent everywhere.
Summarise the sentinels distinctly: -2 marks the domain as another host's delivery (allowed — the wire's parent-not-found rejection stays the arbiter) and -1 as pending. Only genuinely recorded delivery failures by this host still block.