cloudflare-email-routing

Email routing with Cloudflare Workers involves enabling Email Routing in Cloudflare, verifying a destination address, installing postal-mime and mimetext dependencies, creating a Worker to handle inbound emails, and deploying via Wrangler. Configure MX records to point to Cloudflare and set up SPF and DKIM for security.

Yes. Use the postal-mime library to parse inbound email content within Workers, then apply allowlists and blocklists to route or reject messages. The EmailMessage binding provides access to incoming mail, enabling custom filtering logic before forwarding or processing.

Use the send_email binding in your Worker to send outbound emails to verified destination addresses. Compose messages with mimetext, then invoke the binding to deliver mail. Verified destinations must be set up in Cloudflare before deployment.

Set up MX records to route mail to Cloudflare, SPF records to authorize Cloudflare as a sender, and DKIM records to sign outbound emails. These DNS prerequisites ensure email deliverability and prevent spoofing when sending from Workers.

Production-ready patterns in this Skill address 8 common issues, including improper DNS configuration, missing DKIM setup, unverified destination addresses, and parsing errors. Review troubleshooting guidance to avoid deployment failures and ensure reliable email handling.

Yes. The ForwardableEmailMessage binding enables forwarding received emails and composing replies within Workers. Combine with mimetext for message composition and the send_email binding to route replies back to senders or other destinations.