Email deliverability guide

SMTP DNS Setup Guide

How SMTP infrastructure, SPF, DKIM, DMARC, return paths and tracking domains should align.

Already have an Inbox Warmup account? Go directly to Dashboard

How SMTP infrastructure, SPF, DKIM, DMARC, return paths and tracking domains should align.

Key takeaway
A working SMTP login is not enough. Receiving providers also evaluate whether the visible From domain aligns with authenticated sending infrastructure and whether the domain can be trusted.

Why smtp dns setup guide matters

A working SMTP login is not enough. Receiving providers also evaluate whether the visible From domain aligns with authenticated sending infrastructure and whether the domain can be trusted.

Good sending performance comes from several systems working together: a legitimate sender identity, correctly aligned authentication, a reliable connection, controlled volume, relevant recipients and fast action when warning signs appear. This guide is designed to help you review those areas in a logical order instead of changing settings randomly.

Step-by-step process

  1. Identify the real SMTP sending service and IPs — complete this check and record the result before moving to the next stage.
  2. Publish one valid SPF record — complete this check and record the result before moving to the next stage.
  3. Configure DKIM signing for the From domain — complete this check and record the result before moving to the next stage.
  4. Publish DMARC and choose an appropriate policy — complete this check and record the result before moving to the next stage.
  5. Align the return path where supported — complete this check and record the result before moving to the next stage.
  6. Configure branded tracking domains — complete this check and record the result before moving to the next stage.
  7. Set reverse DNS for dedicated IPs when applicable — complete this check and record the result before moving to the next stage.
  8. Retest after DNS propagation — complete this check and record the result before moving to the next stage.

Before you begin

Make sure you control the domain, can edit DNS, can access the sending mailbox or SMTP account, and know which service actually sends the message. Keep a copy of current records before changing anything.

Before you scale

Confirm that authentication passes on real messages, connection errors are resolved, bounces are understood and sending volume is stable. Scale in measured steps rather than moving directly to a provider maximum.

  1. Identify one measurable problem.
  2. Change the smallest relevant setting or behaviour.
  3. Allow enough time for DNS or provider data to update.
  4. Retest using the same method.
  5. Keep the change only when the evidence improves.

Use a controlled improvement cycle

Record the date of each test, the domain or mailbox tested, the sending provider and the exact result. This creates a useful baseline for future troubleshooting. When performance changes, compare the new data with the last known-good configuration instead of replacing several records or providers at once.

A single passing check should not be treated as final proof that the entire sending setup is healthy. Authentication results, SMTP responses and reputation indicators should be reviewed together and compared over time. For example, SPF may pass while DKIM is missing, or an SMTP connection may succeed while the chosen From address is not authorized to relay.

How to interpret the results

What to monitor after setup

Continue reviewing the following signals after the initial configuration. A correct setup can still deteriorate when passwords change, DNS is edited, contact quality drops or campaign volume increases too quickly.

  • SPF, DKIM and DMARC results on real sent messages
  • SMTP rejection, deferral and authentication responses
  • Hard bounces, repeated soft bounces and invalid recipients
  • Complaint and unsubscribe trends
  • Changes in hourly and daily sending volume
  • Provider-specific feedback and reputation data where available
  • Meaningful replies and recipient engagement, not only open tracking

Common mistakes to avoid

  • Adding the SMTP hostname as an SPF include without provider instruction
  • Publishing multiple SPF records
  • Using a DKIM selector that is not enabled on the server
  • Setting a strict DMARC policy before monitoring
  • Ignoring reverse DNS on dedicated infrastructure
Important limitation: Inbox Warmup can help with controlled warmup, authentication checks and infrastructure readiness. No software can guarantee inbox placement, replies or campaign revenue. Results also depend on recipient quality, content, complaints, sending history and mailbox-provider decisions.

Useful tools for this guide

Related Inbox Warmup solutions

Frequently asked questions

Does SMTP automatically configure DNS?

Usually not. DNS records must be published with the domain host using values supplied by the sending service.

Can I include any hostname in SPF?

No. Only include mechanisms documented by the actual sending provider.

What is alignment?

Alignment means the authenticated SPF or DKIM domain corresponds appropriately with the visible From domain for DMARC.

Recommended next step

Use the checks above to document the current state of your domain and mailbox. Fix authentication and connection errors first, then begin controlled warmup and monitor real results before increasing campaign volume.

Next step

Turn this into a controlled warmup plan.

Connect your infrastructure, verify authentication, warm up gradually and understand your reputation before scaling.