Email Deliverability: Checklist and Monitoring
A mail server that accepts your message has done the easy part. Whether the message reaches an inbox depends on your IP’s reputation, your DNS records and how you behave over time. This page is the checklist we use: what to set up before sending, what to recheck after every change, and what to watch so that a silent failure doesn’t run for months.
The records themselves (SPF, DKIM, DMARC, MTA-STS) are explained in Email DNS Authentication.
Before you send
Section titled “Before you send”- Reverse DNS that matches (FCrDNS). The sending IP’s PTR record should name a host
whose A record points back to the same IP, and the server should greet with that name
(
HELO/EHLO). Only whoever owns the IP block can set the PTR, so ask your provider. If you can’t get one, don’t deliver directly: relay through a smarthost (see Running Your Own Email). - Not on a blocklist. Check the IP on Spamhaus, SpamCop and Barracuda. Residential and dynamic ranges sit on the Spamhaus PBL by policy, so mail sent from them directly is rejected wherever Spamhaus is used.
- Outbound port 25 open. Many home ISPs and cloud providers block it. Test it before you plan around direct delivery.
- SPF, DKIM and DMARC aligned for every domain you send from, including app and alert senders.
- A test message to a checker such as mail-tester.com or internet.nl, and to a Gmail address whose headers you can read.
Smarthost or direct delivery?
Section titled “Smarthost or direct delivery?”A smarthost (a relay such as Brevo, Amazon SES or SMTP2GO) lends you its IP reputation. Direct delivery means receivers judge your own IP. The trade-offs:
| Through a relay | Direct from your IP | |
|---|---|---|
| PTR record | Not needed | Required: Gmail, Yahoo, Microsoft and Apple all want forward-confirmed reverse DNS |
| Blocklists | The relay’s shared IPs | Your IP and its range, including Spamhaus’s policy list for end-user space |
| Microsoft (Outlook.com, M365) | Usually fine | New IPs are often blocked (S3150) and need delisting requests |
| Privacy | The relay sees and logs every message; some rewrite links and add tracking by default | Only you and the receiving server |
| Control | The relay’s daily caps, terms and suspensions apply to all your mail | Yours |
| Bounce notices | Some relays refuse null-sender mail | Normal |
| Credentials | A relay key to protect and rotate | None |
What direct delivery needs, in this order:
- A PTR record from whoever owns the IP block (your ISP or hosting provider). It must name a host whose A record points back to the same IP. Use the MX hostname, which is DNS-only; a Cloudflare-proxied name fails the forward check. ISPs usually do this by support ticket.
- The right source address. Check that outbound SMTP really leaves from that IP. Docker masquerades to the host’s primary address unless you add a source NAT rule (lesson 14 on the mailcow page).
- A matching greeting. Set the server’s HELO name (
smtp_helo_namein Postfix) to the PTR name. - Off Spamhaus’s policy list. Business static ranges can still be on the PBL. Removal is free at check.spamhaus.org, but only once rDNS exists, requested from an address at the mail server’s domain. It expires after a year, so put a reminder in the calendar.
- IPv4 only until you also have an IPv6 PTR (
smtp_address_preference = ipv4orinet_protocols = ipv4). - Feedback channels. Google Postmaster Tools and Microsoft SNDS/JMRP both show little below roughly 100 messages a day, so DMARC aggregate reports and your own bounce logs are the main signal at community volume.
Then move gradually. Deliver directly to most destinations, keep Microsoft’s consumer
domains (outlook.com, hotmail.*, live.*, msn.com) on the relay through a
recipient-domain transport map for two to four weeks, and set the relay as Postfix’s
smtp_fallback_relay so temporary failures retry through it (permanent rejections still
bounce). Watch bounces and DMARC reports, then move Microsoft too. Rolling back is
re-assigning the relay.
What Gmail and Yahoo require
Section titled “What Gmail and Yahoo require”Both publish sender rules. Microsoft announced comparable requirements for high-volume senders to Outlook.com in 2025; check its current guidance.
| Requirement | All senders | Bulk senders (Gmail: over 5,000 messages a day) |
|---|---|---|
| Authentication | SPF or DKIM | SPF and DKIM |
| DMARC | — | A published policy (p=none is enough), and DMARC must pass |
| Alignment | — | The From: domain aligns with the SPF or DKIM domain |
| Reverse DNS | Valid forward and reverse DNS for sending IPs | Same |
| Transport | TLS (Gmail) | Same |
| Spam rate | Below 0.3% as reported in Google Postmaster Tools | Same |
| Format | RFC 5321/5322 compliant; no impersonating Gmail From: headers | Same |
| Unsubscribe | — | One-click unsubscribe (RFC 8058) on marketing and subscribed mail, plus a visible link; Yahoo asks that unsubscribes be honoured within 2 days |
A community server sends far below the bulk threshold, but meeting the bulk rules anyway costs little and avoids surprises when a mailing list grows.
After every change or upgrade
Section titled “After every change or upgrade”Run these after any mail server upgrade, relay change, DNS change or firewall change. Most of our mail incidents were a step that silently undid an earlier fix.
- The relay is still assigned. If outbound goes through a smarthost, check that every
domain still routes through it (mailcow: the
postmapcheck on the mailcow page). One of our upgrades lost the relay assignment, and mail went out directly and was rejected. - The containers can still reach the outside. An upgrade that recreates Docker networks can drop NAT or egress routing rules. Check DNS resolution and a connection to the relay from inside the mail containers.
- A test send on every path: person to person (webmail and a mail client), an alias being forwarded, an app or Worker, and a server alert. Each path can break on its own.
- Read the received headers.
Authentication-Resultsshould showspf=passordkim=passwithheader.d=your domain, anddmarc=pass. - Inbound from outside. Send from an external account and check that it arrives and
that the
Received:line shows TLS (with ESMTPS). - The served certificates. Check the certificate on every mail port (below), not the file on disk.
What to monitor
Section titled “What to monitor”-
Certificate expiry on the served endpoint. A renewed file doesn’t help until Postfix and Dovecot reload it. Check what clients actually see:
Terminal window openssl s_client -starttls smtp -connect smtp.example.org:25 -servername smtp.example.org </dev/null 2>/dev/null \| openssl x509 -noout -subject -enddateopenssl s_client -connect imap.example.org:993 -servername imap.example.org </dev/null 2>/dev/null \| openssl x509 -noout -enddateRepeat for 465, 587 (
-starttls smtp) and 4190 (-starttls sieve). -
The queue. Watch the deferred count and group it by reason. Check the envelope sender before calling it an outage: bounce notices have an empty sender (
MAIL FROM:<>), and a smarthost that refuses them fills the queue with retries while normal mail flows fine. -
DMARC and TLS-RPT reports actually arriving. Large receivers send daily aggregate reports for domains they see traffic from. If nothing arrives, the usual cause is a broken report address (a mailbox or alias that doesn’t exist, or a missing authorisation record for an external domain), not perfect mail. Prove the address works before you trust the silence, and before moving MTA-STS from
testingtoenforce. -
Logs that are still being written. Container logs can go stale while the container stays up. Compare the newest log timestamp with the current time before you trust a “no errors” result.
-
Password guessing. Bots spread login attempts across hundreds of IPs, each staying under the per-IP ban threshold, so bans never fire. Watch the total number of failed logins per day. Offer authentication only on submission ports (465/587), not on port 25, and use app passwords for mail clients.
-
Reputation. Google Postmaster Tools shows your spam rate and domain reputation at Gmail; Microsoft SNDS shows data for your IPs.
-
Alerts that reach someone. Set the mail server’s own watchdog or notification address, and send health-check alerts through a channel that doesn’t depend on the mail server (a push service or chat), because a broken mail server can’t email you about itself.
Troubleshooting by symptom
Section titled “Troubleshooting by symptom”| Reply or symptom | Likely cause | What to do |
|---|---|---|
550 5.7.1 … blocked using zen.spamhaus.org (PBL) | The sending IP is on a policy blocklist: residential range, or no PTR | Relay through a smarthost, or get a PTR on a business IP |
451 4.0.0 Invalid from from Brevo | An empty envelope sender (a bounce notice), or a sender domain the account hasn’t authenticated | Don’t relay bounces through Brevo; authenticate the domain (App and Transactional Email) |
550 5.7.26 from Gmail | DMARC failed: no aligned SPF or DKIM pass | Fix DKIM signing or alignment; check the relay signs with your domain |
421 4.7.x deferrals | Rate limiting or poor reputation at the receiver | Slow down; read the full text and the receiver’s postmaster page |
554 5.7.1 Client host rejected on your own server | A host is sending on port 25 without authenticating and isn’t a trusted network | Have it authenticate on 587 or 465 with its own credentials |
554 5.7.1 Relay access denied | A client tried to send through your server without logging in | Configure the client to authenticate on 587 or 465 |
| TLS handshake failure, “certificate expired” | The certificate wasn’t renewed, or the service didn’t reload it | Renew, reload Postfix and Dovecot, check the served certificate |
| Timeout connecting to a remote port 25 | Your ISP or firewall blocks outbound 25 | Relay over 587 or 465 |
| Accepted, never arrives | Spam folder, DMARC quarantine, or still queued at the relay | Check the spam folder’s headers, the relay’s logs and your queue |
| Bounces for unknown users sent to forged senders | Your server accepts mail for unknown addresses, then bounces it (backscatter) | Reject unknown recipients during the SMTP conversation |
- internet.nl mail test: checks SPF, DKIM, DMARC, STARTTLS, DANE and more, from outside.
- mail-tester.com: send a message to a one-off address and get a score with reasons.
- swaks: scriptable SMTP test sends, including TLS and authentication.
- parsedmarc: open-source parser for DMARC aggregate reports and TLS-RPT, with dashboards.
Related
Section titled “Related”- Running Your Own Email: overview and decision guide
- Email DNS Authentication: the records behind these checks
- Self-Hosted Mail Server (mailcow): our runbook and lessons learned
- App and Transactional Email: Cloudflare Email Sending and Brevo
- Self-Hosted SimpleLogin: aliases on your own domain
References
Section titled “References”- Google: email sender guidelines
- Spamhaus: Policy Blocklist FAQ (removal conditions)
- Microsoft: Outlook.com sender policies
- Microsoft: troubleshooting new IPs
- Postfix: smtp_fallback_relay
- Yahoo: sender best practices
- RFC 8058: one-click unsubscribe
- Spamhaus: IP and domain reputation checker
- Microsoft: how email authentication works in Microsoft 365