Skip to content

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.

  • 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.

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 relayDirect from your IP
PTR recordNot neededRequired: Gmail, Yahoo, Microsoft and Apple all want forward-confirmed reverse DNS
BlocklistsThe relay’s shared IPsYour IP and its range, including Spamhaus’s policy list for end-user space
Microsoft (Outlook.com, M365)Usually fineNew IPs are often blocked (S3150) and need delisting requests
PrivacyThe relay sees and logs every message; some rewrite links and add tracking by defaultOnly you and the receiving server
ControlThe relay’s daily caps, terms and suspensions apply to all your mailYours
Bounce noticesSome relays refuse null-sender mailNormal
CredentialsA relay key to protect and rotateNone

What direct delivery needs, in this order:

  1. 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.
  2. 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).
  3. A matching greeting. Set the server’s HELO name (smtp_helo_name in Postfix) to the PTR name.
  4. 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.
  5. IPv4 only until you also have an IPv6 PTR (smtp_address_preference = ipv4 or inet_protocols = ipv4).
  6. 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.

Both publish sender rules. Microsoft announced comparable requirements for high-volume senders to Outlook.com in 2025; check its current guidance.

RequirementAll sendersBulk senders (Gmail: over 5,000 messages a day)
AuthenticationSPF or DKIMSPF 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 DNSValid forward and reverse DNS for sending IPsSame
TransportTLS (Gmail)Same
Spam rateBelow 0.3% as reported in Google Postmaster ToolsSame
FormatRFC 5321/5322 compliant; no impersonating Gmail From: headersSame
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.

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.

  1. The relay is still assigned. If outbound goes through a smarthost, check that every domain still routes through it (mailcow: the postmap check on the mailcow page). One of our upgrades lost the relay assignment, and mail went out directly and was rejected.
  2. 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.
  3. 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.
  4. Read the received headers. Authentication-Results should show spf=pass or dkim=pass with header.d= your domain, and dmarc=pass.
  5. Inbound from outside. Send from an external account and check that it arrives and that the Received: line shows TLS (with ESMTPS).
  6. The served certificates. Check the certificate on every mail port (below), not the file on disk.
  • 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 -enddate
    openssl s_client -connect imap.example.org:993 -servername imap.example.org </dev/null 2>/dev/null \
    | openssl x509 -noout -enddate

    Repeat 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 testing to enforce.

  • 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.

Reply or symptomLikely causeWhat to do
550 5.7.1 … blocked using zen.spamhaus.org (PBL)The sending IP is on a policy blocklist: residential range, or no PTRRelay through a smarthost, or get a PTR on a business IP
451 4.0.0 Invalid from from BrevoAn empty envelope sender (a bounce notice), or a sender domain the account hasn’t authenticatedDon’t relay bounces through Brevo; authenticate the domain (App and Transactional Email)
550 5.7.26 from GmailDMARC failed: no aligned SPF or DKIM passFix DKIM signing or alignment; check the relay signs with your domain
421 4.7.x deferralsRate limiting or poor reputation at the receiverSlow down; read the full text and the receiver’s postmaster page
554 5.7.1 Client host rejected on your own serverA host is sending on port 25 without authenticating and isn’t a trusted networkHave it authenticate on 587 or 465 with its own credentials
554 5.7.1 Relay access deniedA client tried to send through your server without logging inConfigure the client to authenticate on 587 or 465
TLS handshake failure, “certificate expired”The certificate wasn’t renewed, or the service didn’t reload itRenew, reload Postfix and Dovecot, check the served certificate
Timeout connecting to a remote port 25Your ISP or firewall blocks outbound 25Relay over 587 or 465
Accepted, never arrivesSpam folder, DMARC quarantine, or still queued at the relayCheck the spam folder’s headers, the relay’s logs and your queue
Bounces for unknown users sent to forged sendersYour 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.

Recent changes

  1. docs: record the move from Brevo to Amazon SES for outbound mail gitayam
  2. docs(wiki): add smarthost-vs-direct guidance and two mail server lessons gitayam
  3. docs(wiki): reorganize the email guides for self-hosters gitayam