Email Hosting for Client Sites: Getting It Set Up Right

At some point nearly every agency hears the same sentence from a client: "Can we get an email address with our domain?" It's usually asked in passing, like it's a small thing you can just tick off. But the way you answer tends to decide whether that client's email works quietly for the next five years, or becomes a slow drip of "have you checked my spam folder?" messages.

Email is easy to ignore because it's invisible when it works. So this guide is about the setup that stays invisible: real mailboxes on the client's own domain, configured right the first time, without your agency becoming the unofficial IT department for their whole office.

Give them mailboxes they can actually use

The aim is simple on paper: the client gets addresses like [email protected], and those addresses receive and send mail. On a mail server you run on your own hardware, each mailbox is a real account, not a forwarding rule. Give each one its own storage quota and a full inbox from one client can't silently fill up someone else's.

Webmail should be part of the deal. The client opens a browser, logs in, and reads their mail - no Outlook setup, no IT call. If you ever need to move a client onto your hosting from another provider, the existing mail should come along, not get left behind with a forwarder that keeps breaking.

Deliverability is the real skill

The difference between hosting that "mostly works" and hosting that actually works is deliverability. Email servers on the receiving end are picky, and they judge you on a few publicly visible signals:

• SPF says which servers are allowed to send for that domain.
• DKIM signs messages so they can't be tampered with in transit.
• MX records tell the world where to actually deliver the mail.
• TLS encrypts connections so mail isn't readable while it travels.

You don't need to know the deep detail behind any of these to run good hosting - you just need the platform to take care of them. When a mail server goes live it should get its certificate automatically, encrypted from day one with nothing to request or forget, and the DNS records for the domain should sit in the same place you manage everything else so MX, SPF and DKIM live next to the A and CNAME records instead of in a second dashboard.

Keep email inside the plan, not outside the budget

Where agencies usually lose money on email is treating it as an add-on: a separate provider, a separate bill, a separate login, and a margin that quietly disappears. It doesn't have to work that way. If the number of mailboxes a client gets is simply part of the hosting package they're already paying for - same as their storage or their site count - then email turns from a cost centre into another reason the monthly invoice feels obvious.

You control exactly what each server runs. Sending, receiving, secure submission and IMAP access can each be switched on or off by themselves, so a server that only needs inbound mail doesn't run the full stack.

The setup that never gets un-sketched

Do it properly once and email simply works in the background. The client gets their names, you get billing that makes sense, and the "check your spam folder" messages stop coming. That's the quiet win - the client never thinks about email again, which is exactly how you want it.