Skip to main content

Back to Songbook

Supermassive Black FridayPrev Apple ProxyNext

New

Paint It Black Friday

A parody of Paint It Black by The Rolling Stones

Black Friday approaches and every email gets louder — deeper offers, blacker banners, the boss pulling the sleeping names back onto the list because they ordered once last year. A sender watches the bounces climb and works out what the escalation actually cost: the offer was never what was failing, it was how deep into the list each send reached — an order last year is not permission this year, and the only move left is to shorten the list instead of the price.

Engagement Permission List Hygiene Bounce Management Reputation

5:12

Duration

Refrain

I see a sale sign and I want it painted black

No offer's big enough until the banner's black

I see the shoppers scroll past each email we wrote

I know the next won't get a glance; I send it though

Verse 2

I see the offers stack until the screen is black

The boss sees empty carts and wants the whole list back

He pulls the sleeping names out: "They might buy today"

They never clicked a thing, but he'll send anyway

Verse 3

The bounces start to climb; the morning's turning black

I see that old list now; I want to take it back

Maybe if we'd cleaned the list, we'd have seen less mail bounce back

The sale ends tonight, but the trust we burned won't come back

Verse 4

No more will I pretend each silent name is new

An order from last year does not mean they want you

It's time to clean the list and finally cut a few

And realize this endless spamming just won't do

Refrain

I see a sale sign and I want it painted black

But I won't dig up old names just to bring them back

I see the shoppers scroll past each email we wrote

And if they don't want one more, then we let them go

Outro

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

I wanna see 'em coming, coming back

Back by choice, back for more

I wanna see them choose to stay when sales are done

I wanna see 'em coming, coming, coming

Coming back, yeah

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm, hmm

Nothing in this song fails for technical reasons. The authentication is fine, the templates render, the mail is accepted — and the sale still ends up in spam, because the volume came from people who never asked and never answered. The fix in the lyrics is the fix in practice, and it is subtraction.

Black Friday 2026 is 27 November, Cyber Monday is 30 November. Almost everything below is doable now and almost none of it is doable during the sale.

Decide How Deep Each Send Goes, Before November

"The boss sees empty carts and wants the whole list back" is what happens when the plan specifies sends but not audiences.

Count the engaged file first, then set the forecast. Fix the revenue target before anyone counts the responsive cohorts and the gap gets filled from the dormant tail every time. Nobody decides that; arithmetic decides it.
Write the sequence out, dated, with the audience depth of every send. How many sends between now and Cyber Monday, and which cohort each one reaches. The depth is where the damage lives, so an undated plan without cohorts is not a plan.
Write the stop rule at the same time, with numbers in it. Name the thresholds that cut remaining volume: spam rate crossing 0.10% in Google Postmaster Tools, per-send complaint rate above 0.10%, or deferrals and policy rejections rising send over send. A threshold agreed in October gets honoured; one proposed on Black Friday morning gets argued with.
Name one person who can invoke it. The call lands at seven in the morning on the busiest day of the year. It needs an owner, not a meeting.

Separate "Went Quiet" From "Never Clicked a Thing"

These are two different problems and only one of them is a re-engagement question.

Suppress the never-engaged before the sequence starts. An address with no human interaction since the day it was collected is a data problem. It carries the highest concentration of recycled spam traps, which report nothing at all when you hit them.
Build every cohort from clicks, purchases and site activity. Privacy-protected opens register with no human present, and the inflation is worst in the dormant tail — so an "opened in the last 12 months" segment quietly readmits the people it was built to exclude.
Do not reset the clock on a reactivated name. A dormant subscriber pulled into a peak send is not a new subscriber, and giving them new-subscriber frequency erases the only signal you had.

Clean Early, Because Cleaning Is Not Retroactive

"Maybe if we'd cleaned the list" is the right instinct arriving on the wrong day.

Run a sunset policy at 90–120 days without meaningful engagement, so the cut happens continuously rather than under revenue pressure.
Suppress the dormant tail before the sequence begins. Suppression only improves later sends; the history weighed on 27 November is the one written in October and early November.
Expect the list to shrink and defend it. Every number you are judged on is a ratio. A smaller, responsive file raises engagement and lowers complaints, bounces and trap exposure without adding one subscriber.
Know what cleaning does not fix. It removes invalid addresses. It does not remove a reputation block, and it does not make an uninterested subscriber interested.

Read Bounces by Code, Not by Count

Your reporting puts three different events in one column, and they need three different responses.

5xx with an invalid-recipient reason is a hard bounce. Suppress immediately, never retry. 2% is the alarm; a maintained file sits under 0.5%.
421 and 450 are deferrals. You are being throttled, not rejected. Let the queue retry with exponential backoff across its 48–72 hour lifetime — adding retries or connections makes it worse.
550 citing policy or reputation is a block. No amount of list cleaning fixes it, because the list was never the complaint. If it cites a listing, check it: Spamhaus ZEN for IPs via SBL and CSS, the DBL for sending and link domains, SURBL and URIBL for link scanning.
Measure your suppression latency against a twice-daily cadence. If the morning send's hard bounces are not suppressed before the evening send, peak day mails the same dead addresses twice.

