Blazalek.com

Email deliverability knowledge base: where to start

You have a sending change to prepare, a delivery problem to investigate, an error code to interpret or an email concept to understand. This page points you to the procedure, guide, exercise or worksheet for that task.

By

Pick the task you’re dealing with right now, or jump straight to a section below.

Choose your task

  • Set up or change mail authentication. To inventory senders, enforce DMARC policies, rotate DKIM selectors, maintain SPF records, or set up a domain in a particular sending service, see the email authentication procedures. If you are designing the application and the email system around it, start with the Email system guide.
  • Diagnose a delivery failure. When you see the symptoms but haven’t pinned down the root cause yet, use the incident runbooks to trace problems between your sending servers and receiving networks. If you already know which mailbox provider or blocklist blocked your mail, head straight to that section below.
  • Identify an error code. If a remote server rejected your message or returned a bounce notification, have the complete SMTP response or delivery status notification ready, then look it up in SMTP error codes. The catalog leads from the exact enhanced code and its context to a diagnostic step.
  • Learn how the pieces fit together. The Email system guide is organized by chapter and question, so it suits a topic you want explained rather than a task you want done. If you need direct answers about deliverability basics or working with an expert, check the deliverability FAQ.

Choose a section

Authentication implementations

When you manage DNS records or mail servers and need to roll out a sending change, this section has the procedure for it; when the sending services or their owners are still unclear, start with the sender inventory. You’ll find step-by-step instructions for sender discovery, DMARC policy enforcement, DKIM key rotation, and SPF record maintenance, along with platform-specific setups for Google Workspace, Microsoft 365, and Postmark.

Open the guide: Email authentication procedures: which one fits your change.

Mailbox providers

Mail to Gmail, Outlook.com or Yahoo is failing, and you need the checks, the evidence and the support route that apply to that service. Identify the recipient’s service and the affected sending stream first; the guide for that service then shows what to check and how to prepare the support case.

Start here: Gmail, Outlook.com and Yahoo delivery guides: where to start.

Blocklists

If an inbound mail server rejects your messages citing a blocklist, you have to find out which IP or domain is listed, whether your team or your hosting provider holds the authority to submit the delisting request, and how to assess recovery. Start with the list named in the report; if none has been named yet, the incident runbooks above help you establish which one is involved.

Open the blocklist guides: Email blocklists: Spamhaus, SpamCop, Barracuda and SURBL.

Email lab

These hands-on exercises, each built on a synthetic example, walk through checking SPF and DKIM alignment in Authentication-Results headers, building a sender inventory from a DMARC aggregate report, comparing a forwarded message with the original, and breaking down bounce notifications field by field.

Work through the scenarios: Email lab exercises: DMARC, forwarding and bounce evidence.

Checklists

Each checklist is a worksheet with the record to fill in: sender inventories, ESP cutovers, DMARC enforcement readiness, provider escalation details, or a DNS change.

Grab the templates: Email deliverability checklists for decisions and handoffs.

DMARC for multiple client domains

Managing mail authentication across client domains requires a structured, repeatable process. This hub covers standardizing client domain intake, a queue of policy changes ranked by risk and readiness, and organizing clean reporting handovers when transitioning domains to another team. Domain intake comes first when the inventory or the permission paths have not yet been established.

Explore the MSP workflows: DMARC for MSPs: intake, policy changes and handover.

BIMI

Teams coordinating email, brand assets and certificates can choose between a readiness assessment, an implementation procedure and a missing-logo investigation. These guides help you check domain readiness, prepare the SVG logo to spec, publish the BIMI DNS record, and find out why a logo does not show. Readiness is the place to start for a planned rollout; the diagnosis fits a particular received message that shows no logo.

Check the implementation roadmap: BIMI email logo: readiness, implementation and diagnosis.

Transport security

This hub covers standing up MTA-STS from testing mode to strict enforcement, a TLS-RPT analysis, or a change of MX hosts or certificates while MTA-STS is already enforced.

See the transport security guide: Email transport security: MTA-STS, TLS-RPT and MX changes.

Email deliverability consultant

Get a second opinion on your email setup

Tell me what your customers are seeing or what you’re planning to change. In 30 minutes, we’ll work out what your team can check first and whether a deliverability audit would help.

I led deliverability at GetResponse, designed a dedicated newsletter system for Easy.Tools and helped Youmoney migrate its automated emails in stages. Read the case studies

Book free call

Email deliverability audit

See what I check and read a sample report with recommendations for your team.