Guide · Email
Running mail for your own domain takes a few decisions about your network and DNS, then a short list of records and mailboxes. Work through this checklist in order and you will know, before you move any real mail, whether your server can send and receive.
In this guide: The short answer · The checklist · The DNS records · What to expect · Questions
You need four things: a server with a stable public IP, a way to send on port 25 (open it, or use a relay), a name for the mail host with a certificate and a reverse DNS record, and access to your domain’s DNS. Nodekeeper’s mail service, which is part of every plan including Free, then gives you the DNS records to publish, checks them, and hosts the mailboxes and webmail.
Say your studio owns example.org and wants you@example.org mailboxes on a server it already runs for its websites. The checklist below follows that case from a blank domain to a message arriving in webmail.
mail.example.org that points to it. A server behind a home router or
carrier NAT will not receive mail from the internet reliably.example.org as a mail domain.
The panel shows the DNS records that domain needs.you@example.org under the domain, then use the sign-in action on the mailbox list to open its webmail directly from the panel.Nodekeeper lists the exact values for each mail domain, including the DKIM public key. What each one does:
| Record | What it tells the world | Where you set it |
|---|---|---|
| MX | Which host accepts mail for your domain. | Your domain’s DNS |
| SPF | Which servers may send mail for your domain. | Your domain’s DNS |
| DKIM | A public key receivers use to check that a message was signed by your server and not changed on the way. | Your domain’s DNS |
| DMARC | What receivers should do with messages that fail SPF and DKIM, and where to report them. | Your domain’s DNS |
| PTR (reverse DNS) | The name behind your sending IP address. | Your server provider |

If you also use a catch-all address, set it up after the first test messages work, so you can tell a delivery problem from a routing rule.
The mail service runs as its own process under an unprivileged system user, not as root, and mail is queued for outbound delivery with retries and bounce messages.
Only if the provider lets outbound port 25 through, or you configure a relay to send through. Check this first, before you move production mail.
No. The mail features in this guide are in every plan, including Free. Paid plans add other things, such as analytics, collaboration, virtualization and storage.
A new sending IP has no history. Check that the PTR record matches your mail host name, that Verify DNS shows MX, SPF, DKIM and DMARC as correct, and that you are not sending bulk mail from a brand-new address. Reputation builds with normal use over time.
On your own server, at your own storage cost. Mailboxes can be kept in sync between a master node and child nodes if you run more than one.
Install Nodekeeper on the server that already runs your websites, add your domain, and work through the checklist above.
Related: SSL and wildcard certificate management · scheduled backups · web hosting control panel · documentation
Manage websites, office PCs and servers from one panel on your own hardware.