mailsec: honor banner action wire contract - #347
Merged
Conversation
lcbill
approved these changes
Aug 29, 2026
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.
Summary
banner_htmlfieldbanner_messageandunbanner_messageaction namesWhy
The Python client advertised
apply_banner/remove_bannerand sent HTML underbanner. The public API forwardsbanner_html, while mailsec acceptsbanner_message/unbanner_message, so a live P0 capability check through the supported public route could not exercise the provider implementation correctly.Validation
python -m compileall -q limacharliegit diff --checkNo deployment or live provider mutation was performed.