Email Routing
Use routing rules for address-based forwarding; use an Email Worker when incoming mail needs custom processing. Fetch the linked docs before implementing APIs, DNS, configuration, or limits.
| Task | Start here |
|---|---|
| Forward incoming mail to an existing mailbox | Route emails |
| Manage addresses, verification, catch-all rules, or subaddressing | Routing rules and addresses |
| Filter, parse, reply to, or store incoming mail | Email Workers |
| Send a new outbound message | Send emails — Workers binding, REST API, or SMTP |
Forwarding requires verified destinations. Replying within an incoming email event and sending a new outbound message have different requirements; use the relevant API docs.
Reference map
- Configuration: domains, rules, deployment, and local testing.
- API: routing management and inbound/outbound operations.
- Patterns: filtering, parsing, storage, and notifications.
- Troubleshooting: authentication, delivery, and current limits.