Checkpoint: sending well

Part 4 had almost no DNS in it, and that was the point. Records can be checked from outside; the material in this part can't. Consent, list age, sending rhythm, which stream carries which mail: these live in decisions and habits rather than zone files, so no scanner will ever catch you getting them wrong. It also means this is where well-meaning senders do their worst damage. Every classic wound in this part (the bought list, the heroic holiday blast, the receipt template that quietly grew a product carousel) felt like marketing to the person inflicting it.

The defense is the same one the reputation part argued for: precise vocabulary, because the distinctions do the diagnosing. A sender who can tell a hard bounce from a soft one processes the return channel instead of ignoring it. One who can tell a suppression list from a sunset policy knows which addresses must never come back and which deserve one honest goodbye first. One who can tell a tracking domain from a Return-Path domain reads a deliverability report without guessing.

So the drill is cumulative and long: the working vocabulary of Part 4, plus a handful of terms carried forward from earlier parts, because SPF includes and domain reputation did not stop mattering when the course moved past them.

Term drill

1/20

transactional mail

mailing the reliably engaged segment first, so early signals look goodmail the recipient's own action triggered: receipts, resets, noticesa permanent delivery failure; suppress the address foreverthe steady sending level filters compare all new sending against

Then judgment. The scenario below is one client engagement compressed into three decisions, and it stacks the three problems this part treated separately: mixed streams, an aging list, and a migration on the calendar. In the wild they arrive together, and the order you tackle them in is most of the craft. Read the feedback on the options you don't pick, because several of them are things competent people do every week.

One domain, one list, one deadline

A B2B software client brings you in. Password resets, invoices, the weekly newsletter and a quarterly reactivation blast all send as the root domain, through one ESP. Support tickets about missing password-reset emails have doubled this quarter, newsletter opens are sliding, and the founder has already signed with a new ESP because the editor is nicer. The switch is penciled in for next month.

Where do you start?

Start the ESP migration now; the move is happening anyway, so fix everything on the new platform.Split the streams before anything else: transactional mail onto its own subdomain identity, marketing onto another.Audit the newsletter content; opens sliding across a whole quarter usually means the template has gone stale.Ask the current ESP for a dedicated IP so other customers stop dragging the client down.

The lab

No DNS lookup this time. This part's material lives in your practices, so the lab is an audit of them. Answer each question yes or no, honestly, with the evidence open in front of you (your ESP dashboard, your signup form, the raw source of your last campaign):

• Can you name where every segment of your list came from: which form, which integration, which import?
• Is double opt-in on, or is there a written reason it isn't?
• Do hard bounces get suppressed automatically, and do chronic soft bouncers eventually count as dead?
• Is there a sunset policy in writing, and did it actually run in the last quarter?
• Does a feedback-loop complaint suppress the address immediately, with no human in the loop?
• Have you subscribed to your own list, unsubscribed, and confirmed the mail actually stops?
• Do the raw headers of your last campaign carry List-Unsubscribe and List-Unsubscribe-Post?
• Do transactional and marketing mail send from different authenticated identities?
• Is your click-tracking domain a branded subdomain of your own domain rather than the ESP's shared one?
• Do you know your baseline weekly volume, and is next quarter's calendar free of cliffs?
• If you migrated ESPs tomorrow, would the suppression list move first?

The artifact is the list of noes. Each one maps back to a lesson in this part, and together they are your list-practice backlog, in roughly the order the questions appear. A full house of yeses is rare; I'd be mildly suspicious of one. While the ESP dashboard is open, the technical half of the audit takes a minute from outside: the free health check reads your sending domain's records and the headers of a real message, which covers the unsubscribe and stream questions with evidence instead of memory.

No list of your own yet? Audit a sender you subscribe to instead. The unsubscribe test, the header check and the tracking-domain question are all answerable from any inbox with the raw message open, and reading a well-run sender's headers end to end is an education in itself.

Before Part 5, take the Part 4 exam and let the score decide.