Answer first: Email forwarding answers “send this address’s inbound mail somewhere else.” Mailbox hosting answers “this address is a place people work from.” Forwarding-only MX does not give you a reliable send-as identity, searchable company archive, or team workspace. On ArawaMail, forwarding is a mailbox feature: a local copy stays, new mail is resent after destination verification, and each forwarded copy counts toward the monthly transactional allowance.
The founder whose customers replied to hello@ and the thread vanished
A common setup: point MX at a forwarding service, dump [email protected] into a personal Gmail, and reply from Gmail. The customer wrote to the company domain. The reply left from @gmail.com. Threading breaks. SPF and DMARC for the company domain never authorized Gmail as a sender. The next inbound message looks like a new conversation. Support history lives in one person’s personal account.
That is forwarding doing exactly what it was designed to do — relocate inbound mail — and failing at the job the founder thought they bought: a company identity people can write to and hear back from.
Forwarding vs mailbox hosting at a glance
| Job | Forwarding-only | Hosted mailbox |
|---|---|---|
| Receive mail at custom domain | Yes, if MX points at the forwarder | Yes, after receiving is active |
| Keep a searchable copy on the domain | Usually no on pure forwarders | Yes — inbox and sent stay until deleted, subject to storage |
| Send as the custom-domain address | Only if the destination provider is authorized in SPF/DKIM | Yes, after outbound sending is enabled |
| Team access without a shared personal inbox | No | Each person signs in with email + password |
| Replies stay on-brand | Often break (reply from gmail.com) | Compose and send from the mailbox |
| IMAP / device access | Depends on the destination inbox | Documented IMAP 993 and SMTP 465 (use live hostnames from the app, not placeholders) |
When forwarding-only is enough
A one-person site that only needs hello@ to land in a personal Gmail — and will never send as that address — can live on forwarding. Use it when:
- You only need inbound capture, not a send-as identity.
- There is no team that must search a shared history.
- Receipts and product mail already leave from a properly authenticated transactional path, not from the forwarded address.
Even then, changing MX to a forwarder routes new inbound mail only. It does not create a send-as identity unless the destination provider is in SPF and signs aligned DKIM. Simple forwarding often breaks SPF alignment for the original domain. ARC can help some forwarding paths; it is not a substitute for a mailbox that sends as the domain.
When you need mailbox hosting
A two-person studio that needs Sent history, search, and mobile access needs a mailbox. A product team that wants receipts from billing@ and human replies on the same domain needs a mailbox plus API sending — not a forwarder. Choose hosting when:
- Customers must be able to reply to a real address (see receipts should come from an address people can reply to).
- More than one person must see the same thread without sharing a Gmail password.
- You need folders, drafts, archive, and search on the company domain.
- You will send as the address, not only receive it.
ArawaMail mailbox users sign in with email and password. Sending from the mailbox requires outbound sending active on the domain. Mailbox sending is rate limited. Storage on public pricing is 1 / 10 / 50 GB (Free / Pro / Business). Inbox and sent mail remain until deleted, subject to that storage. Calendar and contacts are listed on the pricing table.
How ArawaMail forwarding actually works
ArawaMail forwarding is not a replacement for the mailbox. It is a feature of the mailbox. Documented behavior from Email Accounts:
- New inbound mail is sent to a verified destination and a local copy is kept.
- Destinations must be verified within 24 hours. Forwarding starts only after verification.
- Messages are resent from the local mailbox with Reply-To set to the original sender.
- Existing stored messages are not forwarded.
- A forwarding failure never removes the local copy.
- Forwarded copies count toward the monthly transactional allowance.
- Destinations per mailbox: Free 1 / Pro 5 / Business 10.
If a plan is downgraded, the oldest verified destinations stay active up to the new limit. Extra destinations remain listed as inactive at the current plan limit.
Do not conflate forwarding with catch-all. Catch-all is a routing order for unknown local-parts (exact mailbox → catch-all → discard). Aliases and shared inboxes own naming and plus-addressing. This article owns the buying decision: forward-only versus a place people work from.
Is Cloudflare Email Routing a mailbox?
No. Routing and Workers move or transform inbound messages. They are not a hosted inbox with Sent history, search, and authenticated outbound as the address. See ArawaMail vs Cloudflare Email Service. For team business email on a custom domain, start from the Business Email product page.
How we analyzed this
Claims about ArawaMail forwarding, destination caps, Reply-To rewrite, quota impact, and disable/delete behavior are taken from the Email Accounts and Mailbox docs plus live public pricing. IMAP 993 and SMTP 465 are documented ports; hostnames are placeholders in docs and are not published here. We did not treat Email Routing, Workers, or third-party forwarders as equivalent to a hosted mailbox.
FAQ
Can I just forward founder@domain to Gmail?
Yes, if you only need inbound capture and will not send as that address. The moment customers expect a reply from the domain, you need a mailbox (or a carefully authorized send-as path).
Does ArawaMail forwarding keep a copy?
Yes. New inbound mail is forwarded after verification and a local copy remains. Failures do not delete that copy.
Do forwarded copies use transactional quota?
Yes. Each destination receives a separate copy, and those copies count toward the monthly transactional allowance.
Why can’t I reliably send as the domain from Gmail after forwarding-only MX?
Forwarding changes where inbound mail lands. It does not put Gmail in your SPF or give you aligned DKIM for the company domain. Replies leave as gmail.com unless you separately configure send-as — which is a different, fragile setup.