Your business email is on a free mailbox, and that is costing you
A Gmail or Yahoo address on a quote is a small credibility tax you pay on every message. When to move to your own domain, what a migration actually involves, and the four DNS records that decide whether your mail gets delivered.
This is not a moral argument about professionalism. It is a response-rate argument.
When a quote, an invoice or a first reply arrives from a free mailbox, the reader makes a judgement in under a second, and the judgement is usually that this is a side project. That judgement shows up in reduced replies, in requests for advance payment, and in the number of people who quietly go with the vendor who emailed from their own domain.
The four records that decide delivery
Most mail problems that people blame on "the provider" are authentication problems. Four DNS records decide whether your mail is trusted:
MX tells the world where to deliver mail for your domain. This is the one everyone sets.
SPF is a TXT record listing the servers allowed to send on your behalf. If your app also sends mail, its server has to be in that list or its mail will be marked suspicious.
DKIM is a signature. The sending server signs outgoing mail with a private key; the public key lives in DNS. A valid signature proves the message was not altered in transit.
DMARC is a policy that tells receiving servers what to do when SPF or DKIM fail, and where to send reports. Without it, large providers have no instruction and treat unauthenticated mail with suspicion by default.
The failure mode is subtle. Mail does not bounce. It lands in spam, or in a promotions tab nobody reads, and the sender concludes the recipient is ignoring them.
Why free mailboxes and your domain collide
A very common arrangement is a business domain that forwards to a Gmail address. It looks professional and it is where deliverability quietly breaks.
When you forward mail from your domain to Gmail, and Gmail later sends a reply as your domain, you are sending from infrastructure that your SPF does not authorise and that does not hold your DKIM key. Receivers see a mismatch. This is the mechanism behind the "sent from a Gmail address but the From says my company" warnings, and it gets worse over time as providers tighten policy.
Gmail and Yahoo have both moved toward requiring SPF or DKIM plus DMARC for bulk senders. The direction of travel is only one way. A forwarding arrangement that worked in 2021 is not a safe assumption for next year.
What a migration actually involves
The fear is that moving mail means losing mail. It does not, if you do the steps in order.
- Create the mailboxes at the new provider first. Do not change any DNS yet.
- Copy the existing mail across. Any IMAP client can do this, and most providers will give you a sync tool. This is the slow step and it is the one people skip.
- Verify the copy. Spot-check folders, attachments, and the oldest mail you care about.
- Set them up in their clients. Phone, desktop, webmail. Confirm sending works.
- Change MX as the last step. The moment MX moves, mail starts arriving at the new place. Mail still sitting on the old server is now stranded unless you keep paying for it.
- Publish SPF, DKIM and DMARC. These should be ready before MX moves, not after.
- Leave the old provider in place for a week or two if you can, so nothing in flight is lost.
The ordering is the whole trick. Copy first, switch second. Reversing it is how people lose years of correspondence.
What to check before you sign up anywhere
Ask these questions of any provider, including us:
- What are the sending limits per mailbox per day? Every provider has them. They exist to protect shared sending reputation, and a provider that claims unlimited sending on a shared relay is telling you something about how they treat abuse.
- Are SPF, DKIM and DMARC published for me, or do I do it myself? Doing it yourself is fine if you understand the records. The risk is a typo in a TXT record that silently breaks delivery.
- Where do the mail servers sit? If data residency matters, this is a real question with a real answer, not a marketing line.
- Can I export my mail if I leave? IMAP access means yes. A proprietary sync protocol means it depends.
- What happens to my mail if I stop paying? Some providers delete it immediately. Ask before you need to know.
Aliases instead of mailboxes
A small team usually needs fewer mailboxes than it thinks. Most of the addresses on a business card are not separate humans:
sales@,support@,accounts@,info@can all deliver into one or two real inboxes as aliases.- An alias costs nothing. A mailbox costs a slot on your plan.
- A catch-all at the domain level catches the typos and the old addresses you forgot about.
The pattern that works for most small businesses is two or three real mailboxes with a handful of aliases pointing at them, rather than one mailbox per job title.
What we will not tell you
We will not promise a delivery percentage. Inbox placement depends on the receiving provider's filters, your domain's history, how your list was collected, and how many people mark you as spam. Anyone quoting a guaranteed inbox rate is quoting something they do not control.
What we can tell you is what we do: authentication records published for you, outbound through a relay with an established reputation, and daily caps per mailbox that protect that reputation instead of spending it.
The honest trade
A free mailbox is genuinely fine for a hobby project, a personal address, or a domain you are trying out. The moment you are asking someone to pay an invoice, the address on the invoice is doing commercial work, and it should look like it.
That is the entire argument. Not that free mail is bad, but that business correspondence and personal correspondence have different jobs, and only one of them needs your name on it.
- deliverability
- dns

