Server checklist for reliable email delivery (hostname, PTR)

For server administrators · Updated 2026-10-29

On this page
  1. Before you start
  2. 1. Give the server a real hostname
  3. 2. Make sure the hostname has a certificate
  4. 3. Set reverse DNS (PTR) for the IPv4 address
  5. 4. Check that outgoing port 25 works
  6. 5. Keep the IP address off blocklists
  7. What the control panel already does
  8. Common questions

Mail providers judge both the sending domain and the sending server. Customers can fix SPF, DKIM and DMARC for their domains; the points below are for the server administrator.

Before you start

You need the administrator panel (https://<server>:2087) and access to your server or IP provider's control panel for reverse DNS.

1. Give the server a real hostname

  1. Open Server Settings in the menu (section Server).
  2. Hostname — a name you control, for example server1.example.com, with an A record pointing to the server's IP address.
  3. Save. Changing it updates the system and mail server name and requests its certificate.

The mail server introduces itself to other servers with this name.

2. Make sure the hostname has a certificate

One certificate for the hostname is used by both panels, webmail and the mail server (IMAP, POP3, SMTP). It is issued automatically once the hostname's A record points to the server. To issue it by hand, click Issue hostname certificate under Server Settings → Certificates.

Customers' websites get certificates that also cover mail.<their domain>, so their mail apps can use that name without warnings.

3. Set reverse DNS (PTR) for the IPv4 address

Receivers look up the name behind your server's IP address. It should be the hostname from step 1, and the hostname should point back to the same IP. Reverse DNS is set by whoever owns the IP address, usually in your server provider's control panel, not in this control panel.

Outgoing mail is sent over IPv4, because many providers refuse IPv6 mail from addresses without matching reverse DNS. Set the PTR record for the IPv4 address.

4. Check that outgoing port 25 works

Mail between servers uses port 25. Some server providers block outgoing port 25 on new servers. The sign: in Mail Queue & Spam → Mail queue, mail to every outside domain is deferred with a timeout. Ask your provider to open it.

The firewall opens the mail ports by default: 25, 110, 143, 465, 587, 993, 995, and 2096 for webmail.

5. Keep the IP address off blocklists

  • Look up your server's IP address on public blocklist sites. Bounces in Delivery reports often name the list that blocks you.
  • Keep the hourly sending limit on. It stops one hacked account from sending enough spam to get the whole server listed.
  • Act quickly when Sending limits shows an account that reached its limit.

What the control panel already does

  • A DKIM key per domain, and signing of all outgoing mail.
  • SPF and DMARC records in every new DNS zone hosted here, through the zone template (DNS Zones → Zone template), and a live check for customers under Email deliverability.
  • Spam scoring of incoming mail, and content scoring of mail sent by signed-in customers.

Common questions

Can I send all mail through an external relay (smarthost)?

The control panel has no setting for this. The server delivers mail directly to the receiving servers.

Gmail rejects mail with a message about IPv6.

Outgoing mail prefers IPv4. If you still see this, check that the server has a working IPv4 address and that its PTR record is set.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.