Cloudflare Email Service resource guide for Ross Mail inbound routing, transactional email sending, domain setup, and current integration status.
Cloudflare offers useful email routing and transactional sending capabilities. This resource page documents where they fit; no Cloudflare account, sender domain, token, binding, or routing rule is connected to the app yet.
Send application notifications through a Workers binding, REST API, or authenticated SMTP after onboarding a sending domain and securing the required credentials.
Forward incoming messages to verified destinations or process them with a Cloudflare Worker. Routing is available on Free and Paid Workers plans.
Each infrastructure step needs account-level verification before the application can use it.
Decide whether Cloudflare is for transactional sending, selected inbound aliases, or both. A full user inbox requires a separate mailbox host.
Cloudflare requires a domain in its DNS account. Review the generated MX, SPF, DKIM, and DMARC records before applying any mail DNS changes.
Store the API token as a server-side secret, restrict sender addresses and recipients, and add authenticated send routes only after identity and abuse controls are ready.
Verify accepted, rejected, bounced, and forwarded messages in Cloudflare observability before marking the resource connected.