ALL CASE STUDIES
CASE STUDY / SKY INFRASTRUCTURE

Sending servers that pass receiver checks from day one

As our team added sending servers, small setup faults kept appearing: a server name that did not match its address, internal details leaking into headers and images that would not load. Each looks minor. Together they are the first things receiving systems and blocklists check.

From Sky’s own sending operations. This work was done on sending infrastructure our team runs itself. Server names, domains and addresses are left out, and the figures come from our engineering records.

  • 1 : 1each IP’s HELO name now matches its reverse DNS (PTR) record
  • 3internal headers now removed before mail leaves the server
  • AutoTLS certificates issued at install, including PTR hostnames
  • 200 OKimage links load over HTTPS after the certificate fix
Sky InfrastructurePublished 15 November 2026 Sky operations

What was at stake

Receiving systems check how a sending server introduces itself before they read the message. The HELO name should be the server’s full hostname, and the IP’s reverse DNS (PTR) record should point to a name that points back to the same IP. Gmail asks for valid forward and reverse DNS, and Spamhaus began rolling out a requirement in November 2026 for every sending IP to have a valid HELO, a PTR record and a matching A record.

Headers matter too. Internal details left in a message tell filters how it was produced, and broken images make a message look careless or unsafe.

The challenge

Our team runs its own MTA servers, several with more than one IP address and a sending domain for each IP. As servers were added, faults appeared that no single checker caught.

Some servers introduced themselves with the root domain instead of the mail hostname the PTR record pointed to. Servers with several IPs needed a different HELO name for each IP. Three internal headers, added by our sending software for routing, were reaching recipients. And images in some messages did not load, because the image host had no TLS certificate while the message linked to it over HTTPS.

What Sky did

  1. 01
    Check what the server says. We connected to the servers as a receiving system would and compared the greeting and HELO name with the PTR record of the sending IP.
  2. 02
    Match HELO to PTR, IP by IP. Each IP now introduces itself with the exact hostname assigned to it. The installer uses those names as given instead of adding its own prefixes.
  3. 03
    Strip internal headers. We added the three internal routing headers to the list removed before delivery, on the live servers and in the templates used for new ones.
  4. 04
    Issue certificates automatically. We added a TLS certificate step to the install, covering the server’s domain and its PTR hostnames, so image links work over HTTPS.
  5. 05
    Send bounces to the right place. The Return-Path set in each message is now used as the envelope sender, so bounces return to the right domain and SPF is checked against it.
  6. 06
    Fix the templates, not just the servers. Every change went into the shared install and policy templates as well as the running servers, so a new server does not bring the old faults back.

Before and after, from a receiver’s view

Simplified from our engineering records. Real hostnames are replaced with example.com.

01Before HELO example.com PTR mail.example.com mismatch
02After HELO mail.example.com PTR mail.example.com match
03Before 3 internal routing headers visible to recipients
04After Removed before delivery on every server
05Before https://mail.example.com/img/… certificate error
06After Certificate issued at install → image loads (200 OK)

The results

  • Names that match

    Each sending IP’s HELO name matches its PTR record, and the server greeting shows the mail hostname.

  • Cleaner headers

    Internal routing headers no longer reach recipients.

  • Working images and links

    Servers get a TLS certificate at install, including their PTR hostnames, so images load over HTTPS.

  • A repeatable install

    These fixes are part of the standard install and server templates, so new servers start correct instead of being fixed later.

What this means for you

If you run your own mail servers, or are about to, these are the checks Sky’s infrastructure setup covers before the first warm-up message is sent. The same checks apply to any self-managed MTA.

  • HELO name, PTR record and A record agree for every sending IP
  • SPF, DKIM and DMARC aligned to the domain you send from
  • No internal or debugging headers in delivered mail
  • TLS certificates for image and tracking hosts
  • Return-Path and bounce domain set correctly
Seeing the same problem?

Setting up your own sending servers?

Book a free 30-minute discovery call and tell us what you are seeing. We’ll ask about your setup, volumes and what changed, then suggest the right next step.

  • The call is free. You decide afterwards.
  • If you need our help: SMTP/authentication setup, from $750 (one-time). Scope agreed first.
  • No passwords, API keys or recipient lists needed.

Provider rules and standards

The requirements this work had to meet, from the providers and standards bodies that set them. Rules change, so check the current version before changing a live sending program.

  1. [1]
    Spamhaus Sender Guidelines The November 2026 rollout requiring a valid HELO, a PTR record and a matching A record for every sending IP.
  2. [2]
    Email sender guidelines — Google Workspace Admin Help Gmail’s requirement for valid forward and reverse DNS (PTR) records on sending domains or IPs.
  3. [3]
    RFC 5321: Simple Mail Transfer Protocol The HELO/EHLO command identifies the sending server by its fully qualified domain name.