Cloudflare Email Delivery

Running email for an ERP usually means SMTP credentials, IMAP polling, and a mail provider that may or may not deliver. Cloudflare Email Delivery replaces all of that for Frappe and ERPNext sites whose domains live on Cloudflare. Outgoing mail goes straight to the Cloudflare Email Sending API, and incoming mail arrives from the Cloudflare Email Relay as a signed HTTPS push into Frappe's own inbound pipeline. It's the Frappe adapter in Avunu's Cloudflare Email suite.

Features

• No SMTP to manage. An Email Domain holds a Cloudflare account ID and API token instead of server settings, and saving verifies the token.

• No IMAP polling. Each incoming account gets a webhook URL and secret. Messages are verified by HMAC signature and handed to Frappe's InboundMail, so Append To, auto-replies, attachments, and notifications behave as usual.

• Threading that survives Cloudflare. Frappe keeps its own Message-ID in References, so replies still land on the right document.

• Rate limits and transient errors are retried; bounces Cloudflare rejects up front fail the queue entry with a reason.

• Mixed setups work: accounts on other domains keep SMTP or Frappe Mail.

Getting started

You need Frappe 16, a Cloudflare account on the Workers Paid plan, and a domain onboarded for Email Sending and Email Routing. The README walks through sending, receiving, and the webhook contract.