--- title: Email Service Changelog image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png --- > Documentation Index > Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt > Use this file to discover all available pages before exploring further. [Skip to content](#%5Ftop) # Changelog New updates and improvements at Cloudflare. [ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) Email Service ![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) Jul 17, 2026 1. ### [Preview sent emails in the Activity log](https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-17-email-message-preview/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) You can now preview the content of sent emails directly from the Email Service Activity log. Expand a sent email and open the new **Preview** section to inspect the message as it was sent, across tabs for the rendered **HTML** body, the **Text** body, the **Headers**, the **Attachments**, and the full **Raw** [RFC 5322 ↗](https://datatracker.ietf.org/doc/html/rfc5322) source. ![The rendered HTML preview of a sent email in the Email Service Activity log](https://edgetunnel-b2h.pages.dev/_astro/email-message-preview.Bj6Lk8Y6_ZQJVjF.webp) Previously, the Activity log surfaced delivery and authentication metadata but not the message content, making rendering and content issues harder to debug. Message preview closes that gap. To make messages previewable, turn on **Email preview** in your sending domain's settings. Previews cover messages sent while the setting is turned on and are retained for about seven days. Sending domains onboarded on or after 2026-07-02 have **Email preview** turned on automatically. ![The Email preview setting in a sending domain's settings](https://edgetunnel-b2h.pages.dev/_astro/email-preview-setting.XEd1WIiO_Z1Vc9Dv.webp) Refer to [Email logs](https://edgetunnel-b2h.pages.dev/email-service/observability/logs/#message-preview) for more information. Jul 15, 2026 1. ### [Subscribe to Email Sending events with Queues](https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-15-event-subscriptions/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/)[ Queues ](https://edgetunnel-b2h.pages.dev/queues/) You can now subscribe to **[Email Sending](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/) events** through [Queues event subscriptions](https://edgetunnel-b2h.pages.dev/queues/event-subscriptions/) and receive outbound transactional email lifecycle events on a queue. Each subscription is scoped to one sending domain — either the zone apex, such as `example.com`, or a verified sending subdomain, such as `send.example.com`. Six event types are published: `message.delivered`, `message.deferred`, `message.bounced`, `message.failed`, `message.rejected`, and `message.complained`. Use them to track deliverability, react to bounces and complaints, and drive suppression or retry logic. Email Routing events are not published on this source. Each event includes the message details, delivery status, and SMTP response: ```json { "type": "cf.email.sending.message.delivered", "source": { "type": "email.sending", "zoneId": "023e105f4ecef8ad9ca31a8372d0c353", "domain": "example.com" }, "payload": { "messageId": "0101018f7d0c4d9a-msg-deadbeef", "recipient": "user@example.net", "terminal": true, "delivery": { "status": "delivered", "smtpStatusCode": "250" } } } ``` Refer to [Event subscriptions](https://edgetunnel-b2h.pages.dev/email-service/platform/event-subscriptions/) to see all event types and example payloads. Jun 08, 2026 1. ### [Authenticated SMTP submission now available in beta](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-08-smtp-submission/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) You can now send emails through **Cloudflare Email Service** using authenticated [SMTP submission](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/smtp/) on `smtp.mx.cloudflare.net:465`. SMTP joins the [REST API](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/rest-api/) and the [Workers binding](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/workers-api/) as a third way to send transactional email — useful for existing applications that already speak SMTP and language-native SMTP libraries (Nodemailer, `smtplib`, PHPMailer, JavaMail). | Setting | Value | | -------- | --------------------------------------------------------------------------------- | | Host | smtp.mx.cloudflare.net | | Port | 465 (implicit TLS) | | AUTH | PLAIN or LOGIN | | Username | api\_token | | Password | A Cloudflare API token (account-owned or user-owned) with **Email Sending: Edit** | Submissions enter the same delivery pipeline as the REST API and Workers binding: identical [limits](https://edgetunnel-b2h.pages.dev/email-service/platform/limits/), automatic DKIM and ARC signing, and shared dashboard logs. Send your first email with a single command: ```sh curl --ssl-reqd \ --url "smtps://smtp.mx.cloudflare.net:465" \ --user "api_token:" \ --mail-from "welcome@yourdomain.com" \ --mail-rcpt "user@example.com" \ --upload-file mail.txt ``` Refer to the [SMTP reference](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/smtp/) for authentication details, response codes, and language-specific examples. May 28, 2026 1. ### [Send emails with named recipient addresses](https://edgetunnel-b2h.pages.dev/changelog/post/2026-05-28-named-email-recipients/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) You can now send emails with display names on recipient addresses in addition to the existing `from` support. Pass an object with `email` and an optional `name` field for `to`, `cc`, `bcc`, `replyTo`, or `from`: * [ JavaScript ](#tab-panel-2959) * [ TypeScript ](#tab-panel-2960) **src/index.js** ```js export default { async fetch(request, env) { const response = await env.EMAIL.send({ from: { email: "support@example.com", name: "Support Team" }, to: { email: "jane@example.com", name: "Jane Doe" }, cc: [ "manager@company.com", { email: "team@company.com", name: "Engineering Team" }, ], subject: "Welcome!", html: "

Thanks for joining!

", text: "Thanks for joining!", }); return Response.json({ messageId: response.messageId }); }, }; ``` **src/index.ts** ```ts export default { async fetch(request, env): Promise { const response = await env.EMAIL.send({ from: { email: "support@example.com", name: "Support Team" }, to: { email: "jane@example.com", name: "Jane Doe" }, cc: [ "manager@company.com", { email: "team@company.com", name: "Engineering Team" }, ], subject: "Welcome!", html: "

Thanks for joining!

", text: "Thanks for joining!", }); return Response.json({ messageId: response.messageId }); }, } satisfies ExportedHandler; ``` Plain strings remain fully supported for backward compatibility, and you can mix strings and named objects in the same array. Refer to the [Workers API](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/workers-api/) and [REST API](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/rest-api/) documentation for full request examples. Apr 16, 2026 1. ### [Email Sending now in public beta](https://edgetunnel-b2h.pages.dev/changelog/post/2026-04-16-email-sending-public-beta/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) **[Email Sending](https://edgetunnel-b2h.pages.dev/email-service/api/send-emails/)** is now in public beta. Send transactional emails directly from Workers (`env.EMAIL.send()`) or the REST API, with support for HTML, plain text, attachments, inline images, and custom headers. Email Sending joins [Email Routing ↗](https://blog.cloudflare.com/introducing-email-routing/) under the new **Cloudflare Email Service** — a single service for sending and receiving email on the Cloudflare developer platform. Send an email from a Worker in a few lines of code: * [ JavaScript ](#tab-panel-2957) * [ TypeScript ](#tab-panel-2958) **src/index.js** ```js export default { async fetch(request, env) { const response = await env.EMAIL.send({ from: "notifications@yourdomain.com", to: "user@example.com", subject: "Order confirmed", html: "

Your order has been confirmed

", text: "Your order has been confirmed.", }); return Response.json({ messageId: response.messageId }); }, }; ``` **src/index.ts** ```ts export default { async fetch(request, env): Promise { const response = await env.EMAIL.send({ from: "notifications@yourdomain.com", to: "user@example.com", subject: "Order confirmed", html: "

Your order has been confirmed

", text: "Your order has been confirmed.", }); return Response.json({ messageId: response.messageId }); }, } satisfies ExportedHandler; ``` Email Service also integrates with the [Agents SDK](https://edgetunnel-b2h.pages.dev/agents/), giving your agents a native `onEmail` hook to receive, process, and reply to emails. Combined with the new [Email MCP server ↗](https://github.com/cloudflare/mcp-server-cloudflare) and Wrangler CLI email commands, any agent can send email regardless of where it runs. Start sending and receiving emails from Workers and agents today. Email Sending is available on the Workers paid plan. Refer to the [Email Service documentation](https://edgetunnel-b2h.pages.dev/email-service/) to get started. Jul 21, 2025 1. ### [Subaddressing support in Email Routing](https://edgetunnel-b2h.pages.dev/changelog/post/2025-07-21-subaddressing/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) Subaddressing, as defined in [RFC 5233 ↗](https://www.rfc-editor.org/rfc/rfc5233), also known as plus addressing, is now supported in Email Routing. This enables using the "+" separator to augment your custom addresses with arbitrary detail information. Now you can send an email to `user+detail@example.com` and it will be captured by the `user@example.com` 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](https://edgetunnel-b2h.pages.dev/email-service/api/route-emails/email-handler/) or an [Agent application ↗](https://github.com/cloudflare/agents/tree/main/examples/email-agent). Customers can use this feature to dynamically add context to their emails, such as tracking the source of an email or categorizing emails without needing to create multiple custom addresses. ![Subaddressing](https://edgetunnel-b2h.pages.dev/_astro/subaddressing.x65bljxx_Z2W6LN.webp) Check our [Developer Docs](https://edgetunnel-b2h.pages.dev/email-service/configuration/email-routing-addresses/#subaddressing) to learn how to enable subaddressing in Email Routing. Jun 30, 2025 1. ### [Mail authentication requirements for Email Routing](https://edgetunnel-b2h.pages.dev/changelog/post/2025-06-30-mail-authentication/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) The Email Routing platform supports [SPF ↗](https://datatracker.ietf.org/doc/html/rfc7208) records and [DKIM (DomainKeys Identified Mail) ↗](https://en.wikipedia.org/wiki/DomainKeys%5FIdentified%5FMail) signatures and honors these protocols when the sending domain has them configured. However, if the sending domain doesn't implement them, we still forward the emails to upstream mailbox providers. Starting on July 3, 2025, we will require all emails to be authenticated using at least one of the protocols, SPF or DKIM, to forward them. We also strongly recommend that all senders implement the DMARC protocol. If you are using a Worker with an Email trigger to receive email messages and forward them upstream, you will need to handle the case where the forward action may fail due to missing authentication on the incoming email. SPAM has been a long-standing issue with email. By enforcing mail authentication, we will increase the efficiency of identifying abusive senders and blocking bad emails. If you're an email server delivering emails to large mailbox providers, it's likely you already use these protocols; otherwise, please ensure you have them properly configured. Apr 08, 2025 1. ### [Local development support for Email Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-local-development/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) Email Workers enables developers to programmatically take action on anything that hits their email inbox. If you're building with Email Workers, you can now test the behavior of an Email Worker script, receiving, replying and sending emails in your local environment using `wrangler dev`. Below is an example that shows you how you can receive messages using the `email()` handler and parse them using [postal-mime ↗](https://www.npmjs.com/package/postal-mime): **TypeScript** ```ts import * as PostalMime from "postal-mime"; export default { async email(message, env, ctx) { const parser = new PostalMime.default(); const rawEmail = new Response(message.raw); const email = await parser.parse(await rawEmail.arrayBuffer()); console.log(email); }, }; ``` Now when you run `npx wrangler dev`, wrangler will expose a local `/cdn-cgi/handler/email` endpoint that you can `POST` email messages to and trigger your Worker's `email()` handler: ```bash curl -X POST 'http://localhost:8787/cdn-cgi/handler/email' \ --url-query 'from=sender@example.com' \ --url-query 'to=recipient@example.com' \ --header 'Content-Type: application/json' \ --data-raw 'Received: from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for ; Tue, 27 Aug 2024 15:50:20 +0000 From: "John" Reply-To: sender@example.com To: recipient@example.com Subject: Testing Email Workers Local Dev Content-Type: text/html; charset="windows-1252" X-Mailer: Curl Date: Tue, 27 Aug 2024 08:49:44 -0700 Message-ID: <6114391943504294873000@ZSH-GHOSTTY> Hi there' ``` This is what you get in the console: ```json { "headers": [ { "key": "received", "value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for ; Tue, 27 Aug 2024 15:50:20 +0000" }, { "key": "from", "value": "\"John\" " }, { "key": "reply-to", "value": "sender@example.com" }, { "key": "to", "value": "recipient@example.com" }, { "key": "subject", "value": "Testing Email Workers Local Dev" }, { "key": "content-type", "value": "text/html; charset=\"windows-1252\"" }, { "key": "x-mailer", "value": "Curl" }, { "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" }, { "key": "message-id", "value": "<6114391943504294873000@ZSH-GHOSTTY>" } ], "from": { "address": "sender@example.com", "name": "John" }, "to": [{ "address": "recipient@example.com", "name": "" }], "replyTo": [{ "address": "sender@example.com", "name": "" }], "subject": "Testing Email Workers Local Dev", "messageId": "<6114391943504294873000@ZSH-GHOSTTY>", "date": "2024-08-27T15:49:44.000Z", "html": "Hi there\n", "attachments": [] } ``` Local development is a critical part of the development flow, and also works for sending, replying and forwarding emails. See [our documentation](https://edgetunnel-b2h.pages.dev/email-service/local-development/routing/) for more information. Mar 12, 2025 1. ### [Threaded replies now possible in Email Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-03-12-reply-limits/) [ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/) We’re removing some of the restrictions in Email Routing so that AI Agents and task automation can better handle email workflows, including how Workers can [reply](https://edgetunnel-b2h.pages.dev/email-service/api/route-emails/email-handler/#reply-to-emails) to incoming emails. It's now possible to keep a threaded email conversation with an [Email Worker](https://edgetunnel-b2h.pages.dev/email-service/api/route-emails/email-handler/) script as long as: * The incoming email has to have valid [DMARC ↗](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/). * The email can only be replied to once in the same `EmailMessage` event. * The recipient in the reply must match the incoming sender. * The outgoing sender domain must match the same domain that received the email. * Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops. Here's an example of a Worker responding to Emails using a Workers AI model: **AI model responding to emails** ```ts import PostalMime from "postal-mime"; import { createMimeMessage } from "mimetext"; import { EmailMessage } from "cloudflare:email"; export default { async email(message, env, ctx) { const email = await PostalMime.parse(message.raw); const res = await env.AI.run("@cf/meta/llama-2-7b-chat-fp16", { messages: [ { role: "user", content: email.text ?? "", }, ], }); // message-id is generated by mimetext const response = createMimeMessage(); response.setHeader("In-Reply-To", message.headers.get("Message-ID")!); response.setSender("agent@example.com"); response.setRecipient(message.from); response.setSubject("Llama response"); response.addMessage({ contentType: "text/plain", data: res instanceof ReadableStream ? await new Response(res).text() : res.response!, }); const replyMessage = new EmailMessage( "", message.from, response.asRaw(), ); await message.reply(replyMessage); }, } satisfies ExportedHandler; ``` See [Reply to emails from Workers](https://edgetunnel-b2h.pages.dev/email-service/api/route-emails/email-handler/#reply-to-emails) for more information. ```json {"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/product/email-service/#page","headline":"Email Service Changelog | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/product/email-service/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/cf-twitter-card.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}} ```