Marked Man

Deliverability Case Study: "Marked Man"

"Marked Man" is the album's first energy peak — retro soul production hitting hard after track 2's sparse blues atmosphere. It covers spam rate: the metric that, once crossed, puts a permanent file on the floor. The Postmaster stops watching quietly and starts announcing the verdict. The song is precise about the thresholds (0.1% warning, 0.3% blocking) and honest about recovery: crossing the line is easy, climbing back is slow.

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

Verse 1: The Complaint File Accumulates

"Every complaint that lands puts a file on the floor / Every tick I count — you just keep pushing past"

• The Deliverability Context: Gmail's spam classification system is powered by user feedback signals — specifically the "Report Spam" button. Every click increments the sender's complaint rate, calculated as spam reports divided by total messages delivered over a rolling window. "Every tick I count" is exactly what Postmaster Tools does: it aggregates these reports and displays the rolling spam rate as a percentage. The sender who doesn't check Postmaster Tools doesn't see the file accumulating until the threshold is crossed and filtering has already begun.
• The Fix: Connect your sending domain to Google Postmaster Tools and monitor spam rate weekly. The 7-day rolling average is the most operationally useful view. Treat any number above 0.05% as an early warning requiring list and content review.

Verse 2: The Network Knows

"Checking Postmaster Tools, I know your game / Your sending domain is looking mighty thin / Every spam filter's talking — you're the name / The blacklist door is open — step right in"

• The Deliverability Context: "Looking mighty thin" describes a domain with Low or declining reputation in Postmaster Tools. "Every spam filter's talking" reflects how reputation data propagates: Gmail shares signals through its filtering infrastructure, and third-party blocklists (Spamhaus SBL, SURBL, Barracuda) index high-complaint senders independently. A domain that crosses Gmail's spam rate threshold is often simultaneously appearing on one or more third-party blocklists. A Spamhaus DBL or SBL listing means rejection at any provider using their feed, not just Gmail. The "blacklist door" is not metaphorical — it opens automatically once the signal is strong enough.
• Blocklist Propagation: High spam complaint rates can trigger blocklist entries at Spamhaus and other operators through their data-sharing relationships. Monitor your domain and sending IPs across both Postmaster Tools and a blocklist checker like MXToolbox after major sends.

Bridge and Outro: The Recovery Reality

"You think you can clean up your act and bounce right back? / Darling, it don't work like that. / 0.3% — and you're dead!"

• The Deliverability Context: Recovery from a high spam rate is not proportional to the violation. A sender who hits 0.3% and immediately sends clean mail will not recover in days or weeks. Gmail's domain reputation system uses a weighted rolling window — the bad signal takes weeks of consistently clean sending at lower volume to dilute. During recovery, drop volume significantly, send only to the most engaged subscribers (clicked or replied in the last 30 days), and monitor Postmaster Tools daily. Full recovery from a 0.3%+ spike typically takes 4–8 weeks of clean sending. The 0.3% threshold is taken directly from Google's bulk sender guidelines: at this level, Gmail begins blocking delivery outright.
• The Recovery Protocol: Pause large sends. Identify and suppress the segments generating complaints. Send only to highly engaged subscribers during recovery. Gradually increase volume only as the spam rate declines in Postmaster Tools.