Email forwarding sends a copy of incoming mail to an inbox you already use. A real mailbox stores mail for the custom address and gives that address its own history, sending path, permissions, and often its own inbox.
Forwarding is enough when one person wants hello@yourcompany.com to arrive in Gmail or Outlook.
Choose a mailbox when several people handle the address, replies must come from it reliably, software
needs the full thread, or the custom address must keep its own record.
The difference at a glance
| Question | Forwarding-only address | Real mailbox |
|---|---|---|
| Where does incoming mail live? | Usually in the destination inbox | In the mailbox provider |
| Can you read it in another inbox? | Yes, that is its main purpose | Sometimes, through forwarding, IMAP, or an app |
| Can you reply from the domain? | Only with a separate, correctly configured path | Yes, if the mailbox provider supports sending |
| Does it keep sent mail? | Not unless another service does | Usually |
| Can several people work in it? | Copies can go to people, but state may split | Yes, if the provider supports shared access |
| Can software fetch full threads? | Only if the destination or another system does | Yes, when the provider offers an API or protocol |
| Best fit | Simple delivery to an existing personal inbox | A lasting business identity and conversation log |
The word “forwarding” describes a route, not a mailbox. Some mailbox services include forwarding, which gives you both. Check where the original message remains before assuming the two choices are exclusive.
What email forwarding actually does
A forwarding service accepts mail for your domain and passes it to another address:
customer@example.com
↓
hello@yourcompany.com
↓
founder@gmail.com
This setup is useful for a solo founder. You can publish a company address without checking another inbox every day.
Cloudflare Email Routing is one example. Its official documentation describes rules that route an
address to a verified destination or a Worker. It also offers a catch-all rule for unmatched
addresses. That is routing infrastructure. It does not by itself give hello@yourcompany.com a
normal stored inbox with folders, sent mail, and a conversation history.
Storage differs by provider. A forwarding-only service may not keep a durable copy after delivery. If the destination account is closed, compromised, or cleaned up, the business address may have no separate archive.
Receiving is easy; replying is the test
Forwarding proves that you can receive a message. It does not prove that you can send as the custom address.
If the founder presses Reply in Gmail, the outgoing message may come from founder@gmail.com. To
send from hello@yourcompany.com, the founder needs one of these:
- A mailbox provider that sends for the custom address
- An SMTP relay and valid credentials
- A provider-specific “send as” feature
- A protected reply relay that sends the response through the original mailbox
The domain also needs correct SPF, DKIM, and DMARC records for the service that sends the reply. Do not add a second SPF record. Update the existing policy so it covers every authorized sender.
Google currently lets Gmail users add an address they own under “Send mail as,” often by supplying the other provider's SMTP server. Google has announced that support for sending from third-party addresses in Gmail will end in January 2027. Gmail and Google Workspace aliases hosted by Google are not affected. If a workflow depends on Gmail sending through an unrelated provider, plan for that change now.
Also test what the recipient sees. Google's documentation notes that some recipients may see the Gmail address “on behalf of” the custom address. An apparently correct From line is not the same as a clean, authenticated sending path.
When forwarding is enough
Use forwarding when all of these are true:
- One person owns the conversation.
- That person already works from one trusted inbox.
- A separate history for the company address is not required.
- Replies can use the person's normal address, or a tested sending route exists.
- No application needs mailbox-level access.
- Losing the destination inbox would not remove the only required copy.
For example, hello@tiny-studio.com can forward to the founder's existing Outlook account. If the
address receives a few enquiries each month and only the founder answers, a new daily inbox may add
more work than value.
Forwarding can also suit role addresses that should never start a conversation. An address used only to collect registrar notices or vendor receipts may need delivery but not a separate reply identity.
When you need a real mailbox
Create a mailbox when the address represents ongoing work rather than a convenient route.
The address needs its own record
founder@yourcompany.com may contain contracts, introductions, and account recovery messages. A
private mailbox keeps that history under the company's domain instead of making one personal account
the only record.
Several people answer
If two people handle support@yourcompany.com, separate forwarded copies create uncertainty. One
person may answer without the other seeing the sent message. Both may reply. Neither may know who
owns the request.
A shared mailbox can keep the incoming message, replies, and thread state in one place. Some shared inbox products add assignment and collision controls as well. A basic mailbox does not guarantee those workflow features, so check what the provider includes.
People may change
Company addresses should survive staff changes. When hello@ is only a route into one employee's
account, changing ownership means changing the route and deciding what happens to earlier messages.
A separate mailbox makes the handover clearer.
Software needs context
An application or AI agent often needs the latest thread, attachments, delivery state, and a safe way to reply. A forwarded message is only one copy at one moment. A mailbox API can provide the current conversation and apply access controls to that address.
A hybrid approach: store first, then forward
You can keep a real mailbox and still read copies elsewhere.
Startup Mail uses this model. It stores the original in the Startup Mail mailbox, then forwards a copy to a verified Gmail, Outlook, or other address. The forwarded message has a signed, expiring Reply-To route. Replying to that route sends the response back through the original Startup Mail mailbox and adds it to the conversation.
This avoids relying on Gmail's third-party “Send mail as” feature. It also keeps the custom-domain mailbox as the lasting record.
The trade-off is that forwarding is not synchronization. Reading, starring, archiving, or deleting the copy in Gmail does not make the same change in Startup Mail. Sent folders and labels do not sync either. Each forwarded message gets a relay address that expires after 30 days and can be used once. The reply must come from the verified forwarding address and pass DMARC. Do not save the relay as a contact or reuse it for a later message.
Startup Mail also does not offer aliases, catch-all delivery, POP, IMAP, general SMTP accounts, or Exchange sync. Every receiving address must have a matching mailbox. You cannot open it as a normal mailbox in a third-party client. Use the web inbox, HTTP developer interfaces, or forwarding with the reply relay. If you need every spelling of an address to arrive or full folder synchronization in a desktop client, choose a provider built for those requirements.
Test before publishing the address
Send a message from an unrelated provider, then check the complete round trip:
- Confirm that the message reaches the intended destination.
- Find out whether the forwarding service kept the original.
- Press Reply and inspect the From and Reply-To addresses.
- Confirm that the recipient sees the company address you intended.
- Check SPF, DKIM, and DMARC results in the received message headers.
- Ask a second person to reply to the same thread if the address is shared.
- Test what happens when the forwarding destination rejects mail.
Do not wait for a customer, investor, or account-recovery message to expose a broken reply path.
Frequently asked questions
Can I forward custom-domain email to Gmail and reply from my domain?
Yes, but forwarding alone is not enough. You also need a sending route for the custom address. Note that Google plans to end Gmail's third-party “Send mail as” support in January 2027. A provider-run reply relay or a provider that supports your preferred mail client may be a better long-term route.
Does forwarding leave a copy on the original server?
It depends on the service. A forwarding-only provider may simply relay the message. A mailbox service can store the original and forward another copy. Check the provider's retention rules and test them.
Is forwarding the same as an email alias?
No. Forwarding describes where a message goes. An alias is an additional address attached to an existing mailbox or account. An alias may route internally without using a separate forwarding service.
Can two people share a forwarded address?
They can both receive copies, but they may not share read state, sent mail, or ownership of the conversation. Use a shared mailbox or help desk when coordination matters.
Does Startup Mail forwarding replace Gmail or Outlook?
No. It lets you read forwarded copies there while the original remains in Startup Mail. It does not synchronize folders or mailbox state.
If you are choosing among several kinds of address, read email aliases vs separate mailboxes vs shared inboxes. For a broader setup guide, see custom-domain email without an office suite.