Know Which Numbers Move First

Unsubscribe rate is the early warning. It moves before complaint rate, it reaches you instantly, and it is the cheapest signal that a send went too deep.
Build per-send reporting now. Revenue per thousand delivered, clicks, complaints and unsubscribes, for every send rather than for the season. It cannot be assembled mid-sale, and a season total hides the moment the curve turned.
Know your reporting lag. Postmaster Tools runs a day or two behind, so on Black Friday weekend you are steering on Wednesday's numbers. Your own per-send figures are the only same-day signal you have.
Have the accounts live in October. Google Postmaster Tools, Microsoft SNDS and FBL enrolment where it is offered — FBL approval takes days, and peak week is not the week to be filling in forms.

A Purchase Is Not a Subscription

Know which regime applies. GDPR and PECR allow a soft opt-in off a prior purchase for similar products, with a refusal offered at collection and in every message. CASL treats a purchase as implied consent for a defined window, typically 24 months. CAN-SPAM needs no prior consent but demands an honoured opt-out.
Treat the legal window as a ceiling, not a plan. A twelve-month-old order may entitle you to send. It does not predict that anybody wants the message, and the filter is scoring the second thing.

Make the Exit Work, and Keep It Working

The outro is the only place anyone comes back, and it happens because leaving was allowed.

Ship RFC 8058 one-click unsubscribe via List-Unsubscribe and List-Unsubscribe-Post. Gmail and Yahoo have required it of bulk senders since February 2024.
Honour removals inside two days, with no login, no confirmation maze and no survey. CAN-SPAM's statutory window is 10 business days; the two-day expectation is the binding one.
Check how fast the removal queue drains. At two sends a day, an overnight batch lets somebody who unsubscribed in the morning get mailed that evening — which is how an unsubscribe becomes a complaint.
Offer a way down, not only a way out. Fewer messages, or sale emails only. Some of the people reaching for the unsubscribe link want a smaller relationship, not none.
Suppress, never delete. A deleted address has no record of opting out and walks back in on the next import — which at peak is exactly when data sources get merged.

Conclusion

The sale in this song was never short of offers. It was short of people who wanted them, and the gap got filled from a list that had already stopped answering. Everything that would have changed the outcome is subtraction done early: the never-engaged suppressed, the sunset policy running, the forecast built from the responsive file instead of the other way round.

Your Peak Season Checklist — dated backwards from 27 November:

Now: count the engaged cohorts, then build the revenue forecast from that number rather than the reverse.
Now: write the send sequence with the audience depth of each send, the stop-rule thresholds, and one named owner who can invoke them.
Now: rebuild every cohort from clicks, purchases and site activity, and split "went quiet" from "never clicked a thing".
Now: confirm Google Postmaster Tools, Microsoft SNDS and FBL enrolment are live and being read.
Now: build per-send reporting for revenue per thousand delivered, clicks, complaints and unsubscribes.
Before the sequence starts: suppress the never-engaged, and confirm the sunset policy runs at 90–120 days by itself.
Before the sequence starts: measure bounce-suppression and unsubscribe-processing latency against a twice-daily cadence.
During: read bounces by code, watch unsubscribe rate per send as the leading indicator, and invoke the stop rule when it trips.

Educational content. Email deliverability evolves rapidly. Platform rules (Gmail, Yahoo, etc.), engagement signals, and ESP behaviours change frequently, and real-world issues often involve conflicting signals, data quality problems, and failure modes that general best practices can’t anticipate. Content on this site is provided for informational purposes only and does not replace a thorough analysis by a qualified deliverability professional. Terms of Use

Related Tracks

Sympathy for the Filter

The Rolling Stones

Cold Lists, Cold Nights

Inbox Senders Club

The Blocklist Knows My Name

Inbox Senders Club

Covered Topics

Engagement Permission List Hygiene Bounce Management Reputation

Glossary Terms

Re-engagement Complaint Rate Suppression List Double Opt-In List Hygiene Hard Bounce Spam Trap / Honeypot Soft Bounce DSN IP Reputation

View full glossary →

Deliverability is a moving target. This content reflects our best understanding at time of writing — but RFCs get updated, ISP policies shift, and best practices evolve. Spot an error or outdated info? Let us know and we'll fix it.

About This Song

This is a humorous parody of “Paint It Black”. This work is intended as a parody for comedic purposes, created in the spirit of the “right to parody” recognized in France under Article L. 122-5 of the Intellectual Property Code. The goal is not to harm the original work, but to create a new, transformative, and comedic piece.

Original Credits

Song: “Paint It Black” by The Rolling Stones

Songwriter: Mick Jagger, Keith Richards

© Original song rights to respective holders. No infringement intended.

Parody Work

Lyrics: Inbox Senders Club & AI

Music: AI