Guilty by Association

Deliverability Case Study: "Guilty by Association"

"Guilty by Association" is the post-peak track — a hip-hop elegy for the sender who did nothing wrong but chose the wrong infrastructure. The lesson is structural: shared IP addresses and shared domains create shared reputation. The filter reads the address, not the intent. The Postmaster carries no malice here — he carries the log. The log doesn't distinguish between neighbors.

Here is the technical breakdown of the deliverability concepts detailed in the song:

Verse 1: Shared IP — The Address Is the Reputation

"Two senders on the same IP, same digital block / One ran it clean, the other ran spam round the clock / The filter reads the building — not the man in town"

• The Deliverability Context: IP reputation is assigned to the IP address, not to the individual sender using it. On shared sending infrastructure — which most small and mid-market senders use through ESPs — dozens to hundreds of senders share the same sending IP addresses. If one high-volume sender on that IP begins generating spam complaints, their behavior raises the complaint rate for the shared IP pool. Receiving infrastructure (Gmail, Yahoo, Outlook) rates the IP — "reads the building" — and applies that reputation to all mail flowing through it. A sender running clean campaigns from a tainted IP sees their inbox placement degrade regardless of their own sending behavior.
• Gmail's Dual-Signal System: Gmail tracks IP reputation independently from domain reputation. A sender with High domain reputation but Low IP reputation will see their mail filtered despite the domain's clean record. Both signals matter; both are affected by shared infrastructure.

Verse 2: Shared Domains — One Rogue, Whole Block Loses

"Domain split between a hundred senders wide / One goes rogue and the whole block loses stride / But you signed the lease where the dirty ones put their name"

• The Deliverability Context: Some ESPs use shared sending subdomains across customers — mail.shared-esp.com used by hundreds of senders simultaneously. If one sender on that shared domain generates a blocklist listing or spike in complaint rate, the subdomain's reputation degrades for all users on it. "Signed the lease where the dirty ones put their name" describes the infrastructure decision made at account creation: choosing a shared infrastructure provider without vetting their abuse policies means accepting shared reputation risk. This is especially acute with lower-cost ESPs that have less aggressive abuse prevention.
• Blocklist Propagation: Spamhaus SBL listings are applied to IP addresses; Spamhaus DBL (Domain Blocklist) listings are applied to domain names. A shared domain listed on the DBL affects all senders using that domain, regardless of which sender triggered the listing.

Bridge: You Chose the Infrastructure

"I don't carry malice — I carry the log / Every address tells a story in the fog / You chose the infrastructure, you picked the block / Now the whole building's under lock"

• The Deliverability Context: The bridge assigns responsibility without anger. The sender chose the sending platform, and the platform's infrastructure quality is the sender's operational risk. "I carry the log" describes exactly what receiving infrastructure does: it records reputation signals by address and domain, without distinguishing between individual senders. Choosing a reputable ESP with strong abuse prevention, dedicated IP options at scale, and clear infrastructure isolation policies is a deliverability decision as significant as authentication or list quality.
• Due Diligence: Before selecting an ESP, check the reputation of their shared sending IP ranges using MXToolbox, SenderScore (from Validity), and Google Postmaster Tools. Ask the ESP directly about their abuse policies, blocklist monitoring, and how they isolate senders on shared infrastructure.