feat(email): Add secure reply routing with HMAC signatures #27980
Conversation
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
agents-git-bot
bot
requested review from
a team,
elithrar,
irvinebroque,
rita3ko,
thomasgauvin,
threepointone and
whoiskatrin
as code owners
github-actions
bot
added
product:agents
github-actions
bot
assigned
elithrar,
irvinebroque,
rita3ko,
thomasgauvin,
threepointone and
whoiskatrin
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
agents-git-bot
bot
force-pushed
the
sync-docs-pr-811
branch
from
36a017e to
94316a4
Compare
Sync documentation for PR #811 from cloudflare/agents repository. This PR introduces secure email reply routing with HMAC-SHA256 signed headers: **New Features:** - createSecureReplyEmailResolver - verifies HMAC-SHA256 signatures before routing - signAgentHeaders - manually sign agent routing headers - replyToEmail secret parameter - automatically signs outbound email headers - onNoRoute callback - handle emails that don't match any routing rule **Breaking Changes:** - createHeaderBasedEmailResolver removed (security vulnerability - trusted attacker-controlled headers) - EmailSendOptions type removed (unused) **Documentation Changes:** - Added comprehensive email-routing.mdx guide in /agents/guides/ - Updated agent-class.mdx to simplify email example and add cross-reference Source PR: cloudflare/agents#811 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
agents-git-bot
bot
force-pushed
the
sync-docs-pr-811
branch
from
94316a4 to
8f9546f
Compare
agents-git-bot
bot
changed the title
Synced from cloudflare/agents PR #811 - Add comprehensive email routing guide with secure reply flows - Document HMAC-SHA256 signature verification - Add resolver comparison and usage patterns - Update agent-class.mdx to reference detailed guide - Include API reference for all email routing functions Breaking changes documented: - createHeaderBasedEmailResolver removed - EmailSendOptions type removed New features documented: - createSecureReplyEmailResolver with signature verification - signAgentHeaders for manual header signing - Automatic header signing in replyToEmail - onInvalidSignature callback for debugging - onNoRoute callback for unroutable emails Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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
Sync documentation for PR #811 from cloudflare/agents repository.
This PR introduces secure email reply routing for Agents, preventing unauthorized routing of emails to arbitrary agent instances through header spoofing.
Changes
Security
createHeaderBasedEmailResolvernow throws an error - it trusted attacker-controlled headers for routingcreateSecureReplyEmailResolververifies HMAC-SHA256 signatures before routing repliesNew APIs
createSecureReplyEmailResolver- Secure resolver with signature verificationsignAgentHeaders- Manual header signing for external email servicesreplyToEmailsigning - Automatic header signing for outbound emailsonNoRoutecallback - Callback for handling unroutable emailsOptions & Callbacks
maxAgeoption - Configure signature expiration (default: 30 days)onInvalidSignature- Debug callback with failure reasonsonNoRoute- Handle emails that don't match any routing ruleCleanup
EmailSendOptionstypeFiles Changed
src/content/docs/agents/guides/email-routing.mdxsrc/content/docs/agents/concepts/agent-class.mdxBreaking Changes
createHeaderBasedEmailResolverremoved - Now throws an error with migration guidanceEmailSendOptionsremoved - Was unusedMigration
How It Works
replyToEmail()signs headers with HMAC-SHA256 + timestampcreateSecureReplyEmailResolververifies signature and checks expirationreplyToEmail()requires a secret (or explicitnull)Source