Guide · Email

Self-Hosted Email for Your Domain: A Practical Setup Checklist

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

The short answer

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 [email protected] 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.

The checklist

  1. Choose the server and the mail host name. Use a server with a fixed public IP address, and a host name such as mail.example.org that points to it. A server behind a home router or carrier NAT will not receive mail from the internet reliably.
  2. Check port 25 with your provider. Mail between servers uses port 25. Many cloud and residential providers block outbound 25 by default. Ask yours to open it, or decide now to send through a relay (a smarthost) that you configure in Nodekeeper. Inbound 25 must be reachable from the internet to receive mail.
  3. Ask for a reverse DNS (PTR) record. Receiving servers look up the name behind your sending IP. Set the PTR for the IP to your mail host name, at the provider that owns the IP. You cannot set it in your domain’s DNS.
  4. Get a certificate for the mail host name. Mail apps connect to IMAP and POP3 over TLS and expect a valid certificate for the name they connect to. Certificate management is in the same panel as the mail service.
  5. Install Nodekeeper and add your domain. Mail is included from the Free plan, so you can start with the free download. Add example.org as a mail domain. The panel shows the DNS records that domain needs.
  6. Publish the DNS records, then run the DNS check. The next section lists them. After the records are live, use Verify DNS: it resolves each record through public DNS and shows what the world actually sees.
  7. Create the first mailbox and open webmail. Create [email protected] under the domain, then use the sign-in action on the mailbox list to open its webmail directly from the panel.
  8. Send and receive in both directions. Send from the new mailbox to an address at a large outside provider, and reply to it. Check that both messages arrive and look at where they land (inbox or spam). This is the first real test of your port 25, PTR and DNS work.
  9. Connect your mail apps. Add the mailbox in a desktop or phone client with IMAP or POP3 over TLS against the mail host name, not the domain, so the certificate matches.
  10. Plan what happens next. Decide how the mail will be backed up, who watches the outbound queue, and how you will handle spam, since there is no built-in inbound spam or virus filtering today.

The DNS records, in plain words

Nodekeeper lists the exact values for each mail domain, including the DKIM public key. What each one does:

DNS records a mail domain needs
RecordWhat it tells the worldWhere you set it
MXWhich host accepts mail for your domain.Your domain’s DNS
SPFWhich servers may send mail for your domain.Your domain’s DNS
DKIMA public key receivers use to check that a message was signed by your server and not changed on the way.Your domain’s DNS
DMARCWhat 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
Mail domain page in the panel with the DNS records to publish (MX, SPF, DKIM, DMARC) and a Verify DNS result showing all four as OK; domains and the DKIM key redacted
A mail domain’s DNS guide in the panel: the records to publish, and the Verify DNS result showing MX, SPF, DKIM and DMARC. Domains and the DKIM key are redacted.

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.

What to expect, stated plainly

Limits and prerequisites
  • There is no built-in filtering of inbound spam or viruses today. Plan for it before you give mailboxes to people who receive a lot of external mail.
  • Nobody can promise inbox placement. Delivery depends on your IP’s reputation, your DNS records, your sending volume and the content of the mail.
  • Nodekeeper is software that runs on your server. The server, its IP reputation and the stored mail stay your responsibility; Nodekeeper does not host your mailboxes.
  • Back up mailboxes like any other data. Backup schedules and destinations are in the same panel.

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.

Questions

Can I run this on a cloud VPS?

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.

Do I need a paid plan?

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.

Why does my first test message land in spam?

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.

Where do the mailboxes live?

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.

Start with the free download

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

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
[email protected] WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.