A Cloudflare Email Worker is programmable inbound code. It is not a searchable company mailbox. If you pointed MX at a Worker and then asked why last month’s support thread cannot be found, the architecture is doing what it was designed to do: process and route mail; it does not provide a complete searchable mailbox by default.
Use a Worker when you want to build an inbound processing function. Workers can persist messages through storage integrations; you must implement history, search, access control, and retention yourself. Use a hosted mailbox when a human or an approved assistant must read history, star a thread, and send from the same domain. Use one deliberately configured inbound routing path per domain. A hybrid needs explicit forwarding, storage, or webhook integration; publishing unrelated MX sets does not duplicate mail.
What an Email Worker actually is
Cloudflare Email Service splits inbound routing from outbound sending. The inbound pipeline is SMTP receipt → authentication checks → rule match → forward, Worker, or drop. An Email Worker exposes an email(message, env, ctx) handler. That handler is code-shaped inbound, not webmail.
export default {
async email(message, env, ctx) {
// parse, forward, reply, or reject — this is not an inbox
if (message.to.includes('inbound+receipts@')) {
// write to a billing table, then drop or forward
}
}
}Public Cloudflare docs describe inbound message size around 25 MiB, routing-rule and destination-address account limits, and Workers Free CPU limits that can fail heavy handlers with EXCEEDED_CPU. Wrangler can bind inbound addresses for Worker routing rules. None of that creates IMAP, a Sent folder humans share, or MCP OAuth to a company mailbox.
Cloudflare Email Sending is a separate outbound product. Do not treat its quotas as Arawa Mail facts. Arawa Mail’s documented product surface provides mailboxes and a sending API. This comparison describes user-facing capabilities rather than making claims about its underlying infrastructure.
What a real mailbox is
Arawa Mail onboards a Cloudflare zone so it can publish MX for inbound and DKIM, SPF, and MAIL FROM for outbound. After receiving and sending are active, users get a mailbox with Inbox, Search, Sent, Drafts, Starred, Archive, Spam, and Trash. API-originated mail lands in Sent so admins can see outbound activity.
MCP can search, read, send, archive, and trash one approved mailbox. It cannot administer domains, manage drafts or spam, or download attachments. MCP talks to a mailbox, not to a Worker runtime.
Mailbox sending is rate limited per account. Application mail should use an API key. Humans and assistants still need the mailbox when they must own the From address and keep history. See Give agents a mailbox, not just an API key and Connect an AI assistant (MCP).
How we analyzed this
This is an architecture split, not a feature-price comparison. Product comparison lives on ArawaMail vs Cloudflare Email Service. Domain OAuth and DNS activation live in How to Connect a Cloudflare Domain to ArawaMail. Record shapes live in ArawaMail DNS Records. Here the only question is: who owns MX, and what can you search after the message is accepted?
Decision table: Worker, forwarder, or mailbox
| Need | Email Worker | Routing forwarder | Hosted mailbox |
|---|---|---|---|
| Parse receipts into a table | Yes | Weak | No, unless you also run app code |
| Search last month’s support thread | Only if you build storage and search | Only in the destination inbox | Yes |
| Shared Sent and drafts | No | No company Sent | Yes |
| IMAP / webmail for a five-person team | No | No | Yes |
| MCP on an approved mailbox | Custom MCP implementation required | No | Yes |
| Personal Gmail dump of hello@ | Overkill | Enough | Better if you need history |
| Outbound from the same domain | Separate sending product | Reply lives wherever Gmail sent it | Mailbox + HTTP API |
When a forwarder is enough
A Cloudflare routing forwarder is an address rule, not a company system of record. Forwarding hello@ to a founder’s Gmail works until someone asks for last quarter’s vendor thread and the only copy sits in one personal Sent folder. That gap is the same problem described in Email Forwarding vs Mailbox Hosting.
MX and hybrid routing need an explicit design
Arawa Mail warns when existing MX points elsewhere before receiving activation. Inbound Email Workers run through Cloudflare routing. Activating a different receiving configuration can replace the existing MX path. If MX never pointed at Arawa Mail, Arawa Mail does not store the Cloudflare-routed messages. A supported forwarding or application integration can connect stages, but verify exactly where mail is stored, how authentication survives forwarding, and which service accepts each address. Do not expect mixed MX records to deliver a copy to both.
Good Worker use: inbound+receipts@ on an address you do not need to search as mail, parsed into billing, then dropped or forwarded. Good mailbox use: support@ that three people search, star, and answer, with MCP drafts a human reviews before send. Hybrid anti-pattern: mixing two independent MX configurations and expecting both systems to store every message. Separate subdomains can have separate MX configurations.
For team inboxes and devices, start from Business Email and IMAP vs POP3. Connect-device hostnames belong in current product docs, not in this article.
Pick one MX owner
If the inbound object is a function, use a Worker; search requires a separate storage and indexing design. If the inbound object is a conversation, give the domain a mailbox and let Arawa Mail publish MX. Cloudflare Sending SMTP on port 465 is not a substitute for that mailbox. One owner. One Sent folder. One place an assistant is allowed to read.
FAQ
Can an Email Worker replace hello@ for a five-person team?
No. The team will lose shared search, Sent, drafts, and a mailbox MCP can be scoped to.
If I route MX to Cloudflare Workers, can Arawa Mail still receive?
Not on that same MX path. Receiving follows whoever publishes MX.
Where do sent replies live if only a Worker exists?
Wherever the reply code or the forwarded destination sent them. There is no company Sent folder.
Can a Worker expose MCP tools?
A developer can build an MCP server using Workers and storage. That is custom software; an Email Worker alone does not provide Arawa Mail’s mailbox-scoped OAuth or tools.
Should I use a Worker in front of Arawa Mail?
Usually no. Pick one inbound owner.
Sources and review
Reviewed on 3 October 2026. Product behavior follows the linked documentation; examples are illustrative.