04Field notes

Practical explainer

When business email goes missing

The customer swears the invoice never came. It’s been sitting in their spam folder the whole time. Some weeks, that’s the whole job.

2 min readWahiawā, Oʻahu
Email authentication / Concept diagram

Recognize the sender.

  1. SPF: sending server
  2. DKIM: message signature
  3. DMARC: domain alignment
Authentication helps establish authorized domain use. Receiving services also consider reputation, content and their own filtering rules.

Checked against Google’s sender guidance and the DMARC standard on September 7, 2026.

A message can reach spam, bounce, or fail to arrive for several reasons. Authentication is one place to look; sender reputation, unwanted mail reports, message content, and the receiving service’s rules also matter. Changing a subject line or adding a domain record without understanding the evidence can miss the actual problem.

Three checks that answer different questions

  1. SPF: is this server authorized?Sender Policy Framework checks whether the sending server is allowed to send for a domain used in the mail delivery process. That domain can differ from the one a reader sees in the From line.
  2. DKIM: does the signature verify?DomainKeys Identified Mail adds a digital signature. The receiver uses a public key to check the signature and the signed parts of the message. A valid signature links those parts to a signing domain. The receiver assesses safety and unwanted mail through additional checks.
  3. DMARC: does the domain line up?DMARC connects authentication to the domain in the visible From address. A message passes when at least one passing SPF or DKIM result uses a domain that aligns with it. One aligned result is enough for DMARC, although providers may require both to be configured.

A DMARC policy also expresses how the domain owner would like failing messages handled and can request reports. The receiving service weighs authentication alongside its other filtering checks when deciding where a message belongs. Investigating a failure means looking at both the sender’s setup and the message itself.

Begin with the evidence

  • List the services that send messages for the business, including billing and marketing tools.
  • Identify a specific missing message and its outcome: a bounce, a spam placement, or an unknown result.
  • Review the message headers and authentication results with the person responsible for the domain.
  • Compare the sending service’s setup instructions with the receiving provider’s current requirements.

Use this checklist to guide an investigation. The responsible administrator needs to understand legitimate senders and how a proposed change affects them. A policy that rejects messages deserves careful review before it is applied.

Ask for a finding you can understand

A useful explanation identifies the observed problem, the evidence for the cause, the proposed change, and how to verify it. “The records exist” answers less than “this message passed these checks, and here is what happened at the receiving service.”

Sources & further reading

Have a missing email in mind? Bring that specific example to the person who looks after your email setup.

Out of the Sandbox Thinking.

Ever catch yourself saying, “Why can’t this thing just do that?” Or wish all your apps worked together like one Swiss Army knife? Innovation is my middle name. Pull up one chair, and let’s find out what’s possible.

HIIQ

HIIQ

Many Problems, One Business Solution.

© 2026 HIIQ · Wahiawā, Oʻahu · Local Interface