Choosing a business email provider: what actually matters

Pick a mailbox provider on four things: whether it supports per-domain DKIM, whether it gives you IMAP/SMTP and OAuth access, what its published sending limits are, and whether it shares outbound IPs with tenants you cannot see. Storage, interface and bundled apps are easy to compare and rarely the thing you regret.

First, a distinction most comparisons blur. Mailbox hosting gives your team addresses they read and reply from. Bulk sending — campaigns, sequences, transactional mail — belongs on an email service provider or an API-based sender. Running a campaign through a mailbox provider's SMTP will hit per-day recipient limits and is not what the infrastructure is for. Most businesses need both.

The criteria that matter

The categories

Google Workspace and Microsoft 365 are where almost all B2B email lives. That matters for a specific, under-appreciated reason: these two also *receive* most of your mail, their filters are the ones you are trying to satisfy, and tooling in the email ecosystem is built for them first — OAuth connections, API access, audit logs, DKIM per domain, conditional access. If your business email is a cost centre you want to stop thinking about, this is the default answer.

Zoho Mail is the usual choice when budget dominates, including a free tier whose limits change — check current terms rather than an article, and confirm whether IMAP/SMTP access is included at the tier you are considering, because webmail-only access blocks every external tool.

Fastmail is a strong independent option with good standards support, custom domains and proper IMAP. It has no office suite behind it, which is either the point or a dealbreaker.

Proton Mail leads on end-to-end encryption. The trade-off is mechanical: E2E encryption means encrypted search and a bridge application for IMAP access, and automated tooling integrates less easily. Choose it for a privacy requirement, not for convenience.

Registrar- and host-bundled mailboxes (the mailbox included with your domain or your web hosting) are the cheapest route and the most common source of avoidable deliverability problems. Outbound usually goes through shared IPs used by many other tenants on the same platform, so you inherit their throttling and their listings — including temporary 451 deferrals that have nothing to do with your sending. Fine for a receive-only address or a very small team; not where you put outbound that matters.

Published sending limits worth knowing

These are mailbox limits, not campaign budgets. Hitting them is a sign you should be sending through an ESP, not a sign you should buy more mailboxes. Limits change, so verify against current provider documentation before planning against them.

What to set up on day one, whichever you choose

1. DKIM for every domain and subdomain you send from, at the selector the provider gives you.
2. One SPF record per domain, inside the 10 DNS-querying mechanism and 2 void lookup limits. Each added tool's include: eats the budget.
3. DMARC with `rua`, read the reports, then move toward enforcement. Add np=reject so non-existent subdomains cannot be spoofed.
4. Phishing-resistant multi-factor authentication, ideally passkeys or hardware keys, on every mailbox and on the DNS account.
5. A separate subdomain for bulk and outbound sending, warmed on its own. Reputation is per domain and a subdomain does not inherit the root's standing.
6. Alerting on mailbox forwarding rules and OAuth app grants. Attacker-created forwarding rules are the standard follow-up to a compromise, and revoking a password does not revoke a token.
7. Verification on delivered mail: read Authentication-Results on a real received message and confirm dmarc=pass with header.from aligned.

What not to do

• Do not choose on storage and bundled apps. You will never notice the storage and you will notice the DKIM support every month.
• Do not run campaigns or cold sequences through a mailbox provider's SMTP at volume.
• Do not put outbound prospecting on the same domain as your invoices and password resets.
• Do not buy a host-bundled mailbox for a sales team and then wonder why Microsoft defers your mail.
• Do not pick a provider without an IMAP export path.
• Do not add mailboxes to work around a sending limit without warming each one.
• Do not assume a new provider inherits your old reputation. A migration starts a new reputation on the new infrastructure, and it needs ramping.

MailPilot connects to all of these: warm-up over OAuth for Gmail and Outlook, or over SMTP/IMAP for Zoho, Fastmail, host-provided mailboxes, custom SMTP and sending services including SendGrid, Amazon SES, Mailgun and Postmark. It checks SPF, DKIM and DMARC on mail as delivered, tracks per-mailbox reputation daily, and measures real inbox placement per provider — which is how you find out whether a cheap bundled mailbox is quietly costing you the inbox. There is a free plan, and every plan includes unlimited mailboxes.