Skip to content

formatting issue #23856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 22, 2025
Merged

formatting issue #23856

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/email-routing/setup/email-routing-addresses.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ You can enable subaddressing at **Email** > **Email Routing** > **Settings**.

Once enabled, you can use subaddressing with any of your custom addresses. For example, if you send an email to `[email protected]` it will be captured by the `[email protected]` custom address. The `+detail` part is ignored by Email Routing, but it can be captured next in the processing chain in the logs, an [Email Worker](/email-routing/email-workers/) or an [Agent application](https://github.com/cloudflare/agents/tree/main/examples/email-agent).

If a custom address '[email protected]` already exists, it will take precedence over '[email protected]'. This prevents breaking existing routing rules for users, and allows certain sub-addresses to be captured by a specific rule.
If a custom address `[email protected]` already exists, it will take precedence over `[email protected]`. This prevents breaking existing routing rules for users, and allows certain sub-addresses to be captured by a specific rule.

## Destination addresses

Expand Down