Private Email Server Setup

What a private email server is

A private email server is a mail system running on a server you rent or own, sending from IP addresses assigned to you rather than a pool shared with other customers. Outgoing mail leaves through your own mail transfer agent, signed with your own DKIM keys, from IPs whose history reflects only your behaviour.

That independence cuts both ways. Nobody else can damage your reputation, but nobody else is looking after it either. A private server only works well when authentication, reverse DNS, warm-up, bounce processing and monitoring are all in place from the first day. Our job is to make the setup viable in practice, not just technically running.

Who a private server suits, and who it doesn’t

A private server makes sense when your volume is steady, your lists are permission-based, and you want control over how and when mail leaves. Signs you may have outgrown a shared service include:

• Delivery drops that you can’t explain and your provider can’t either.
• Per-message pricing becoming a meaningful line in your budget at predictable volumes.
• A need for custom retention, logging or data-location arrangements that a hosted service won’t offer.
• Several brands or business units that need their own sending identity and separate reputation.

It is usually the wrong choice for small or irregular senders. An IP that sends a few hundred messages one week and nothing for a month never builds a stable reputation. In that case we will recommend shared SMTP instead, and explain why.

What’s included

• Server provisioning with a provider that allows outbound port 25 and lets you set reverse DNS.
• Mail stack installation, typically Postfix for sending, with Dovecot and filtering if you also need mailboxes.
• Authentication: SPF, DKIM with 2048-bit keys, and DMARC starting in monitoring mode.
• PTR records on every sending IP, matched to a forward hostname and the server’s HELO name.
• TLS on all SMTP and submission ports with valid certificates.
• Hardening: closed relay, authenticated submission only, a firewall, brute-force protection and automatic security updates.
• Bounce and complaint processing wired into your suppression list.
• A warm-up plan built around your most engaged subscribers.
• Written documentation of every setting, credential location and routine task.

How we deliver it

1. Discovery. We learn your volume, mail types, list sources and current provider, and confirm your lists are opt-in.
2. Design. We decide how many IPs and sending subdomains you need and whether transactional and marketing mail should be separated.
3. Build. Server, mail stack, DNS and TLS are configured, then checked from outside rather than trusted from the config files.
4. Test. Real messages go to Gmail, Outlook and Yahoo test accounts, and we read the headers to confirm SPF, DKIM and DMARC pass and align.
5. Warm-up. Volume ramps gradually while we watch acceptance, deferrals and complaint signals, adjusting the pace as we go.
6. Handover. You receive documentation and a walkthrough, and ongoing care if you want it.

Tools and standards we work with

We choose the stack to fit the job. Postfix is our usual sending engine; Postal suits teams who want a web interface and API; Mailcow suits businesses that want mailboxes and webmail in one package. Authentication follows SPF, DKIM and DMARC, with MTA-STS and TLS-RPT added where inbound security matters. Reputation is tracked through Google Postmaster Tools, Microsoft SNDS and the major blocklists.

What affects timeline and cost

• How many sending IPs and domains are involved.
• Whether you need mailboxes and webmail or only outbound sending.
• How quickly your hosting provider responds to reverse DNS and port 25 requests.
• The length of warm-up, which depends on your target volume and the engagement of your list, not on our schedule.
• Whether existing sending history, suppression lists and templates need migrating.

Common mistakes we see

The most frequent failure is sending full volume from a brand-new IP on the first day. Others include forgetting reverse DNS, leaving the server as an open relay, skipping bounce handling so dead addresses are mailed repeatedly, and building something only one person understands. Each of these is avoidable with planning, which is why documentation is part of the deliverable rather than an extra.

For the wider picture, read our email infrastructure guide, or browse all email infrastructure services. When you’re ready, tell us about your sending.

Frequently asked questions