send: refuse replies no remote recipient host can accept - #36
Merged
Conversation
Per SPEC §10.3 a host rejects a reply whose parent it has not stored (code 6). Found live: chain replies to a domain whose copy of the parent never arrived bounce there with no feedback to the sender. On send of a draft with pid, verify each remote recipient domain against the parent's recorded delivery: refuse with 409 (naming the domains and the add-to / new-thread remedy) when the parent was never addressed to the domain or every delivery attempt there concluded in rejection. Parents still in flight pass — sequencing in-flight chains is the host's outbound concern (fmsgd, tracked separately) — as does the parent's originating domain, which retains its own outgoing messages. 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.
Per SPEC §10.3 a host rejects a reply whose parent it has not stored (code 6). Found live: chain replies to a domain whose copy of the parent never arrived bounce there with no feedback to the sender. On send of a draft with pid, verify each remote recipient domain against the parent's recorded delivery: refuse with 409 (naming the domains and the add-to / new-thread remedy) when the parent was never addressed to the domain or every delivery attempt there concluded in rejection. Parents still in flight pass — sequencing in-flight chains is the host's outbound concern (fmsgd, tracked separately) — as does the parent's originating domain, which retains its own outgoing messages.