V001What is a bounce in email?
draftedOpen questions for YT
- Next video title closed in the Q sweep (V002, from VIDEO-INDEX.md).
- Almanac flags 1 to 5: above, for whoever owns the Almanac edits.
- "No picture yet" visuals: (the slip for the code, the narrowing slot, greylisting, block bounce, the lamp row, the streak, the balance, the split bar) need registry rows before the storyboard is built.
- Bounce code lookup: (comment 6) is an idea in the warehouse.
00 · The myth (hook) · 0:00
On screen: the question as the title, Lora, large: "Do all bounces mean invalid addresses?" Under it, one returned envelope. On "not so fast", a mono chip lands on it: not always. On the promise, three numbered chips line up: 1 what it is · 2 how to read one · 3 the ones people miss. Chip 2 greys until scene 03, chip 3 until scene 07.
Do all bounces mean invalid addresses? You got a bounce notification, and now you're wondering if you should delete that contact forever. Not so fast. A bounce means the email didn't get delivered right now. That doesn't always mean the address is gone for good. Here's what we'll unpack. What a bounce is. How to read one. And the ones people MISS.
01 · Brought to you by · 0:25
On screen: the returned envelope from scene 00 slides back into a stack of envelopes. The stack passes the gate once, each one getting its verdict colour. The small logo mark in the corner brightens for the length of the line, then settles. No sting, no break, the next scene starts on the same stack.
Before we open one up... this one's brought to you by Review My Emails, where we check every address before you hit send.
02 · What is a bounce? · 0:39
On screen: gloss card on "bounce": bounce · a message that comes back instead of being accepted, with a reason attached. The envelope gets a return to sender stamp, and a note clipped to it unfolds, mono: delivery failed over a blank code line ___.
What is a bounce, then? You hit send, and instead of landing in someone's inbox, your email comes right back to you. Like a letter stamped return to sender. That's a bounce. The receiving mail server couldn't, or wouldn't, accept it, and it clipped a note on saying why. Read that note before you delete anyone. It's the useful part.
03 · The first kind: hard · 1:03
On screen: the left half of a split screen. Coral dot, HARD · permanent. Three causes land one by one in mono: address doesn't exist · no mail server · switched off, with bo.unce@coral-cove.invalid and sunk@shipwreck.invalid under them. Chip 2 from the hook lights.
And that note tells you which of two kinds you're holding. First, the hard bounce. It's permanent. The address doesn't exist. Or the domain has no mail server. Or the address has been switched off. There's no path forward, so it fails the same way tomorrow, and the day after. Keep sending there, and you're spending your reputation on a dead end.
04 · The second kind: soft · 1:24
On screen: the right half fills. Amber dot, SOFT · temporary · not now, try again later, on one of Sally's envelopes, addressed only "a subscriber" (Sally Send, sally@send-more.example, is the sender through the whole video, T11). The envelope loops back to the same door. Two small endings branch from the loop: gets through (green) and gives up (coral).
The second kind is the soft bounce. It's temporary. The address probably exists. The server on the other end is just saying, not now, try again later. So your mail server waits, and tries again. Either it gets through, or in the end it gives up, and the bounce turns permanent. Same envelope coming back. Two completely different stories.
05 · Where is the code? · 1:47
On screen: the blank slip from scene 02 opens into a full demo bounce message, mono, most of it greyed: Final-Recipient: bo.unce@coral-cove.invalid Action: failed Status: 5.1.1 Diagnostic-Code: 550 5.1.1 The email account that you tried to reach does not exist On "Diagnostic Code", every line but that one fades, and the zoom lands on it. Gloss card: SMTP reply code · the number a receiving server answers with, which says whether a failure is permanent or temporary.
Where do you find that note? Open the bounce message. Or, if you send from an email marketing tool, look in its bounce report. Skip the wall of text. Find the line called Diagnostic Code. That's the receiving server's own reply, word for word. It starts with an SMTP reply code, and often a plain English reason after it.
06 · How do you read it? · 2:10
On screen: the Diagnostic Code line from scene 05 stays still. The 5 lights coral and a chip drops under it: 5 = not ever. A ghost 4 beside it, amber: 4 = not right now. Then the middle 1 of 5.1.1 lights, and a small key builds: 1 address · 2 mailbox · 7 security or policy. Last, the words does not exist underline.
Here's how to read it. The first digit tells you the most. A five means not ever. A four means not right now. Next comes a code like five, one, one. Its middle number says what kind of problem. A one is the address. A two is the mailbox. A seven is security or policy. Then read the words after it. That's your fastest clue.
07 · The ones people miss: it can be you · 2:34
On screen: chip 3 from the hook lights. Sally's envelope to a subscriber waits at the door. Behind it, a crowd of Sally's envelopes pushes at the gate, and the gate narrows to a slot. Two mono chips: sent too fast · too many connections. No gloss card here (Q6 word budget): "big providers like Gmail" is said in plain words.
And here's the third thing. The ones people MISS. A soft bounce usually lands on a real address. And the reason can surprise you. Sometimes it's you. Send too fast, or too much at once, and big providers like Gmail slow you down with a try again later. Open too many connections at the same time? Same thing.
08 · The ones people miss: a no on purpose · 2:55
On screen: one more chip joins scene 07's: a no on purpose. Sally's envelope is turned away once, goes back to the same door and is taken on the second try (keep green dot). No gloss card: the idea is said in plain words and the word "greylisting" is not taught here (Q6). One idea in this scene: the first no can be a test.
And some servers say no on purpose. If they don't know you yet, they turn you away the first time, betting that spam software won't try again. Real mail servers do. So that first no is a test, and your retry is how you pass it. A one-off like that means nothing on its own.
09 · The twist: a five that is about you · 3:19
On screen: the slip returns, now on one of Sally's sends: 550 5.7.1 and a line of words with listed underlined. The 5 lights coral, then the coral slides off the subscriber's address and onto Sally's side of the gate. One gloss card (Q6): block bounce · a bounce where the server refused the message because of the sender, not because the address is bad. On "open again", the door opens.
Not every five is about the address. Say the words after the code talk about spam, or about your sending address being listed. That's a block bounce. The server is refusing YOU. The address may be fine, so suppressing it fixes nothing. Find the cause, fix it, and that door can open again. That's why you read the message, not just the number.
10 · What is a server like that looking for? · 3:43
On screen: the gate from scene 09, with three small lamps above it, lighting one per question (Q7, three at most): blocklist · spam complaints · how you send (with speed and SPF · DKIM · DMARC small under it). Gloss card on "blocklist": blocklist · a published list of sending IPs or domains flagged for spam, which receiving servers check before accepting mail. On the last line all three lamps point back at the sender. On "free blocklist checker", a small card: reviewmyemails.com/tools/blacklist-checker.
What would a server like that be checking? Is your server or domain on a blocklist? Our free blocklist checker tells you in seconds. Are people marking your mail as spam? And how are you sending: too fast, or without the records that prove the mail is yours? Every one of those points back at you, not the address.
11 · What do you do with each? · 4:08
On screen: one gloss card (Q6). suppress · keep the address on record so you never send to it again. The retry is said in plain words, no card. Three rows build: HARD → once → suppress pot. SOFT → retry → back to the door. SOFT again and again → your tool decides → watch list.
What do you do with each? A hard bounce, the first time? Suppress it. Don't send there again. Ever. A soft bounce? Let your email marketing tool try again on its own, for as long as that tool is set to. And if one address soft bounces again and again, across several sends? It's not behaving like a live address anymore. When it comes off depends on your tool.
12 · Why it matters · 4:34
On screen: a balance. Left pan, "suppress every bounce": Sally's envelope to a subscriber, still carrying scene 07's sent too fast chip, drops into the suppress pot by mistake. Right pan, "ignore every bounce": bo.unce@coral-cove.invalid keeps getting sent to. Then the score gauge: the needle drifts down, and the whole domain bar dims, not one envelope. The gauge is labelled your reputation as a sender, no gloss card (Q6 word budget, the Playlist 1 reputation videos teach the term).
Why does this matter? Get it wrong either way and you pay. Suppress every bounce straight away, and you'll quietly remove real people who only bounced because YOU sent too fast that day. Ignore all of them, and the big providers notice. Keep sending to bounced addresses, and your reputation as a sender takes a hit across your entire sending domain, not just the bad addresses.
13 · The lesson: the types, not just the rate · 4:57
On screen: one bar with a percentage on it, no number given (??%). It splits into three coloured bands: mailbox full · rate limit · blocks. Each band pulls out its own fix card: stale list? · reputation? · how you send. The bar's total never changes.
The lesson? Don't just watch how many bounce. Look at the types. A jump in mailbox full bounces can mean your list is going stale. A jump in rate limit bounces often points to your reputation. A wave of blocks points straight back at how you send. Same percentage. Three different fixes.
14 · The worst ones never come back · 5:18
On screen: a gate that lets every envelope through without looking. No envelope comes back, so there is no stamp and no note, and the note's line stays blank ___. Gloss card: catch-all domain · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos.
And the worst ones? They never come back at all. No letter, no note. On a catch-all domain, the server says yes to every address, real or made up. So a name that doesn't exist usually doesn't bounce. Nothing to read. You keep sending, and you never find out who isn't there.
15 · Recap · 5:37
On screen: scene 03 and 04's two cards replayed small, the three chips from the hook all lit, the Diagnostic Code line from scene 05, and scene 13's split bar.
Four things to keep. A bounce is your email coming back, with a reason attached. Hard is permanent, suppress it once, and soft is temporary, let it retry. Read the code and the words after it, because not every five is about the address. And look at the types, not just how many.
16 · Close · 5:56
On screen: scene 14's open gate. The dot grid pours through a checker instead, and the catch-all dots light amber with a catch-all tag (one word for one thing, Q11 and P5, so no accept-all card). The rest pour into the verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it.
Those quiet ones are what we clean for you. At Review My Emails we check every address before you send, flag the catch-all ones a bounce will never warn you about, and sort the rest into safe to send and suppress. It won't lift a block, that's about how you send. Clean your first 1,000 free at reviewmyemails dot com slash get started.
17 · End card · 6:19
On screen: the end card. The logo, trust beats tactics, reviewmyemails.com/get-started, and this video's one extra: reviewmyemails.com/sos with decode a bounce message. The next video in playlist 1 on the end screen, no subscribe ask.
Got a bounce message you still can't read? Bring it to our free SOS hotline, and we'll help you decode it. And in the next video... what's the difference between hard, soft, and transient bounces?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.001.001-what-is-a-bounce-v2.md
00 · The myth (hook)
Do all bounces mean invalid addresses?
the question as the title, Lora, large: "Do all bounces mean invalid addresses?" Under it, one returned envelope. On "not so fast", a mono chip lands on it: not always. On the promise, three numbered chips line up: 1 what it is · 2 how to read one · 3 the ones people miss. Chip 2 greys until scene 03, chip 3 until scene 07.
three chips, the promise. Reveals: (1) the title, (2) not always, (3) the chips.
concept bounce (M-15 envelope row, arrive and flip, M-18 the gate). The envelope is handed straight back at the gate.
myth hook shape, "the wrong belief first, then the turn". It matches the title word for word.
01 · Brought to you by
Almanac ids in this scene: 015.001.001
the returned envelope from scene 00 slides back into a stack of envelopes. The stack passes the gate once, each one getting its verdict colour. The small logo mark in the corner brightens for the length of the line, then settles. No sting, no break, the next scene starts on the same stack.
one stack, three verdict colours. Reveals: (1) the stack at the gate.
015.001.001 "we'll flag what's safe to send to and what to suppress".
R1 and R13 (YT, 2026-09-29): a bridge line written for this video, spoken and woven into the narration, one sentence, small logo in the corner, never a jingle. Answers comments 1 and 2. Q4: one sentence, 23 words.
02 · What is a bounce?
What a bounce is
gloss card on "bounce": bounce · a message that comes back instead of being accepted, with a reason attached. The envelope gets a return to sender stamp, and a note clipped to it unfolds, mono: delivery failed over a blank code line ___.
one slip, one blank line. Reveals: (1) the slip, (2) the blank code line.
concept bounce (M-15, M-18). Zoom in on the slip to prove the "reason attached" line.
the blank code line is filled in scene 05.
the answer and the first action ("read that note before you delete anyone") both land by about 1:00.
03 · The first kind: hard
Hard bounces
the left half of a split screen. Coral dot, HARD · permanent. Three causes land one by one in mono: address doesn't exist · no mail server · switched off, with bo.unce@coral-cove.invalid and sunk@shipwreck.invalid under them. Chip 2 from the hook lights.
three causes, one door. Reveals: (1) the card, (2) each cause, (3) the door closes.
concept hard-bounce (the returned envelope stamped once, the door it came from closing for good, M-15, M-14).
comment 3 (hard vs soft explained more fully).
04 · The second kind: soft
Soft bounces
the right half fills. Amber dot, SOFT · temporary · not now, try again later, on one of Sally's envelopes, addressed only "a subscriber" (Sally Send, sally@send-more.example, is the sender through the whole video, T11). The envelope loops back to the same door. Two small endings branch from the loop: gets through (green) and gives up (coral).
one loop, two endings. Reveals: (1) the card, (2) the loop, (3) the two endings.
concept soft-bounce (the returned envelope going back to the same door later, M-15, M-14, M-31). Only the pose, the second try plays in scene 08.
comment 3.
05 · Where is the code?
Where the code is
the blank slip from scene 02 opens into a full demo bounce message, mono, most of it greyed: Final-Recipient: bo.unce@coral-cove.invalid Action: failed Status: 5.1.1 Diagnostic-Code: 550 5.1.1 The email account that you tried to reach does not exist On "Diagnostic Code", every line but that one fades, and the zoom lands on it. Gloss card: SMTP reply code · the number a receiving server answers with, which says whether a failure is permanent or temporary.
four lines, one kept. Reveals: (1) the whole message, (2) the rest fades, (3) the zoom on the Diagnostic Code line.
no picture yet in the concept registry (smtp-reply-code is gloss tier, visual null). Proposed: the slip itself, reused from scene 02. Demo address from the library only.
comments 4 and 5 (what code, where).
06 · How do you read it?
How to read the code
the Diagnostic Code line from scene 05 stays still. The 5 lights coral and a chip drops under it: 5 = not ever. A ghost 4 beside it, amber: 4 = not right now. Then the middle 1 of 5.1.1 lights, and a small key builds: 1 address · 2 mailbox · 7 security or policy. Last, the words does not exist underline.
one line, three parts lit in order. Reveals: (1) first digit, (2) middle number and its key, (3) the words.
smtp-reply-code, no picture yet. The same slip, one part lighting at a time.
comment 5 (how to read it).
07 · The ones people miss: it can be you
Soft bounces you would not expect
chip 3 from the hook lights. Sally's envelope to a subscriber waits at the door. Behind it, a crowd of Sally's envelopes pushes at the gate, and the gate narrows to a slot. Two mono chips: sent too fast · too many connections. No gloss card here (Q6 word budget): "big providers like Gmail" is said in plain words.
the crowd is the volume, the slot is the limit. Reveals: (1) chip 3, (2) the crowd and the slot, (3) the two chips.
concept mailbox-provider (the door with the gate, M-14, M-18). The narrowing slot: no picture yet (registry throttling has the word, not yet the picture).
comment 9 (soft bounce examples people would not think to check).
08 · The ones people miss: a no on purpose
Soft bounces you would not expect
one more chip joins scene 07's: a no on purpose. Sally's envelope is turned away once, goes back to the same door and is taken on the second try (keep green dot). No gloss card: the idea is said in plain words and the word "greylisting" is not taught here (Q6). One idea in this scene: the first no can be a test.
one envelope, two tries. Reveals: (1) the chip, (2) the first no, (3) the second try taken.
concept soft-bounce (M-15, M-14, M-31), the second try plays. Greylisting has no picture yet (greylisting is gloss tier, visual null).
comment 9, and the second half of comment 7 (the soft bounce you shrug off). The "same kind across a whole send" line moved out: scene 13 carries it (types, not the rate). The "spam filter not sure" example was cut so the scene holds one idea (Q sweep).
09 · The twist: a five that is about you
The twist
the slip returns, now on one of Sally's sends: 550 5.7.1 and a line of words with listed underlined. The 5 lights coral, then the coral slides off the subscriber's address and onto Sally's side of the gate. One gloss card (Q6): block bounce · a bounce where the server refused the message because of the sender, not because the address is bad. On "open again", the door opens.
the same five, moved from the address to the sender. Reveals: (1) the slip, (2) the coral moves, (3) the door opens.
concept blocklist (a book held open at the gate). block-bounce is gloss tier, no picture yet.
no blocklist is named, it is "a blocklist". The block is never a reason to suppress the address (hard content rules). Nothing implies a list clean lifts it.
comment 7 (some hard bounces are not forever, that's why you read the message).
10 · What is a server like that looking for?
Almanac ids in this scene: 015.005.003
What a server checks
the gate from scene 09, with three small lamps above it, lighting one per question (Q7, three at most): blocklist · spam complaints · how you send (with speed and SPF · DKIM · DMARC small under it). Gloss card on "blocklist": blocklist · a published list of sending IPs or domains flagged for spam, which receiving servers check before accepting mail. On the last line all three lamps point back at the sender. On "free blocklist checker", a small card: reviewmyemails.com/tools/blacklist-checker.
three lamps, three checks. Reveals: one per question, then all three together.
concept blocklist (the book at the gate) for the first lamp. The lamp row: no picture yet.
says what the server checks, never that a list clean fixes any of it. SPF, DKIM and DMARC are on screen only, not glossed, and each has its own video. The Almanac's fifth check (content filter matches, 015.005.003) is left out of the VO so the scene stays at three, nothing is changed.
comment 8.
11 · What do you do with each?
What to do with each
one gloss card (Q6). suppress · keep the address on record so you never send to it again. The retry is said in plain words, no card. Three rows build: HARD → once → suppress pot. SOFT → retry → back to the door. SOFT again and again → your tool decides → watch list.
three rows, one move each. No window and no count drawn on them (R2, R6). Reveals: one row at a time.
concept suppression-list (the third verdict pot with its lid closing, M-23, M-24) for the hard row. Concept soft-bounce (M-15, M-14, M-31) for the retry row. The streak: no picture yet.
R2 and R6 (YT, 2026-09-29): no retry window and no fixed count, it depends on the tool.
says "email marketing tool", never "ESP".
12 · Why it matters
Why it matters
a balance. Left pan, "suppress every bounce": Sally's envelope to a subscriber, still carrying scene 07's sent too fast chip, drops into the suppress pot by mistake. Right pan, "ignore every bounce": bo.unce@coral-cove.invalid keeps getting sent to. Then the score gauge: the needle drifts down, and the whole domain bar dims, not one envelope. The gauge is labelled your reputation as a sender, no gloss card (Q6 word budget, the Playlist 1 reputation videos teach the term).
two pans, one gauge. Reveals: (1) left pan, (2) right pan, (3) the gauge.
concept sender-reputation (the score gauge, M-33). The balance: no picture yet.
states a cost, not a promise. No bounce rate number. No inbox placement guarantee.
comment 9 (a fresher example than "a full inbox that week").
13 · The lesson: the types, not just the rate
Read the types, not the rate
one bar with a percentage on it, no number given (??%). It splits into three coloured bands: mailbox full · rate limit · blocks. Each band pulls out its own fix card: stale list? · reputation? · how you send. The bar's total never changes.
the bar is the rate, the bands are the types. Same total, three different mixes. Reveals: (1) the bar, (2) the split, (3) the three fix cards.
bounce-rate is gloss tier, no picture yet. Proposed: this bar. The term itself is not glossed here (Q6), V014 "What is bounce rate?" owns it. Scene 08's old "the same kind, across a whole send" idea lives here now.
no bounce rate number is shown or spoken, the bar reads ??% so nothing looks like a target (N6).
comment 10.
14 · The worst ones never come back
Almanac ids in this scene: 021.002.013
The ones that never bounce
a gate that lets every envelope through without looking. No envelope comes back, so there is no stamp and no note, and the note's line stays blank ___. Gloss card: catch-all domain · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos.
a pile behind the gate with no count on it, and an empty slip. Reveals: (1) the open gate, (2) the blank slip.
concept catch-all (a gate that lets every envelope through without looking). The catch-all video (021.002.013) owns the full explanation, this is a one-scene look (S6).
R15 (YT, 2026-09-29): the pivot before the pitch, backed by 021.002.013. "Usually" keeps inside C17 (the Almanac is split on whether a catch-all ever bounces).
comment 11.
15 · Recap
The four things
scene 03 and 04's two cards replayed small, the three chips from the hook all lit, the Diagnostic Code line from scene 05, and scene 13's split bar.
callbacks only, four things, so four lines (hard and soft share one, the two kinds). Reveals: one per sentence.
callbacks only (recipe R10), no new picture.
the VO said four things but listed five. Hard and soft are now one sentence, so the count is true and nothing is cut. Chapter renamed to match.
16 · Close
Almanac ids in this scene: 015.001.001, 021.002.013
Clean your list
scene 14's open gate. The dot grid pours through a checker instead, and the catch-all dots light amber with a catch-all tag (one word for one thing, Q11 and P5, so no accept-all card). The rest pour into the verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it.
the grid pours into pots, no share shown. Reveals: (1) the amber catch-all dots, (2) the pots, (3) the CTA.
concept list-cleaning (the dot grid pouring into the three verdict pots, M-25, M-23, M-24).
R15 (YT, 2026-09-29): "that is what we clean for you", only where the Almanac backs it (021.002.013, 015.001.001).
the clean is only about addresses. It says out loud that it won't lift a block, and nothing implies it fixes SPF, DKIM, DMARC, MX or a blocklist (S10). "Review My Emails" is spelled out.
17 · End card
Almanac ids in this scene: 005.006.007, 015.001.001
Clean your list
the end card. The logo, trust beats tactics, reviewmyemails.com/get-started, and this video's one extra: reviewmyemails.com/sos with decode a bounce message. The next video in playlist 1 on the end screen, no subscribe ask.
one card, four lines. Reveals: the card, then the next video.
R14 (YT, 2026-09-29): the end card rotates. Always the logo, trust beats tactics and /get-started, plus one extra that fits. For a video about reading bounce messages that is /sos.
015.001.001 "drop them in our SOS hotline and we'll help you decode them".
V002, 005.006.007, its Almanac question word for word, "What's the difference between hard, soft, and transient bounces?" (order from VIDEO-INDEX.md). The old small GAP is closed.
comment 12. Totals: 18 scenes (00 to 17), 1,015 spoken words (counted 2026-09-30, after the Q sweep and the s15 count fix). About 6:07 at 166 words a minute, about 6:20 with scene breaks. Every scene is 20 to 70 words (S2). 8 glossed words (Q6): bounce, hard bounce, soft bounce, SMTP reply code, block bounce, blocklist, suppress, catch-all domain. Short cut (Q10, over 5 minutes): scenes 00, 02, 03, 04 and 11, then the CTA line of 16. About 1:45. The answer and the first action land by 1:00 in both cuts.
V002What's the difference between hard, soft, and transient bounces?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Scene 10's picture: the halves circle of dots.
- C9 knock-on Settled by R6: scene 07 says it depends on the tool, no count.
- "No picture yet" visuals: the slip stack (SMTP code), the streak row, the source bars (bounce rate), the sorting desk.
00 · Three kinds of bounce? (hook) · 0:00
On screen: the title, Lora, large: "Hard, soft or transient?" Three thin-line cards in a row, labelled hard, soft, transient. On "here's the catch", the transient card slides onto the soft card and sits behind it. Three numbered chips line up: 1 read the code · 2 what to do · 3 when the code fools you. Chip 3 stays greyed until scene 08.
Hard bounce. Soft bounce. Transient bounce. Sally Send sees all three words in her dashboards, so that's three kinds of bounce, right? Here's the catch. There are only TWO, and one of them has a second name. Let's sort them out in three steps. How to read each one from its code. What to do with each. And when the code alone can fool you.
01 · Brought to you by, woven in · 0:25
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Sorting bounces gets easier when fewer come back, so Review My Emails clears the dead addresses off your list first.
02 · One digit decides · 0:33
On screen: two slips side by side. Left slip 5__, the 5 in coral. Right slip 4__, the 4 in amber. Gloss cards as the words are said: hard bounce · permanent, it will fail the same way every time. soft bounce · temporary, it might work next time.
Start with the code. Sally's newsletter just came back from two readers. Every bounce comes back with a reply code from the receiving server, like the note clipped to a letter stamped return to sender. The first digit tells you which kind you're holding. A five means permanent. That's a hard bounce. A four means temporary. That's a soft bounce. Five, suppress. Four, wait.
03 · The hard codes · 0:58
On screen: the first slip grows a second code 5.1.1 and the camera zooms on its first digit to prove it matches. Gloss card: enhanced status code · a longer code, like 5.1.1, whose first digit matches and whose rest gives the reason.
Sometimes you'll see a longer code beside it, like five point one point one. That's an enhanced status code. Same first digit, with a more specific reason after it.
04 · The soft codes · 1:33
On screen: two amber slips, mono: 421 service not available · 450 mailbox busy. The address marina@tidewell-supply.example sits on the second. Gloss card: MTA · mail transfer agent, the server doing the sending. On "tries again", a small loop arrow circles the stack. On "the next video", a greyed chip: next: how many retries?
The second one went to Marina, a loyal reader, and her address is fine. Soft bounces come back with a four hundred code. Something is wrong right now, but it might clear. Four twenty one, service not available. Four fifty, mailbox busy. That's Marina's. You don't need to step in. Your MTA, the server doing the sending, holds the letter and tries again on its own.
05 · Where transient fits · 1:58
On screen: chip 1 lights. The word transient lifts off its old card and lands as a second name tag on the soft card. The two cards hold, and every slip on screen drops into one of the two. (The permerror aside is cut in the Q sweep, Q6 word budget. It belongs to the SPF videos.)
Where does transient fit, then? It doesn't get its own box. Transient is just another word for soft bounce. You'll see it in some dashboards and in older documentation. It's there to remind you the problem is temporary, and the server should try again. There is no third kind. Two boxes, and every bounce goes in one of them.
06 · Rule one, hard is once · 2:21
On screen: chip 2 lights. A row of three send slots for bo.unce@pearl-diver.invalid. Slot 1 takes a coral stamp. On "not after three", slots 2 and 3 are struck through and fade. The envelope drops into the suppress pot and the lid closes. Gloss card: suppress · keep the address on record so you never send to it again.
Now, what to do with each. This is where most senders get it wrong. Rule one. Suppress every hard bounce the first time it happens. Not after three. Not after one more try, just in case. ONCE. And don't send to it again next month, hoping the mailbox came back. Hard bounces are the ones that damage your sender reputation, if you keep piling them up.
07 · Rule two, soft gets a limit · 2:46
On screen: a row of send slots for marina@tidewell-supply.example, no band and no count. Amber dots fill the slots one per send. Beside the suppress pot, a small dial labelled your tool decides. On "isn't coming back", the last dot greys and a cobwebbed door (video 1 scene 05) fades in behind it.
Rule two. Give soft bounces a limit. How many in a row before you suppress? It depends on the tool. There's no fixed count. Some email marketing tools do this for you. Many don't. Check yours, in its bounce or suppression settings. Because a soft bounce that keeps coming back usually isn't temporary anymore. A server that keeps timing out probably isn't coming back.
08 · Rule three, read the words · 3:10
On screen: the suppress pot, lid open. A small handful of addresses lifts out for a look, each with its reply slip. Then a day column fills with coral dots, every one tagged with the same server name, and a magnifier lands on the tag: same server, same day.
What do you do about that? Every so often, pull a sample of your suppressed addresses and spot check them. Do they look like real dead addresses? And if forty get suppressed in one day, all from the same mail server, that's not a wave of dead mailboxes. That's a misreading. Check the raw reply before you accept it.
09 · Rules four and five, the whole list · 4:15
On screen: gloss card: bounce rate · the share of your emails that come back undelivered. Four bars rise side by side, one per source, labelled A, B, C, D. Three stop at the same short height. The fourth keeps climbing to ten times that height, in coral.
Rule four. Watch your bounce rate as a whole, not one address at a time. One bounce is a single returned letter. The rate is the whole returns pile. And rule five. Track where your addresses came from. If one source brings you ten times the bounce rate of the others, that source is feeding you garbage.
10 · Half the job · 4:36
On screen: one envelope goes in through a door marked accepts everything, and the door closes. Hold. Nothing comes back out. No slip, no notice. Then the checking desk lamp finds the same address and tags it amber, catch-all.
Some addresses never land in either box. A server that takes every address, real or made up, usually won't bounce a name that doesn't exist. The mail just disappears. No code, no rule to apply. Those show up when you check the list before you send.
11 · Recap · 5:05
On screen: the two cards from scene 00, the three chips all lit, the 5 and 4 slips under them.
Your checklist, then. There are two kinds of bounce, not three. Five hundred codes are hard, suppress them once. Four hundred codes are soft, let them retry, and suppress the ones that keep coming back. Read the Diagnostic Code line, as well as the number. And spot check your suppressed pile, because your tool can read it wrong.
12 · Close · 5:26
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 3, no subscribe ask.
If your bounce rate feels high, your list may need a clean. Review My Emails flags what's safe to send to, and what to suppress, and you can run the same check at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how many times should my system retry sending after a soft bounce?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.006.007-hard-soft-transient-bounces.md
00 · Three kinds of bounce? (hook)
Three kinds of bounce?
the title, Lora, large: "Hard, soft or transient?" Three thin-line cards in a row, labelled hard, soft, transient. On "here's the catch", the transient card slides onto the soft card and sits behind it. Three numbered chips line up: 1 read the code · 2 what to do · 3 when the code fools you. Chip 3 stays greyed until scene 08.
a count of cards. 3 cards, then 2. Reveals: (1) three cards, (2) transient slides onto soft, the count reads 2, (3) the three chips.
concept hard-bounce and soft-bounce card faces (M-15, M-14). The slide is new motion on existing pieces.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
one sentence, 20 words, brand said here and in the close only.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · One digit decides
One digit decides
two slips side by side. Left slip 5__, the 5 in coral. Right slip 4__, the 4 in amber. Gloss cards as the words are said: hard bounce · permanent, it will fail the same way every time. soft bounce · temporary, it might work next time.
one digit, drawn large, the only filled glyph on each slip. Reveals: (1) the 5 slip, (2) the 4 slip, (3) the 5 slip drops toward the suppress pot and the 4 slip curls back toward the door, the two moves the digit decides.
the answer (two kinds) is in the hook, and the first action (five, suppress, four, wait) now lands here, by about 1:00.
callback to video 1 scene 04 (the slip's first digit lights and pulls its card). Concept smtp-reply-code has no picture yet.
03 · The hard codes
The hard codes
the first slip grows a second code 5.1.1 and the camera zooms on its first digit to prove it matches. Gloss card: enhanced status code · a longer code, like 5.1.1, whose first digit matches and whose rest gives the reason.
the same slip, one digit lit twice. Reveals: (1) the 5.1.1 appears, (2) the zoom.
the scene 03 slip. Enhanced status code: no registry row. Split from scene 03 so each scene stays under 70 words (S2).
04 · The soft codes
The soft codes
two amber slips, mono: 421 service not available · 450 mailbox busy. The address marina@tidewell-supply.example sits on the second. Gloss card: MTA · mail transfer agent, the server doing the sending. On "tries again", a small loop arrow circles the stack. On "the next video", a greyed chip: next: how many retries?
a count of slips, 2 soft codes, each with its 4 lit. Reveals: (1) 421, (2) 450, (3) the retry loop, (4) the next video chip.
concept soft-bounce (M-15, M-14, M-31) for the loop. mta is gloss tier, no picture yet.
451 is left out (gloss check C2). "Message too large" is left out (C3). No retry window is spoken (C6 belongs to the next video).
05 · Where transient fits
Transient is soft
chip 1 lights. The word transient lifts off its old card and lands as a second name tag on the soft card. The two cards hold, and every slip on screen drops into one of the two. (The permerror aside is cut in the Q sweep, Q6 word budget. It belongs to the SPF videos.)
the count of kinds stays 2 while a third word joins one of them. Reveals: (1) the name tag moves, (2) the slips drop into the two boxes.
the two cards from scene 00.
06 · Rule one, hard is once
Hard bounces: once
chip 2 lights. A row of three send slots for bo.unce@pearl-diver.invalid. Slot 1 takes a coral stamp. On "not after three", slots 2 and 3 are struck through and fade. The envelope drops into the suppress pot and the lid closes. Gloss card: suppress · keep the address on record so you never send to it again.
a count of sends. One filled slot, the rest struck out. The number is 1. Reveals: (1) slot 1 stamped, (2) slots 2 and 3 struck, (3) into the pot.
concept suppression-list (the third verdict pot with its lid closing, M-23, M-24).
07 · Rule two, soft gets a limit
Soft bounces: a limit
a row of send slots for marina@tidewell-supply.example, no band and no count. Amber dots fill the slots one per send. Beside the suppress pot, a small dial labelled your tool decides. On "isn't coming back", the last dot greys and a cobwebbed door (video 1 scene 05) fades in behind it.
a count of amber dots that keeps growing, with no mark where suppression starts. The missing mark is the point (R6). Reveals: (1) the slots, (2) to (4) one amber dot per send, (5) the dial, (6) the cobwebbed door.
R6 (YT, 2026-09-29): when a repeatedly soft-bouncing address is suppressed depends on the tool, no fixed count. "Three to five in a row" is reworded. R2 applies too, no retry count.
concept soft-bounce (M-15, M-14, M-31). The streak row: no picture yet (same gap as video 1 scene 06). The cobwebbed door is video 1's pose, reused.
08 · Rule three, read the words
Almanac ids in this scene: 015.004.014, 015.016.007
When the code fools you
the suppress pot, lid open. A small handful of addresses lifts out for a look, each with its reply slip. Then a day column fills with coral dots, every one tagged with the same server name, and a magnifier lands on the tag: same server, same day.
a sample lifted from the pot, then a day's column all from one source. Reveals: (1) the sample, (2) the day column fills, (3) the magnifier on the tag.
concept suppression-list (M-23, M-24). The day column: no picture yet.
never implies a list clean fixes the blocked case.
015.016.007 "Pull a sample of your suppressed addresses periodically and spot-check the classification." / 015.004.014 "spot patterns, like 40 suppressions in one day all from the same mail server, that signal a misclassification event rather than a real deliverability problem" / "Keep an audit trail of every suppression with the raw bounce reason attached".
T5, the action that goes with the twist. "Forty" is the Almanac's own example, not a threshold (N6).
09 · Rules four and five, the whole list
Almanac ids in this scene: 005.006.007
Watch the whole list
gloss card: bounce rate · the share of your emails that come back undelivered. Four bars rise side by side, one per source, labelled A, B, C, D. Three stop at the same short height. The fourth keeps climbing to ten times that height, in coral.
bar height. Three bars at 1 unit, one at 10. The comparison is the drawing. Reveals: (1) the three short bars, (2) the tall bar climbs.
bounce-rate is gloss tier, no picture yet. Proposed: these bars.
no bounce rate number is spoken or shown. The Almanac gives several (C4). The 10x is a ratio between sources, quoted from 005.006.007, not a rate.
10 · Half the job
Almanac ids in this scene: 005.003.010, 005.008.002, 005.013.008
The one you never see
one envelope goes in through a door marked accepts everything, and the door closes. Hold. Nothing comes back out. No slip, no notice. Then the checking desk lamp finds the same address and tags it amber, catch-all.
the count of returned slips is zero. The empty space where a slip should land is the picture. Reveals: (1) the envelope goes in, (2) nothing returns, (3) the lamp tags it.
concept catch-all (the registry's door that accepts everything) and the checking desk.
R15 (YT, 2026-09-29): pivot before the pitch, backed by the catch-all and accept-all answers only. "Some servers" and "quietly drop" keep to the Almanac's own "usually do not bounce" (C17 and C18 are not voiced: no count, and no claim that catch-alls never bounce). "Usually won't bounce" keeps inside C17.
005.003.010 "Catch-all servers usually do not bounce. They accept and then silently drop." / 005.008.002 "Every address on the domain accepts mail at the SMTP layer, then the message is dropped" / 005.013.008 "a real validator will identify these domains and flag them accordingly."
moved before the recap (Q3) as 10b and reworded so it shares no line with the other videos' pivots (Q1).
11 · Recap
Two kinds, five rules
the two cards from scene 00, the three chips all lit, the 5 and 4 slips under them.
the count of cards, 2, held.
callbacks only, no new picture.
12 · Close
Clean your list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is only about addresses. Nothing implies it fixes SPF, DKIM, DMARC, a blocklist or the blocked IP from scene 08. Totals: 17 scenes. 924 spoken words (recounted 2026-10-04, RME-33.66 cut-out pass). About 5:34 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2). Short cut (Q10, over 5 minutes, added in the RME-182.1 review pass): scenes 00, 02, 05, 06 and 07, then the CTA line of 12. About 2:00. The answer and the first action land by 1:00 in both cuts.
V003How many times should my system retry sending after a soft bounce?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- The headline number Settled by R2: scene 05 says it depends on the tool, no number.
- C12, urgent mail Settled by R5. Old 07b said both, the Q sweep cut it, so it is not voiced now.
- "No picture yet" visuals: the queue box, the doubling timeline, the deferral bars, the streak row.
- Urgent mail (old 07b) and the header walk-through (old 04d): were cut for length in the Q sweep.
00 · How many times do you knock? (hook) · 0:00
On screen: the title, Lora, large: "How many times do you knock?" Sally's envelope at a door. Knock marks appear one at a time beside the door, each one a small tick, and the row ends in a ?. On the promise, three numbered chips line up under the door: 1 how many · 2 the spacing · 3 what to ask. Chips 2 and 3 grey until their scenes (04 and 08).
Sally Send's email to Marina soft bounced. Marina's server pushed back with a temporary error, like a knock on a door that nobody answered yet. How many times should Sally knock before she walks away? The honest answer is that it depends on the tool. Let's take it in three. How many, and who decides. Why the SPACING matters. And what to ask your own tool.
01 · Brought to you by, woven in · 0:24
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some of those addresses should be off your list already, and Review My Emails flags them for you before you send.
02 · Where the message waits · 0:31
On screen: an amber 4__ slip. Marina's envelope slides into a queue box beside the sending desk. Gloss card: deferred message · an email that got a temporary no, waiting in a queue to be tried again. A loop arrow runs from the queue back to the door.
A soft bounce comes with a four hundred code. The server is saying, not right now, try again later. It doesn't mean the address is bad. Something got in the way, a busy server or a temporary block. So the message becomes a deferred message. It waits in a queue, like a parcel on the shelf at the depot, and your sending server knocks again on its own.
03 · How many, and who decides · 0:54
On screen: chip 1 lights. Two slips drop. The coral 5__ slip, on bo.unce@pearl-diver.invalid, goes straight into the suppress pot, and the lid closes. The amber 4__ slip goes to three sending desks side by side, each with its own knock row at the same door. Desk one's row stops after a short streak of amber. Desk two runs two rows, one tight, one wide. Desk three's ticks follow the door's replies, a small 4__ slip over each tick. No row carries a count.
How many tries, then? Only the fours get any. A five hundred code is a permanent no, so you suppress the address and move on. For the fours, it depends on the tool. Some stop after several soft bounces in a row. Some treat each kind differently. And some go by what the receiving server says back. Your tool's support can tell you which.
04 · The spacing · 1:17
On screen: chip 2 lights. A timeline runs left to right. Each retry is a tick. The gap after each tick is twice the gap before it, so the ticks spread out as they go. Gloss card: exponential backoff · waiting a bit longer before each new try. On "pound on a door", the other version plays above it: ticks packed tight and even, in coral, and the server door starts to shut.
Now, the spacing. Think of knocking on a friend's door. A good setup knocks again soon, to catch a short outage. Then it waits longer, and longer. That's exponential backoff. Why does it matter? Pound on a door that's already swamped and you look aggressive. Some servers start treating you as a threat.
05 · The first no can be a test · 1:37
On screen: the door from scene 00. Sally's envelope gets a small amber 451 try again later. Beside it, a crowd of grey envelopes from a spam machine gets the same slip, and all of them walk off screen. Only Sally's envelope comes back, knocks, and the door opens for it. Gloss card: greylisting · a server turning away an unknown sender the first time, and letting it in when it tries again. On "never arrives", a second version plays small: her envelope turns away after one knock, and the door stays shut.
Sometimes that first no is on PURPOSE. Some servers turn away any sender they don't know yet, the first time, and wait to see who comes back. That's called greylisting. Real mail servers knock again within minutes. Spam machines move on. So the retry isn't a chore. It's the password. Give up too quickly, and that mail never arrives at all.
06 · The kind of soft bounce changes the plan · 2:00
On screen: two timelines stacked, the same length. Top, doesn't know you yet: one quick second tick. Bottom, rate limited: ticks far apart, and the gate in front of the door narrows. Gloss card: throttling · a server slowing down how fast it accepts your mail.
The kind of soft bounce changes the plan too. A server that doesn't know you yet wants you back within minutes, so a quick second knock makes sense. But a temporarily deferred error might mean you're being rate limited. The server is throttling you, slowing down how fast it takes your mail. Then the smarter play is to space your knocks further apart.
07 · Where the deferrals pile up · 2:24
On screen: four bars, one per receiving domain, labelled A, B, C, D. First pose: one bar tall, three short. Second pose: all four tall. Gloss card: mailbox provider · the service your reader receives mail with, like Gmail. Last, the queue box from scene 02 as the depot shelf: parcels stack on faster than they leave.
Where do you see which one you've got? Open your tool's bounce report and group the soft bounces by the domain they went to. Lots at one mailbox provider usually means it's rate limiting you. Spread across every domain? That points to something on your side. A few in any send is normal. A queue that keeps growing is not.
08 · Three questions for your tool · 2:46
On screen: chip 3 lights. The sending desk. Three question cards stack beside it, one per question, and each gets a teal tick as it is said.
Who does all this knocking? Almost every email marketing tool retries soft bounces for you. Run your own mail server, and the retries are yours to set up. The details vary, so ask support three things. How many retries before an address is suppressed? What's the total retry window? And can you see soft bounces in your reports? Only ever see hard bounces? Your tool is likely absorbing the retries.
09 · The address that never stops soft bouncing · 3:08
On screen: a row of send columns, one per send. Marina's address is amber in every column. The amber row lengthens by one column per send, then an arrow points to the suppress pot, labelled look at suppressing. The lid does not close on its own. On the last line, the checking desk lamp finds the same address before the first send and tags it.
And the address that soft bounces send after send? That's your cue to look at suppressing it. Repeated soft bounces on one address are often a sign the problem isn't temporary at all. Many of those should have come off your list before you ever sent.
10 · Recap · 3:26
On screen: the scene 04 timeline, small, the three chips all lit, the scene 07 bars, the three question cards.
Here's your week. Retry the fours, never the fives. Check that your tool knocks again fast, then widens the gaps. Group your soft bounces by domain, and change the plan for the kind you see. And ask your tool the three questions.
11 · Close · 3:42
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: V004, no subscribe ask.
If your list keeps handing you the same soft bounces, it may need a clean. At Review My Emails we flag the addresses you should already have suppressed, before you send. Stuck on one right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what's the difference between rejected and bounced?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.007.001-how-many-soft-bounce-retries.md
00 · How many times do you knock? (hook)
How many retries?
the title, Lora, large: "How many times do you knock?" Sally's envelope at a door. Knock marks appear one at a time beside the door, each one a small tick, and the row ends in a ?. On the promise, three numbered chips line up under the door: 1 how many · 2 the spacing · 3 what to ask. Chips 2 and 3 grey until their scenes (04 and 08).
a count of knocks with no total. The ? where the total would be is the point. Reveals: (1) the envelope at the door, (2) the knocks and the ?, (3) the three chips.
concept soft-bounce (the returned envelope going back to the same door, M-15, M-14, M-31).
the old 00b promise is folded in here, and the chips are paid in the order they are said (1 in scene 03, 2 in 04, 3 in 08).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.007.003
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner. Q4: one sentence, 22 words.
015.007.003 "[RME Clean] can flag the addresses you should already have suppressed."
02 · Where the message waits
The message waits
an amber 4__ slip. Marina's envelope slides into a queue box beside the sending desk. Gloss card: deferred message · an email that got a temporary no, waiting in a queue to be tried again. A loop arrow runs from the queue back to the door.
the queue's fill. One envelope in the box. Reveals: (1) the 4 slip, (2) the envelope into the queue, (3) the loop arrow.
concept esp (the sending desk, M-02, M-12). deferred-message is gloss tier, no picture yet. Proposed: this queue box.
03 · How many, and who decides
Almanac ids in this scene: 015.007.001, 015.007.002, 015.007.004
It depends on the tool
chip 1 lights. Two slips drop. The coral 5__ slip, on bo.unce@pearl-diver.invalid, goes straight into the suppress pot, and the lid closes. The amber 4__ slip goes to three sending desks side by side, each with its own knock row at the same door. Desk one's row stops after a short streak of amber. Desk two runs two rows, one tight, one wide. Desk three's ticks follow the door's replies, a small 4__ slip over each tick. No row carries a count.
the 5 gets zero knocks. Three knock rows of different lengths and spacings, none labelled. The difference between the rows is the point. Reveals: (1) the 5 into the pot, (2) desk one, (3) desk two, (4) desk three.
concept suppression-list (M-23, M-24) and concept esp (M-02, M-12), three times.
R2 (YT, 2026-09-29): no single number, it depends on the tool. No count or window is said or shown (C5, C6, C7, C8 stay in the ledger, none voiced).
the answer (it depends on the tool) is in the hook at about 0:15, and the first action (ask your tool's support) lands here, by about 1:15.
015.007.002 "retry logic only applies to temporary failures (4xx codes). A 5xx response is a permanent rejection... You don't retry those. You suppress the address and move on." / 015.007.004 "the exact retry count, total window, and conversion threshold vary quite a bit from one platform to the next" / 015.007.001 "A 'temporarily deferred' error... spacing your retries further apart is the smarter play" / 015.007.004 "Good questions to ask".
04 · The spacing
The spacing
chip 2 lights. A timeline runs left to right. Each retry is a tick. The gap after each tick is twice the gap before it, so the ticks spread out as they go. Gloss card: exponential backoff · waiting a bit longer before each new try. On "pound on a door", the other version plays above it: ticks packed tight and even, in coral, and the server door starts to shut.
gap width. Each gap is drawn exactly twice the last (1, 2, 4, 8 units), so the doubling is the drawing. No minute labels (C8). No end tick (C6). The tight coral row against the widening row is the comparison. Reveals: (1) the first quick tick, (2) the widening gaps, (3) the hammering row, (4) the door starts to shut.
no registry row for exponential backoff. Proposed: this timeline. The old 04b is folded in.
05 · The first no can be a test
Almanac ids in this scene: 001.001.034
The first no is a test
the door from scene 00. Sally's envelope gets a small amber 451 try again later. Beside it, a crowd of grey envelopes from a spam machine gets the same slip, and all of them walk off screen. Only Sally's envelope comes back, knocks, and the door opens for it. Gloss card: greylisting · a server turning away an unknown sender the first time, and letting it in when it tries again. On "never arrives", a second version plays small: her envelope turns away after one knock, and the door stays shut.
one door, two kinds of sender. The ones that leave against the one that returns is the whole point. Reveals: (1) the slip on both, (2) the crowd leaves, (3) Sally's second knock opens the door, (4) the give-up version.
concept soft-bounce (M-15, M-14, M-31), the second knock. Greylisting is glossed here now (Q5): V001 no longer names it, so there is no "from the first video" callback.
001.001.034 "a receiving mail server temporarily rejects an unfamiliar sender with an SMTP 4xx response... on the first delivery attempt, expecting legitimate senders to retry within minutes while spam botnets move on" / "The only time greylisting causes real problems is if your sending server gives up too quickly."
T3, the one surprise in this video, said by its content (Q1). "It's the password" is framing, not a fact.
06 · The kind of soft bounce changes the plan
New to them, or rate limited
two timelines stacked, the same length. Top, doesn't know you yet: one quick second tick. Bottom, rate limited: ticks far apart, and the gate in front of the door narrows. Gloss card: throttling · a server slowing down how fast it accepts your mail.
tick spacing on two equal lines. Close ticks against wide ticks is the whole comparison, no minute labels. Reveals: (1) the doesn't-know-you line, (2) the rate limited line, (3) the gate narrows.
concept throttling (the gate narrowing, M-18, M-15).
07 · Where the deferrals pile up
Where the deferrals pile up
four bars, one per receiving domain, labelled A, B, C, D. First pose: one bar tall, three short. Second pose: all four tall. Gloss card: mailbox provider · the service your reader receives mail with, like Gmail. Last, the queue box from scene 02 as the depot shelf: parcels stack on faster than they leave.
bar height is the count of deferrals per domain. One tall bar against four tall bars is the difference between the two stories. Then the queue's fill level, rising. Reveals: (1) one tall bar, (2) all four tall, (3) the queue rising.
concept mailbox-provider (M-14, M-18). The bars and the rising queue: no picture yet. The old 08b is folded in.
the bounce report in the viewer's own email marketing tool, grouped by receiving domain.
08 · Three questions for your tool
Almanac ids in this scene: 015.007.001
Three questions for your tool
chip 3 lights. The sending desk. Three question cards stack beside it, one per question, and each gets a teal tick as it is said.
a count of questions, 3. Reveals: (1) question 1, (2) question 2, (3) question 3.
concept esp (the sending desk, M-02, M-12).
says "email marketing tool", never "ESP". Names no vendor (C10 is about a named vendor).
the question says "my system", and 015.007.001 says "If you're building your own sending infrastructure or using a lower-level API, you'll need to configure this yourself." That key point was missing, it is one sentence now. On screen, a small second desk with no logo, tagged your own server: you set this.
09 · The address that never stops soft bouncing
Almanac ids in this scene: 015.007.001, 015.007.003
When retrying stops helping
a row of send columns, one per send. Marina's address is amber in every column. The amber row lengthens by one column per send, then an arrow points to the suppress pot, labelled look at suppressing. The lid does not close on its own. On the last line, the checking desk lamp finds the same address before the first send and tags it.
the length of the amber row is the count of sends that bounced. No threshold mark on it (C9). Reveals: (1) to (3) one amber column per send, (4) the arrow to the pot, (5) the lamp.
concept suppression-list (M-23, M-24) and the checking desk.
the list-side problem this topic owns, retries spent on addresses that should have been suppressed already, in place of the old catch-all pivot (catch-alls are not soft bounces). It sits before the recap (Q3).
no count, and no "your tool turns it into a hard bounce" (C9).
015.007.001 "If an address keeps soft-bouncing across multiple send attempts over time, that's your cue to look at when to suppress it entirely. Repeated soft bounces on the same address are often a signal the problem isn't temporary at all." / 015.007.003 "[RME Clean] can flag the addresses you should already have suppressed."
10 · Recap
The four moves
the scene 04 timeline, small, the three chips all lit, the scene 07 bars, the three question cards.
the doubling gaps, held.
callbacks only. The last lesson scene, ending on the action (Q3).
11 · Close
Clean your list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: V004, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is only about addresses. Nothing implies it fixes throttling or a reputation problem from scene 07. Totals: 12 scenes (00 to 11). 679 spoken words (recounted 2026-10-04, RME-33.66 cut-out pass). About 4:02 at 166 words a minute, about 4:15 with scene breaks. Every scene is 20 to 70 words (S2). 6 glossed words.
V004What's the difference between "rejected" and "bounced"?
waiting on YTOpen questions for YT
- Call 7 wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Flag 1 (C11) Settled by R3: broad meaning everywhere, the strict sense only here, where the video is about the difference.
- Flag 2: blackholing Settled 2026-10-04 (RME-33.67): the behaviour is voiced (option B), the word is not.
- No picture yet Drawn 2026-10-04 in the cut-out look (RME-33.67): the conversation board, the notice, the log book, the unit grids and the rest. See "Cut-out redo" below.
00 · Rejected or bounced? · 0:00
On screen: the three chips line up under the two envelopes: 1 where each one happens · 2 why the timing matters · 3 how to tell which you got.
Which one did Sally get, and does it matter? It's worth three questions. Where does each one happen? Why does the timing matter? And how do you tell which one you got?
01 · Brought to you by, woven in · 0:34
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Refused at the door or handed back later, it starts with an address, which is why Review My Emails checks every one before you send.
02 · The conversation · 0:44
On screen: each block gets a small green 2xx tick. The key builds under the four blocks: 2xx yes green, 4xx not right now amber, 5xx no coral. On "250 OK", the last block turns solid green and the envelope crosses the line into the receiver's side. The 250 OK label sits on the last block, no gloss card (Q6), the VO says what it means in plain words.
And at every step, the receiving server answers with a code. A two means yes. A four means not right now. A five means no. The last yes, after the message itself, is two fifty OK. That's the moment the receiver takes the message off your hands.
03 · Rejected · 1:24
On screen: the door from scene 03 stays shut. Nothing comes out of it. Back at the sending desk, one line writes itself into the desk's own log book, no hand and no clerk (T11): bo.unce@kelp-street.invalid 550 5.1.1 User unknown. The inbox beside the desk stays empty.
When you're refused at the door, the receiving server never sends you a bounce message at all. It never took the parcel, so it has nothing to send back. Your OWN sending system writes the failure down. That's why a rejection shows up in your tool's log, or its bounce report, and never in anyone's inbox.
04 · Bounced · 2:18
On screen: a second envelope, a different shape, comes back out of the door on its own, addressed From: MAILER-DAEMON and To: your Return-Path, with Kai's address quoted inside. One gloss card (Q6): asynchronous bounce · a message the server accepted, then returned later in a separate email. The notice and the failure address are said in plain words, no cards.
The receiver has to tell you, separately. It sends back its own email, a delivery notice, from something like MAILER DAEMON. It goes to the address you gave for failures, not the one your readers see, so it's easy to miss. That's an asynchronous bounce. Accepted now. Returned later.
05 · Why the timing matters · 2:59
On screen: gloss card on "suppression list" (reused from video 1). Then the numbers, one click each: 1. A grid of 100 dots. 8 turn coral. Label: 8 in every 100. 2. A block of 200 small squares, each one 1,000 addresses: 200,000 sent. 3. 16 of the 200 squares fill coral: 16,000 dead addresses. 4. Two lanes under the squares. Top lane, "rejected": all 16 coral squares drop into the suppress pot at once, stamped inside a second. Bottom lane, "bounced": the same 16 trickle in one by one across three marks, minutes · hours · days, and a few never arrive.
Why does the difference matter? Speed. A rejection feeds your suppression list inside a second. An asynchronous bounce can take minutes. Hours. Or days. Say you're sending to two hundred thousand people, and eight in every hundred addresses are dead. That's sixteen thousand. With rejections, you know about each one while the send is still running, and you stop wasting connections on them almost straight away.
06 · The one that can go missing · 3:24
On screen: the smudged notice, marked vague · malformed · another language, beside the rejection's crisp stamp 550 5.1.1 User unknown.
Open question: Blackholing, a third way a notice goes missing (gloss check gap 1, no C number, see the gap file).
And even when it arrives, it can be vague, badly formatted, or written in the receiver's own language. A rejection comes with a code that tells you exactly why.
07 · Why big providers refuse at the door · 3:55
On screen: the door with its gate. A bad address reaches it and is turned back at the gate, not let in. Gloss card: backscatter · bounce notices sent to someone whose address was forged, for mail they never sent. Then the same address sent again and again, each one stamped 550, and the score gauge's needle drifts down. No other card: "big providers" and "your reputation as a sender" are plain words here (Q6).
And this is why most big mailbox providers reject bad addresses during the conversation, instead of accepting them and bouncing later. Refusing at the door keeps them from sending backscatter. Which puts it back on you. If you keep hitting five fifties on the same addresses and ignore them, that pattern burns your reputation as a sender faster than the volume itself.
08 · How to tell which you got · 4:20
On screen: the returned notice from scene 04 sets off back along the road, and fades halfway. Nothing reaches the sending desk. The address stays on the list, lit as if nothing happened. Then the checking desk lamp finds the same address before the next send and tags it coral.
Which leaves the failure you never hear about. If a delivery notice goes missing on its way back, nothing tells you that address failed. It stays on your list, and you keep sending to it. A check before you send doesn't wait for a notice to come back.
09 · Recap · 5:10
On screen: scene 02's four blocks replayed small, once stopping at block 3 (coral), once passing block 4 (green) with the notice coming back. The three chips from the hook all lit.
Next time something fails, check the log line first. On the same line as the address? Rejected, refused at the door, and you knew in under a second. A separate notice later? Bounced, accepted then sent back, if the notice makes it back at all. Either way, suppress the dead ones.
10 · Close · 5:30
On screen: the dot grid pours into the three verdict pots. The CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 5, "What causes invalid MX record?". No subscribe ask.
Not sure how many addresses on your list are quietly failing? At Review My Emails we find them and flag them for removal, before you send. The check is called RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what causes invalid MX record?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.001.004-rejected-vs-bounced.md
00 · Rejected or bounced?
Rejected or bounced?
the three chips line up under the two envelopes: 1 where each one happens · 2 why the timing matters · 3 how to tell which you got.
callback to scene 00's two envelopes.
question hook. It matches the title word for word, and the "never come back at all" line is paid off in scene 06.
a count of three chips. Reveals: one chip per question.
T12: the three questions are spoken now, and hand off to scene 02's "Start with where".
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 25 words, brand said here and in the close only.
02 · The conversation
Where it all happens
each block gets a small green 2xx tick. The key builds under the four blocks: 2xx yes green, 4xx not right now amber, 5xx no coral. On "250 OK", the last block turns solid green and the envelope crosses the line into the receiver's side. The 250 OK label sits on the last block, no gloss card (Q6), the VO says what it means in plain words.
the conversation is a count. Four blocks, one per step, so the viewer can count where a refusal lands in scene 03.
as scene 02. Split from scene 02 so each scene stays under 70 words (S2). The on-screen beats that follow this VO move here from scene 02.
scene 03 stops at block 3. Scene 04 gets past block 4.
03 · Rejected
Almanac ids in this scene: 015.001.004
Rejected: refused on the spot
the door from scene 03 stays shut. Nothing comes out of it. Back at the sending desk, one line writes itself into the desk's own log book, no hand and no clerk (T11): bo.unce@kelp-street.invalid 550 5.1.1 User unknown. The inbox beside the desk stays empty.
where the refusal lands is a count. Three blocks reached, the fourth never lit.
M-02 (the sending desk) and M-14 (the door). The log book: no picture yet.
nothing returned from the door, one line written at the desk. Reveals: (1) the shut door, (2) the log line written, (3) the empty inbox.
015.001.004 "The receiver never generates a DSN because it never accepted responsibility for the message in the first place. Your own outbound system is the one writing the bounce record into your logs or your ESP's reporting."
T3, the one twist, and T2 (where a rejection shows up).
04 · Bounced
Almanac ids in this scene: 015.001.004
Bounced: accepted, then sent back
a second envelope, a different shape, comes back out of the door on its own, addressed From: MAILER-DAEMON and To: your Return-Path, with Kai's address quoted inside. One gloss card (Q6): asynchronous bounce · a message the server accepted, then returned later in a separate email. The notice and the failure address are said in plain words, no cards.
as scene 04. Split from scene 04 so each scene stays under 70 words (S2). The on-screen beats that follow this VO move here from scene 04.
"in the strict sense" is the Almanac's own phrase from 015.001.004, kept word for word, so the video does not overrule video 1. See flag 1.
05 · Why the timing matters
Almanac ids in this scene: 015.001.004
Speed of the signal
gloss card on "suppression list" (reused from video 1). Then the numbers, one click each: 1. A grid of 100 dots. 8 turn coral. Label: 8 in every 100. 2. A block of 200 small squares, each one 1,000 addresses: 200,000 sent. 3. 16 of the 200 squares fill coral: 16,000 dead addresses. 4. Two lanes under the squares. Top lane, "rejected": all 16 coral squares drop into the suppress pot at once, stamped inside a second. Bottom lane, "bounced": the same 16 trickle in one by one across three marks, minutes · hours · days, and a few never arrive.
8 of 100 is 8 dots of 100. 16,000 of 200,000 is 16 squares of 200 (8 in every 100 of 200,000 is 16,000, it computes). The wait is the distance a square travels along the lane, not a number. No time is drawn to scale, the marks are named, not measured.
M-25 (the dot grid) for the 100 dots, M-26 (the dot fraction) for the 16 of 200, M-23 (the suppress pot). The two lanes: no picture yet. M-48 was named here before, but it sorts a hundred drawn figures, which T11 rules out (RME-182.1 review pass).
"Say" makes it an example, as 015.001.004 gives it ("If you are sending 200,000 messages and 8% of the addresses are dead"). It is never shown as a benchmark or a normal rate.
06 · The one that can go missing
Almanac ids in this scene: 015.001.004, 015.016.010
A notice can get lost
the smudged notice, marked vague · malformed · another language, beside the rejection's crisp stamp 550 5.1.1 User unknown.
as scene 06. Split from scene 06 so each scene stays under 70 words (S2). The on-screen beats that follow this VO move here from scene 06.
07 · Why big providers refuse at the door
Refused at the door
the door with its gate. A bad address reaches it and is turned back at the gate, not let in. Gloss card: backscatter · bounce notices sent to someone whose address was forged, for mail they never sent. Then the same address sent again and again, each one stamped 550, and the score gauge's needle drifts down. No other card: "big providers" and "your reputation as a sender" are plain words here (Q6).
concept mailbox-provider (M-14, M-18). Concept sender-reputation (M-33, the gauge). Backscatter has no registry row.
names no provider (RME-33.67, no names anywhere), the Almanac's "most mailbox providers" said in plain words. No reputation number, no promise.
08 · How to tell which you got
Almanac ids in this scene: 015.001.001, 015.001.004
The one you never see
the returned notice from scene 04 sets off back along the road, and fades halfway. Nothing reaches the sending desk. The address stays on the list, lit as if nothing happened. Then the checking desk lamp finds the same address before the next send and tags it coral.
the road and the returned notice from scene 04, and the checking desk.
"email marketing tool", never "ESP", in VO and on screen.
the count of notices that reach the desk is zero. The empty space where the notice should land is the picture. Reveals: (1) the notice fades halfway, (2) the address stays lit on the list, (3) the lamp tags it.
this topic's own invisible problem (the lost notice from scene 06), in place of the catch-all pivot, which V001 and V002 already use in this playlist (Q1). It sits before the recap (Q3). The blackholing GAP is not voiced (G4, H6): only a notice lost on the way back, which the Almanac states.
015.001.004 "Async DSNs travel back over open SMTP and can be lost. The Return-Path domain might be misconfigured, a spam filter might quietly drop the DSN" / 015.001.001 "we'll flag what's safe to send to and what to suppress".
09 · Recap
The three things
scene 02's four blocks replayed small, once stopping at block 3 (coral), once passing block 4 (green) with the notice coming back. The three chips from the hook all lit.
callbacks only, no new picture.
10 · Close
Find what's quietly failing
the dot grid pours into the three verdict pots. The CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 5, "What causes invalid MX record?". No subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
concept list-cleaning (M-25, M-23, M-24).
only about addresses. Nothing implies cleaning fixes a reputation block, the Return-Path setup or a spam filter. "Review My Emails" spelled out. Totals: 19 scenes. 916 spoken words (counted 2026-09-30, Q sweep). About 5:31 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2). Short cut (Q10, over 5 minutes, added in the RME-182.1 review pass): scenes 00, 02, 03, 04, 04b and 08, then the CTA line of 10. About 2:05. The answer (different moments) is in the hook, and the action (read the log line) is scene 08.
V005What causes "invalid MX record"?
waiting on YTOpen questions for YT
- Call 7 wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Flag 1 (C1) Settled by R4. Card 7 is cut here, 005.008.005 owns the no-MX case.
- Flag 2: the trailing dot, add an Almanac entry or cut dashed card 6.
- No picture yet: for the MX record label, the two hops, the priority bars, the TTL ring and MX validation.
00 · Invalid MX record · 0:00
On screen: the title question, Lora, large: "What causes invalid MX record?" Under it, a returned envelope with its slip, mono: invalid MX record. Beside it, two small green ticks: domain exists · DNS resolves. Three chips line up: 1 what an MX record is · 2 the five ways it breaks · 3 whose problem it is. Chip 3 stays greyed until scene 08.
Sally Send emails her supplier, Tidewell Supply, and it bounces back with something like invalid MX record. The domain exists. DNS resolves. Everything looks fine on the surface. What's broken, then? Most often, the record names a mail server with no address behind it. Three things make sense of it. What an MX record is. The five ways it breaks. And the one that matters most... whose problem it is.
01 · Brought to you by, woven in · 0:22
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
An address can look fine on a domain that can't take mail, so Review My Emails checks the domain too.
02 · What an MX record is · 0:30
On screen: gloss card: MX record · the entry that says which server takes mail for a domain. The MX line lifts off and becomes the address label on an envelope. Then three versions of the label, one per click: blank, smudged, pointing at an empty lot. On "receiving", an arrow shows mail coming IN to the domain, and a crossed-out arrow going out.
That entry is the MX record, and it's the address label on the envelope. If the label is missing, smudged, or points to a building that doesn't exist, the mail has nowhere to go, and it comes straight back. One thing people mix up. MX records are for RECEIVING email. They don't affect your ability to send.
03 · How the lookup works · 1:07
On screen: no gloss card (Q6), the VO says what priority means as it goes. Two bars, one per MX record: a short bar labelled 10 · primary and a bar twice its height labelled 20 · backup. The short bar lights first.
And if a domain has more than one MX record, each one carries a priority number. The lower the number, the higher the priority. So ten is tried first, and twenty is the backup.
04 · The most common cause · 1:43
On screen: the cause row appears for the first time: five card slots and one dashed one. Card 1 lights: no A record. The two hops from scene 03 replay. Hop 1 works. Hop 2 ends in no answer, the arrow stopping at a wall.
Which gives you the most common cause, the one behind Sally's bounce. The MX record says mail dot tidewell supply. But that hostname has no A record. Your server finds the name, tries to turn it into an address, and hits a dead end. That's probably the most common reason you'll see this error.
05 · Cause two, an alias · 2:02
On screen: 3 syntax errors: the record line with one character highlighted wrong, mail.tidewel-supply.example. 4 priority, no hostname: the line MX 10 followed by an empty slot.
Three. Plain syntax errors. A typo in the hostname, a missing or extra character, or the priority written wrong. Easy to miss when you're staring at a long list of records. And four. An MX record with a priority, but no hostname at all. Most mail servers reject that outright.
07 · How to check · 3:27
On screen: a plain terminal panel, one line per click, all in mono: dig MX tidewell-supply.example → 10 mail.tidewell-supply.example. nslookup -type=MX tidewell-supply.example (for Windows). dig A mail.tidewell-supply.example → no answer, lit coral. It points back to card 1.
How do you check? Run an MX lookup on the domain from your computer's terminal. It shows the domain's MX records and their hostnames. Then look up each hostname, to check it turns into an address. If any comes back with no answer, that's your break. The exact commands, for Mac, Linux and Windows, are in the description.
08 · Whose problem it is · 3:49
On screen: on the right, a phone icon, tell them another way. Then four envelopes to that one domain, every one turning coral at the same moment.
Your best bet is to reach them some other way, and let them know. And because it's the domain that's broken, every address at that domain fails together, not just one.
06 · The one that fixes itself (now after 08b, RME-33.67) · 2:42
On screen: the ring of 60 ticks from scene 06, half empty. Two envelopes set off for tidewell-supply.example. One is read against the old, crossed-out label and comes back. The other is read against the new one and goes in.
Open question: The trailing dot, one cause from 015.008.003 not voiced (gloss check gap 2, no C number, see the gap file).
Why does it cause such confusing bounce patterns? Because until every server's copy runs out, some of them still read the old label, and some read the new one. The same domain can bounce for one send and work for the next. So if you just changed a record, wait out the TTL before you go digging.
09 · What to do with those addresses · 4:24
On screen: the building from scene 02b, its mailroom lit green: MX ok. Gloss card: MX validation · asking a domain's DNS whether it has a mail server at all. Then one door inside the building stays dark, with a ? on it.
And when the MX looks fine? That only proves the domain takes mail. Checking it is called MX validation. It can't tell you whether the mailbox you're writing to is there. A working domain can still hide an address that isn't.
10 · Recap · 5:06
On screen: the cause row, all five lit, the dashed card still dashed. The three chips from the hook all lit.
Next time you see it, do three things. An MX record is the address label for a domain's mail, so start there. Run the two lookups, the MX, then the A record behind it, because a hostname with no A record is the most common break. And before you go digging, ask whose DNS it is.
11 · Close · 5:27
On screen: a building with no mailroom, then the dot grid pouring into the three verdict pots. The CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono. End screen: V006, "What does user unknown mean?" (the next video by V number, S8). No subscribe ask.
Cleaning won't fix anyone's DNS. What it does is check the address as well as the domain, and that's the job Review My Emails does before you send. Stuck on one right now? Bring it to our free SOS hotline. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what does user unknown mean?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.008.003-invalid-mx-record.md
00 · Invalid MX record
Almanac ids in this scene: 015.008.003
What's broken?
the title question, Lora, large: "What causes invalid MX record?" Under it, a returned envelope with its slip, mono: invalid MX record. Beside it, two small green ticks: domain exists · DNS resolves. Three chips line up: 1 what an MX record is · 2 the five ways it breaks · 3 whose problem it is. Chip 3 stays greyed until scene 08.
concept bounce (M-15, M-18), the envelope handed back with its slip.
question hook, the error as the viewer reads it in their own bounce report.
the answer (most often, a mail server name with no address behind it, 015.008.003 "probably the most common cause") now lands in the hook, by about 0:20. "Or MX lookup failed" was cut to make room, the error slip on screen can still show both wordings.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 20 words, brand said here and in the close only.
02 · What an MX record is
The address label
gloss card: MX record · the entry that says which server takes mail for a domain. The MX line lifts off and becomes the address label on an envelope. Then three versions of the label, one per click: blank, smudged, pointing at an empty lot. On "receiving", an arrow shows mail coming IN to the domain, and a crossed-out arrow going out.
M-12 (the fillable envelope) for the label. Split from scene 02 so each scene stays under 70 words (S2). The metaphor is said straight (V10).
03 · How the lookup works
Almanac ids in this scene: 017.001.001
Two lookups, not one
no gloss card (Q6), the VO says what priority means as it goes. Two bars, one per MX record: a short bar labelled 10 · primary and a bar twice its height labelled 20 · backup. The short bar lights first.
priority is height: the bar for 20 is twice the bar for 10, and the shortest bar goes first.
no registry row for priority. Split from scene 03 so each scene stays under 70 words (S2).
192.0.2.1 is the documentation range the Almanac itself uses in 017.001.001. No real IP address on screen.
04 · The most common cause
Cause 1: no A record
the cause row appears for the first time: five card slots and one dashed one. Card 1 lights: no A record. The two hops from scene 03 replay. Hop 1 works. Hop 2 ends in no answer, the arrow stopping at a wall.
the causes are a count. Card 1 of 5 lit.
M-20 (the case file opened and empty). No picture yet for the dead end.
05 · Cause two, an alias
Causes 2 to 4
3 syntax errors: the record line with one character highlighted wrong, mail.tidewel-supply.example. 4 priority, no hostname: the line MX 10 followed by an empty slot.
cards 3 and 4 of 5 light, one per click.
M-20 (the case files). Split from scene 05 so each scene stays under 70 words (S2).
07 · How to check
Look it up yourself
a plain terminal panel, one line per click, all in mono: dig MX tidewell-supply.example → 10 mail.tidewell-supply.example. nslookup -type=MX tidewell-supply.example (for Windows). dig A mail.tidewell-supply.example → no answer, lit coral. It points back to card 1.
a plain terminal panel, no picture needed. The commands stay on screen for the eye, and the VO no longer reads them out (P7, Q8: where and how in one line, the syntax in the description).
the domain on screen is always the reserved tidewell-supply.example, never the Almanac's placeholder, which sits on a real-looking ending.
08 · Whose problem it is
Whose DNS is it?
on the right, a phone icon, tell them another way. Then four envelopes to that one domain, every one turning coral at the same moment.
M-15 (the envelope row) for the four that fail together. Split from scene 08 so each scene stays under 70 words (S2).
"every address at that domain" is a count. Four envelopes, all four fail on the same click.
06 · The one that fixes itself (now after 08b, RME-33.67)
Almanac ids in this scene: 005.008.005, 015.008.003
Cause 5: a recent change
the ring of 60 ticks from scene 06, half empty. Two envelopes set off for tidewell-supply.example. One is read against the old, crossed-out label and comes back. The other is read against the new one and goes in.
3600 seconds drawn as 60 ticks of one minute each, and the ring emptying is the wait.
callback to scene 02b's address label and scene 06's ring.
one domain, two copies of its label, two outcomes. Reveals: (1) the half-empty ring, (2) the old-label envelope returns, (3) the new-label one goes in.
015.008.003 "If the MX was just updated, old DNS resolvers may still be caching the previous (broken) version. This one resolves itself once the TTL expires, but it can cause confusing bounce patterns in the meantime." The "wait out the TTL" action follows from "resolves itself once the TTL expires".
T1 and T9, the why behind "confusing". Scene 06 split so each stays under 70 words (S2).
09 · What to do with those addresses
Almanac ids in this scene: 005.003.012
The one you never see
the building from scene 02b, its mailroom lit green: MX ok. Gloss card: MX validation · asking a domain's DNS whether it has a mail server at all. Then one door inside the building stays dark, with a ? on it.
the building from 02b. mx-validation is gloss tier, no picture yet.
"email marketing tool", never "ESP".
one lit mailroom, one dark door. Reveals: (1) the mailroom lights, (2) the dark door.
this topic's own invisible problem, what an MX check cannot see, in place of the stock catch-all pivot (V001 and V002 carry it in this playlist). It sits before the recap (Q3). The line was in the close before, now it earns the pitch.
005.003.012 "It tells you whether the domain accepts mail. It doesn't tell you whether the specific address exists on that server." (gloss check row 17)
10 · Recap
The three things
the cause row, all five lit, the dashed card still dashed. The three chips from the hook all lit.
callbacks only, no new picture.
11 · Close
Clean before you send
a building with no mailroom, then the dot grid pouring into the three verdict pots. The CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono. End screen: V006, "What does user unknown mean?" (the next video by V number, S8). No subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
concept list-cleaning (M-25, M-23, M-24). mx-validation is gloss tier, no picture yet.
says outright that cleaning does not fix DNS. Nothing implies it fixes MX, SPF, DKIM or DMARC. "Review My Emails" spelled out. Totals: 18 scenes. 930 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 5:36 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2). Short cut (Q10, over 5 minutes, added in the RME-182.1 review pass): scenes 00, 02b, 04, 07 and 08, then the CTA line of 11. About 1:50. The answer is in the hook and the action (run the two lookups, then ask whose DNS it is) follows straight after.
V006What does “user unknown” mean?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C13, new: which yearly decay rate the Almanac should carry (20 to 25 or 20 to 30 percent), and whether the registry's list-decay gloss keeps a number.
- "No picture yet" visuals: the slot row, the lit slip with its two captions, the five cause cards, the re-import sheet, the side tray.
- C26 and C37, found in the RME-182.1 review pass: not voiced as a side.
00 · Nobody by that name (hook) · 0:00
On screen: the title, Lora, large: "What does “user unknown” mean?". An envelope addressed to bo.unce@coral-cove.invalid reaches a door. Behind the door, a row of mail slots with name tags. No tag matches. Three numbered chips: 1 what it means · 2 where it comes from · 3 what to do.
Sally Send's email came back with two words. User unknown. What does that mean? And should she send it again, just to check? Here's the whole story, in three parts. What it means. Where it comes from. And what to do.
01 · Brought to you by, woven in · 0:15
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Most user unknown addresses can be caught before you ever send, during the validation check Review My Emails runs on every list.
02 · What the server is saying · 0:23
On screen: under the slip, two captions side by side: The email account that you tried to reach does not exist and User unknown. A bracket joins them: same meaning.
And the wording changes from server to server. Some spell it out, the email account that you tried to reach does not exist. Older ones just say, user unknown. Same meaning. Nobody by that name lives here.
03 · Where it comes from · 1:00
On screen: chip 2 lights. Five cards deal in, one per reason, each an envelope with its story: 1. wren@mailbx.invalid, with the intended wren@mailbox.example ghosted above it and the missing o circled. 2. a coupon slip clipped to a blank address. 3. una.subscribe@pearl-diver.invalid, with an empty desk. 4. a closed padlock on a mailbox. 5. a stack of envelopes with a bought tag, coral.
Where do user unknown bounces come from? Five common reasons. One. Someone typed their address wrong at signup. Two. Someone used a fake address, to get a download or a discount. Three. The person left their company, and IT deleted the account. Four. The account was closed, for inactivity or a policy problem. And five. The address was made up. A bought list, a data append, a scraped contact.
04 · Why retrying never fixes it · 1:25
On screen: chip 3 lights. The door from scene 00. A second envelope knocks, a third, each comes back with the same coral 550 5.1.1 slip. The slips stack. Then a single coral stamp over the stack: once is enough.
What should Sally do, then? First, don't send it again, just to check. The address doesn't exist on that server, and it's not going to exist if you retry. Don't wait for a pattern. A single user unknown is enough.
05 · Out, and into the pot · 1:39
On screen: bo.unce@coral-cove.invalid lifts out of the list and drops into the suppress pot. The lid closes. Then a fresh import sheet slides in carrying the same address, and it hits the closed lid and stops. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
Then do two things. Remove the address from your active list. And add it to your suppression list. That second step stops the address slipping back in, the next time someone re-imports a list. Most email marketing tools suppress hard bounces for you. Where do you check? Open your tool's suppression list and search for an address you know hard bounced. If it's there, your tool is doing it.
06 · When it isn't user unknown · 2:04
On screen: two coral slips side by side, both starting 550. Left: 5.1.1 user unknown, it goes into the suppress pot. Right: 5.7.1 rejected, policy, it does not go in the pot. It is set aside on its own tray, labelled not the address, and its words light up.
Before you suppress, one check. Not every five fifty means it's gone. Read the words on the Diagnostic Code line, the server's own reason in the bounce message, not just the code. User unknown, or mailbox does not exist, is a real dead one. If the words talk about spam, policy, or your reputation, the address isn't the problem. Suppressing it fixes nothing. Fix what the words point at.
07 · A lot of them at once · 2:29
On screen: the block of flats from scene 02. Its front door is now marked accepts everything, the channel's catch-all door (V002 scene 10b). A letter to a real name goes in. madeupname@ goes in the same way. Nothing comes back out. The coral 550 5.1.1 slip from scene 02 hangs beside the door, blank this time. Gloss card: catch-all · a mail server that accepts every address at its domain, real or not.
Open question: C13: the yearly decay rate.
Validation catches most of them. But some made-up names never come back as user unknown at all. On a catch-all domain, the server accepts every address, real or invented. An email to a made-up name there doesn't bounce. No reply, no code, nothing to read. The letter goes in through a front door that takes every name, and nothing comes back out.
08 · Recap · 3:12
On screen: the three chips, all lit, small at the top. Under them, four callback pictures light one per move: the slip stack stamped once is enough (04), the closed pot lid (05), the two 550 slips (06), the validation gate (07).
To wrap up. Never retry a user unknown, suppress it the first time. Check your tool's suppression list is catching them. Read the words before you suppress. And validate any segment you haven't mailed in a while, before you send to it.
09 · Close · 3:27
On screen: the dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: playlist 2 video 2, no subscribe ask.
Review My Emails checks for both before you send. It flags the user unknowns, and it flags the catch-alls that never tell you, as catch-alls, not as deliverable. Rather we did it for you? That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a suppression list?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.006.008-what-does-user-unknown-mean.md
00 · Nobody by that name (hook)
User unknown?
the title, Lora, large: "What does “user unknown” mean?". An envelope addressed to bo.unce@coral-cove.invalid reaches a door. Behind the door, a row of mail slots with name tags. No tag matches. Three numbered chips: 1 what it means · 2 where it comes from · 3 what to do.
a row of slots and zero matches. The empty match is the point. Reveals: (1) the envelope at the door, (2) the slots with no match, (3) the three chips.
concept hard-bounce (the returned envelope stamped once, the door closing, M-15, M-14).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What the server is saying
What it means
under the slip, two captions side by side: The email account that you tried to reach does not exist and User unknown. A bracket joins them: same meaning.
two wordings, one meaning. Reveals: (1) the long wording, (2) the short one, (3) the bracket.
the answer (no mailbox by that name, a hard bounce) and the first action (don't send it again) both land here, by about 0:40.
callback to scene 02's slip.
the long wording is shown without naming the provider it comes from. The 4xx and 5xx lesson is not re-taught, only the callback line.
Scene 02 split so each stays under 70 words (S2).
03 · Where it comes from
Where it comes from
chip 2 lights. Five cards deal in, one per reason, each an envelope with its story: 1. wren@mailbx.invalid, with the intended wren@mailbox.example ghosted above it and the missing o circled. 2. a coupon slip clipped to a blank address. 3. una.subscribe@pearl-diver.invalid, with an empty desk. 4. a closed padlock on a mailbox. 5. a stack of envelopes with a bought tag, coral.
a count of causes, 5, one card per click. Reveals: (1) to (5) one card each.
concept hard-bounce for the frame. The five cause cards: no picture yet.
the typo pair is a made-up personal inbox on .invalid, never a typo of a real provider.
04 · Why retrying never fixes it
What to do
chip 3 lights. The door from scene 00. A second envelope knocks, a third, each comes back with the same coral 550 5.1.1 slip. The slips stack. Then a single coral stamp over the stack: once is enough.
the stack of identical slips. More knocks, same answer, every time. Reveals: (1) the second knock, (2) the third knock, (3) the stamp.
concept hard-bounce (M-15, M-14).
05 · Out, and into the pot
Suppress it
bo.unce@coral-cove.invalid lifts out of the list and drops into the suppress pot. The lid closes. Then a fresh import sheet slides in carrying the same address, and it hits the closed lid and stops. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
one address, one pot, the lid shut. The re-import bouncing off the lid is the reason for the pot. Reveals: (1) out of the list, (2) into the pot, lid closes, (3) the re-import stops at the lid.
concept suppression-list (the third verdict pot with its lid closing, M-23, M-24).
says "email marketing tool", never "ESP".
06 · When it isn't user unknown
Almanac ids in this scene: 005.006.018, 011.009.012, 015.005.001
Read the words too
two coral slips side by side, both starting 550. Left: 5.1.1 user unknown, it goes into the suppress pot. Right: 5.7.1 rejected, policy, it does not go in the pot. It is set aside on its own tray, labelled not the address, and its words light up.
two slips, same first number, two different paths. Reveals: (1) both slips, (2) the left into the pot, (3) the right set aside, its words lit.
concept suppression-list (M-23, M-24). The policy slip is concept block-bounce (defined by 015.005.001, no picture yet). The side tray: no picture yet.
no blocklist is named. Nothing implies list cleaning fixes a policy or reputation block. C26 (does a 5.7.1 point at the sender or the recipient's own rule) is not voiced: the line says only what both sides agree on, the address is not the problem and the words say what is (005.006.018, 011.009.012). RME-182.1 review pass, it replaced "Look at your sending instead", one side of C26.
07 · A lot of them at once
Almanac ids in this scene: 005.004.002, 005.006.008, 005.011.001, 005.011.002, 005.011.003, 021.002.013
The ones that never say it
the block of flats from scene 02. Its front door is now marked accepts everything, the channel's catch-all door (V002 scene 10b). A letter to a real name goes in. madeupname@ goes in the same way. Nothing comes back out. The coral 550 5.1.1 slip from scene 02 hangs beside the door, blank this time. Gloss card: catch-all · a mail server that accepts every address at its domain, real or not.
two letters in, one real and one made up, and no slip for either. Reveals: (1) the door marked accepts everything, (2) the made-up name goes in, (3) the blank slip.
concept catch-all (the registry's gate, M-18, or the same door from scene 00, M-14, see the one choice in the piece map). No figure and no signing (T11): the RME-182.1 review pass removed "a front desk that signs for every letter".
Q3: moved before the recap. Q1: the twist label is gone, the scene says its surprise in its own words. Q2: a bounce and list topic, so the catch-all pivot fits.
021.002.013 "When a mail server is configured as a catch-all, it accepts delivery attempts for any address at that domain, even completely made-up ones. So an email sent to madeupname@somecompany.example doesn't bounce. It just... lands somewhere." / "A bounce never comes back, so there's nothing to work with."
T3 (the one twist) and T6 (the pivot before the pitch, R15). On screen the made-up name has no domain, the Almanac's example domain is not shown.
08 · Recap
Four moves
the three chips, all lit, small at the top. Under them, four callback pictures light one per move: the slip stack stamped once is enough (04), the closed pot lid (05), the two 550 slips (06), the validation gate (07).
a count of four moves, one lit picture each. Reveals: (1) to (4), one per move.
callbacks only (S5). Four pictures in place of a list read aloud (Q7, RME-182.1 review pass).
09 · Close
Almanac ids in this scene: 021.002.013
Clean your list
the dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: playlist 2 video 2, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is only about addresses. Nothing implies it fixes the policy rejection in scene 06. It "flags" catch-alls, never "catches" them as bad (021.002.013: validation "can't verify the mailbox"), and "deliverable", never "valid", as the verdict word (V6). Totals: 12 scenes. 633 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 3:49 at 166 words a minute, about 4:03 with scene breaks. Every scene is 20 to 70 words (S2). 4 glossed words (Q6). Under 5 minutes, so no "Short cut:" note (Q10).
V007What is a suppression list?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C14 Settled by R10: no timing in the video. The three Almanac pages go to YT's own review (#almanac-to-check, via the PM).
- "No picture yet" visuals: the import sheets, the master file above two desks, the lean card, the misfiled reply card, the spam button icon.
00 · They came back (hook) · 0:00
On screen: the title, Lora, large: "What is a suppression list?". una.subscribe@pearl-diver.invalid slides out of the list through the unsubscribe door. A calendar flips seven pages. A fresh import sheet slides in, and the same address is on it, highlighted coral. Three numbered chips: 1 what it is · 2 what goes in · 3 your own copy.
Someone unsubscribes from Sally Send's newsletter. A week later, she imports a fresh list, and their address is on it. Do they get her next campaign? Without a suppression list, yes, they do. So what is a suppression list? Three answers cover it. What it is. What goes in. And why you keep your own copy.
01 · Brought to you by, woven in · 0:20
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Addresses that don't exist, the ones that land on a suppression list by bouncing, are ones Review My Emails can flag before you send.
02 · The master override · 0:29
On screen: three sheets slide toward the send button from three sides, labelled new import, bought data, customer sync. Each carries one coral address. At the gate before the send, each coral address is pulled off and dropped into the pot. The rest go through.
It works as a master override. Even if a suppressed address turns up in a new import, a bought data set, not that you'd do that, or a synced customer list, the doorman catches it before anything goes out. Your part is making sure every send, from every source, gets checked against it first.
03 · What goes in · 1:01
On screen: chip 2 lights. Four addresses drop into the pot, one per click, each with its reason tag: 1. una.subscribe@pearl-diver.invalid · unsubscribed 2. bo.unce@coral-cove.invalid · hard bounce (the envelope from video 1, with its 550 5.1.1 slip) 3. walked.the.plank@ship.invalid · spam complaint, a small spam button icon beside it 4. abandon.ship@hull.invalid · manual removal
What goes in? Usually four kinds of address. Unsubscribes. People who opted out. Hard bounces. Addresses that failed for good, like one that doesn't exist. Spam complaints. People who hit the spam button. And manual removals. Addresses you add yourself, for a legal request, a customer service situation, or anything else that calls for it.
04 · Why it matters · 1:21
On screen: one line of text above the pot, still: CAN-SPAM · GDPR · CASL: honour opt-outs. Then the only thing that moves: a reputation meter. An envelope goes from the send button to walked.the.plank@ship.invalid, and the meter drops. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
Why does getting it right matter? The law says so. The big email laws all require you to honour opt-outs, and that means keeping real suppression data. And your sender reputation says so too. Mailing people who already complained, or already unsubscribed, is one of the fastest ways to damage your standing with mailbox providers.
05 · Your tool has one. Keep your own too · 1:40
On screen: gloss card: bounce rate · the share of your emails that come back undelivered (Q5, re-glossed for a viewer arriving from search, RME-182.1). The list opens as a timeline. A cluster of entries bunches up in one short window, marked summer. A magnifier finds an open and a click in the history of one entry, and a small restore arrow lifts it off the list.
How do you catch it? Look at the suppression list itself, not just your bounce rate, the share of mail that comes back. If a cluster of addresses got suppressed in a short window, especially around summer or late December, check whether they had opened or clicked before. An engaged subscriber who suddenly bounced is a red flag. Most tools let you restore one, once you have the evidence.
06 · Don't delete it, keep it lean · 2:52
On screen: the doorman's list. Each hard bounce entry carries a small coral 1 send tag, the send it cost. Then an import sheet and an old segment of grey dots sit outside the door, not yet sent to.
One thing the list itself can't show you. Every hard bounce on it got there by bouncing first. It cost you a send, and it counted against your reputation, before the doorman learned its name. They often turn up when you import a list, or mail old contacts again.
07 · Recap · 3:32
On screen: the three chips, all lit, with the pot, the four reason tags and the lean card, small.
Quick recap. Treat your suppression list as the doorman's list, the master override, and check every send against it. Put unsubscribes, hard bounces, complaints and manual removals on it. Keep your own copy, lean, and never delete it to tidy up. And look at it regularly for real readers who never left.
08 · Close · 3:51
On screen: the dot grid pours into the three verdict pots, the suppress pot's lid closing last. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: playlist 2 video 3, no subscribe ask.
Review My Emails checks the list before that first send, so addresses that don't exist get flagged before they cost you. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how accurate are email validation services?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.004.009-what-is-a-suppression-list.md
00 · They came back (hook)
What is a suppression list?
the title, Lora, large: "What is a suppression list?". una.subscribe@pearl-diver.invalid slides out of the list through the unsubscribe door. A calendar flips seven pages. A fresh import sheet slides in, and the same address is on it, highlighted coral. Three numbered chips: 1 what it is · 2 what goes in · 3 your own copy.
one address, out and back in. The seven calendar pages are the "week later". Reveals: (1) the unsubscribe, (2) the week, (3) the import with the address back, (4) the three chips.
concept suppression-list (the third verdict pot, M-23, M-24) is teased, not shown yet. The import sheet: the re-import sheet proposed in video 1 scene 05.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The master override
What it is
three sheets slide toward the send button from three sides, labelled new import, bought data, customer sync. Each carries one coral address. At the gate before the send, each coral address is pulled off and dropped into the pot. The rest go through.
three ways in, one check, zero coral addresses out. Reveals: (1) to (3) one sheet per click caught at the gate.
concept suppression-list (M-23, M-24, M-18 for the gate). The three sheets: no picture yet.
the answer (a list your system never sends to) lands in 02, and the first action (check every send against it) lands here, by about 1:00. Split from 02 so each scene stays under 70 words (S2).
"bought data" is the Almanac's own aside, said with a wink, not a how-to.
03 · What goes in
What goes in
chip 2 lights. Four addresses drop into the pot, one per click, each with its reason tag: 1. una.subscribe@pearl-diver.invalid · unsubscribed 2. bo.unce@coral-cove.invalid · hard bounce (the envelope from video 1, with its 550 5.1.1 slip) 3. walked.the.plank@ship.invalid · spam complaint, a small spam button icon beside it 4. abandon.ship@hull.invalid · manual removal
a count of kinds, 4, the pot filling one layer per kind. Reveals: (1) to (4) one address each.
concepts suppression-list (M-23, M-24) and hard-bounce (M-15, M-14). The complaint is a spam button icon, no picture yet. The registry's complaint-rate picture (M-48, the people sort) is out until the cast is picked (T11, RME-182.1).
04 · Why it matters
Almanac ids in this scene: 005.005.001, 008.004.008, 008.004.010
Why it matters
one line of text above the pot, still: CAN-SPAM · GDPR · CASL: honour opt-outs. Then the only thing that moves: a reputation meter. An envelope goes from the send button to walked.the.plank@ship.invalid, and the meter drops. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
the meter's level. One send to a complainer, one clear drop, no value on the scale. Reveals: (1) the law line, (2) the send, (3) the meter drops.
concepts sender-reputation (the score gauge, M-33) and suppression-list.
laws are named in one line on screen only, never a section number or a day count (C14). The VO says "the big email laws" (Q6, one new technical word per scene, and that word here is sender reputation). No fine amounts.
R10 (YT, 2026-09-29): no opt-out timing in the video. The C14 GAP is closed. YT reviews the Almanac side herself: 005.005.001 (GDPR Art. 21, ten business days), 008.004.008 (GDPR immediate), 008.004.010 (cites Art. 17). For the PM to post to #almanac-to-check.
05 · Your tool has one. Keep your own too
Almanac ids in this scene: 015.004.013
Your own copy
gloss card: bounce rate · the share of your emails that come back undelivered (Q5, re-glossed for a viewer arriving from search, RME-182.1). The list opens as a timeline. A cluster of entries bunches up in one short window, marked summer. A magnifier finds an open and a click in the history of one entry, and a small restore arrow lifts it off the list.
a cluster in time, one entry with history, one restore. Reveals: (1) the cluster, (2) the history, (3) the restore arrow.
concept suppression-list (M-23, M-24). The timeline: no picture yet.
says "email marketing tool", never "ESP". Names no vendor.
015.004.013 "look at your suppression list regularly, not just your bounce rate. If you see a cluster of addresses suppressed in a short window, especially around peak vacation periods (late December, summer), that's worth investigating. Check whether those addresses have any engagement history before the suppression. An engaged subscriber who suddenly 'bounced' is a red flag worth a closer look." / "most ESPs let you manually restore suppressed addresses if you have evidence the suppression was incorrect".
T2 and T5, where to look and what to do.
06 · Don't delete it, keep it lean
Almanac ids in this scene: 005.006.008, 005.012.010, 005.012.011, 008.004.009, 008.004.010
Before they cost you
the doorman's list. Each hard bounce entry carries a small coral 1 send tag, the send it cost. Then an import sheet and an old segment of grey dots sit outside the door, not yet sent to.
one send per hard bounce entry, then the unsent pile. Reveals: (1) the tags, (2) the import sheet and the old segment waiting.
concept suppression-list (M-23, M-24). The per-entry tag: no picture yet.
Q3: moved before the recap. Q2: a list topic, the pivot is the list's own blind spot, no catch- all.
005.006.008 "If you're seeing a lot of user-unknown bounces after importing a list or re-engaging old contacts, that's usually list decay at work... Validate before sending to any dormant segment to catch these before they hit your bounce rate." / 008.004.009 "mailing people who've already complained or unsubscribed is one of the fastest ways to damage your standing".
T6, the pivot before the pitch (R15 shape): the problem the viewer cannot see on their own.
07 · Recap
The three things
the three chips, all lit, with the pot, the four reason tags and the lean card, small.
the four tags in the pot, held.
callbacks only.
08 · Close
Clean your list
the dot grid pours into the three verdict pots, the suppress pot's lid closing last. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: playlist 2 video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is about addresses only. It does not keep anyone's suppression list for them, and nothing implies it handles unsubscribes or complaints. Totals: 13 scenes. 693 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 4:10 at 166 words a minute, about 4:25 with scene breaks. Every scene is 20 to 70 words (S2). Under 5 minutes, so no Short cut note (Q10).
V008How accurate are email validation services?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C15: the share of B2B catch-all, 15 to 25 percent of domains or 15 to 35 percent of addresses.
- The blocklist checker link in 005.003.006: right tool, or should the answer point elsewhere?
- "No picture yet" visuals: the 100 cell bar with the amber gap, the probe card at a door, the locked mailbox, the desk in shadow, the two-bar hiding version.
00 · Ninety eight percent accurate (hook) · 0:00
On screen: the title, Lora, large: "How accurate are email validation services?" Returned envelopes drop onto a desk, one after another, into a small pile. A small grey tag sits on the pile: up to 98% accurate. As the last envelopes land, the tag is pushed down under them. Four numbered chips, the VO's words: 1 what that number measures · 2 three kinds of address that fool it · 3 one thing nobody can see · 4 how to test a validator on your list. Chips 2 to 4 stay grey until their scenes.
Sally Send ran her list through a validation service. It promised up to ninety eight percent accuracy. Then her first campaign went out, and the bounces didn't match the promise. How accurate are email validation services? Four things decide it. What that number measures. Three kinds of address that fool it. One thing nobody can see. And how to test a validator on YOUR list.
01 · Brought to you by, woven in · 0:23
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails checks every address on your list before you send, and when a server won't give a straight answer, it says so.
02 · What the number measures · 0:32
On screen: chip 1 lights. marina@tidewell-supply.example at a door. A small probe card goes to the door and comes back with a green yes. A second card, on a made-up name at the same door, comes back coral no. Gloss card: SMTP handshake · asking the receiving server if a mailbox exists, without sending anything. Then the up to 98% tag from scene 00 comes back, and gets a second line beneath it: on normal mailboxes. On "your own list first", a small stack of address cards labelled your list slides in beside the door.
Where does the number come from? The validator goes to the receiving server's door and asks, do you have a mailbox by this name? That's an SMTP handshake. No message is sent. On a normal mailbox, like a personal inbox, you usually get a clean yes or no. That's the ninety to ninety eight percent. Your list probably isn't all normal. So test any validator on your own list first.
03 · The door that says yes to everyone · 0:57
On screen: chip 2 lights, with a counter 1 of 3. The door for saltmarsh-outfitters.example. A probe for finn@ comes back yes. A probe for asdfgh@ comes back yes too. Both cards turn amber. Gloss card: catch-all · a mail server that accepts every address at its domain, real or not.
Which kinds of address fool it? There are three. One. A catch-all domain. That's a door that says yes to every caller, real name or not, and sorts it out later, inside. Ask about a real person, you get yes. Ask about a made-up name, you still get yes. So a validator can't verify it, without sending mail.
04 · The address that exists, but maybe nobody reads it · 1:18
On screen: counter 2 of 3. admin@saltmarsh-outfitters.example at the door. The probe comes back green yes, then the desk behind the door stays in shadow with a small question mark over it, and the card turns amber. Gloss card: role address · an address for a job or a team, like info@ or admin@, not for one person.
Two. A role address, like info at, or admin at. Here the server says yes, and it's telling the TRUTH. The address exists. But the validator can't know if anyone is watching that inbox. The door opens, and you can't see if anyone's at the desk.
05 · The server that plays dead · 1:35
On screen: counter 3 of 3. A door with the gate narrowing in front of it (the throttling gate). The probe card waits, a small clock turning, then comes back with no answer at all, a blank card that turns amber. Gloss card: throttled · a server slowing down or stalling the checks it's asked to answer.
Three. A throttled server. Some servers play dead, to protect themselves from spam. You ask, and nobody comes to the door. They stall, or give a vague, try again later. They might refuse the check altogether. That leaves the validator to guess, or, if it's honest, to say unknown.
06 · What no validator can see · 1:52
On screen: chip 3 lights. wren@mailbox.example. Two green ticks light beside it: written properly · domain has mail servers. Then the mailbox itself, drawn as a closed box, stays grey with a small lock and the label still read?. Gloss card: mailbox provider · the service your reader receives mail with.
And the one thing nobody can see at all. The big mailbox providers don't share whether an inbox is still active. So a validator can confirm the address is written properly, and the domain has mail servers. But it can't see inside the mailbox. It can't tell you for sure if someone is still reading.
07 · Your list is not average · 2:12
On screen: chip 4 lights. The up to 98% tag unfolds into an outlined, empty 100 cell bar with a thin grey dashed tick at 98, labelled small the headline. A small grey note: say: 20% catch-all · 15% role. Then the 20 cells under the tick fill amber, labelled might be 20 points lower. A small 100 stamp appears to the right, and gets crossed out.
How do you test a validator on your list? First, know what your list is made of. The headline assumes normal mailboxes. Say twenty percent of your list sits on catch-all domains, and fifteen percent are role addresses. Your real accuracy might be twenty points lower than the headline. And no validator hits a hundred percent. One that claims it is inflating its numbers.
08 · Test it on your list · 2:35
On screen: the results file, one row per address, the label column lit. The column counts itself into bars: a tall green bar labelled deliverable, separate amber bars labelled catch-all, role, unknown, and a coral bar. Beside it, the other version: only two bars, deliverable and undeliverable, with the amber cells hidden inside the green bar and a small ? on it.
Next, read the labels that come back. They're in the results file, the column next to each address. An honest validator shows catch-all, role and unknown as their own groups. One that only says deliverable or not is hiding its guesses inside deliverable.
09 · Recap · 3:06
On screen: the four chips all lit, the three doors small in a row, each amber, the locked mailbox beside them, the scene 07 bar with its 20 amber cells.
Four things to keep. The headline measures normal mailboxes. Catch-alls, role addresses and throttled servers fool it. No validator can see inside the mailbox. And test it yourself. A thousand of your own addresses through the validator, then read the label column.
10 · Close · 3:21
On screen: the dot grid pours into the three verdict pots, keep, monitor and suppress. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 4, no subscribe ask.
Test before you trust. When Review My Emails can't tell, it flags the address for caution instead of faking a verdict. You see keep, monitor and suppress, not a guess dressed up as deliverable. Not sure which validator to trust? Ask our free SOS hotline. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a dead domain?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.003.006-how-accurate-is-validation.md
00 · Ninety eight percent accurate (hook)
How accurate is it?
the title, Lora, large: "How accurate are email validation services?" Returned envelopes drop onto a desk, one after another, into a small pile. A small grey tag sits on the pile: up to 98% accurate. As the last envelopes land, the tag is pushed down under them. Four numbered chips, the VO's words: 1 what that number measures · 2 three kinds of address that fool it · 3 one thing nobody can see · 4 how to test a validator on your list. Chips 2 to 4 stay grey until their scenes.
the pile of returned envelopes is the bounces, and they bury the small 98% tag. The claim is a label, never drawn full size (LESSONS N7). The pile carries no count. Reveals: (1) the envelopes and the tag, (2) the pile covers the tag, (3) the four chips.
concept email-validation (M-12, M-24).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What the number measures
A normal mailbox
chip 1 lights. marina@tidewell-supply.example at a door. A small probe card goes to the door and comes back with a green yes. A second card, on a made-up name at the same door, comes back coral no. Gloss card: SMTP handshake · asking the receiving server if a mailbox exists, without sending anything. Then the up to 98% tag from scene 00 comes back, and gets a second line beneath it: on normal mailboxes. On "your own list first", a small stack of address cards labelled your list slides in beside the door.
two probes, two clean answers, one of each colour. Reveals: (1) the probe and its green yes, (2) the coral no, (3) the on normal mailboxes line under the tag, (4) the your list stack.
the answer (the number holds on normal mailboxes, and your list is not all normal) and the first action (test on your own list) both land here, by about 1:00.
concept smtp-handshake is gloss tier, no picture yet. Proposed: this probe card at a door.
03 · The door that says yes to everyone
Catch-all domains
chip 2 lights, with a counter 1 of 3. The door for saltmarsh-outfitters.example. A probe for finn@ comes back yes. A probe for asdfgh@ comes back yes too. Both cards turn amber. Gloss card: catch-all · a mail server that accepts every address at its domain, real or not.
two different questions, the same answer. The two identical yes cards are the point. Reveals: (1) the real name's yes, (2) the made-up name's yes, (3) both turn amber.
concept catch-all (M-18, M-15).
04 · The address that exists, but maybe nobody reads it
Role addresses
counter 2 of 3. admin@saltmarsh-outfitters.example at the door. The probe comes back green yes, then the desk behind the door stays in shadow with a small question mark over it, and the card turns amber. Gloss card: role address · an address for a job or a team, like info@ or admin@, not for one person.
a true yes, then the unknown behind it. Reveals: (1) the green yes, (2) the shadowed desk and the question mark, (3) the card to amber.
the door (M-14) and a plain desk object. The registry's role-address picture also uses M-07, a drawn person, which T11 rules out (RME-182.1 review pass).
05 · The server that plays dead
Throttled servers
counter 3 of 3. A door with the gate narrowing in front of it (the throttling gate). The probe card waits, a small clock turning, then comes back with no answer at all, a blank card that turns amber. Gloss card: throttled · a server slowing down or stalling the checks it's asked to answer.
the wait is the clock. No answer comes back, and the blank card is the result. Reveals: (1) the gate narrows, (2) the clock turns, (3) the blank card, amber.
concept throttling (M-18, M-15).
06 · What no validator can see
The inside of the mailbox
chip 3 lights. wren@mailbox.example. Two green ticks light beside it: written properly · domain has mail servers. Then the mailbox itself, drawn as a closed box, stays grey with a small lock and the label still read?. Gloss card: mailbox provider · the service your reader receives mail with.
the ticks the checks can light, then one place no check reaches. Whatever lights, still read? stays locked (the handshake's yes from scene 02 is not a tick for this, Q12). Reveals: (1) tick one, (2) tick two, (3) the locked box.
concept mailbox-provider (M-14, M-18).
07 · Your list is not average
Almanac ids in this scene: 005.003.006
Test it on your list
chip 4 lights. The up to 98% tag unfolds into an outlined, empty 100 cell bar with a thin grey dashed tick at 98, labelled small the headline. A small grey note: say: 20% catch-all · 15% role. Then the 20 cells under the tick fill amber, labelled might be 20 points lower. A small 100 stamp appears to the right, and gets crossed out.
one bar, held still. The only filled shape is the 20 amber cells, the Almanac's "20 points lower", drawn to scale under the tick. The claimed 98 stays a thin dashed tick, never a filled bar (N7). The example mix is a small note, not a drawing, so no picture claims a sum. Reveals: (1) the outlined bar and the tick, (2) the example note, (3) the 20 amber cells, (4) the 100 crossed out.
the bar grows out of the scene 00 tag. No picture yet. M-29's dashed gap is the nearest library piece (see the pieces map).
"Say" makes the mix 005.003.006's own worked example, never a benchmark. "Might" is the Almanac's hedge. The benchmark ranges for catch-all share (C15) stay out.
08 · Test it on your list
Test before you trust
the results file, one row per address, the label column lit. The column counts itself into bars: a tall green bar labelled deliverable, separate amber bars labelled catch-all, role, unknown, and a coral bar. Beside it, the other version: only two bars, deliverable and undeliverable, with the amber cells hidden inside the green bar and a small ? on it.
the label column counted into bars. Five labelled bars against two bars is the honest-versus-hiding comparison. Bar heights are illustrative and carry no numbers. Reveals: (1) the column, (2) the five bars build from it, (3) the two bar version with the ?.
the desk from scene 08. The two-bar version: no picture yet.
T2, where the labels sit. Scene 08 split so each stays under 70 words (S2).
09 · Recap
What to remember
the four chips all lit, the three doors small in a row, each amber, the locked mailbox beside them, the scene 07 bar with its 20 amber cells.
three amber doors and one locked box, the amber gap held.
callbacks only.
10 · Close
Almanac ids in this scene: 005.003.006
Clean your list
the dot grid pours into the three verdict pots, keep, monitor and suppress. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
no accuracy percentage is claimed for Review My Emails. No inbox promise. "We can't see inside a mailbox either" says what a clean does not do (LESSONS 2), backed by 005.003.006 "No service can perfectly predict whether someone's still checking their inbox". Totals: 12 scenes. 624 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 3:46 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2). Under 5 minutes, so no "Short cut:" note (Q10).
V009What is a dead domain?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C16: the bounce rate lines in 005.008.001 and 005.003.002 disagree.
- C1 Settled by R4: video 5 (005.008.005) voices it. This video keeps to the no MX and no A case.
- "No picture yet" visuals: the four lookup cards, the placeholder page frame, the stairs of checks, the bounce report table, the 50,000 dot grid, the calendar.
00 · The address that stopped working (hook) · 0:00
On screen: the title, Lora, large: "What is a dead domain?" sunk@shipwreck.invalid on a card in front of a lit shop sign. The address never moves. The sign behind it goes dark, and the card turns coral. Envelopes keep arriving at the dark door. Four numbered chips, the VO's words: 1 what makes a domain dead · 2 how they end up on your list · 3 how to spot one before you send · 4 why you can't ignore them. Chips 2 to 4 stay grey until their scenes.
The address worked when a subscriber typed it into Sally Send's signup form. Then the company folded. Nobody told her. Every campaign since has bounced off it, and she's still sending. So what is a dead domain? Let's take it in four parts. What makes a domain dead. How they end up on your list. How to spot one before you send. And why you can't ignore them.
01 · Brought to you by, woven in · 0:25
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
For every address on a list it cleans, Review My Emails checks whether the mail still has somewhere to land.
02 · Nowhere to land · 0:32
On screen: chip 1 lights. A door for shipwreck.invalid. A green tick for registered, a web browser frame showing a plain placeholder page. Then the mail slot in the door, bricked up, and an envelope bouncing off it, and sunk@shipwreck.invalid lifts off the list. Gloss card: dead domain · a domain with no working mail server, so mail has nowhere to land.
First, what makes a domain dead. A dead domain is one that no longer has a working mail server. The domain might still be registered. The website might even load a placeholder page. Like a shop that closed, with the sign still up. But send mail to any address there, and it has nowhere to land. No mail server is taking connections. Every address on it comes off your list.
03 · Two kinds of dead in the records · 0:57
On screen: four empty card slots in a row, the first two labelled records, then cards 1 and 2 fill, one per click. Card 1: an empty address book page, no route drawn. A small next video tag sits on it. Card 2: an arrow from the address book to an empty lot. No gloss card here: the records are taught in video 5 (PM call, taught once per playlist).
A domain can go dead in a few ways, and each one fails a little differently. Two of them live in its records. The record that tells mail where to go is gone, so nothing tells a sending server where to deliver. More on that record in the next video. Or the record IS there, but the server it points to no longer exists. Same result.
04 · Dead at the server, or expired · 1:21
On screen: cards 3 and 4 fill the last two slots, labelled server and registration. Card 3: an arrow to a real building with its lights off, and its slip goes amber 4__ then coral 5__. Card 4: a registration tag with its date crossed out, and the whole card dims.
Then there's the server itself. The record points somewhere real, but nothing answers. The server was switched off, or the company shut down. You get temporary failures at first, and in the end they turn permanent. And last, the whole domain expired. The registration lapsed, and after a while, everything goes dark.
05 · How they get on your list · 1:40
On screen: chip 2 lights. A list of green cards. One per click, a card goes dark with a small tag: folded, abandoned, stopped paying, moved domain. Then two lists side by side, the same length: signed up with a few dark cards, bought or scraped with many more. No gloss card: "business lists" is said in plain words, so there is no B2B to explain.
How do they end up on your list? Quietly. The company folded. The side project was abandoned. The owner stopped paying for the domain, or the business moved to a new one and let the old one go. Business lists rot the fastest, because small businesses fold all the time. And bought or scraped lists start out with a much higher share of dead domains than real signups.
06 · Three checks before you send · 2:04
On screen: chip 3 lights. Three steps rise left to right like stairs, each taller than the last, labelled DNS lookup, SMTP handshake, full validation. On each step, sunk@shipwreck.invalid gets stopped. Gloss card: SMTP handshake · asking the receiving server if a mailbox exists, without sending anything.
How do you spot one before you send? Three checks, cheapest first. One. A DNS lookup. Ask the domain where its mail goes. If there's nowhere to go, it's dead. Free and fast. Two. An SMTP handshake. Ask the mail server if it answers. Three. Full validation. A service does both, plus more checks of its own.
07 · The cheap way: read your bounces · 2:25
On screen: a bounce report table, two rows light up coral one per click, mono: host unknown, domain not found. A third row carries only the code, 5.1.2, lit with them, never read aloud. Gloss card (Q5, re-glossed for a viewer arriving from search, taught in Playlist 1): hard bounce · permanent, it will fail the same way every time.
Not ready to validate? Then watch your bounces. Where? In your email marketing tool's bounce report, the reason next to each hard bounce, the permanent kind. Anything that says host unknown, or domain not found... is a dead domain. The shop is shut.
08 · Why you can't ignore them · 2:40
On screen: chip 4 lights. One coral slip, mono 550 5.1.2 Host unknown, drops onto a dot grid of 50,000. First pose: a handful of dots turn coral, too few to notice. Second pose: 3,000 dots turn coral, a visible patch. Third pose: the patch's colour bleeds into a thin coral outline around the whole grid. Labelled in this example: 50,000 addresses. Gloss card: sender reputation · the score mailbox providers give you as a sender, based on how you've behaved.
Why can't you just ignore them? Every message to a dead domain is a hard bounce, sent to an address that will never work. A handful of them, on a list of fifty thousand, won't move the needle. Three thousand will. And the damage doesn't stay with the dead addresses. It hits your sender reputation, and that affects every other address on your list.
09 · Remove them, and don't look back · 3:03
On screen: the dark shop from scene 00. A calendar flips page after page while envelopes keep arriving at the dark door, each one coming back coral. Then a bounce log opens at last, long, every line the same domain.
And nobody tells you. When a company folds, or a domain lapses, nothing sends you a notice. The address just stops working. So you keep mailing it for months, sometimes years, until someone finally looks at the bounce logs. By then, every one of those sends was another hard bounce.
10 · Recap · 3:34
On screen: the four kinds-of-dead cards small, the dark cards list, the three steps, the closed pot, the four chips lit.
Pulling it together. Know the sign of a dead domain, nowhere for mail to land. Expect them to pile up quietly, fastest on business lists, and nobody will warn you. Check before you send, with a DNS lookup, a handshake, or full validation. And when you find one, remove it on sight.
11 · Close · 3:53
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 5, no subscribe ask.
Don't wait for the logs. A clean finds the dead domains before you send, and puts those addresses in suppress. A dead domain stays dead. The clean makes sure you stop mailing it. Or run the same check at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a domain with missing MX records?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.008.001-what-is-a-dead-domain.md
00 · The address that stopped working (hook)
What is a dead domain?
the title, Lora, large: "What is a dead domain?" sunk@shipwreck.invalid on a card in front of a lit shop sign. The address never moves. The sign behind it goes dark, and the card turns coral. Envelopes keep arriving at the dark door. Four numbered chips, the VO's words: 1 what makes a domain dead · 2 how they end up on your list · 3 how to spot one before you send · 4 why you can't ignore them. Chips 2 to 4 stay grey until their scenes.
the envelopes keep coming while the door stays dark, a count that only grows. Reveals: (1) the card and the lit sign, (2) the sign goes dark, the card turns coral, (3) the envelopes pile up, (4) the four chips.
one door from the doors street (M-14) with the envelope row (M-15) arriving at it. The registry's dead-domain picture (M-13) is a parcel handed to a person at a desk, so it waits for the cast (T11), and the parcel is not V001's letter (Q9).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Nowhere to land
Nowhere to land
chip 1 lights. A door for shipwreck.invalid. A green tick for registered, a web browser frame showing a plain placeholder page. Then the mail slot in the door, bricked up, and an envelope bouncing off it, and sunk@shipwreck.invalid lifts off the list. Gloss card: dead domain · a domain with no working mail server, so mail has nowhere to land.
two things look alive (registered, a web page) and the one that matters for mail does not. Reveals: (1) the registered tick, (2) the placeholder page, (3) the bricked slot and the bounce, (4) the address lifts off the list.
the answer (no working mail server) and the first action (it comes off your list) both land here, by about 1:00.
one door from the doors street (M-14), the envelope (M-12). The page frame and the bricked slot: no picture yet. The word "parked" is not said (see the review pass, row 3).
03 · Two kinds of dead in the records
Dead in the records
four empty card slots in a row, the first two labelled records, then cards 1 and 2 fill, one per click. Card 1: an empty address book page, no route drawn. A small next video tag sits on it. Card 2: an arrow from the address book to an empty lot. No gloss card here: the records are taught in video 5 (PM call, taught once per playlist).
a count of four slots, two filled. Reveals: (1) the four slots, (2) card 1, (3) card 2.
concept dns (M-20 the case files, as in bounce video 5). No record name is said or shown.
Q1 and the QA panel: the hook already counts four things, so this scene says "a few ways", the Almanac's own words ("a few flavors of dead"), instead of a second "four". RME-182.1: the old "two places, records or server" split filed an expired domain under the server, which the Almanac never does, so it is gone.
04 · Dead at the server, or expired
Switched off, or expired
cards 3 and 4 fill the last two slots, labelled server and registration. Card 3: an arrow to a real building with its lights off, and its slip goes amber 4__ then coral 5__. Card 4: a registration tag with its date crossed out, and the whole card dims.
the four slots, now all filled. On card 3 the slip changing colour, amber to coral, is the temporary turning permanent. Reveals: (1) card 3, (2) its slip turns coral, (3) card 4.
concept soft-bounce and hard-bounce colours on the slip (M-15, M-14).
no retry window length (bounce playlist C6). No word on squatters or traps.
05 · How they get on your list
They pile up quietly
chip 2 lights. A list of green cards. One per click, a card goes dark with a small tag: folded, abandoned, stopped paying, moved domain. Then two lists side by side, the same length: signed up with a few dark cards, bought or scraped with many more. No gloss card: "business lists" is said in plain words, so there is no B2B to explain.
the count of dark cards. The bought list has visibly more dark cards than the signed-up list. No share is claimed, the two counts are illustrative. Reveals: (1) to (4) one tag per click, (5) the two lists side by side.
concept list-decay (M-25, M-22).
06 · Three checks before you send
Spot it before you send
chip 3 lights. Three steps rise left to right like stairs, each taller than the last, labelled DNS lookup, SMTP handshake, full validation. On each step, sunk@shipwreck.invalid gets stopped. Gloss card: SMTP handshake · asking the receiving server if a mailbox exists, without sending anything.
step height is the cost, cheapest to most expensive, in the Almanac's order. No prices. Reveals: (1) to (3) one step per click.
concept email-validation (M-12, M-24) on step 3. smtp-handshake is gloss tier, the probe card at a door proposed in video 3.
07 · The cheap way: read your bounces
Or read your bounces
a bounce report table, two rows light up coral one per click, mono: host unknown, domain not found. A third row carries only the code, 5.1.2, lit with them, never read aloud. Gloss card (Q5, re-glossed for a viewer arriving from search, taught in Playlist 1): hard bounce · permanent, it will fail the same way every time.
a count of two spoken labels and one code on screen. Reveals: (1) host unknown, (2) domain not found with its 5.1.2 row.
concept bounce (M-15, M-18).
"email marketing tool", never "ESP".
08 · Why you can't ignore them
A handful, or thousands
chip 4 lights. One coral slip, mono 550 5.1.2 Host unknown, drops onto a dot grid of 50,000. First pose: a handful of dots turn coral, too few to notice. Second pose: 3,000 dots turn coral, a visible patch. Third pose: the patch's colour bleeds into a thin coral outline around the whole grid. Labelled in this example: 50,000 addresses. Gloss card: sender reputation · the score mailbox providers give you as a sender, based on how you've behaved.
dots, drawn to scale. A handful against 3,000 out of 50,000 is the Almanac's own comparison. The outline around the whole grid is "every other address on your list". Reveals: (1) the handful, (2) the 3,000, (3) the outline.
concept sender-reputation (M-33). The slip is hard-bounce (M-15, M-14), a callback, not re-taught.
no bounce rate percentage is voiced or shown (C16). No provider named, no day of the week.
09 · Remove them, and don't look back
Almanac ids in this scene: 005.008.001
Nobody tells you
the dark shop from scene 00. A calendar flips page after page while envelopes keep arriving at the dark door, each one coming back coral. Then a bounce log opens at last, long, every line the same domain.
sends piling up over time, then one long log. Reveals: (1) the calendar flips, (2) the envelopes keep coming back, (3) the log opens.
callback to scene 00's dark shop. The calendar: no picture yet.
QA panel: this is the video's real surprise, so it is the twist (T3), said in its own words (Q1), before the recap (Q3). Scene 02's "still registered" stays as a plain fact.
005.008.001 "None of that triggers a notification to you. The address just stops working, and you keep mailing it for months or years until you look at your bounce logs." / "Every message you send to a dead domain is a hard bounce."
T6, the pivot before the pitch (R15 shape).
10 · Recap
What to do
the four kinds-of-dead cards small, the dark cards list, the three steps, the closed pot, the four chips lit.
four cards, three steps, one closed pot.
callbacks only.
11 · Close
Clean your list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: video 5, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is only about addresses. Nothing implies it repairs sender reputation. Totals: 13 scenes. 713 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 4:18 at 166 words a minute, about 4:35 with scene breaks. Every scene is 20 to 70 words (S2). Under 5 minutes, so no "Short cut:" note (Q10).
V010What is a domain with missing MX records?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C1 Settled by R4: scene 04 says it depends on the receiving side, all three outcomes. Almanac addition candidate: "some that should bounce do not bounce at all".
- "No picture yet" visuals: the empty MX slot, the four cause cards, the three gates.
- End screen, settled by the Video PM 2026-09-29: points to V011, "What's a synchronous vs asynchronous bounce?" (015.001.014, Bounces, part 2).
- GAP-D, wording in 005.008.005: "if your validation is showing a lot of missing-MX failures, check the domain existence step" reads the wrong way round.
- R4 wording (RME-182.1): the VO says "it depends on the receiving side", as R4 does.
00 · Looks fine, isn't (hook) · 0:00
On screen: the title, Lora, large: "What is a domain with missing MX records?" no.such.fish@empty.sea.invalid on a card. Two green ticks light beside it: well formed · website loads. Then a third slot, empty, with a dashed outline: MX. Three numbered chips, the VO's words: 1 what's missing · 2 the four ways it happens · 3 what to do with those addresses. Chips 2 and 3 stay grey until their scenes.
A lead fills in Sally Send's contact form. The address looks perfect. Their website loads. But their domain is missing the one record that tells mail where to go. What is a domain with missing MX records, then? One with no route for email. Suppress every address on it. Three parts to this. What's missing. The four ways it happens. And what to do with those addresses.
01 · Brought to you by, woven in · 0:24
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Before a single send, Review My Emails asks each address's domain whether it's set up to take email at all.
02 · What an MX record does · 0:31
On screen: chip 1 lights. The case files. One opens for tidewell-supply.example and shows one line in mono, MX 10 mail.tidewell-supply.example, and an arrow runs from a sending desk to that server. Then the file for empty.sea.invalid opens, and the MX line is blank. The arrow starts, and has nowhere to point. Gloss card, the same line as bounce video 5: MX record · the entry that says which server takes mail for a domain.
First, what's missing. The MX record, the domain's address label. It's the entry that tells other mail servers where to deliver email for a domain. No MX record, and there's no routing information for email. An envelope with no address label has nowhere to go, however nice the envelope looks.
03 · A website is not an inbox · 0:49
On screen: the empty.sea.invalid file again. An A line lights green and a small web page frame loads beside it. The MX line stays blank. Gloss card, the same line as bounce video 5 (P5): A record · the entry that turns a name into the numeric address a server connects to.
The website can work perfectly while email has no route at all. How? A website uses a different record, an A record, which points at the web server. Two records, two jobs. One for the web, one for mail. So a domain can load a perfectly good website, and still have no MX record at all.
04 · So does it always bounce? · 1:09
On screen: the arrow with no target from scene 02 splits three ways. Path 1: it turns back and a coral slip lands, mono 550 Host not found. Path 2: it bends to the A line's web page frame, which has no mail slot. Path 3: it fades out with no slip at all.
What happens when you send? It depends on the receiving side. Many bounce it straight away, as a permanent failure, with a message like host not found. Some servers fall back to the website's address instead, and a web server rarely takes mail. And some that should bounce, don't bounce at all.
05 · Two ways it starts on their side · 1:28
On screen: chip 2 lights. A row of four empty card slots, then cards 1 and 2 fill, one per click. Card 1: a web page frame with no mail slot. Card 2: a registration tag, crossed out then re-stamped, the MX line flickering off and staying off.
Why would a domain be missing MX records? There are four ways it happens. One. It was only ever registered for a website. Someone set up a site, and never set up email. Two. The domain expired, and then got renewed. In the gap, the records can go out of step, and the MX record doesn't always come back properly.
06 · Two more, a move and a typo · 1:49
On screen: cards 3 and 4 fill the last two slots. Card 3: two servers, the old one's MX line removed before the new one's is drawn, a blank moment between them. Card 4: wren@mailbx.invalid, with the missing letter highlighted.
Three. The company moved to a new email provider, and removed the old MX record before adding the new one. And four. A typo at signup. A mistyped domain often points to a domain that doesn't exist at all.
07 · What to do with those addresses · 2:03
On screen: chip 3 lights. The no.such.fish@empty.sea.invalid card drops into the suppress pot, and the lid closes. Gloss card: suppress · stop sending to an address, and keep it from being added back.
Which leaves the addresses themselves. From a list hygiene point of view, it's simple. Any address at a domain with missing MX records should be suppressed. Suppress it, and move on.
08 · Where it should be caught · 2:15
On screen: a contact form card and a business card, each with a neat address in mono on a reserved .invalid domain from the library (no.such.fish@empty.sea.invalid, lost.at.sea@nowhere.invalid). Both look right. Then each one is checked against the case files from scene 02, and neither file has an MX line.
Reading the list won't catch them, either. These addresses look fine. They sit on contact forms and business cards, perfectly well formed, and the website behind them may even load. None of that tells you whether the domain takes email. The only way to know is to ask the domain itself.
09 · Recap · 2:57
On screen: the blank MX line, the four cause cards small, the closed pot, the three chips lit.
Here's what to do. Don't take a working website as proof of email. Watch for the four ways it happens, from a web only domain to a typo. Suppress every address at a domain with no MX record. And catch them at the domain check, before they ever reach your list.
10 · Close · 3:15
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next video, V011 (Bounces, part 2), no subscribe ask.
Every clean asks each domain before you send. It won't add anyone's missing records. Instead, it flags every address to suppress. Need help with one today? Our SOS hotline is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what's a synchronous versus asynchronous bounce?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.008.005-domain-missing-mx-records.md
00 · Looks fine, isn't (hook)
Almanac ids in this scene: 005.008.005
Missing MX records
the title, Lora, large: "What is a domain with missing MX records?" no.such.fish@empty.sea.invalid on a card. Two green ticks light beside it: well formed · website loads. Then a third slot, empty, with a dashed outline: MX. Three numbered chips, the VO's words: 1 what's missing · 2 the four ways it happens · 3 what to do with those addresses. Chips 2 and 3 stay grey until their scenes.
two ticks lit, the third slot empty. The empty slot is the whole video. Reveals: (1) the card, (2) the two ticks, (3) the empty MX slot, (4) the three chips.
concept dns (M-20, the case files).
hook in a scene the viewer is in (a contact form lead, backed by 005.008.005 "These addresses might appear on contact forms or business cards"). It promises nothing a GAP holds.
the answer (no route for email, 005.008.005 "Without MX records, there's no routing information") and the action (suppress, 005.008.005 "any address at a missing-MX domain should be suppressed") now land in the hook, by about 0:20. Before, the action waited until 2:05. Scene 07 still gives the why.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What an MX record does
The routing entry
chip 1 lights. The case files. One opens for tidewell-supply.example and shows one line in mono, MX 10 mail.tidewell-supply.example, and an arrow runs from a sending desk to that server. Then the file for empty.sea.invalid opens, and the MX line is blank. The arrow starts, and has nowhere to point. Gloss card, the same line as bounce video 5: MX record · the entry that says which server takes mail for a domain.
one file with a line and an arrow, one file with no line and no target. Reveals: (1) the working file and its arrow, (2) the blank file, (3) the arrow with no target.
concept dns (M-20), as in bounce video 5. mx-record is gloss tier, no picture yet.
video 4 named no record and pointed forward to this scene, so the MX record (here) and the A record (scene 03) are taught once, in this video. The MX line is the same line and picture as bounce video 5, so it is also a callback to playlist 1. The DNS gloss card is dropped here, it was glossed there.
stops at "no routing information". What happens next is scene 04.
03 · A website is not an inbox
Web and email are separate
the empty.sea.invalid file again. An A line lights green and a small web page frame loads beside it. The MX line stays blank. Gloss card, the same line as bounce video 5 (P5): A record · the entry that turns a name into the numeric address a server connects to.
two lines in one file, one filled and one blank. Reveals: (1) the A line and the web page, (2) the blank MX line held.
concept dns (M-20). A record has no registry row.
says nothing yet about whether mail can use the A record. Scene 04 does (R4).
04 · So does it always bounce?
Almanac ids in this scene: 005.008.005, 017.002.005, 017.002.010
Does it always bounce?
the arrow with no target from scene 02 splits three ways. Path 1: it turns back and a coral slip lands, mono 550 Host not found. Path 2: it bends to the A line's web page frame, which has no mail slot. Path 3: it fades out with no slip at all.
three paths from one arrow, drawn the same weight, no share on any. Reveals: (1) the bounce, (2) the A record path, (3) the silent path.
concept dns (M-20), the arrow from scene 02, the A line from scene 03.
R4 (YT, 2026-09-29): C1, all three are true, voiced as "it depends on the receiving side". The GAP is closed. "Some do not bounce at all" is YT's own addition, listed as an Almanac addition candidate. The review pass found 017.002.010 already says it in part ("fail silently for some senders"), so YT may not need a new entry. One wording flag for YT: R4 says "the receiving side", while 017.002.010 and 017.002.005 say the A record fallback is a choice some sending servers make. The VO keeps R4's words (her ruling) and "some servers" stays neutral.
005.008.005 "This produces an immediate hard bounce the first time you try to send: typically a 550 or similar permanent failure response with a message like 'No such domain' or 'Host not found.'" / 017.002.010 "A record routing is a legacy fallback some senders use when no MX exists, delivering to the domain's web server IP instead... the target host rarely runs SMTP on port 25." / "some that should bounce don't": YT, R4, and 017.002.010 "If your MX record is missing or broken, inbound mail will fail, and it'll fail silently for some senders while others send a bounce."
05 · Two ways it starts on their side
Four ways it happens
chip 2 lights. A row of four empty card slots, then cards 1 and 2 fill, one per click. Card 1: a web page frame with no mail slot. Card 2: a registration tag, crossed out then re-stamped, the MX line flickering off and staying off.
a count of four slots, two filled. Reveals: (1) the four empty slots, (2) card 1, (3) card 2.
no registry row for the four causes. Proposed: these cause cards.
06 · Two more, a move and a typo
Four ways it happens
cards 3 and 4 fill the last two slots. Card 3: two servers, the old one's MX line removed before the new one's is drawn, a blank moment between them. Card 4: wren@mailbx.invalid, with the missing letter highlighted.
the four slots, now all filled. On card 3, the blank moment between the old line going and the new one arriving is the cause, drawn as a gap in time. Reveals: (1) card 3, (2) the blank moment, (3) card 4.
card 4 reuses the typo domain address from the demo names library.
07 · What to do with those addresses
Suppress it
chip 3 lights. The no.such.fish@empty.sea.invalid card drops into the suppress pot, and the lid closes. Gloss card: suppress · stop sending to an address, and keep it from being added back.
one card, one pot, the lid closed. Reveals: (1) the card into the pot, (2) the lid closes.
concept suppression-list (M-23, M-24).
"a definitive failure, not a temporary or inconclusive one" is not voiced. It leans on C1 side A. Only "suppress it" is said, which both sides support.
08 · Where it should be caught
Almanac ids in this scene: 005.003.013, 005.008.005
You can't see it by looking
a contact form card and a business card, each with a neat address in mono on a reserved .invalid domain from the library (no.such.fish@empty.sea.invalid, lost.at.sea@nowhere.invalid). Both look right. Then each one is checked against the case files from scene 02, and neither file has an MX line.
two good-looking addresses, zero MX lines found. Reveals: (1) the two cards, (2) the lookup, (3) no MX line for either.
concept dns (M-20).
Q3: moved before the recap. Q2: a list topic, the pivot is this topic's own blind spot, no catch- all.
005.008.005 "It doesn't matter how well-formed the address looks or whether the domain resolves for web traffic." / "These addresses might appear on contact forms or business cards" (the rest of that sentence, "they can never receive email", is C1 side A and is not voiced). The typo line that was here repeated scene 06 word for word and was cut in the RME-182.1 review pass. "Ask the domain itself" is the DNS check, 005.003.013 "checks whether the domain after the @ actually exists in DNS and is configured to receive mail".
T6, the pivot before the pitch (R15 shape).
09 · Recap
What to do
the blank MX line, the four cause cards small, the closed pot, the three chips lit.
four cards, one closed pot.
callbacks only.
10 · Close
Almanac ids in this scene: 015.001.014
Clean your list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next video, V011 (Bounces, part 2), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is only about addresses. "It won't add anyone's missing records" says what it does not do (it was "won't fix anyone's DNS", but "DNS" is never glossed in this video, Q5). S8: the playlist's last video now names the next one, 015.001.014, by its Almanac question ("vs" said as "versus"), inside the bounces playlists the PM picked for this end screen. No more "end of this playlist". Totals: 12 scenes. 597 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 3:35 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2). Under 5 minutes and over 2, so no "Short cut:" note is needed (Q10, R12).
V011What's a "synchronous" vs "asynchronous" bounce?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Overlap, settled by the Video PM 2026-09-29: kept as a video, rebuilt around the new part.
- "No picture yet": the send report row, the three-link chain, the question card.
00 · Delivered, and failing (hook) · 0:00
On screen: the title, Lora, large: "What's a synchronous vs asynchronous bounce?" A send report, one row held still: marina@tidewell-supply.example · delivered in green. Behind the report, faint, the same envelope coming back, again and again, and never reaching the row. Two numbered chips, the VO's words: 1 the three jobs your email marketing tool has to do · 2 the one question to ask it. Chip 2 grey.
Sally Send's report says delivered. But some of those addresses fail every single send, and the report never shows it. What's a synchronous versus an asynchronous bounce? One is a no on the spot. The other is a yes first, and the failure notice comes later, if at all. Two things matter. The three jobs your email marketing tool has to do. And the one question to ask it.
01 · Brought to you by, woven in · 0:26
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some addresses fail quietly on every single send, and Review My Emails finds them before you send to them again.
02 · The two, in pictures · 0:34
On screen: a send report row, delivered, with a green tick. Zoom in on the tick: it is a signature on a courier's slip, not a letterbox. Behind it, the parcel sits in a back room, never placed in any box. The same row repeats down the page, send after send, green every time.
Delivered, on your report, only means the receiving server signed for it. It doesn't mean the message reached a mailbox. The server can figure out later that it can't put it anywhere. So an address can look fine on every report, and still be failing, silently, every single send.
03 · The three jobs, and the question · 1:14
On screen: one envelope passes through the gate that lets every envelope through without looking, and the gate swings shut behind it. Hold. Nothing comes back out. No slip, no notice. Then the checking lamp finds the same address and tags it amber, catch-all. Gloss card, the registry line: catch-all · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos.
And some addresses never send a notice at all. A server that takes every address, real or made up, can quietly drop the mail. No bounce fires. Your report still says delivered, and your tool has nothing to catch.
04 · Recap · 2:12
On screen: the green row, the three-link chain, the question card, both chips lit.
Three things to do. Don't read delivered as reached the mailbox. Compare your tool's bounce numbers with what you'd expect. And ask how it handles the notices that come back to your Return-Path. If any of the three jobs is missing, bad addresses are staying on your list.
05 · Close · 2:30
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 2, no subscribe ask.
Don't assume your list is cleaner than it is. Check it. At Review My Emails we find the addresses that are quietly failing, before you send. It won't fix your tool's bounce handling, that part is your tool's job. The check is called RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a block bounce?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.001.014-synchronous-vs-asynchronous-bounce.md
00 · Delivered, and failing (hook)
Synchronous vs asynchronous
the title, Lora, large: "What's a synchronous vs asynchronous bounce?" A send report, one row held still: marina@tidewell-supply.example · delivered in green. Behind the report, faint, the same envelope coming back, again and again, and never reaching the row. Two numbered chips, the VO's words: 1 the three jobs your email marketing tool has to do · 2 the one question to ask it. Chip 2 grey.
one green word on the report, a count of returning envelopes behind it that keeps growing. Reveals: (1) the row, (2) the returning envelopes, (3) the chips.
concept bounce (M-15, M-18), the envelope handed back.
H5, the chips are the new part only. There is no chip for the two kinds, they are a callback (S6, PM call 2026-09-29).
the answer (a no on the spot, or a yes first and a notice later, if at all) now lands in the hook, by about 0:15. "Which is the whole point of the question" was cut, it joined nothing to nothing (T12).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 20 words, brand said here and in the close only.
02 · The two, in pictures
Almanac ids in this scene: 015.001.014
What delivered means
a send report row, delivered, with a green tick. Zoom in on the tick: it is a signature on a courier's slip, not a letterbox. Behind it, the parcel sits in a back room, never placed in any box. The same row repeats down the page, send after send, green every time.
one green tick, repeated, with nothing behind it. Reveals: (1) the report row, (2) the zoom to the signature, (3) the parcel in the back room, (4) the ticks repeat.
no picture yet for the signature slip. Proposed: the courier's slip, reused from the rejected versus bounced video.
Q5: "You met these two in the rejected versus bounced video" is gone. Both words are said in one plain line each, for a viewer who arrives from search, with the conversation picture replayed. "sometimes" is the answer's "can get lost", not a frequency (V12). Takes no side on C11 (the question's own words).
015.001.014 "The receiving server accepts your message with a 250 OK during the SMTP session, so your ESP logs it as 'delivered.' But then, sometime later, the receiving system figures out it can't actually put it in a mailbox." / "you can have addresses sitting on your list that look fine but are silently failing every single send."
T3, the one twist, and T9.
03 · The three jobs, and the question
Almanac ids in this scene: 005.003.010, 005.008.002, 005.013.008, 015.001.014
The one you never see
one envelope passes through the gate that lets every envelope through without looking, and the gate swings shut behind it. Hold. Nothing comes back out. No slip, no notice. Then the checking lamp finds the same address and tags it amber, catch-all. Gloss card, the registry line: catch-all · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos.
the count of returned slips is zero. The empty space where a slip should land is the picture. Reveals: (1) the envelope goes in, (2) nothing returns, (3) the lamp tags it.
concept catch-all (M-18, M-15, the registry's gate that lets every envelope through) and the checking lamp from playlist 1 video 4 (08c). The door was swapped for the registry's gate in the RME-182.1 review pass (P5).
"ask", never accuse the tool (V8). The answer's "before assuming your list is cleaner than it is" sits in the close.
005.003.010 "Catch-all servers usually do not bounce. They accept and then silently drop." / 005.008.002 "Every address on the domain accepts mail at the SMTP layer, then the message is dropped" / 005.013.008 "a real validator will identify these domains and flag them accordingly."
T2 (where to look) and T5 (the action). Scene 03 split so each stays under 70 words (S2).
R15 (YT, 2026-09-29): pivot before the pitch, backed by the catch-all and accept-all answers only. "Some servers" and "quietly drop" keep to the Almanac's own "usually do not bounce" (C17 and C18 are not voiced: no count, and no claim that catch-alls never bounce).
moved before the recap as 03c (Q3) and reworded to grow out of this video's own "delivered" idea, so it shares no line with the other pivots (Q1, Q2). This video owns the catch-all picture in Bounces part 2. V014 05b calls it back in one beat (corrected in the RME-182.1 review pass, it used to say "the only catch-all pivot").
04 · Recap
The recap
the green row, the three-link chain, the question card, both chips lit.
callbacks only.
callbacks only (S5).
05 · Close
Check the list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 2, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not fix (S10). Totals: 9 scenes. 460 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 2:46 at 166 words a minute, plus scene breaks, so about 2:55 on the clock. Every scene is 20 to 70 words (S2). Short cut (R12): removed in the taste pass. The video now runs past 2:00, so no Short cut is made from it.
V012What is a block bounce?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C25 (ledger): content with a good reputation, 015.005.001 against 021.001.001.
- C26 (ledger): does a 5.7.1 policy rejection mean the sender (015.005.001, 015.005.004) or the recipient organization's rule (011.009.012)?
- "No picture yet": the door with reason cards, the block slip, the row of doors.
00 · Real address, working server, no delivery (hook) · 0:00
On screen: the title, Lora, large: "What is a block bounce?" marina@tidewell-supply.example behind a door, green, address real. The server light on, green, server running. Sally's envelope comes back anyway, with a coral slip, mono Message rejected, no code on it (C26). Three numbered chips, the VO's words: 1 what a block bounce is · 2 the four usual reasons · 3 what to do. Chips 2 and 3 grey.
Sally Send's email bounced. The address is real. The server is running. And her message still didn't get through. What is a block bounce? It's a no aimed at you, the sender, not at the address. Let's take it in three. What a block bounce is. The four usual reasons. And what to do.
01 · Brought to you by, woven in · 0:21
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A dead address and a blocked sender look alike in a bounce log, so Review My Emails sorts out the addresses first.
02 · It's about you · 0:29
On screen: chip 1 lights. Three slips side by side, the callback from playlist 1: hard · address gone, soft · a hiccup, and a third, new, block · about you. The third one turns to face Sally. Gloss card, the registry line: block bounce · a bounce where the server refused the message on reputation grounds rather than because the address is bad. Then a card pins to the door, not you.
Start with what it is. The receiving server refuses your message on purpose. Not because the address is gone. That's a hard bounce. And not because of a hiccup on their side. That's a soft bounce. A block bounce is about YOU. Like a note on the door with your name on it. Whoever you came to see, the door stays shut for you.
03 · Reasons one and two · 0:54
On screen: chip 2 lights. A reason card flips up on the door, one per click: your IP is on a blocklist (the registry's book held open at the door, one line lit), then your domain's reputation (a reputation gauge low). The address behind the door stays green. One gloss card (Q6), the registry line: blocklist · a published list of sending IPs or domains flagged for spam, which receiving servers check before accepting mail. Reputation is said in plain words, the gauge carries it.
Why would they block you? Four usual reasons. One. Your sending IP is on a blocklist, and the receiving server checks that list before it lets anyone in. Two. Your domain has a poor reputation as a sender. Mailbox providers track how people treat your mail over time, and high complaints and low engagement drag it down.
04 · Reasons three and four · 1:15
On screen: the door's card changes twice more: your content (one hypey subject line sitting beside two weak-signal marks, no callback to another video, Q5), then your authentication (three small record cards, one cracked). The address stays green. No gloss card (Q6): the VO says what the three records do, and the acronyms sit on the three small cards.
Three. Your content. Hypey copy on top of weak signals, like low engagement or missing authentication, can tip the balance. And four. The records that prove your mail is yours, SPF, DKIM or DMARC, aren't set up right, and some servers reject it outright.
05 · Suppressing won't fix it · 1:32
On screen: chip 3 lights. Marina's green address drops into the suppress pot, and a second envelope, to a different address at the same server, comes back with the same coral slip. The pot lid lifts, and the address comes back out. A wrench icon appears on Sally's side.
The thing everyone reaches for first, suppressing the address, fixes nothing. The address was fine. The same block will hit every message you send to that server, whoever it's for. But block bounces aren't always permanent either. They often come from a problem you can fix, and then the note comes off the door.
06 · Investigate, and look for the pattern · 1:53
On screen: the door from scene 02, with two reason cards pinned to it: reputation and content. One card is torn off, the door stays shut. The second is torn off, and the door opens.
And keep going after the first answer. The reasons can stack. A reputation problem AND a content problem, and both need fixing before the door opens for you. Fix only one, and the door can stay shut.
07 · Recap · 2:31
On screen: the door with its four cards, the pot lid lifting, the row of doors, the chips lit.
When you see one, then. Don't suppress the address. Read the words on the Diagnostic Code line. Run the free blocklist checker, and check your SPF, DKIM and DMARC. Then look at your reputation and your content. And if blocks show up everywhere, look at your whole sending setup.
08 · Close · 2:49
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, no subscribe ask.
Fix what the block is about, and keep the addresses honest. Review My Emails checks the addresses, so you know which ones are dead. A clean won't lift a block. Worried about a blocklist? Start with our free blocklist checker. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what does blocked by policy mean in bounce codes?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.005.001-what-is-a-block-bounce.md
00 · Real address, working server, no delivery (hook)
Block bounces
the title, Lora, large: "What is a block bounce?" marina@tidewell-supply.example behind a door, green, address real. The server light on, green, server running. Sally's envelope comes back anyway, with a coral slip, mono Message rejected, no code on it (C26). Three numbered chips, the VO's words: 1 what a block bounce is · 2 the four usual reasons · 3 what to do. Chips 2 and 3 grey.
two green lights, one coral slip. Reveals: (1) the green address, (2) the green server, (3) the envelope comes back, (4) the chips.
concept bounce (M-15, M-18). block-bounce is gloss tier, no picture yet. Proposed: the door with its card.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 22 words, brand said here and in the close only.
02 · It's about you
What a block bounce is
chip 1 lights. Three slips side by side, the callback from playlist 1: hard · address gone, soft · a hiccup, and a third, new, block · about you. The third one turns to face Sally. Gloss card, the registry line: block bounce · a bounce where the server refused the message on reputation grounds rather than because the address is bad. Then a card pins to the door, not you.
three slips, and the arrow on the third points back at the sender, the other two point at the recipient. Reveals: (1) hard and soft, called back, (2) the block slip, (3) its arrow turns to Sally.
playlist 1's slips (M-15, M-14). The block slip: no picture yet.
03 · Reasons one and two
The four usual reasons
chip 2 lights. A reason card flips up on the door, one per click: your IP is on a blocklist (the registry's book held open at the door, one line lit), then your domain's reputation (a reputation gauge low). The address behind the door stays green. One gloss card (Q6), the registry line: blocklist · a published list of sending IPs or domains flagged for spam, which receiving servers check before accepting mail. Reputation is said in plain words, the gauge carries it.
a count of reasons, two of four. The address stays green, the reason card changes. Reveals: (1) the four empty slots, (2) reason 1, (3) reason 2.
concept blocklist (M-18, M-20), concept sender-reputation (M-33).
04 · Reasons three and four
The four usual reasons
the door's card changes twice more: your content (one hypey subject line sitting beside two weak-signal marks, no callback to another video, Q5), then your authentication (three small record cards, one cracked). The address stays green. No gloss card (Q6): the VO says what the three records do, and the acronyms sit on the three small cards.
four of four reasons, one picture held still. Reveals: (1) reason 3, (2) reason 4.
concept spam-filter (M-18, M-37), the registry's picture, not a callback (P5, Q5), concepts spf, dkim, dmarc.
reason three is said the way the myth short says it (PM call 2026-09-29, C25). The answer's "even if your reputation is otherwise fine" is not voiced, and neither is "words alone never do it". Only the line both sides support is said: on top of weak signals, content can tip the balance (G3).
05 · Suppressing won't fix it
What to do
chip 3 lights. Marina's green address drops into the suppress pot, and a second envelope, to a different address at the same server, comes back with the same coral slip. The pot lid lifts, and the address comes back out. A wrench icon appears on Sally's side.
two different addresses, one identical slip. The count of slips does not fall when you suppress. Reveals: (1) into the pot, (2) the second slip, same text, (3) out of the pot, (4) the wrench.
concept suppression-list (M-23, M-24).
06 · Investigate, and look for the pattern
Almanac ids in this scene: 015.005.001
Investigate, and look for the pattern
the door from scene 02, with two reason cards pinned to it: reputation and content. One card is torn off, the door stays shut. The second is torn off, and the door opens.
two reasons, both removed before the door opens. Reveals: (1) the two cards, (2) one removed, door shut, (3) both removed, door open.
the door with its reason cards, the same object as scenes 02 to 06 (P2). No person is drawn (T11).
015.005.001 "The causes of block bounces can stack on top of each other too. You might have a reputation issue AND a content issue, and both need to be addressed before delivery improves."
T9, one more sentence of how. Scene 06 split so each stays under 70 words (S2).
07 · Recap
Three things to remember
the door with its four cards, the pot lid lifting, the row of doors, the chips lit.
callbacks only.
callbacks only.
08 · Close
Fix the sender, clean the list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/blacklist-checker, the free blocklist checker, named in the VO above (Q11: one name for one tool, the same as scene 06).
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not fix (a block). Nothing implies cleaning fixes reputation, a blocklist or authentication. Totals: 10 scenes. 510 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 3:04 at 166 words a minute, plus scene breaks, so about 3:14 on the clock (scene times re-timed from the counts). Every scene is 20 to 70 words (S2).
V013What does "blocked by policy" mean in bounce codes?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C26: , shared with video 2: what a 5.7.1 policy rejection points at.
- "No picture yet": the house rules book on its stand.
00 · One company says no (hook) · 0:00
On screen: the title, Lora, large: "What does "blocked by policy" mean in bounce codes?" Sally's envelope to finn@saltmarsh-outfitters.example comes back with a coral slip, mono 550 5.7.1 Message rejected by organization policy. Four numbered chips, the VO's words: 1 whose policy it is · 2 what usually trips it · 3 how to tell it from spam filtering · 4 what to do. Chips 2 to 4 grey.
Sally Send sends a proposal to a buyer at a company she'd love to work with. It bounces. Two words in the reply. Blocked by policy. What does blocked by policy mean in bounce codes? Their company wrote a rule, and her message broke it. Four parts to it. Whose policy it is. What usually trips it. How to tell it from spam filtering. And what to do.
01 · Brought to you by, woven in · 0:26
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some bounces are about the address and some aren't, and Review My Emails settles the address side before you send.
02 · Whose policy it is · 0:34
On screen: chip 1 lights. Saltmarsh Outfitters' door, with a thick house rules book on a stand beside it, labelled their rules. Sally's envelope stops at the door. A small spam filter icon beside the door stays grey, not involved. Gloss card: policy · a rule the receiving company set for what mail it accepts.
Whose policy is it? Theirs. The receiving company wrote the rule, not a filter. Think of their building's house rules. No parcels for the payroll office. No unknown couriers. It's not a spam filter judging your content. It's their IT team saying, we don't accept mail like this, from senders like you, to mailboxes like that.
03 · The code family · 0:55
On screen: playlist 1 video 2's 5.1.1 slip, small, called back. Beside it, a new slip 5.7.1, its second digit lit coral, labelled security and policy. The first 5 on both glows.
Look at the longer code in the reply. Here it usually starts five point seven, the family for security and policy refusals. And the five at the front still means permanent.
04 · What usually trips it, part one · 1:07
On screen: chip 2 lights. The house rules book by the door turns one page per trip, each page headed with its name: blocked attachment (a paperclip, .zip crossed out), internal-only address (payroll@saltmarsh-outfitters.example, staff only), approved senders only (a short list, Sally's name missing).
What usually trips it? One. An attachment type they block, like a program file or a zip with a password. Two. Mail from outside to an internal-only address, like payroll. Three. You're not on their approved sender list.
05 · What usually trips it, part two · 1:22
On screen: the same rulebook turns three more pages, each headed with its name: DMARC reject (the record card, reject lit, a failed check), encryption required (a lock), keyword rule (one word highlighted). On page 4, a small tag your rule (T3). Gloss card, the registry line: DMARC · a policy on top of SPF and DKIM saying what a receiving server should do when a message fails, and where to send reports.
Four. Your DMARC says reject, and your mail failed it. That rule is your own, not theirs, but it lands under the same code. Five. They only take mail sent encrypted. And six, less common, a keyword or content rule, especially in regulated industries.
06 · Policy or spam filter? · 1:39
On screen: chip 3 lights. Two slips side by side, both starting 5.7.1. Left, the word organization lights in the text. Right, the word spam lights. The shared 5.7.1 greys out, the words stay lit.
How do you tell it from spam filtering? Read the words. Where? On the Diagnostic Code line of the bounce, after the code. A policy bounce talks about the ORGANIZATION. A spam filter bounce talks about the message. It usually says spam, or high probability of spam, or it links to a blocklist. The same code can turn up on both, so the words decide.
07 · What to do · 2:03
On screen: the house rules book from scene 02. The .zip card on Sally's envelope is swapped for a small link card, and the envelope goes through. A second envelope keeps knocking at the same rule, and a small gauge beside it drops one notch per knock.
And change what tripped the rule. If it was a zip file, send a link to a shared folder instead. If it was DMARC, fix your alignment before you send again. What you don't do is keep retrying the same message. A five is permanent. Knocking again on a door with a house rule only costs you reputation.
08 · One company, or everyone? · 2:48
On screen: one door with one coral slip. Then the doors street, many doors, many coral slips, each showing DMARC. An arrow turns back to Sally's side.
A policy bounce might have nothing to do with how good a sender you are. One bounce from one company doesn't mean you have a deliverability problem. It means THEY have rules, and you tripped one. But a pattern across lots of recipients, with DMARC in the words, points back at your setup.
09 · Recap · 3:08
On screen: the rulebook, the two slips with their words, the two ticks, the chips lit.
Next time it happens, read the words on the Diagnostic Code line. Reach the person another way, paste them the bounce, and ask to be allowed. Change what tripped the rule. Don't resend the same message. And if it happens across lots of recipients, look at your own setup.
10 · Close · 3:27
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
Read the bounce, and ask for permission. Your side of it is the list, and at Review My Emails we check the addresses you send to. A clean won't get you past a company's rules. Stuck on one right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is bounce rate?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-011.009.012-blocked-by-policy.md
00 · One company says no (hook)
Blocked by policy
the title, Lora, large: "What does "blocked by policy" mean in bounce codes?" Sally's envelope to finn@saltmarsh-outfitters.example comes back with a coral slip, mono 550 5.7.1 Message rejected by organization policy. Four numbered chips, the VO's words: 1 whose policy it is · 2 what usually trips it · 3 how to tell it from spam filtering · 4 what to do. Chips 2 to 4 grey.
one envelope, one slip. Reveals: (1) the send, (2) the slip, (3) the chips.
concept bounce (M-15, M-18).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 20 words, brand said here and in the close only.
02 · Whose policy it is
Whose policy it is
chip 1 lights. Saltmarsh Outfitters' door, with a thick house rules book on a stand beside it, labelled their rules. Sally's envelope stops at the door. A small spam filter icon beside the door stays grey, not involved. Gloss card: policy · a rule the receiving company set for what mail it accepts.
the rulebook lit, the filter grey. Reveals: (1) the door and its rulebook, (2) the envelope stops, (3) the filter stays grey.
the door (M-14) and a house rules book on a stand (no picture yet, proposed), reused through the video.
03 · The code family
Whose policy it is
playlist 1 video 2's 5.1.1 slip, small, called back. Beside it, a new slip 5.7.1, its second digit lit coral, labelled security and policy. The first 5 on both glows.
the second digit sorts the family. Reveals: (1) the old 5.1.1 slip (callback), (2) the 5.7.1 slip, second digit lit, (3) both 5s glow.
playlist 1's slips (M-15, M-14). No new gloss card, the enhanced status code card is playlist 1 video 2's (S6).
one callback scene (S6). The 5.1 and 5.4 comparisons go to the description (P7).
04 · What usually trips it, part one
What usually trips it
chip 2 lights. The house rules book by the door turns one page per trip, each page headed with its name: blocked attachment (a paperclip, .zip crossed out), internal-only address (payroll@saltmarsh-outfitters.example, staff only), approved senders only (a short list, Sally's name missing).
a count of six pages, three turned. The rulebook holds still, the page changes (P1, P2). Reveals: (1) to (3) one page each.
the rulebook.
05 · What usually trips it, part two
What usually trips it
the same rulebook turns three more pages, each headed with its name: DMARC reject (the record card, reject lit, a failed check), encryption required (a lock), keyword rule (one word highlighted). On page 4, a small tag your rule (T3). Gloss card, the registry line: DMARC · a policy on top of SPF and DKIM saying what a receiving server should do when a message fails, and where to send reports.
six of six pages turned. Reveals: (1) to (3) one page each.
the rulebook, concept dmarc (M-18, M-35).
06 · Policy or spam filter?
How to tell it from spam filtering
chip 3 lights. Two slips side by side, both starting 5.7.1. Left, the word organization lights in the text. Right, the word spam lights. The shared 5.7.1 greys out, the words stay lit.
two slips, one code, two different words. The code fades, the words hold. Reveals: (1) the policy slip, (2) the spam slip, (3) the code greys out.
the slips.
07 · What to do
Almanac ids in this scene: 011.009.012
What to do
the house rules book from scene 02. The .zip card on Sally's envelope is swapped for a small link card, and the envelope goes through. A second envelope keeps knocking at the same rule, and a small gauge beside it drops one notch per knock.
one fix that passes, one repeat that costs. Reveals: (1) the zip swapped for a link, (2) it passes, (3) the repeat knocks and the gauge drops.
concept sender-reputation (the score gauge, M-33). The house rules book: no picture yet.
"not a reputation problem" is cut (PM call on C26, G2). "Allow list" is plain English for the answer's "whitelist". The other steps (change what tripped it, don't retry) go to the description (P7).
011.009.012 "If it was a .zip attachment, send a link to a shared folder instead. If it was DMARC, fix your alignment before resending." / "Do not keep retrying the same message. 5.7.x is a 5xx code, which means permanent failure. Retrying just wastes your sender reputation."
T9, one more step of how. Scene 07 split so each stays under 70 words (S2).
08 · One company, or everyone?
What to do
one door with one coral slip. Then the doors street, many doors, many coral slips, each showing DMARC. An arrow turns back to Sally's side.
one slip against many. Reveals: (1) one door, (2) many doors, (3) the arrow back.
the doors street (M-14).
09 · Recap
Four things to remember
the rulebook, the two slips with their words, the two ticks, the chips lit.
callbacks only.
callbacks only.
10 · Close
Ask, don't retry
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do (S10). Totals: 12 scenes. 607 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 3:39 at 166 words a minute, plus scene breaks, so about 3:51 on the clock (scene times re-timed from the counts). Every scene is 20 to 70 words (S2).
V014What is bounce rate?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C4, C16, C19: once YT rules on a bounce-rate line, a scene can be added after scene 04.
- "No picture yet": the 10,000 dot grid with its blurred report card.
00 · A few hundred came back (hook) · 0:00
On screen: the title, Lora, large: "What is bounce rate?" A grid of 10,000 small teal dots, all sent. A scatter of them, a few hundred, turn coral and drift back. The report card beside it shows bounce rate with its number blurred. A mailbox provider's gate at the edge of the frame turns toward the blurred number. Three numbered chips, the VO's words: 1 what it counts · 2 why it's watched · 3 what to do when it climbs. Chips 2 and 3 grey.
Sally Send sends ten thousand emails. A few hundred come back. Her report turns that into one number. And that one number is what mailbox providers read. What is bounce rate? Here's the plan. What it counts. Why it's watched. And what to do when it climbs.
01 · Brought to you by, woven in · 0:18
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Fewer of those come back when the list is checked first, and Review My Emails checks every address before you send.
02 · What it counts · 0:27
On screen: a demo campaign report, most of it greyed. The bounces row lights, then splits into hard and soft. A click on hard opens a short list of addresses on reserved .invalid domains, each with its reason beside it. No rate is shown on screen.
Where do you find it? In your campaign report, the one your tool builds after every send. Look for the bounce figure, and see if your tool splits it into hard and soft. If it does, open the list behind the number. That's where the addresses and their reasons are.
03 · Why it's watched · 1:11
On screen: chip 2 lights. The mailbox provider's gate looks at Sally's grid, and the coral share glows. Then a chain builds beside it, small, with each link labelled as it is said (Q5: the picture replays with its words, no "remember"): bounces to reputation to the gate, which narrows one step. Gloss card, the registry line: mailbox provider · the service your reader receives mail with, such as a consumer or workplace inbox. It decides where your message lands.
Why is it watched so closely? Because mailbox providers use it to judge whether you're a responsible sender. A tall stack of returned letters means the addresses are wrong. A high bounce rate says you're mailing bad data. It works like a chain. Bounces wear down your reputation. And reputation drives blocking decisions.
04 · Two numbers, not one · 1:31
On screen: the stack of returned letters from scene 02 splits in two. One side, a wrench: DNS · blocklisted IP · encryption, and its slips fade away as the wrench turns. The other side, coral slips 5.1.1 and 5.1.2, and they drop into the suppress pot.
Some of your bounce rate may have nothing to do with your list. A broken DNS setup, a blocklisted IP, broken encryption. Fix those, and those bounces stop, with no address removed. But a user unknown or a domain not found? No setting fixes that. The address has to come off.
05 · What to do when it climbs · 2:02
On screen: the callback from V011 03c, one beat: one envelope passes through the gate that lets every envelope through, and nothing comes back. The lamp tags it amber, catch-all. Gloss card, the registry line: catch-all · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos.
And one kind never shows up in the number at all. A catch-all domain says yes to every address at it, real or made up, and usually won't bounce the fake ones. So a low bounce rate can still hide addresses nobody reads.
06 · Recap · 2:39
On screen: the grid with its coral share and formula line, the chain, the pot, the chips lit.
Before your next send, then. Find the bounce figure in your campaign report. Watch the hard bounce rate on its own. Open the list behind it and read the reasons. Fix the setup for the technical ones. And clean and suppress the dead ones.
07 · Close · 2:56
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, no subscribe ask.
Clean before the next send. Review My Emails takes the bad addresses out first. It won't undo past bounces, or fix your setup. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what does invalid recipient address mean?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-004.004.001-what-is-bounce-rate.md
00 · A few hundred came back (hook)
Bounce rate
the title, Lora, large: "What is bounce rate?" A grid of 10,000 small teal dots, all sent. A scatter of them, a few hundred, turn coral and drift back. The report card beside it shows bounce rate with its number blurred. A mailbox provider's gate at the edge of the frame turns toward the blurred number. Three numbered chips, the VO's words: 1 what it counts · 2 why it's watched · 3 what to do when it climbs. Chips 2 and 3 grey.
10,000 dots, drawn one each. A few hundred turn coral, no count label (the Almanac says "a few hundred"). The report number stays blurred on purpose (N6). Reveals: (1) the grid, (2) the coral dots come back, (3) the blurred number, (4) the gate turns to it, (5) the chips.
concept bounce (M-15, M-18), the dot grid.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 21 words, brand said here and in the close only.
02 · What it counts
Almanac ids in this scene: 004.004.001
What it counts
a demo campaign report, most of it greyed. The bounces row lights, then splits into hard and soft. A click on hard opens a short list of addresses on reserved .invalid domains, each with its reason beside it. No rate is shown on screen.
one number that opens into its list. Reveals: (1) the report, (2) the bounces row lights, (3) the split, (4) the list behind it.
the formula is one line under the grid, not a scene (S2). No worked result. The Almanac's example lands on a threshold (C4, C16).
the dot grid from scene 00, now as a report. No picture yet for the report.
004.004.001 "Your ESP translates these codes into 'hard bounce' (permanent failure) or 'soft bounce' (temporary failure) and records them in your campaign report."
T2, where the number lives. No rate is shown (N6, C4).
03 · Why it's watched
Almanac ids in this scene: 021.006.011
Why it's watched
chip 2 lights. The mailbox provider's gate looks at Sally's grid, and the coral share glows. Then a chain builds beside it, small, with each link labelled as it is said (Q5: the picture replays with its words, no "remember"): bounces to reputation to the gate, which narrows one step. Gloss card, the registry line: mailbox provider · the service your reader receives mail with, such as a consumer or workplace inbox. It decides where your message lands.
the same grid, the coral share lit, and the gate narrowing one step with it. No mark is drawn where it narrows (C19). Reveals: (1) the gate, (2) the coral glows, (3) the chain, (4) the gate narrows.
concept mailbox-provider (M-14, M-18), and the chain and gate from 021.006.011 (P5, S6).
the chain is said in one line and drawn, no "Remember the chain from the myths video?" (Q5). No level is said to trigger anything (C19).
04 · Two numbers, not one
Almanac ids in this scene: 015.016.006
Two kinds of fix
the stack of returned letters from scene 02 splits in two. One side, a wrench: DNS · blocklisted IP · encryption, and its slips fade away as the wrench turns. The other side, coral slips 5.1.1 and 5.1.2, and they drop into the suppress pot.
one pile, two halves, two different fixes. Reveals: (1) the split, (2) the wrench clears one half, (3) the other half into the pot.
concept suppression-list (M-23, M-24). The wrench half: no picture yet.
015.016.006 "Technical bounces (DNS misconfiguration, broken TLS, IP blocklisting) and reputation-based 4xx rejections can be cleared by fixing infrastructure or rehabilitating sender reputation, no list changes required." / "Hard bounces returning SMTP 5.1.1 (user unknown) or 5.1.2 (domain not found) cannot be fixed any other way... the address has to be suppressed."
T3, the one twist. No blocklist is named. Nothing says a clean fixes the technical half (S10).
05 · What to do when it climbs
Almanac ids in this scene: 005.003.010, 005.008.002, 005.013.008, 021.002.013
The one you never see
the callback from V011 03c, one beat: one envelope passes through the gate that lets every envelope through, and nothing comes back. The lamp tags it amber, catch-all. Gloss card, the registry line: catch-all · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos.
the count of returned slips is zero. The empty space where a slip should land is the picture. Reveals: (1) the envelope goes in, (2) nothing returns, (3) the lamp tags it.
concept catch-all (M-18, M-15, the registry's gate), V011's picture called back (S6). The door was swapped for the registry's gate in the RME-182.1 review pass (P5).
R15 (YT, 2026-09-29): pivot before the pitch, backed by the catch-all and accept-all answers only. "Usually won't bounce" keeps to the Almanac's own "usually do not bounce" (C17 and C18 are not voiced: no count, and no claim that catch-alls never bounce). V011 03c owns this picture, this scene calls it back in one beat and re-glosses the word for a viewer from search (S6, Q5).
005.003.010 "Catch-all servers usually do not bounce. They accept and then silently drop." / 005.008.002 "Every address on the domain accepts mail at the SMTP layer, then the message is dropped" / 005.013.008 "a real validator will identify these domains and flag them accordingly."
reworded from the stock pivot so it grows out of this video's number (Q1, Q2), and moved before the recap as 05b (Q3). "Usually won't bounce" keeps inside C17. Backed by 005.003.010 "Catch-all servers usually do not bounce" and 021.002.013 "you have no way of knowing whether the person you're trying to reach actually exists".
06 · Recap
Three things to remember
the grid with its coral share and formula line, the chain, the pot, the chips lit.
callbacks only.
callbacks only.
07 · Close
Clean before the next send
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
no rate, no "keeps you under" claim. Says what a clean does not do (S10). Totals: 11 scenes. 515 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 3:06 at 166 words a minute, plus scene breaks, so about 3:17 on the clock (scene times re-timed from the counts). Every scene is 20 to 70 words (S2). Short cut (R12): removed in the taste pass. The video now runs past 2:00, so no Short cut is made from it.
V015What does "invalid recipient address" mean?
draftedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- End screen, settled by the Video PM 2026-09-29: playlist 2.
- "No picture yet": the address card under a magnifier.
00 · But I checked that list (hook) · 0:00
On screen: the title, Lora, large: "What does "invalid recipient address" mean?" A list with a big green tick, checked. One envelope comes back anyway, coral slip, mono 550 invalid recipient. Four numbered chips, the VO's words: 1 what the server is saying · 2 the usual causes · 3 what to check · 4 where to fix it. Chips 2 to 4 grey.
Invalid recipient address. And Sally Send's first thought is, but I checked that list. What does invalid recipient address mean? It's a hard bounce, and the cause is often the address itself. What the server is saying. The usual causes. What to check. And where to fix it.
01 · Brought to you by, woven in · 0:18
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A broken address is easier to catch before it bounces, which is why Review My Emails checks every one, format and all.
02 · What the server is saying · 0:27
On screen: one word card, invalid, held still. It slides first under a checker's lamp at the desk, before the gate (no desk, the lamp alone), and stamps a malformed address. Then it slides onto a returned bounce slip, mono 550 invalid recipient, on the far side of the gate.
One word, two places. When a checker calls an address invalid, it breaks the basic rules before any mail server sees it. When a bounce says invalid recipient, that's a server's reply, after your mail reached it.
03 · The usual causes · 1:00
On screen: chip 2 lights. Four cards in a row. Cards 1 and 2 are small callbacks, greyed: mailbox doesn't exist (hygiene video 1's empty desk), their rules (video 3's house rules book). Cards 3 and 4 light up: broken format, malformed syntax. The magnifier moves to card 3.
What usually causes it? Four things. The mailbox doesn't exist. The server's own rules turned it away. The format is broken. Or the syntax is malformed underneath. The last two are the ones people miss.
04 · What a broken address looks like · 1:14
On screen: chip 3 lights. One address card under the magnifier, and one thing wrong per click, the wrong character circled in coral: wren@mailbx.invalid (the missing letter), finn@saltmarsh-outfitters.___ (the missing ending), marina @tidewell-supply.example (the space), pearl@anchor,oar.example (the comma).
What do you check? Take a sample of those addresses and look, by eye. Where? Export the bounced addresses from your tool's bounce report, and sort them by domain, so the odd ones stand out. A typo in the domain. A missing ending, like dot com. An extra space. A strange character. Each one looks almost right, and none of them can take mail.
05 · If they look fine · 1:38
On screen: a clean-looking address card, no circle. A small note beside the receiving server: picky. The confirmed broken cards from scene 04 drop into the suppress pot. The clean-looking card holds, with no verdict drawn on it (C37, G3).
Sometimes they look perfectly fine to you. The address is spelled right, the ending is there. But the check might be specific to that provider. Some servers are picky, and turn away what another server would take. So remove the ones you've confirmed are invalid.
06 · Fix it where it came in · 1:55
On screen: chip 4 lights. A signup form, with the address field. The typo from scene 04 is typed into it, and the field now catches it before it reaches the list. Beside it, an import file with the same check. Then the suppress pot's lid locks.
Where do you fix it? At the source, where the mistake got in. If it's a data entry problem, fix your signup form, or your import. And most email marketing tools let you suppress addresses automatically after they bounce. Turn that on, so the same ones don't come back again.
07 · Recap · 2:14
On screen: the two slips, the four cause cards, the magnifier, the form, the chips lit.
Before the next send, then. Export the bounced addresses and look at a sample, by eye. Remove the ones you've confirmed are broken. Fix the form or the import they came in through. And make sure your tool suppresses them automatically after they bounce.
08 · Close · 2:31
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: playlist 2, Keeping a list healthy (Video PM, 2026-09-29), opening on V006, no subscribe ask.
Check the list before the next send, format and all. At Review My Emails we catch the broken formats already on your list, and you can run the same check at signup, through our API. A clean won't fix your signup form. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what does user unknown mean?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.003.013-invalid-recipient-address.md
00 · But I checked that list (hook)
Invalid recipient address
the title, Lora, large: "What does "invalid recipient address" mean?" A list with a big green tick, checked. One envelope comes back anyway, coral slip, mono 550 invalid recipient. Four numbered chips, the VO's words: 1 what the server is saying · 2 the usual causes · 3 what to check · 4 where to fix it. Chips 2 to 4 grey.
a green tick and a coral slip, side by side. Reveals: (1) the ticked list, (2) the slip, (3) the chips.
concept hard-bounce (M-15, M-14).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
one sentence, 22 words, brand said here and in the close only.
02 · What the server is saying
Almanac ids in this scene: 005.007.013, 015.003.013
One word, two places
one word card, invalid, held still. It slides first under a checker's lamp at the desk, before the gate (no desk, the lamp alone), and stamps a malformed address. Then it slides onto a returned bounce slip, mono 550 invalid recipient, on the far side of the gate.
one word, two positions, before the gate and after it. The gate is the difference. Reveals: (1) the word card, (2) at the desk, (3) on the slip.
the gate (concept mailbox-provider, M-14, M-18) and V004's checking lamp. No new picture.
one callback line for 550 and 553 (S6). The hard bounce and the 5 are not re-taught.
R11 (YT, 2026-09-29): one shared "invalid" line, word for word the same in 005.007.013 and 015.003.013, so the word means the same to a viewer. GAP-F is closed.
005.007.013 "An invalid address fails basic email rules before it even reaches a mail server." / 015.003.013 "The cause is usually a nonexistent mailbox, malformed syntax (missing @, invalid characters, no TLD), or a local policy rule on the recipient server. It's a hard bounce".
03 · The usual causes
The usual causes
chip 2 lights. Four cards in a row. Cards 1 and 2 are small callbacks, greyed: mailbox doesn't exist (hygiene video 1's empty desk), their rules (video 3's house rules book). Cards 3 and 4 light up: broken format, malformed syntax. The magnifier moves to card 3.
a count of four, two called back grey and two new and lit. Reveals: (1) card 1, (2) card 2, (3) cards 3 and 4 light.
callbacks, then the address card under a magnifier (proposed).
the callbacks to "the user unknown story from the hygiene playlist" and "the policy video" are gone from the VO, each cause is said in its own words. Four items, so the four cards carry them as a picture, one card per cause.
04 · What a broken address looks like
What to check
chip 3 lights. One address card under the magnifier, and one thing wrong per click, the wrong character circled in coral: wren@mailbx.invalid (the missing letter), finn@saltmarsh-outfitters.___ (the missing ending), marina @tidewell-supply.example (the space), pearl@anchor,oar.example (the comma).
one card held still, one character circled per click, a count of four. Reveals: (1) to (4) one fault each.
the address card under a magnifier.
every example is on a reserved ending or has its ending blanked out. No real provider.
05 · If they look fine
What to check
a clean-looking address card, no circle. A small note beside the receiving server: picky. The confirmed broken cards from scene 04 drop into the suppress pot. The clean-looking card holds, with no verdict drawn on it (C37, G3).
the four broken cards go, the clean-looking one holds with no verdict. Reveals: (1) the clean card and the note, (2) the four into the pot.
concept suppression-list (M-23, M-24).
06 · Fix it where it came in
Where to fix it
chip 4 lights. A signup form, with the address field. The typo from scene 04 is typed into it, and the field now catches it before it reaches the list. Beside it, an import file with the same check. Then the suppress pot's lid locks.
the fault is stopped at the door, before the list. Reveals: (1) the form catches it, (2) the import catches it, (3) the lid locks.
a signup form (no picture yet) and suppression-list (M-23, M-24) for the lock. The registry's opt-in pieces include M-07, a drawn person, so they are not used (T11, RME-182.1 review pass).
07 · Recap
Four things to remember
the two slips, the four cause cards, the magnifier, the form, the chips lit.
callbacks only.
callbacks only.
08 · Close
Almanac ids in this scene: 005.001.004
Check before you send
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: playlist 2, Keeping a list healthy (Video PM, 2026-09-29), opening on V006, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not fix (the form) and what it does catch here, the broken formats (S10). Backed by 005.001.004 "Validation catches syntax errors." Totals: 10 scenes. 457 spoken words (recounted 2026-09-30, RME-182.1 review pass). About 2:45 at 166 words a minute, plus scene breaks, so about 2:55 on the clock (scene times re-timed from the counts). Every scene is 20 to 70 words (S2).
V016What is opt-in vs opt-out?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- The law scene (03): option A (EU and US, no law named), B (GDPR and CAN-SPAM named, with the ten business days), or play without it.
- "No picture yet" visuals: the order-in-time strip and its flip, the two law stamps and ten ticks, the lists tipping toward spam.
00 · Legal, and still in spam (hook) · 0:00
On screen: the title, Lora, large: "What is opt-in vs opt-out?" Sally's envelope goes out with a small green legal? stamp, and lands in a folder marked spam. Two numbered chips, the VO's words: 1 what each one means · 2 why legal isn't enough. Chip 2 stays grey until its scene.
Sally Send emails customers who never signed up for her emails. It might even be legal where she is. So why does her mail keep landing in spam? What is opt-in versus opt-out? Two things answer it. What each one means. And why legal isn't enough.
01 · Brought to you by, woven in · 0:17
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Permission covers who asked, and Review My Emails covers the other half, whether each address still works, before you send.
02 · What each one means · 0:27
On screen: chip 1 lights. One strip, two steps. Marina's hand ticks an empty box and presses sign up, and only then does the envelope leave. Gloss card: opt-in · the subscriber actively signed up before you sent anything. Then the same strip flips end to end: the envelope leaves for Kai first, and later Kai's hand finds the unsubscribe link. Gloss card: opt-out · you send by default, and the reader has to act to stop it.
What does each one mean? Opt-in means the subscriber had to actively sign up. They took a deliberate action to say yes, and no email goes out until they asked. Like an invitation. Opt-out flips that. You can email people by default, and they have to take action to stop hearing from you. Like turning up uninvited, until someone asks you to leave.
03 · What the law allows · 0:51
On screen: two stamps side by side. EU stamps opt-in required. US stamps opt-out allowed, with a small unsubscribe link under it. No law names on screen, no ten-day ticks.
And the law? In the EU, opt-in is required. In the US, opt-out is allowed, with a working unsubscribe link.
04 · Why legal isn't enough · 0:59
On screen: Sally's list, all addresses looking alike in mono. A few carry faint tags only the viewer sees: data append, bought, scraped. Then a scan line passes over the list and three of the tagged rows turn coral.
And the addresses nobody chose often came from somewhere else. A data append. A bought file. A scraped contact. Some of those were made up, or belong to nobody at all. They look exactly like the real ones, until you send.
05 · Recap · 2:01
On screen: the order-in-time strip and its flip, the short bars tipping, the two chips lit.
In short. Legal is the floor, and engagement is what gets you into the inbox. Look at where each address on your list came from. Then anyone who never deliberately said yes, customers who only bought included, gets one email asking them to confirm.
06 · Close · 2:21
On screen: the dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono. End screen: video 2, the soft opt-in video (off hold since R7), no subscribe ask.
Ask before you send, then check the list. No clean can turn an opt-out list into an opt-in one. What it does is find the addresses that don't work, before you send. Rather we did it for you? That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is soft opt-in under EU law?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.001.004-opt-in-vs-opt-out.md
00 · Legal, and still in spam (hook)
Opt-in vs opt-out
the title, Lora, large: "What is opt-in vs opt-out?" Sally's envelope goes out with a small green legal? stamp, and lands in a folder marked spam. Two numbered chips, the VO's words: 1 what each one means · 2 why legal isn't enough. Chip 2 stays grey until its scene.
one envelope, one stamp, one wrong folder. Reveals: (1) the stamp, (2) the spam folder, (3) the chips.
concept opt-in (M-14, M-07).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What each one means
What each one means
chip 1 lights. One strip, two steps. Marina's hand ticks an empty box and presses sign up, and only then does the envelope leave. Gloss card: opt-in · the subscriber actively signed up before you sent anything. Then the same strip flips end to end: the envelope leaves for Kai first, and later Kai's hand finds the unsubscribe link. Gloss card: opt-out · you send by default, and the reader has to act to stop it.
order in time on one strip. Tick first, envelope second. Then the same strip flipped, envelope first, choice second. Reveals: (1) the tick, (2) the envelope, (3) the strip flips, (4) the unsubscribe.
concept opt-in (M-14, M-07), then the same strip mirrored.
03 · What the law allows
Almanac ids in this scene: 008.001.004
What the law allows
two stamps side by side. EU stamps opt-in required. US stamps opt-out allowed, with a small unsubscribe link under it. No law names on screen, no ten-day ticks.
two stamps, one each. Reveals: (1) the EU stamp, (2) the US stamp and its link.
the strip from scene 02, its two versions stamped. No new picture.
R7 (YT, 2026-09-29): regions, no law names, no ten-day timing. The GAP is closed. The scene is exactly 20 words, the floor (S2).
008.001.004 "Under GDPR, opt-in is required for marketing to EU residents. Under CAN-SPAM (US), opt-out is technically permitted. You can email someone without prior consent as long as you include a functioning unsubscribe link". GAP-G (the body's "within 10 business days" against the In short's "honored within 10 business days") stays in the ledger, not voiced.
04 · Why legal isn't enough
Almanac ids in this scene: 005.006.008, 008.001.003, 008.001.004
Ask first
Sally's list, all addresses looking alike in mono. A few carry faint tags only the viewer sees: data append, bought, scraped. Then a scan line passes over the list and three of the tagged rows turn coral.
a list where a few rows are not what they seem. Reveals: (1) the list, (2) the faint tags, (3) the scan finds the coral rows.
concept list-cleaning (the dot grid, M-25). The tag overlay: no picture yet.
005.006.008 "The address was fabricated (data append, purchased list, scraped contact)" as a cause of user unknown bounces. 008.001.004 "People who never asked to receive your emails don't engage with them."
T6, the pivot before the pitch (R15 shape). The pitch stays addresses only (S10).
Q3: moved before the recap. Q2: the pivot comes from this topic (where no-consent lists come from), no catch-all.
05 · Recap
Two things to remember
the order-in-time strip and its flip, the short bars tipping, the two chips lit.
callbacks only.
callbacks only.
06 · Close
Ask first
the dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono. End screen: video 2, the soft opt-in video (off hold since R7), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid pours into the three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do. No inbox promise. Totals: 9 scenes. 406 spoken words (counted 2026-09-29, taste pass). About 2:45 at 166 words a minute, about 2:56 with scene breaks. Every scene is 20 to 70 words (S2). Short cut (R12): removed in the taste pass. The video now runs past 2:00, so no Short cut is made from it.
V017What is soft opt-in under EU law?
waiting on YTOpen questions for YT
- HOLD, law rulings Settled by R7: no law named, scene 02 carries one legal sentence. OFF hold.
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- "No picture yet": the side gate with four locks (proposed registry row), the shoe and arrows.
00 · Customers who never ticked the box (hook) · 0:00
On screen: the title, Lora, large: "What is soft opt-in under EU law?" A receipt from Saltmarsh Outfitters with a customer's name. Beside it, an empty consent box, unticked. Three numbered chips, the VO's words: 1 what soft opt-in is · 2 the four conditions · 3 where it stops. Chips 2 and 3 grey.
Sally Send runs a shop. A customer bought from her last month, but never ticked a box to get her emails. The customer lives in the EU. Can Sally email them? That's what soft opt-in under EU law is for. Three things answer it. What soft opt-in is. The four conditions. And where it stops.
01 · Brought to you by, woven in · 0:21
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Soft opt-in decides who you may email, and whether those addresses still work is the part Review My Emails checks before you send.
02 · The carve-out · 0:30
On screen: chip 1 lights. Video 1's opt-in strip, small (tick, then envelope). Beside it a side gate opens for customers only, with four closed locks on it. Gloss card: explicit consent · a deliberate yes, like ticking an empty box to ask for your emails.
Start with what it is. In the EU, marketing email needs explicit consent first, a deliberate yes before you send. But there's a carve-out for existing customers. That's soft opt-in. Think of the shop assistant who says, you bought the shoes, want to hear about the laces? It lets you email a customer about similar products, without asking first, if four conditions are ALL met.
03 · Conditions one and two · 0:55
On screen: chip 2 lights. Lock 1 opens over the customer's receipt. Lock 2 opens over a shelf of Saltmarsh Outfitters products. A partner's flyer tries the lock and it stays shut.
What are the four? One. You got their address during a sale, or while talking about one. Two. You're promoting your OWN similar products or services. Not a partner's offers. Not something unrelated.
04 · Conditions three and four · 1:07
On screen: lock 3 opens over the checkout page, where a clear no thanks to emails choice sits beside the address field. Lock 4 opens over an envelope with an unsubscribe link in its footer. The side gate swings open.
Three. You gave them a clear chance to opt out when you first collected their address. Where would that be? On your checkout page, right where they typed their email. And four. Every email after that has an easy way to opt out.
05 · The word that does the work · 1:23
On screen: a running shoe on the left. An arrow to a hiking boot, short and green. An arrow to a pile of coins, long, bending, coral, with a small ? on it.
Even a real customer can be off limits, if what you send isn't similar. The word similar does real work. Someone who bought running shoes can reasonably expect to hear about other footwear. Emailing them about your new financial products stretches it well past its intent. The link between what they bought and what you promote has to be obvious, not explained.
06 · Where it stops · 1:47
On screen: the customer's receipt from scene 00, the email line in mono. One letter of the domain is wrong, saltmarsh-outfiters.invalid, and a small coral dot appears beside it. The receipt itself stays crisp.
And there's one thing the four conditions can't tell you. Whether the address works. Customers type their email at checkout in a hurry, and a mistyped domain often points to a domain that doesn't exist at all. The receipt looks fine. The address never will.
07 · Recap · 2:17
On screen: the gate with four open locks, the shoe and boot, the narrow gate, the chips lit.
Your checklist, before you count a customer in. Check your checkout page offers a clear opt-out. Check every email carries one. Check what you're sending is your own, and plainly similar to what they bought. If you can't tick all four, ask for a yes first.
08 · Close · 2:36
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, the warmup tools video (off hold since R8), no subscribe ask.
Tick all four before you count a customer in, then check the addresses too. Consent is yours to prove. The addresses are what we check. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what tools can help with cold email warmup?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.001.014-soft-opt-in-eu-law.md
00 · Customers who never ticked the box (hook)
Soft opt-in
the title, Lora, large: "What is soft opt-in under EU law?" A receipt from Saltmarsh Outfitters with a customer's name. Beside it, an empty consent box, unticked. Three numbered chips, the VO's words: 1 what soft opt-in is · 2 the four conditions · 3 where it stops. Chips 2 and 3 grey.
a receipt present, a tick absent. Reveals: (1) the receipt, (2) the empty box, (3) the chips.
concept opt-in (M-14, M-07), the empty box.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The carve-out
What soft opt-in is
chip 1 lights. Video 1's opt-in strip, small (tick, then envelope). Beside it a side gate opens for customers only, with four closed locks on it. Gloss card: explicit consent · a deliberate yes, like ticking an empty box to ask for your emails.
one side gate, four locks. Reveals: (1) the opt-in strip (callback), (2) the side gate, (3) the four locks.
concept opt-in (M-14, M-07). The side gate: no picture yet.
opt-in was taught in video 1.
03 · Conditions one and two
The four conditions
chip 2 lights. Lock 1 opens over the customer's receipt. Lock 2 opens over a shelf of Saltmarsh Outfitters products. A partner's flyer tries the lock and it stays shut.
a count of locks, two of four open. Reveals: (1) lock 1, (2) lock 2, (3) the partner flyer bounces off.
the side gate from scene 02.
04 · Conditions three and four
The four conditions
lock 3 opens over the checkout page, where a clear no thanks to emails choice sits beside the address field. Lock 4 opens over an envelope with an unsubscribe link in its footer. The side gate swings open.
four of four locks open, and only then the gate moves. Reveals: (1) lock 3, (2) lock 4, (3) the gate opens.
the side gate.
05 · The word that does the work
Similar means similar
a running shoe on the left. An arrow to a hiking boot, short and green. An arrow to a pile of coins, long, bending, coral, with a small ? on it.
arrow length is distance from what they bought. Short and straight passes, long and bent fails. Reveals: (1) the shoe, (2) the boot arrow, (3) the coins arrow.
no picture yet.
06 · Where it stops
Almanac ids in this scene: 005.008.005
Before you count them in
the customer's receipt from scene 00, the email line in mono. One letter of the domain is wrong, saltmarsh-outfiters.invalid, and a small coral dot appears beside it. The receipt itself stays crisp.
one letter wrong on a good-looking receipt. Reveals: (1) the receipt, (2) the wrong letter lights, (3) the coral dot.
the receipt from scene 00. Typo form from the demo-names library (.invalid).
R7 (YT, 2026-09-29): no law named. The ePrivacy Directive gloss and the GDPR line are cut.
Q3: moved before the recap. Q2: the pivot comes from this topic (the address typed at checkout), no catch-all.
005.008.005 "Mistyped domains at signup often point to nonexistent domains with no DNS at all, let alone MX records." / "It doesn't matter how well-formed the address looks".
T6, the pivot before the pitch (R15 shape). "In a hurry" is framing, not a fact.
07 · Recap
Three things to remember
the gate with four open locks, the shoe and boot, the narrow gate, the chips lit.
callbacks only.
callbacks only.
08 · Close
Check all four
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, the warmup tools video (off hold since R8), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (consent). Totals: 10 scenes. 467 spoken words (counted 2026-09-29, taste pass). About 2:58 at 166 words a minute, about 3:10 with scene breaks. Every scene is 20 to 70 words (S2).
V018What tools can help with cold email warmup?
waiting on YTOpen questions for YT
- RULE-1b (the HOLD) Settled by R8: a neutral explainer, OFF hold, no names, no prices, no recommending.
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Scene 04 option Settled by R8: both sides, neutrally.
- C22: warmup length, not voiced either way.
- "No picture yet": the history bar, the ring of inboxes.
00 · A fresh domain, and a promise (hook) · 0:00
On screen: the title, Lora, large: "What tools can help with cold email warmup?" A new domain card, anchor-oar.example, cold blue, with an empty history bar. A plug labelled warmup tool hovers beside it. Three numbered chips, the VO's words: 1 how warmup tools work · 2 why they help, or don't · 3 what they can't do. Chips 2 and 3 grey.
Sally Send just set up a fresh domain for cold outreach. A warmup tool says it'll get it ready. So what tools can help with cold email warmup? Three things answer it. How warmup tools work. Why they help, or don't. And what they can't do.
01 · Brought to you by, woven in · 0:17
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Warmup works on your domain, while Review My Emails works on your list, checking that the people you write to are there.
02 · How they work · 0:27
On screen: chip 1 lights. Sally's inbox plugs into a ring of other inboxes. Envelopes pass around the ring. On each arrival: an open, a not spam tick, now and then a reply arrow. Gloss card: warmup · slowly ramping up what you send from a new domain.
Start with how they work. Warmup means slowly ramping up what you send from a new domain. A tool automates part of it. You connect your inbox and set a daily volume. Your account sends to other accounts in the tool's network, and they send back. They open your emails, mark them as not spam, and sometimes reply. It's a rehearsal, with an audience that's paid to clap.
03 · What it gets you · 0:51
On screen: chip 2 lights. The empty history bar from the hook starts to fill, a thin first stretch, from grey to teal.
What does that get you? A new domain has no sending history at all. A warmup tool helps it get past zero, so it isn't a complete stranger when your real outreach starts.
04 · Does it build real reputation? · 1:03
On screen: the history bar from scene 03 holds its thin stretch. Beside it, the ring from scene 02 turns, and a mailbox provider's gate watches it. The ring's envelopes pass the gate lighter, a paler teal, than a single real envelope that follows.
Does that build your reputation? It builds sending HISTORY. Whether that becomes lasting reputation is less clear. Mailbox providers increasingly discount mail passed around a pool of accounts, because the pattern doesn't look like real people. The same accounts, opening and replying, day after day. The audience claps, but the critics aren't fooled.
05 · What they can't fix · 1:24
On screen: chip 3 lights. The ring keeps turning, and beside it two things it can't reach: a cracked SPF record card, and a list with coral rows. Neither changes. Gloss card: SPF · the record that says which servers may send email for your domain.
What can't they do? They can't fix a broken SPF record. They can't make up for a poor list. And if your setup isn't right before you start, the tool is wasting its time. So check your setup first. Our free SPF checker shows you what your SPF record says, and whether it's right, before any warmup starts.
06 · The jump at the end · 1:45
On screen: the history bar from scene 03, part filled. A sudden tall spike of envelopes hits it, and the fill drains back.
And when the warmup ends, don't jump straight to high cold volume. Do that, and you can undo the work in a week.
07 · What matters more than any tool · 1:53
On screen: Sally's warmed-up inbox, its small sending history bar green. A cold list slides in, and a scatter of its addresses turn coral as they hit dead domains. The green bar dips with each one.
And no rehearsal fixes the audience itself. A tool can't make up for a poor list. Cold lists, bought or scraped, start out with far more dead domains than real signups. Every one of those is a hard bounce on a brand new domain, the one you just spent weeks warming. You can't see which ones by looking.
08 · Recap · 2:32
On screen: the ring, the unchanged SPF card and list, the two ticks and the real replies, the three chips lit.
Here's the order that works. Check your setup first, SPF and DKIM. Know that a warmup tool builds history, and providers increasingly discount it. Start real outreach small, to a targeted list, early. And when the warmup ends, don't jump straight to high volume.
09 · Close · 2:48
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
Get your setup right, and make sure the people you write to are there. Cleaning a list won't warm a domain. It checks who you're writing to. Stuck on one right now? Our SOS hotline is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what options should a preference center offer? For example, frequency and content types.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-010.003.008-cold-email-warmup-tools.md
00 · A fresh domain, and a promise (hook)
Warmup tools
the title, Lora, large: "What tools can help with cold email warmup?" A new domain card, anchor-oar.example, cold blue, with an empty history bar. A plug labelled warmup tool hovers beside it. Three numbered chips, the VO's words: 1 how warmup tools work · 2 why they help, or don't · 3 what they can't do. Chips 2 and 3 grey.
an empty history bar. Reveals: (1) the domain card, (2) the empty bar, (3) the plug, (4) the chips.
no registry row for warmup. Proposed: the history bar.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · How they work
How warmup tools work
chip 1 lights. Sally's inbox plugs into a ring of other inboxes. Envelopes pass around the ring. On each arrival: an open, a not spam tick, now and then a reply arrow. Gloss card: warmup · slowly ramping up what you send from a new domain.
the ring. Every envelope out comes back. Reveals: (1) the plug in, (2) mail goes round, (3) the opens and ticks, (4) a reply.
no picture yet. Proposed: the ring of inboxes.
no product is named or drawn (R8, hard content rules).
03 · What it gets you
How warmup tools work
chip 2 lights. The empty history bar from the hook starts to fill, a thin first stretch, from grey to teal.
the bar leaves zero. It is drawn short on purpose, with no end mark and no week labels (C22). Reveals: (1) the bar at zero, (2) the first stretch.
the history bar from scene 00.
04 · Does it build real reputation?
Almanac ids in this scene: 010.003.008, 021.009.007
Why they help, or don't
the history bar from scene 03 holds its thin stretch. Beside it, the ring from scene 02 turns, and a mailbox provider's gate watches it. The ring's envelopes pass the gate lighter, a paler teal, than a single real envelope that follows.
the same stretch of history, weighed two ways. Pale for the ring's mail, full teal for a real person's. No share and no number. Reveals: (1) the gate watches the ring, (2) the pale envelopes, (3) the real envelope.
the history bar and the ring, concept mailbox-provider (M-14, M-18) for the gate.
R8 (YT, 2026-09-29): a neutral explainer, both sides said, no recommending. RULE-1b's GAP is closed. "The theory is solid" is not voiced as advice, and nothing tells the viewer to use a tool.
010.003.008 "your domain accumulates positive sending history before you start real outreach" / 021.009.007 "Warmup tools build infrastructure history, not durable sender reputation." / "Gmail and Outlook increasingly discount this traffic because the engagement pattern... doesn't match human behavior."
05 · What they can't fix
What they can't do
chip 3 lights. The ring keeps turning, and beside it two things it can't reach: a cracked SPF record card, and a list with coral rows. Neither changes. Gloss card: SPF · the record that says which servers may send email for your domain.
the ring turns, the two cards don't change. Reveals: (1) the cracked SPF card, (2) the coral list, (3) the ring turning with both unchanged.
concept spf (M-18, M-15).
06 · The jump at the end
Almanac ids in this scene: 010.003.008
What they can't do
the history bar from scene 03, part filled. A sudden tall spike of envelopes hits it, and the fill drains back.
one spike, and the filled bar shrinking. Reveals: (1) the spike, (2) the drain.
the history bar.
no week count or volume number. 010.003.008's "undo months of work in a week" is voiced as "undo the work in a week", because "months" sits oddly beside its own "2-4 weeks" (C22).
07 · What matters more than any tool
Almanac ids in this scene: 005.008.001, 010.003.008
Who you write to
Sally's warmed-up inbox, its small sending history bar green. A cold list slides in, and a scatter of its addresses turn coral as they hit dead domains. The green bar dips with each one.
the warmed history bar against the coral hits. Reveals: (1) the green history bar, (2) the list slides in, (3) the coral hits and the dip.
concept sender-reputation (the score gauge, M-33) for the bar.
R8. The old "how to use one well" framing is gone. This scene talks about setup and real people, and never tells the viewer to use a warmup tool.
Q3: moved before the recap. Q2: the pivot comes from this topic (cold lists on a freshly warmed domain), no catch-all.
010.003.008 "They can't fix a broken SPF record or make up for poor list quality." / 005.008.001 "Lists you bought, scraped, or got through B2B lead databases start out with a much higher dead-domain rate than organic signups" / "Every message you send to a dead domain is a hard bounce."
T6, the pivot before the pitch (R15 shape). "Weeks" is the warmup length word, voiced with no figure (C22).
08 · Recap
Three things to remember
the ring, the unchanged SPF card and list, the two ticks and the real replies, the three chips lit.
callbacks only.
callbacks only.
09 · Close
Setup first, then real people
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do (warm a domain). Totals: 11 scenes. 519 spoken words (counted 2026-09-29, taste pass). About 3:12 at 166 words a minute, about 3:25 with scene breaks. Every scene is 20 to 70 words (S2).
V019What options should a preference center offer? (e.g., frequency, content types)
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- "No picture yet": the footer doors, toggles and pipes (proposed registry row), the calendar strip.
00 · One way out (hook) · 0:00
On screen: the title, Lora, large: "What options should a preference center offer?" An email footer with a single door marked unsubscribe. The subscriber's envelope stack piles higher, and they walk to the one door. Four numbered chips, the VO's words: 1 the content types · 2 the frequency and pause options · 3 the extras · 4 the one test for every option. Chips 2 to 4 grey.
A subscriber loves Sally Send's newsletter. They're just getting too much of it this month. And the footer gives them one way out. Unsubscribe. So what options should a preference center offer? Four things answer it. The content types. The frequency and pause options. The extras. And the one test for every option.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
People choose what they get in a preference center, and Review My Emails checks that each address can still get it.
02 · Content types · 0:28
On screen: chip 1 lights. The footer grows a second door, preferences. Behind it, a row of toggles, one per stream Sally sends: newsletter, offers, events. Each toggle has its own thin pipe to its own send. Gloss card: preference center · a page where a reader chooses what they want from you, instead of only choosing to leave.
Start with the content types. A preference center should give people a reason to stay, not just a door to leave through. So look at the email streams you send. Open your last few months of sends and sort them by kind. Newsletters, offers, product updates, event invites, educational content, account notices. List the ones that exist. And don't invent categories just to look thorough.
03 · Frequency · 0:52
On screen: chip 2 lights. Three toggles, daily · weekly · monthly. The subscriber picks weekly. A calendar strip shows one envelope a week. Then the other version: important news! envelopes fill every day of the week anyway, and the weekly toggle cracks.
Next, frequency. Daily, weekly, or a monthly digest works well, when you have the content to back it up. But be honest. If picking weekly still means daily emails whenever you have important news, that erodes trust faster than having no preference center at all. Because the reader chose, and you ignored the choice. Only offer frequencies you'll HONOUR.
04 · The pause button · 1:13
On screen: a pause toggle with two settings, 30 days and 60 days. The subscriber picks 30. The calendar strip goes quiet for 30 days, drawn as 30 empty squares, then her envelopes start again and she stays.
Then add a pause. Stop the emails for thirty or sixty days. It's one of the most underused tools a preference center has. Because a lot of people who unsubscribe aren't done with you forever. They're just overwhelmed right now. Give them a second door, one marked, see you next month.
05 · The extras · 1:33
On screen: chip 3 lights. One line of four small labels, topics · channels · profile · privacy, named together and left still. Then one toggle does something: format, plain text or HTML. The subscriber flips it, and it greys out with a small tag, can your tool do this?
Then the extras. Topics, channels, profile updates and privacy controls, where they apply to you. And plain text or HTML? Worth knowing. But check that your email marketing tool can act on it first.
06 · The one test · 1:45
On screen: the footer with its doors, now two: unsubscribe and see you next month. Behind the list, a few envelopes quietly grey out without touching either door. One of them comes back coral.
But a preference center only hears from people who click the link. Others leave without a word. People change jobs and stop using their work email. They abandon old accounts. The address that was fine last year becomes a hard bounce, and no toggle ever tells you. You find out when it bounces.
07 · Recap · 2:21
On screen: the toggle row, the calendar strip with its quiet stretch, the five pipes, the four chips lit.
The whole job, in order. Sort your last few months of sends, and offer only the content types you send. Offer frequencies you'll honour, and a pause. Add the extras that apply. Then test every option. Does picking it change what arrives?
08 · Close · 2:37
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, the IP warming video, no subscribe ask.
Give people a reason to stay, then keep the list clean. A clean tells you which addresses are safe to send to, before they bounce. To see who's still engaged, there's RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... how can IP warming be automated by your email marketing tool?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.005.002-preference-center-options.md
00 · One way out (hook)
Preference center options
the title, Lora, large: "What options should a preference center offer?" An email footer with a single door marked unsubscribe. The subscriber's envelope stack piles higher, and they walk to the one door. Four numbered chips, the VO's words: 1 the content types · 2 the frequency and pause options · 3 the extras · 4 the one test for every option. Chips 2 to 4 grey.
one door. The count of ways out is one. Reveals: (1) the footer, (2) the stack grows, (3) the one door, (4) the chips.
no registry row for preference center. Proposed: the footer with one door, then more.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Content types
The content types
chip 1 lights. The footer grows a second door, preferences. Behind it, a row of toggles, one per stream Sally sends: newsletter, offers, events. Each toggle has its own thin pipe to its own send. Gloss card: preference center · a page where a reader chooses what they want from you, instead of only choosing to leave.
one toggle, one pipe, one real stream. Reveals: (1) the second door, (2) the toggles, (3) each pipe draws to its send.
no picture yet. Proposed: toggles with pipes. The made-up buckets are set up here in one line and paid off in scene 06 (batch D review, point 1).
03 · Frequency
Frequency and pause
chip 2 lights. Three toggles, daily · weekly · monthly. The subscriber picks weekly. A calendar strip shows one envelope a week. Then the other version: important news! envelopes fill every day of the week anyway, and the weekly toggle cracks.
envelopes per week on the calendar strip. One against seven. Reveals: (1) the three toggles, (2) weekly picked, one envelope, (3) seven envelopes, the crack.
no picture yet. Proposed: the calendar strip.
04 · The pause button
Frequency and pause
a pause toggle with two settings, 30 days and 60 days. The subscriber picks 30. The calendar strip goes quiet for 30 days, drawn as 30 empty squares, then her envelopes start again and she stays.
30 empty squares are the 30 days. Reveals: (1) the toggle, (2) 30 empty squares, (3) the envelopes return.
the calendar strip.
05 · The extras
The extras
chip 3 lights. One line of four small labels, topics · channels · profile · privacy, named together and left still. Then one toggle does something: format, plain text or HTML. The subscriber flips it, and it greys out with a small tag, can your tool do this?
one extra acts, the rest are named in one line. Reveals: (1) the four labels, (2) the format toggle, (3) it greys, the tag.
the toggles.
"email marketing tool", never "ESP".
06 · The one test
Almanac ids in this scene: 005.011.001
Who is still there
the footer with its doors, now two: unsubscribe and see you next month. Behind the list, a few envelopes quietly grey out without touching either door. One of them comes back coral.
addresses that leave by neither door. Reveals: (1) the two doors, (2) the quiet greying, (3) the coral return.
the footer doors from scene 00 and 04.
Q3: moved before the recap. Q2: the pivot comes from this topic (the people who never open the preference center), no catch-all.
005.011.001 "People change jobs and stop using their work email. They abandon old personal accounts and switch to new ones." / "What was once a valid, deliverable address becomes a hard bounce."
T6, the pivot before the pitch (R15 shape). The pitch stays addresses only (S10).
07 · Recap
Four things to remember
the toggle row, the calendar strip with its quiet stretch, the five pipes, the four chips lit.
callbacks only.
callbacks only.
08 · Close
Give them a reason to stay
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, the IP warming video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do. The next video's question is spoken as "your email marketing tool", not the Almanac's "ESPs" (V5 exception, settled by the Video PM). Totals: 10 scenes. 480 spoken words (counted 2026-09-29, taste pass). About 3:01 at 166 words a minute, about 3:13 with scene breaks. Every scene is 20 to 70 words (S2).
V020How can IP warming be automated by your email marketing tool?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C22, IP warming length: not voiced either way.
- "No picture yet": the staircase (proposed registry row), the dial, the list wall feeding the first bar, the shared IP card (proposed gloss "one sending address used by many senders together").
00 · A hundred thousand on day one (hook) · 0:00
On screen: the title, Lora, large: "How can IP warming be automated by your email marketing tool?" A new IP card, blank. A wall of 100,000 dots rushes through it at once, and a large share turns amber (deferred) and coral (spam). Three numbered chips, the VO's words: 1 why a new IP needs warming · 2 the three things smart warming does · 3 your part. Chips 2 and 3 grey.
Sally's moving to a new IP. If she sends a hundred thousand emails from it on day one, receiving servers treat it as suspicious, and a big chunk gets deferred or sent to spam. So how can IP warming be automated by her email marketing tool? Three things answer it. Why a new IP needs warming. The three things smart warming does. And your part.
01 · Brought to you by, woven in · 0:23
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A ramp works best on addresses that exist, so Review My Emails checks every one before your first warming send.
02 · Why a new IP needs warming · 0:31
On screen: chip 1 lights. The blank IP card. A staircase of daily bars rises beside it, each a little taller than the last, with no numbers on the bars. Gloss cards: IP reputation · the part of your reputation that belongs to the server you send from. IP warming · building up how much you send from a new address gradually, so a receiving server can learn you. Then, on the last line, the IP card shows a small yours alone tag, and beside it a second card, shared, with several senders' dots on it. Gloss card: shared IP · one sending address used by many senders together.
Start with why. A new IP has no IP reputation yet. It's a new face in town, and nobody knows it. IP warming fixes that by starting small, and scaling up day by day, until you reach full volume. It takes weeks, not days. And it's for senders moving to an IP of their own. A low-volume sender often does better on a shared IP.
03 · The automated part · 0:55
On screen: chip 2 lights. The staircase, with a small dial beside it turning the next bar's height. Three empty slots appear under it, 1, 2, 3.
What's automated? Your email marketing tool decides, day by day, how much goes through the new IP. Same idea as warming by hand, without you babysitting it. And smart warming does three things.
04 · Engaged readers first · 1:08
On screen: slot 1 fills. The first short bars are drawn in keep green, the readers who open and click. Small open and click ticks rise from them toward a mailbox provider's gate. A small grey loop of the same few addresses sits off to the side, crossed out, labelled warmup pool.
One. It sends to your most engaged readers first. Real people on your list who open and click, not a warmup pool. They're the friends who vouch for the new face in town. Their good signals teach mailbox providers this new IP sends wanted mail.
05 · It listens · 1:24
On screen: slot 2 fills. The staircase. A coral spike appears under one bar, and the next bars flatten. Then green ticks stay high, and the next bars step up faster. A rigid staircase beside it, printed, never changes.
Two. It reacts to what happens. If bounces spike, or complaints tick up, it slows the ramp by itself. If engagement stays strong, it can speed up. A fixed day one, day two schedule can't do that.
06 · One ramp per mailbox provider · 1:37
On screen: slot 3 fills. Three gates, A, B, C, each with its own staircase, rising at different speeds. Gate A reaches the top first. Gloss card: mailbox provider · the service your reader receives mail with.
And three. It ramps each receiving mailbox provider on its own. You'd think one ramp fits all. It doesn't. They each have different patience. One may be happy well before another. So a good system speeds up where it's welcome, and holds back where it isn't yet.
07 · Your part · 1:55
On screen: the ramp line from scene 05, climbing. A handful of coral dots from the first group hit it, and each one flattens the climb a little. The line reaches full volume later than its dashed twin that had no coral dots.
One thing the dashboard won't show you. Smart warming listens. If bounces spike, it slows the ramp down by itself. So every dead address in that first engaged group costs you days. You can't tell which ones they are by looking at the list. The new face in town gets introduced to people who moved away.
08 · Recap · 2:37
On screen: the staircase, the three slots filled, the three gates, the green slice in the first bar, the chips lit.
Your list for moving day. Turn on your tool's automated warming. Hand it your best engaged readers first. Keep order and account emails off the warming IP. And check the reputation dashboards every few days while it ramps.
09 · Close · 2:52
On screen: the staircase with a coral spike, then the same staircase, clean, stepping up smoothly. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V021 (Keeping a list healthy, part 2), no subscribe ask.
Let the tool ramp, and give it good addresses. Checking can't warm an IP. It keeps bad addresses out of the ramp. You can run the same check at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a disposable email provider?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-009.002.016-automated-ip-warming.md
00 · A hundred thousand on day one (hook)
Automated IP warming
the title, Lora, large: "How can IP warming be automated by your email marketing tool?" A new IP card, blank. A wall of 100,000 dots rushes through it at once, and a large share turns amber (deferred) and coral (spam). Three numbered chips, the VO's words: 1 why a new IP needs warming · 2 the three things smart warming does · 3 your part. Chips 2 and 3 grey.
100,000 dots in one go. The share that turns amber and coral is drawn as "a big chunk", no percentage (the Almanac gives none). Reveals: (1) the blank IP, (2) the rush, (3) the colours, (4) the chips.
no registry row for IP warming. Proposed: the staircase from scene 02.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Why a new IP needs warming
Almanac ids in this scene: 009.002.007
Why a new IP needs warming
chip 1 lights. The blank IP card. A staircase of daily bars rises beside it, each a little taller than the last, with no numbers on the bars. Gloss cards: IP reputation · the part of your reputation that belongs to the server you send from. IP warming · building up how much you send from a new address gradually, so a receiving server can learn you. Then, on the last line, the IP card shows a small yours alone tag, and beside it a second card, shared, with several senders' dots on it. Gloss card: shared IP · one sending address used by many senders together.
bar height is the day's volume, each bar taller than the one before. No labels and no end date (C22). Reveals: (1) the blank card, (2) the first short bar, (3) the staircase rises, (4) the yours alone tag and the shared card.
no picture yet. Proposed: the staircase. The two glosses above are the registry's own lines for ip-reputation and ip-warmup (P5). shared IP has no registry row yet, proposed line above.
the last two sentences call back to 009.002.007, where a dedicated IP is the wrong move for most senders.
03 · The automated part
The three things smart warming does
chip 2 lights. The staircase, with a small dial beside it turning the next bar's height. Three empty slots appear under it, 1, 2, 3.
the dial sets the next bar. Three empty slots are the three things. Reveals: (1) the dial, (2) the three slots.
concept esp (M-02, M-12), the sending desk, with the dial.
"email marketing tool", never "ESP".
04 · Engaged readers first
The three things smart warming does
slot 1 fills. The first short bars are drawn in keep green, the readers who open and click. Small open and click ticks rise from them toward a mailbox provider's gate. A small grey loop of the same few addresses sits off to the side, crossed out, labelled warmup pool.
the first bars are all green. Reveals: (1) green first bars, (2) the ticks rise, (3) the pool, crossed out.
IP warming here means real readers on your own IP. The line takes no side on warmup tools. R8 (YT, 2026-09-29): we may say what they do, never recommend them. Video 3 is that explainer.
concept engagement-signal (M-15, M-12).
05 · It listens
The three things smart warming does
slot 2 fills. The staircase. A coral spike appears under one bar, and the next bars flatten. Then green ticks stay high, and the next bars step up faster. A rigid staircase beside it, printed, never changes.
the slope of the staircase. It flattens after the spike, steepens with strong engagement. The printed one keeps one slope. Reveals: (1) the spike and the flattening, (2) the steeper steps, (3) the printed staircase.
the staircase.
06 · One ramp per mailbox provider
The three things smart warming does
slot 3 fills. Three gates, A, B, C, each with its own staircase, rising at different speeds. Gate A reaches the top first. Gloss card: mailbox provider · the service your reader receives mail with.
three staircases, three slopes. Reveals: (1) the three gates, (2) the three staircases rise, (3) A tops out first.
concept mailbox-provider (M-14, M-18).
07 · Your part
Almanac ids in this scene: 009.002.016
Good addresses in
the ramp line from scene 05, climbing. A handful of coral dots from the first group hit it, and each one flattens the climb a little. The line reaches full volume later than its dashed twin that had no coral dots.
two ramp lines, one slowed by bounces, one not. Reveals: (1) the climbing line, (2) the coral hits flatten it, (3) the dashed twin arriving sooner.
the ramp line from scene 05. No new picture.
009.002.016 names Google Postmaster Tools as where to watch. Not named in the VO (no vendor or provider names). The description links the Almanac page, which names it.
Q3: moved before the recap. Q2: the pivot comes from this topic (bounces slow the ramp), no catch- all.
009.002.016 "If bounces spike or complaints tick up, the system slows the ramp automatically." / "The first batches go to subscribers who consistently open and click."
T6, the pivot before the pitch (R15 shape). "Costs you days" follows from "slows the ramp", no figure given.
08 · Recap
Three things to remember
the staircase, the three slots filled, the three gates, the green slice in the first bar, the chips lit.
callbacks only.
callbacks only.
09 · Close
Clean before you warm
the staircase with a coral spike, then the same staircase, clean, stepping up smoothly. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V021 (Keeping a list healthy, part 2), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the staircase with and without the spike. No counts in the pots.
concept list-cleaning.
says what a clean does not do (warm an IP). No inbox promise. Totals: 11 scenes. 520 spoken words (counted 2026-09-29, taste pass). About 3:15 at 166 words a minute, about 3:28 with scene breaks. Every scene is 20 to 70 words (S2).
V021What is a disposable email provider?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C29 (ledger): disposable inbox lifespan, minutes or hours against a few days.
- GAP-E (ledger): the blocklist checker line in 005.007.023, same shape as GAP-A.
- "No picture yet": the dispenser, the two guards.
00 · The free guide, and a throwaway inbox (hook) · 0:00
On screen: the title, Lora, large: "What is a disposable email provider?" Sally's guide goes out to a signup card, gone.in.60.seconds@burner.invalid. The card's inbox icon fades to grey. Sally's next envelope arrives at the grey card. Three numbered chips, the VO's words: 1 what one is · 2 why it costs you · 3 the three defences. Chips 2 and 3 grey.
Sally Send offers a free guide. Someone grabs it with a throwaway inbox, and never looks at it again. Soon that address is dead, and Sally is still mailing it. So what is a disposable email provider? Three things answer it. What one is. Why it costs you. And the three defences.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some addresses on your list were never meant to last, and Review My Emails finds them before your next send.
02 · What one is · 0:27
On screen: chip 1 lights. A dispenser hands out inbox cards, one per press, each on burner.invalid. A person takes one, uses it on a signup form, and drops it. Gloss card: disposable email provider · a service that hands out temporary inboxes that soon stop working.
Start with what one is. A disposable email provider hands out instant, temporary inboxes. No signup, no login. It's like a hotel key card that stops working at checkout. People use them to get a freebie or a trial, without handing over their real address. And those inboxes go dead quickly.
03 · Why it costs you: no one's there · 0:46
On screen: chip 2 lights. The signup card from the hook. Two empty engagement ticks beside it (open, click) stay unlit. The card turns coral as it bounces, and a small bounce-rate bar beside it grows, with no numbers. Gloss card, playlist 1's line: bounce rate · the share of your emails that come back undelivered.
Why does it cost you? They wanted the freebie, not your emails. So they'll never open, and never click. Then the inbox expires. You mail a dead inbox, you get a bounce, and your bounce rate climbs.
04 · Why it costs you: they pile up · 1:00
On screen: the signup form lets card after card through. A stack of burner.invalid cards grows on the list. A mailbox provider's gate reads the stack's label, temporary inboxes, and a reputation gauge dips.
It isn't only the bounces that count against you, though. It's where they come from. Mailbox providers know which domains hand out temporary inboxes. So a pile of bounces from those domains tells them how your list was built. If your signup form doesn't screen them, they pile up, and your sender reputation drops.
05 · Defences one and two · 1:20
On screen: chip 3 lights. The signup form grows two guards, one per click. Guard 1: a confirm email that the throwaway card can't open, so it never joins. Guard 2: a list of disposable domains, and burner.invalid is on it, so the card is turned away. Gloss card, the line from the double opt-in video: double opt-in · people confirm by clicking a link in an email before they join your list.
What are the three defences? One. Use double opt-in, so people have to confirm from a real inbox. Two. Check addresses at signup. There are free lists of disposable domains to check against, so your form can compare each new address before it's accepted.
06 · Defence three · 1:37
On screen: a signup card with a throwaway address on a reserved .example domain, green for a moment. A small timer runs down beside it, the card greys, and the list row beside it stays exactly the same. Then the campaign goes out, and that row comes back coral.
Here's what makes them hard to spot. At signup, a throwaway address looks like any other. It even works, for a while. Then the key card stops working, and the address is dead long before your next campaign. Nothing on your list changes. You find out when it bounces.
07 · Recap · 2:11
On screen: the fading card, the stack and the gauge, the two guards and the pot, the chips lit.
Three moves, then. Turn on double opt-in. Check new addresses against a disposable domain list at signup. And for the ones already in, sort your current list by domain, look for the throwaway ones, and validate before every big send.
08 · Close · 2:25
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 2, no subscribe ask.
Guard the form, and check the list. Your form stops new throwaway signups. A clean catches the ones already in. Or run the same check at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a risky email address?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.007.023-disposable-email-provider.md
00 · The free guide, and a throwaway inbox (hook)
Disposable email providers
the title, Lora, large: "What is a disposable email provider?" Sally's guide goes out to a signup card, gone.in.60.seconds@burner.invalid. The card's inbox icon fades to grey. Sally's next envelope arrives at the grey card. Three numbered chips, the VO's words: 1 what one is · 2 why it costs you · 3 the three defences. Chips 2 and 3 grey.
one card, its inbox fading while the envelopes keep coming. Reveals: (1) the guide goes out, (2) the inbox fades, (3) the next envelope, (4) the chips.
concept disposable-address (M-14, M-12).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What one is
What one is
chip 1 lights. A dispenser hands out inbox cards, one per press, each on burner.invalid. A person takes one, uses it on a signup form, and drops it. Gloss card: disposable email provider · a service that hands out temporary inboxes that soon stop working.
the card's life, a short bar that runs out. No time labels (C29). Reveals: (1) the dispenser, (2) the card used on a form, (3) the card dropped and fading.
concept disposable-address (M-14, M-12). disposable-provider is gloss tier. Proposed: the dispenser.
03 · Why it costs you: no one's there
Why it costs you
chip 2 lights. The signup card from the hook. Two empty engagement ticks beside it (open, click) stay unlit. The card turns coral as it bounces, and a small bounce-rate bar beside it grows, with no numbers. Gloss card, playlist 1's line: bounce rate · the share of your emails that come back undelivered.
two unlit ticks, then one coral card, then a bar that grows. Reveals: (1) the unlit ticks, (2) the card turns coral, (3) the bar grows.
concept hard-bounce (M-15, M-14).
04 · Why it costs you: they pile up
Why it costs you
the signup form lets card after card through. A stack of burner.invalid cards grows on the list. A mailbox provider's gate reads the stack's label, temporary inboxes, and a reputation gauge dips.
the stack's height, then the gauge's drop. Reveals: (1) the cards pile up, (2) the gate reads the label, (3) the gauge dips.
concept sender-reputation (M-33).
05 · Defences one and two
The three defences
chip 3 lights. The signup form grows two guards, one per click. Guard 1: a confirm email that the throwaway card can't open, so it never joins. Guard 2: a list of disposable domains, and burner.invalid is on it, so the card is turned away. Gloss card, the line from the double opt-in video: double opt-in · people confirm by clicking a link in an email before they join your list.
a count of defences, two of three. Reveals: (1) guard 1, (2) guard 2.
concept opt-in (M-14, M-07). double-opt-in is gloss tier.
06 · Defence three
Almanac ids in this scene: 005.007.023
Before you send
a signup card with a throwaway address on a reserved .example domain, green for a moment. A small timer runs down beside it, the card greys, and the list row beside it stays exactly the same. Then the campaign goes out, and that row comes back coral.
one address, alive, then dead, with its row unchanged. Reveals: (1) the green card, (2) the timer runs out, (3) the unchanged row, (4) the coral return.
concept list-cleaning (the dot grid, M-25). The timer: no picture yet.
Q3: moved before the recap. Q2: the pivot comes from this topic (throwaways look normal at signup), no catch-all.
005.007.023 "temporary inboxes which expire within minutes or hours" / "the address expires after a few days. You mail to a dead inbox, you get a bounce" / "Harder to spot if you're not validating at all." C29 (how long they last) is not voiced as a figure.
T6, the pivot before the pitch (R15 shape).
07 · Recap
Three things to remember
the fading card, the stack and the gauge, the two guards and the pot, the chips lit.
callbacks only.
callbacks only.
08 · Close
Validate before you send
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 2, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do (S10). The next video's question is the Almanac's, with its quote marks dropped for the ear (S8). Totals: 10 scenes. 447 spoken words (counted 2026-09-29, taste pass). About 2:50 at 166 words a minute, about 3:02 with scene breaks. Every scene is 20 to 70 words (S2).
V022What is a “risky” email address?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C30 (ledger): when a subscriber counts as inactive.
- C31 (ledger): how many emails a re-engagement run is.
00 · Never bounces, never opens (hook) · 0:00
On screen: the title, Lora, large: "What is a "risky" email address?" kai@driftwood-goods.example as a dot. Envelopes arrive, none bounce, none are opened. Four numbered chips, the VO's words: 1 what makes an address risky · 2 the usual kinds · 3 why it hurts · 4 what to do. Chips 2 to 4 grey.
One address on Sally Send's list has never bounced. It's never opened, either. Not once. And she keeps sending to it, because nothing looks wrong. So what is a risky email address? Four things answer it. What makes an address risky. The usual kinds. Why it hurts. And what to do.
01 · Brought to you by, woven in · 0:18
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A risky address looks fine from the outside, which is why at Review My Emails we check every one before you send.
02 · What makes an address risky · 0:26
On screen: chip 1 lights. the quiet address's dot sits between the three verdict pots, keep, monitor and suppress, and doesn't move toward any of them. One small coral spam flag flickers once. Gloss card, the registry line: risky address · an address that takes your mail without bouncing and never does anything with it.
Start with what makes an address risky. A risky address takes your mail without bouncing, and never does anything with it. Like a house with a working letterbox and the lights always off. It looks fine. It receives mail. And then, nothing. Yet the quietest address on your list can be the one that finally marks you as spam.
03 · Risky is not toxic · 0:49
On screen: two dots side by side. A toxic dot drops a reputation gauge in one sharp fall. Kai's risky dot lowers it a notch at a time, one notch per send.
And risky isn't toxic. A toxic address, like a breached account, destroys your reputation. A risky one quietly drags it down. You keep sending, you see nothing back, and your engagement rate sinks.
04 · The usual kinds · 1:01
On screen: chip 2 lights. Five dots join Kai's in the middle, one per click, each with its tag: catch-all (the gate that waves everyone through, from the myth video), role (admin@saltmarsh-outfitters.example, one door with a crowd behind it), old company domain, expired forward, long inactive. Gloss cards, the registry lines: catch-all domain · a domain that says yes to every address at it, real or not. role-based address · an address tied to a job rather than a person, like info@ or support@.
What are the usual kinds? Catch-all domains, where you can't tell if the person is real. Role addresses, like info at or support at, that change hands. Old company domains, after a downsize or a move. Forwards that have expired. And people who haven't engaged in a long time.
05 · Why it hurts · 1:19
On screen: chip 3 lights. A mailbox provider's gate watches the middle group of dots. A pattern line draws across them, flat. Then the gate narrows for Sally's next send. One dot on its own, the gate stays open. Many dots, it narrows.
Why does it hurt? Mailbox providers don't just check your reputation. They watch engagement. Send to addresses that never open or click, and they notice the pattern. Then they treat your future mail more skeptically. One quiet subscriber isn't a problem. Lots of them are.
06 · What to do · 1:36
On screen: a street of houses, each with a working letterbox. A few have the lights off, and from the street they look the same as the rest. A lamp passes along the street and tags those few amber: catch-all · old company domain.
The trouble is, some risky addresses look exactly like good ones. A catch-all domain, where you don't know if the person is real. An old company domain, after a downsize. The letterbox still takes the post. Nothing on the list tells you which houses are empty.
07 · Recap · 2:20
On screen: the still dot, the five kinds, the narrowing gate, the pots filling, the chips lit.
Your to-do, in order. Sort your list by last open or click, and find the ones gone quiet. Send them a short re- engagement campaign. Remove the ones who don't respond. And at signup, ask for a person's own address, not info at or support at.
08 · Close · 2:37
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, no subscribe ask.
Find them, try to win them back, and let the rest go. Nobody can make an address open. A clean tells you which ones to keep, monitor or suppress. And to see who's still engaged, there's RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a rented list?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.007.009-risky-email-address.md
00 · Never bounces, never opens (hook)
Risky addresses
the title, Lora, large: "What is a "risky" email address?" kai@driftwood-goods.example as a dot. Envelopes arrive, none bounce, none are opened. Four numbered chips, the VO's words: 1 what makes an address risky · 2 the usual kinds · 3 why it hurts · 4 what to do. Chips 2 to 4 grey.
envelopes in, zero bounces, zero opens. Two counters stay at 0. Reveals: (1) the dot, (2) the envelopes, (3) the two zeros, (4) the chips.
concept risky-address (M-25, M-23), the dot that neither greens nor greys.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What makes an address risky
What makes an address risky
chip 1 lights. the quiet address's dot sits between the three verdict pots, keep, monitor and suppress, and doesn't move toward any of them. One small coral spam flag flickers once. Gloss card, the registry line: risky address · an address that takes your mail without bouncing and never does anything with it.
the dot's position, still, in the middle. Reveals: (1) the three pots, (2) the dot stays put, (3) the spam flag flickers.
concept risky-address (M-25, M-23).
03 · Risky is not toxic
What makes an address risky
two dots side by side. A toxic dot drops a reputation gauge in one sharp fall. Kai's risky dot lowers it a notch at a time, one notch per send.
the gauge's drop, one sharp fall against a slow slide. Reveals: (1) the sharp fall, (2) the slow slide.
concept sender-reputation (M-33).
no spam trap named as a toxic example.
04 · The usual kinds
The usual kinds
chip 2 lights. Five dots join Kai's in the middle, one per click, each with its tag: catch-all (the gate that waves everyone through, from the myth video), role (admin@saltmarsh-outfitters.example, one door with a crowd behind it), old company domain, expired forward, long inactive. Gloss cards, the registry lines: catch-all domain · a domain that says yes to every address at it, real or not. role-based address · an address tied to a job rather than a person, like info@ or support@.
a count of five kinds, five dots in the middle. Reveals: (1) to (5) one dot each.
concepts catch-all (M-18, M-15), role-address (M-14, M-07). Callbacks.
05 · Why it hurts
Why it hurts
chip 3 lights. A mailbox provider's gate watches the middle group of dots. A pattern line draws across them, flat. Then the gate narrows for Sally's next send. One dot on its own, the gate stays open. Many dots, it narrows.
the number of still dots against the width of the gate. One dot, open. Many, narrower. No share labelled (N6). Reveals: (1) the flat line, (2) one dot and an open gate, (3) many dots and a narrow gate.
concept engagement-signal (M-15, M-12), mailbox-provider (M-14, M-18).
06 · What to do
Almanac ids in this scene: 005.007.009
Before you send
a street of houses, each with a working letterbox. A few have the lights off, and from the street they look the same as the rest. A lamp passes along the street and tags those few amber: catch-all · old company domain.
a street where a few houses are empty. Reveals: (1) the street, (2) the lamp, (3) the amber tags.
concept catch-all for the first tag. The street: no picture yet.
Q3: moved before the recap. Q1: reworded so no stock pivot line repeats.
005.007.009 "catch-all domains (company.example accepts mail to anyone@company.example, so you don't know if it's real)" / "old corporate domains from companies that downsized or changed email providers" / "It looks valid, it receives mail, and then... nothing."
T6, the pivot before the pitch (R15 shape).
07 · Recap
Four things to remember
the still dot, the five kinds, the narrowing gate, the pots filling, the chips lit.
callbacks only.
callbacks only.
08 · Close
Find them first
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do (S10). Totals: 10 scenes. 477 spoken words (counted 2026-09-29, taste pass). About 3:01 at 166 words a minute, about 3:13 with scene breaks. Every scene is 20 to 70 words (S2).
V023What is a rented list?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- "No picture yet": the fence and its closed gate.
00 · A paid send, and nothing kept (hook) · 0:00
On screen: the title, Lora, large: "What is a rented list?" Two gardens side by side, the owner's full, Sally's own bed empty. Sally hands a seed packet (her email) over the fence. the owner's garden blooms for a moment. Sally's bed stays empty. Three numbered chips, the VO's words: 1 how a rented list works · 2 why it doesn't build your reputation · 3 when it makes sense. Chips 2 and 3 grey.
Sally Send pays a newsletter owner to send her offer to their subscribers. The email goes out. And when it's over, Sally has no new addresses and no new reputation. So what is a rented list? Three questions settle it. How a rented list works. Why it doesn't build your reputation. And when it makes sense.
01 · Brought to you by, woven in · 0:20
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
The list worth building is your own, and that's the one Review My Emails checks, address by address, before you send.
02 · How a rented list works · 0:29
On screen: chip 1 lights. the owner's garden behind a fence. Sally's seed packet goes over the fence and is sown in the owner's beds, by the owner. Sally's side of the fence shows a closed gate: addresses: not yours. Gloss card: rented list · paying someone to send your email to their subscribers, without ever getting the addresses.
Start with how a rented list works. You pay a list owner or a data broker. You give them your message. They send it for you, to their subscribers, from their setup. You never see the addresses. And you can't import them into your own email marketing tool afterwards. It's sowing your seeds in someone else's garden.
03 · Who they said yes to · 0:50
On screen: a reader in the owner's garden holds a card, I opted in to the owner. Sally's email arrives with an unfamiliar name on it. Two outcomes, one per click: a sponsored tag, then a spam? tag in coral.
Even if the list is fully opted in, those people said yes to the list owner. Not to you. To them, your email is from a stranger. At best it looks like a sponsored spot in someone else's newsletter. At worst, spam. How many complaints you get depends on the owner's audience, and how openly they explained the deal.
04 · Why it doesn't build your reputation · 1:12
On screen: chip 2 lights. A reputation gauge above the owner's garden rises with the opens. A second gauge above Sally's own bed doesn't move. The fence stays shut. Gloss card, hygiene video 4's line: sender reputation · the score mailbox providers give you as a sender, based on how you've behaved.
Why doesn't it build your reputation? Because you're borrowing someone else's. The opens and replies on a rented send don't build your domain's sender reputation with mailbox providers. Whatever grows, grows on their side of the fence. When the rental ends, you're exactly where you started.
05 · When it makes sense · 1:29
On screen: the fence from scene 02. Two more gardens appear beside the owner's, signed co-registration and contest, each with the same small tag: permission given to someone else.
And watch for the same deal under other names. Co-registration, where one signup form ticks you in alongside other brands. Contest lists, where people entered to win something. Same basic problem as the garden. The permission was given to someone else.
06 · Recap · 2:08
On screen: the fence, the two gauges, the one sprout, the chips lit.
What to take away. Don't rent a list to grow one. If you rent for awareness, ask how the owner explained the deal to their subscribers. Watch for the same problem in co-registration and contest lists. And put your effort into people who sign up to you directly.
07 · Close · 2:26
On screen: Sally's own bed, the sprout. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
Grow your own list, and keep it clean. Nobody can check a list you never see. We check the one that's yours. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what's the difference between invalid and undeliverable?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.002.006-rented-list.md
00 · A paid send, and nothing kept (hook)
Rented lists
the title, Lora, large: "What is a rented list?" Two gardens side by side, the owner's full, Sally's own bed empty. Sally hands a seed packet (her email) over the fence. the owner's garden blooms for a moment. Sally's bed stays empty. Three numbered chips, the VO's words: 1 how a rented list works · 2 why it doesn't build your reputation · 3 when it makes sense. Chips 2 and 3 grey.
Sally's bed, empty before and after. Reveals: (1) the two gardens, (2) the seed packet over the fence, (3) Sally's bed still empty, (4) the chips.
the garden bed from the re-engagement registry picture (M-03, M-04), reused.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · How a rented list works
How a rented list works
chip 1 lights. the owner's garden behind a fence. Sally's seed packet goes over the fence and is sown in the owner's beds, by the owner. Sally's side of the fence shows a closed gate: addresses: not yours. Gloss card: rented list · paying someone to send your email to their subscribers, without ever getting the addresses.
the fence. Everything that grows stays on the owner's side. Reveals: (1) the packet over, (2) the owner sows it, (3) the closed gate.
the gardens. No picture yet for the fence.
03 · Who they said yes to
How a rented list works
a reader in the owner's garden holds a card, I opted in to the owner. Sally's email arrives with an unfamiliar name on it. Two outcomes, one per click: a sponsored tag, then a spam? tag in coral.
one yes, given to one name. The name on the email doesn't match. Reveals: (1) the opt-in card, (2) the stranger's email, (3) sponsored, (4) spam.
concept opt-in (M-14, M-07), called back from the sending playlist.
04 · Why it doesn't build your reputation
Why it doesn't build your reputation
chip 2 lights. A reputation gauge above the owner's garden rises with the opens. A second gauge above Sally's own bed doesn't move. The fence stays shut. Gloss card, hygiene video 4's line: sender reputation · the score mailbox providers give you as a sender, based on how you've behaved.
two gauges. One moves, Sally's doesn't. Reveals: (1) the owner's gauge rises, (2) Sally's stays put, (3) back to the empty bed.
concept sender-reputation (M-33).
05 · When it makes sense
Almanac ids in this scene: 005.002.004, 005.002.006
When it makes sense
the fence from scene 02. Two more gardens appear beside the owner's, signed co-registration and contest, each with the same small tag: permission given to someone else.
three gardens, one tag. Reveals: (1) co-registration, (2) contest, (3) the shared tag.
the gardens and fence from scene 02.
005.002.006 "co-registration lists and contest lists carry the same fundamental problem of permission that was given to someone else."
T9, one more beat. Scene 05 split so each stays under 70 words (S2). The one-line meaning of co-registration is framing, the Almanac links its own answer 005.002.004.
06 · Recap
Three things to remember
the fence, the two gauges, the one sprout, the chips lit.
callbacks only.
callbacks only.
07 · Close
Grow your own
Sally's own bed, the sprout. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do (S10). No law line. Totals: 9 scenes. 448 spoken words (counted 2026-09-29, taste pass). About 2:49 at 166 words a minute, about 3:00 with scene breaks. Every scene is 20 to 70 words (S2).
V024What’s the difference between invalid and undeliverable?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- GAP-F Settled by R11: scene 04b is the shared "invalid" line, word for word the same as 015.003.013 scene 02b.
- "No picture yet": the desk checkpoint.
00 · Two bounces, not the same (hook) · 0:00
On screen: the title, Lora, large: "What's the difference between invalid and undeliverable?" Two envelopes, both with a coral mark: wren@mailbx.invalid and ossie@kelp-street.example. Three numbered chips, the VO's words: 1 what invalid means · 2 what undeliverable means · 3 why the difference matters. Chips 2 and 3 grey.
Two addresses on Sally Send's list failed. One was never going to work. The other worked fine last month. So what's the difference between invalid and undeliverable? It comes down to three parts. What invalid means. What undeliverable means. And why the difference matters.
01 · Brought to you by, woven in · 0:15
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some addresses were never going to work at all, and Review My Emails catches those before you ever send to them.
02 · What invalid means · 0:23
On screen: chip 1 lights. A road from Sally's desk to a row of doors. Wren's envelope has a label with a gap where the letter should be, and it never leaves the desk. A small letter beside it, addressed 123 Main, no city. Gloss card: invalid · an address that isn't written correctly, or whose domain doesn't exist.
Start with what invalid means. The address breaks the basic rules before it reaches any mail server. Like sending a letter to one twenty three Main, with no city. The postman can't even start. It isn't written in the standard format, or the domain doesn't exist at all.
03 · Catch it before you send · 0:40
On screen: a checkpoint at the desk. Wren's envelope stops there, and drops into the suppress pot.
And you catch those with validation, before you ever hit send. Where do you see them? In your validation results, flagged as invalid, next to each address. Invalid addresses should never reach a server at all.
04 · What undeliverable means · 0:53
On screen: one word card, invalid, held still. It slides first under a checker's lamp at the desk, before the gate, and stamps a malformed address. Then it slides onto a returned bounce slip, mono 550 invalid recipient, on the far side of the gate.
One word, two places. When a checker calls an address invalid, it breaks the basic rules before any mail server sees it. When a bounce says invalid recipient, that's a server's reply, after your mail reached it.
05 · A four or a five · 1:28
On screen: chip 3 lights. Two lanes: invalid · catch at the desk and undeliverable · handle at the door. In the undeliverable lane, the amber slip gets a loop arrow (try again), and the coral slip goes to the pot.
Why does the difference matter? Because they're handled differently. Invalid, catch before you send. Undeliverable, handle as it bounces. Not every rejection is permanent, though. Look at the first digit of the code in your bounce report. A four might clear tomorrow, so give it a few tries. A five is done.
06 · Recap · 1:48
On screen: the road, the envelope stopped at the desk, the envelope at the door, the two lanes, the chips lit.
Two jobs, then. Validate before you send, and remove everything flagged invalid. For the ones that bounce, read the first digit. A five, suppress it. A four, give it a few tries before you decide.
07 · Close · 2:01
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, no subscribe ask.
Catch the invalid ones before you send, and handle the rest as they bounce. No check can stop an address dying later. It tells you which ones are dead now. Rather we did it for you? That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what are common soft bounce reasons?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.007.013-invalid-vs-undeliverable.md
00 · Two bounces, not the same (hook)
Invalid vs undeliverable
the title, Lora, large: "What's the difference between invalid and undeliverable?" Two envelopes, both with a coral mark: wren@mailbx.invalid and ossie@kelp-street.example. Three numbered chips, the VO's words: 1 what invalid means · 2 what undeliverable means · 3 why the difference matters. Chips 2 and 3 grey.
two envelopes, the same coral mark, two different stories. Reveals: (1) the two envelopes, (2) the chips.
concept bounce (M-15, M-18).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What invalid means
What invalid means
chip 1 lights. A road from Sally's desk to a row of doors. Wren's envelope has a label with a gap where the letter should be, and it never leaves the desk. A small letter beside it, addressed 123 Main, no city. Gloss card: invalid · an address that isn't written correctly, or whose domain doesn't exist.
distance travelled, zero. The envelope stops at the start of the road. Reveals: (1) the road, (2) the broken label, (3) it stays at the desk.
the road (M-02, from bounce video 5's lookup). The label: concept email (M-12).
03 · Catch it before you send
What invalid means
a checkpoint at the desk. Wren's envelope stops there, and drops into the suppress pot.
the checkpoint sits at zero distance, where the envelope stopped. Reveals: (1) the checkpoint, (2) into the pot.
concept email-validation (M-12, M-24).
04 · What undeliverable means
Almanac ids in this scene: 005.007.013, 015.003.013
One word, two places
one word card, invalid, held still. It slides first under a checker's lamp at the desk, before the gate, and stamps a malformed address. Then it slides onto a returned bounce slip, mono 550 invalid recipient, on the far side of the gate.
one word, two positions, before the gate and after it. The gate is the difference. Reveals: (1) the word card, (2) at the desk, (3) on the slip.
the gate (concept mailbox-provider, M-14, M-18) and the checking desk. No new picture.
R11 (YT, 2026-09-29): one shared "invalid" line, word for word the same in 005.007.013 and 015.003.013, so the word means the same to a viewer. GAP-F is closed.
005.007.013 "An invalid address fails basic email rules before it even reaches a mail server." / 015.003.013 "The cause is usually a nonexistent mailbox, malformed syntax (missing @, invalid characters, no TLD), or a local policy rule on the recipient server. It's a hard bounce".
05 · A four or a five
Why the difference matters
chip 3 lights. Two lanes: invalid · catch at the desk and undeliverable · handle at the door. In the undeliverable lane, the amber slip gets a loop arrow (try again), and the coral slip goes to the pot.
two lanes, and in the second one, one slip loops and one stops. Reveals: (1) the two lanes, (2) the amber loop, (3) the coral to the pot.
the road, suppression-list (M-23, M-24).
no count of tries (bounce playlist C9). "A few tries" from the answer is not voiced.
06 · Recap
Three things to remember
the road, the envelope stopped at the desk, the envelope at the door, the two lanes, the chips lit.
callbacks only.
callbacks only.
07 · Close
Catch them at the desk
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not do (S10). No "valid" as a verdict. Totals: 9 scenes. 391 spoken words (counted 2026-09-29, taste pass). About 2:26 at 166 words a minute, about 2:37 with scene breaks. Every scene is 20 to 70 words (S2).
V025What are common soft bounce reasons?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- End screen for the last video in the series (PM): settled by the Q sweep (2026-09-30): the next video, V026.
- "No picture yet": the three new slips, the crossed-out 422, the campaign grid.
00 · A pile of soft bounces (hook) · 0:00
On screen: the title, Lora, large: "What are common soft bounce reasons?" A pile of amber slips. Most fade out. Two stay lit. Three numbered chips, the VO's words: 1 the seven usual reasons · 2 the code that doesn't exist · 3 when a soft bounce is a signal. Chips 2 and 3 grey.
Sally Send's report shows a pile of soft bounces. Most of them mean nothing. A few are telling her something about her list. So what are common soft bounce reasons? Three things answer it. The seven usual reasons. The code that doesn't exist. And when a soft bounce is a signal.
01 · Brought to you by, woven in · 0:18
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Sometimes a soft bounce is your list talking, and Review My Emails checks every address on it before you send.
02 · The four everyday ones · 0:27
On screen: chip 1 lights. Seven empty slip slots in a row. Four fill, one per click, each with playlist 1's picture and its code: 451 greylisting, 421 rate limiting, 421 or 451 server error, and last 452 mailbox full. Gloss card, said in the VO too for a viewer from search (Q5): greylisting · a server turning a message away the first time, and accepting it when a real sender tries again.
A soft bounce is a temporary no. Its code starts with a four. Like a shop door with a back in five minutes sign. What are the seven usual reasons? Four are everyday ones. Greylisting, a server turning away a first try on purpose. Rate limiting, where you sent too fast or too much. A server having a bad day. And the classic, a full mailbox.
03 · The three that are new · 0:49
On screen: the last three slots fill: network or DNS blip, connection limit (a row of open lines, one refused), policy deferral (a message held at the gate, not turned away).
And three more. A blip in the network or the DNS on the way, with nothing wrong with the address. Connection limits, where a big provider caps how many connections one IP can hold open. And policy deferrals, where the provider doesn't want the message right now, for a reason that isn't a hard no.
04 · The code that doesn't exist · 1:09
On screen: chip 2 lights. A 422 slip slides into the row, doesn't fit any slot, and gets crossed out. A small label: web code, not email.
One code you can stop chasing, because it doesn't exist. There is no four twenty two in email. That's a web code. If you see it in a bounce log, someone's misreporting, or mixing things up. So don't lose an afternoon on it.
05 · One-off, or a pattern? · 1:26
On screen: chip 3 lights. Two rows of weeks. Marina's row: one amber slip, then green every week after. Ossie's row: amber every week, the row lengthening one week per click, and his mailbox icon filling and never emptying.
When is a soft bounce a signal? A one-off soft bounce means nothing. But the same address soft bouncing week after week is a hygiene signal. The back in five sign that never comes down. Where do you see that? Sort your soft bounces by address, and look for the same ones every send. A mailbox that never clears usually means the person has abandoned it.
06 · Across the whole campaign · 1:50
On screen: one envelope goes in through a door marked accepts everything, and the door closes. Hold. Nothing comes back out. No slip, no notice. Then the checking desk lamp finds the same address and tags it amber, catch-all.
Worse than any soft bounce is the one that never comes back. Some servers accept every address, then quietly drop the mail. No bounce fires, so nothing tells you. That's the kind of address a clean looks for.
07 · Recap · 2:21
On screen: the seven slips, the crossed-out 422, the two week rows, the chips lit.
Here's your routine. Let the one-off soft bounces retry. Sort your soft bounces by address, and look at the ones that repeat. Treat a mailbox that never clears as abandoned. Ignore any four twenty two. And if rate limits spread across a whole campaign, look at your reputation.
08 · Close · 2:39
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V026 (Myths), no subscribe ask.
Let the one-offs retry, and notice the patterns. Cleaning can't fix a rate limit, but it finds the addresses that have quietly gone. Stuck on one right now? Our SOS hotline is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... is a catch-all domain the same as a valid address?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.006.004-common-soft-bounce-reasons.md
00 · A pile of soft bounces (hook)
Soft bounce reasons
the title, Lora, large: "What are common soft bounce reasons?" A pile of amber slips. Most fade out. Two stay lit. Three numbered chips, the VO's words: 1 the seven usual reasons · 2 the code that doesn't exist · 3 when a soft bounce is a signal. Chips 2 and 3 grey.
a pile, most fading, two holding. No counts. Reveals: (1) the pile, (2) most fade, (3) two stay, (4) the chips.
concept soft-bounce (M-15, M-14, M-31).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The four everyday ones
The seven usual reasons
chip 1 lights. Seven empty slip slots in a row. Four fill, one per click, each with playlist 1's picture and its code: 451 greylisting, 421 rate limiting, 421 or 451 server error, and last 452 mailbox full. Gloss card, said in the VO too for a viewer from search (Q5): greylisting · a server turning a message away the first time, and accepting it when a real sender tries again.
a count of seven slots, four filled. Reveals: (1) the seven slots, (2) to (5) one slip each.
playlist 1's slips and pictures (M-15, M-14, M-31, M-18).
03 · The three that are new
The seven usual reasons
the last three slots fill: network or DNS blip, connection limit (a row of open lines, one refused), policy deferral (a message held at the gate, not turned away).
seven of seven slots filled. Reveals: (1) to (3) one slip each.
concept mailbox-provider (M-14, M-18) for the gate.
04 · The code that doesn't exist
The code that doesn't exist
chip 2 lights. A 422 slip slides into the row, doesn't fit any slot, and gets crossed out. A small label: web code, not email.
seven slots full, the eighth slip has nowhere to go. Reveals: (1) the 422 slip, (2) no slot, (3) crossed out.
the slip row.
05 · One-off, or a pattern?
When a soft bounce is a signal
chip 3 lights. Two rows of weeks. Marina's row: one amber slip, then green every week after. Ossie's row: amber every week, the row lengthening one week per click, and his mailbox icon filling and never emptying.
the length of the amber run. One against many. Reveals: (1) Marina's one slip, (2) Ossie's run grows, (3) the full mailbox.
the streak row (playlist 1 video 3 scene 10's picture).
no count of weeks or sends that turns it into a suppression (C9).
06 · Across the whole campaign
Almanac ids in this scene: 005.003.010, 005.008.002, 005.013.008
The one you never see
one envelope goes in through a door marked accepts everything, and the door closes. Hold. Nothing comes back out. No slip, no notice. Then the checking desk lamp finds the same address and tags it amber, catch-all.
the count of returned slips is zero. The empty space where a slip should land is the picture. Reveals: (1) the envelope goes in, (2) nothing returns, (3) the lamp tags it.
concept catch-all (the registry's door that accepts everything) and the checking desk.
Q3: moved before the recap. Q2: a bounce topic, so the catch-all pivot fits, reworded (Q1).
R15 (YT, 2026-09-29): pivot before the pitch, backed by the catch-all and accept-all answers only. "Some servers" and "quietly drop" keep to the Almanac's own "usually do not bounce" (C17 and C18 are not voiced: no count, and no claim that catch-alls never bounce).
005.003.010 "Catch-all servers usually do not bounce. They accept and then silently drop." / 005.008.002 "Every address on the domain accepts mail at the SMTP layer, then the message is dropped" / 005.013.008 "a real validator will identify these domains and flag them accordingly."
07 · Recap
Three things to remember
the seven slips, the crossed-out 422, the two week rows, the chips lit.
callbacks only.
callbacks only.
08 · Close
Notice the pattern
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V026 (Myths), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
says what a clean does not fix (a rate limit, S10). Nothing implies cleaning fixes reputation. Totals: 10 scenes. 494 spoken words (counted 2026-09-29, taste pass). About 3:01 at 166 words a minute, about 3:13 with scene breaks. Every scene is 20 to 70 words (S2).
V026Is a “catch-all domain” the same as a valid address?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- The third kind of catch-all address (scene 04): stays cut, or a held-word-free line goes in.
- How many silent sends (scene 07): option A (five campaigns), option B (two or three sends), or option C (no number).
- C17 (ledger): do catch-all addresses ever bounce?
- "Valid" in the title. The title and hook keep the Almanac question word for word (LESSONS 1.3), so "valid" is heard once, as the viewer's own word.
- Next-video line (scene 09): names "Do bounce rates directly cause blocking?", the next script in this batch.
- "No picture yet" visuals: the three identical reply slips, the curtain over the doors, the flipping report card, the streak row.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Is a catch-all domain the same as a valid address? (hook) · 0:00
On screen: the title question, Lora, large: "Is a catch-all domain the same as a valid address?" Under it, the myth in quotes: "It didn't bounce, so it's good." A stamp tries to land on it, DELIVERABLE, and slides off (the verdict word we use, LESSONS V6. The title keeps the Almanac question). Three numbered chips, the VO's words: 1 what a catch-all is · 2 why your checker can't see past it · 3 what to do with them.
Is a catch-all domain the same as a valid address? Sally Send sent to an address. It didn't bounce. So it's good. Here's the catch. On a catch-all domain, a made-up name doesn't bounce either. Three things to see. What a catch-all is. Why your checker can't see past it. And what to do with them.
01 · Brought to you by, woven in · 0:22
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails flags which addresses sit on a catch-all domain, and that check has to happen before you send.
02 · A server that says yes to everything · 0:31
On screen: chip 1 lights. The door at tidewell-supply.example with the gate open. Two envelopes arrive, marina@tidewell-supply.example and ????@tidewell-supply.example, and both pass. Gloss card: catch-all · a domain that says yes to every address at it, real or not. Behind the gate, three little paths: a person, a folder, a bin.
Start with what it is. A catch-all domain isn't an address at all. It's a server setting. Think of a front desk that signs for any name. Send to a real person at that company. Signed for. Send to a name nobody has, at the same domain. Also signed for. It takes the message, and decides later. Pass it to a person, file it, or drop it.
03 · Why your checker gets a shrug · 0:56
On screen: chip 2 lights. The checking desk sends three questions to the gate. Three reply slips come back, all reading 250 yes, identical. A label drops beside the pile, amber: CATCH-ALL. A struck-through DELIVERABLE fades under it. Gloss card: SMTP handshake · asking the receiving server, without sending, whether a mailbox exists. One word for the thing, "catch-all", in VO and on screen (LESSONS P5). No second label name is shown.
Why does that break your checker? Most checks ask the receiving server a question, without sending anything. Do you have a mailbox with this name? That's an SMTP handshake. A catch-all says yes to every name. So the yes tells you the domain takes mail. Not that a person is behind the address. That's why a good checker labels these catch-all, or unknown. Never DELIVERABLE.
04 · Who's behind the gate · 1:20
On screen: two catch-all gates side by side, each with a door behind it. marina@tidewell-supply.example: a door opens, the envelope goes in, green. kai@driftwood-goods.example: the door stays shut, dust on the step, grey. Then a curtain drops across both gates, and the two doors look the same from the road.
Open question: The third kind of catch-all address is not voiced.
Who's behind that gate, then? Some addresses are real, and someone reads them. Those are fine. Some are real, but abandoned. The mailbox exists, and nobody has looked at it in years. Your emails go nowhere useful. And from the outside, you can't tell which is which. That's the whole problem.
05 · Why "no bounce" means nothing here · 1:39
On screen: the email tool's report card: bounced 0%, delivered 100%, all green. Then the card flips over. Behind it, the envelopes sit unread in a pile behind the gate, and a small gauge beside the mailbox provider door edges down.
Catch-all servers usually don't bounce. They accept, and then sometimes silently drop. So a zero percent bounce rate on these addresses means nothing. Your email tool shows everything as delivered. Your reputation looks fine on the surface, while the mail you send into silence keeps telling mailbox providers that nobody wants it.
06 · Don't delete them all, don't send to them all · 1:59
On screen: chip 3 lights. Two big buttons, both struck through: delete all catch-alls and send to all catch-alls. Between them, a third path lights amber: a short trial.
What do you do? Not the two easy things. Don't suppress every catch-all address. That's too aggressive. A lot of them are real people at real companies, who typed their real work email into your form. And don't just send to all of them either, mixed in with your confirmed addresses. Give them a short trial, in their own segment, then stop.
07 · A short trial, and let engagement decide · 2:22
On screen: Sally's list in mono, a column of company addresses on reserved .example domains, all alike. A magnifier passes over them and finds nothing. Then a probe card goes to each domain, and a few come back amber, catch-all.
Open question: How many silent sends before a catch-all address comes off.
- Option A, 021.002.013 (the main answer)
- Option B, 005.003.010
- Option C, ship without a number
There's one part you can't do yourself. A catch-all domain looks like any other company's domain. Nothing in the address gives it away, unless you happen to recognise the domain. The only way to know is to ask the server, and that's a check you run before you send, not something you read off the list.
08 · Recap · 3:07
On screen: the open gate, the three identical 250 slips, the amber short trial bucket. All three chips lit.
Here's the plan for catch-alls. Treat a catch-all as a setting, not a green light. Put those addresses in their own segment. Give them a short trial. Read the engagement column, not the bounces. And stop mailing the ones that stay silent.
09 · Close · 3:22
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots, and the catch-all dots land in the middle pot, amber. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
Asking every domain before you send is our job at Review My Emails. We tell you which addresses to keep, which to watch, and which to drop, and catch-alls land in watch, never valid. You can run the same check at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. Up next... do bounce rates directly cause blocking?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.013-catch-all-not-valid-myth.md
00 · Is a catch-all domain the same as a valid address? (hook)
The myth
the title question, Lora, large: "Is a catch-all domain the same as a valid address?" Under it, the myth in quotes: "It didn't bounce, so it's good." A stamp tries to land on it, DELIVERABLE, and slides off (the verdict word we use, LESSONS V6. The title keeps the Almanac question). Three numbered chips, the VO's words: 1 what a catch-all is · 2 why your checker can't see past it · 3 what to do with them.
none yet. The stamp that will not stick is the point. Reveals: (1) the question and the myth, (2) the stamp sliding off, (3) the three chips.
concept catch-all (the gate that lets every envelope through, M-18, M-15).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · A server that says yes to everything
What a catch-all is
chip 1 lights. The door at tidewell-supply.example with the gate open. Two envelopes arrive, marina@tidewell-supply.example and ????@tidewell-supply.example, and both pass. Gloss card: catch-all · a domain that says yes to every address at it, real or not. Behind the gate, three little paths: a person, a folder, a bin.
two envelopes in, two through, no difference between them. Reveals: (1) Marina's envelope through, (2) the made-up one through, (3) the three paths behind the gate.
concept catch-all (M-18, M-15).
03 · Why your checker gets a shrug
Why checks can't see
chip 2 lights. The checking desk sends three questions to the gate. Three reply slips come back, all reading 250 yes, identical. A label drops beside the pile, amber: CATCH-ALL. A struck-through DELIVERABLE fades under it. Gloss card: SMTP handshake · asking the receiving server, without sending, whether a mailbox exists. One word for the thing, "catch-all", in VO and on screen (LESSONS P5). No second label name is shown.
a count of reply slips, three, all the same. Same answer to every question is the whole mechanism. Reveals: (1) the questions go out, (2) three identical 250 slips, (3) the amber label, DELIVERABLE struck.
concept email-validation (the envelope through the row of checks, M-12, M-24) meeting catch-all (M-18, M-15). smtp-handshake is gloss tier, no picture yet. Proposed: the three identical slips.
04 · Who's behind the gate
Almanac ids in this scene: 021.002.013
Who's behind the gate
two catch-all gates side by side, each with a door behind it. marina@tidewell-supply.example: a door opens, the envelope goes in, green. kai@driftwood-goods.example: the door stays shut, dust on the step, grey. Then a curtain drops across both gates, and the two doors look the same from the road.
two doors behind one curtain. The curtain makes two different outcomes look identical. Reveals: (1) the read door, (2) the abandoned door, (3) the curtain.
concept catch-all (M-18, M-15) and risky-address (the dot that neither greens nor greys, M-25, M-23) for the abandoned door.
05 · Why "no bounce" means nothing here
No bounce, no news
the email tool's report card: bounced 0%, delivered 100%, all green. Then the card flips over. Behind it, the envelopes sit unread in a pile behind the gate, and a small gauge beside the mailbox provider door edges down.
the front of the card says 0 and 100. The back shows the pile. The difference between the two sides is the lie. Reveals: (1) the green report, (2) the flip, (3) the gauge edging down.
concept delivered-not-inboxed (the clerk signs, then the bin) and sender-reputation (the score gauge, M-33). mailbox-provider (M-14, M-18) for the door.
"usually", never "never" (C17). No inbox placement promise. No spam folder percentage.
06 · Don't delete them all, don't send to them all
What to do
chip 3 lights. Two big buttons, both struck through: delete all catch-alls and send to all catch-alls. Between them, a third path lights amber: a short trial.
two exits closed, one open. Reveals: (1) delete all, struck, (2) send all, struck, (3) the short trial lights.
concept suppression-list (the pot with the lid, M-23, M-24), lid staying open.
07 · A short trial, and let engagement decide
Almanac ids in this scene: 005.003.010, 005.007.012, 021.002.013
Before you send
Sally's list in mono, a column of company addresses on reserved .example domains, all alike. A magnifier passes over them and finds nothing. Then a probe card goes to each domain, and a few come back amber, catch-all.
a list that looks uniform until each domain is asked. Reveals: (1) the list, (2) the magnifier finds nothing, (3) the probes, (4) the amber tags.
concept catch-all (the gate that lets every envelope through). The probe card: video 3's.
021.002.013 "Run your list through a validation tool. Any decent one will return a 'catch-all' or 'accept-all' result for these domains." / "(You can't do this reliably by eye unless you recognise specific domains.)"
T6, the pivot before the pitch (R15 shape).
08 · Recap
The three things
the open gate, the three identical 250 slips, the amber short trial bucket. All three chips lit.
the three identical slips, held.
callbacks only.
09 · Close
Know what you're sending to
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots, and the catch-all dots land in the middle pot, amber. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean only labels addresses. It does not claim to turn a catch-all into a confirmed address, and nothing implies it fixes reputation, SPF, DKIM, DMARC or a blocklist. "Big old import" only, the answer's "list purchase" is left out so the video never sounds like it blesses buying lists. Totals: 11 scenes. 603 spoken words (recounted 2026-09-30, Q sweep). About 3:47 at 166 words a minute, about 4:00 with scene breaks. Every scene is 20 to 70 words (S2).
V027Do bounce rates directly cause blocking?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Thresholds (scene 05): stay out (the script's state), or one number goes in.
- C20 (ledger): how long bounce damage lasts, weeks or months.
- The "Yes, bounces trigger throttling" In short in 015.011.006: worth a look beside 021.006.011, not changed by this script.
- "No picture yet" visuals: the switch, the balance scale, the chain with its narrowing gate, the send bars.
- Next-video line (scene 09): names "Is double opt-in mandatory?", the next script in this batch.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Do bounce rates directly cause blocking? (hook) · 0:00
On screen: the title question, Lora, large: "Do bounce rates directly cause blocking?" A big switch labelled BLOCK sits under it. A bounce slip drops on the switch, and the switch does not move. Three numbered chips, the VO's words: 1 what leads to a block · 2 one send or a pattern · 3 three moves for the moment your bounces spike.
Do bounce rates directly cause blocking? Sally Send's bounces spiked, and she's wondering if Gmail is about to slam the door. Half right. High bounces don't flip a blocking switch on their own. But they do tell mailbox providers something about your list. Here's the path, in three steps. What leads to a block. One send or a pattern. And three moves for the moment your bounces spike.
01 · Brought to you by, woven in · 0:23
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails sorts your list into what to keep, what to watch and what to suppress, before you send.
02 · Hard and soft don't weigh the same · 0:31
On screen: a one-beat callback to playlist 1: the door closing for good and the envelope back at the same door, small, side by side. They slide onto a balance scale. On the left pan, a coral slip on bo.unce@coral-cove.invalid and one on sunk@shipwreck.invalid. On the right pan, two amber soft bounce slips. The left pan sinks hard. Gloss cards: hard bounce · permanent, the address does not work and will not start working. soft bounce · temporary, the server said not right now.
First, not every bounce counts the same. A hard bounce means the address doesn't exist, or the domain is gone. A soft bounce is temporary. A busy server, a short outage. Mailbox providers care much more about the hard ones. Because a pile of dead addresses suggests you're sending to a stale list, or worse, to addresses you bought, not earned.
03 · The chain, not the switch · 0:56
On screen: chip 1 lights. The switch from scene 00 fades for good. In its place a chain builds link by link, left to right: bounces, signal, reputation, and the last link hooks onto the mailbox provider's gate, still wide open. The reputation link carries the score gauge, its needle drifting down. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
What happens instead? Bounces don't cause the block directly. They damage your sender reputation. And reputation is what drives blocking decisions at Gmail, Outlook and Yahoo. It's a chain. Bounces send a signal. The signal lowers your reputation. And a low reputation is what gets you blocked.
04 · The block comes in stages · 1:14
On screen: the same chain, held still. Only the gate at its end changes, narrowing one step per click, with one small label each: slowed · more to spam · closed for now · closed for good. Gloss card: throttling · a server slowing down how fast it accepts your mail.
The block doesn't arrive all at once. It comes in stages, like a door closing slowly, not slamming. First they slow down how much of your mail they take. That's throttling. Then more of it goes to spam. If it keeps going, a temporary block. Repeat it, and the block can be for good. Which means you get warnings, if you know where to look.
05 · One bad send, or a pattern · 1:39
On screen: chip 2 lights. A row of send bars, one per campaign. First pose: one tall coral bar in a row of short ones. Second pose: every bar tall. The gauge from scene 03 barely moves in the first pose and sinks in the second. Third pose: a new segment block snaps onto the list, and the next bar shoots up, with an arrow back to the block labelled where did these come from?
Open question: Bounce-rate levels.
What moves that chain? Rarely one campaign on its own. It's repeated high hard bounces, across multiple sends. That pattern looks like a low quality sender. A sudden spike still matters, though. A big jump right after you add a new segment can speed up the damage. Not because of the number itself, but because of what it says about where those addresses came from.
06 · Three moves, right now · 2:03
On screen: chip 3 lights. Three move cards stack, each with a teal tick as it is said. Card 1: the new segment block unplugs from the list. Card 2: the coral slips drop into the suppress pot, lid closes. Card 3: the amber slips loop back once, twice, and the ones still amber drop into the pot.
What do you do right now? Three moves. One. If a new segment caused the spike, stop sending to it. Seriously, stop. Two. Suppress every hard bounced address, immediately. Don't keep retrying them. Three. Let your tool retry the soft bounces, and suppress the ones that keep failing.
07 · Then watch, and let it recover · 2:20
On screen: the new segment block from scene 05, all its dots the same teal before the send. The send goes out, and a patch of dots turns coral as the bars rise. Then the same block, rewound, with the coral dots found and lifted out before the send.
One part of this you can't see coming. That spike started with a new segment. Before you sent, every address in it looked fine. The dead ones only showed themselves by bouncing, on your domain, in your report. The time to find them was before they went out.
08 · Recap · 3:01
On screen: the chain and its gate from scene 03, small, the row of tall bars, the three move cards. All three chips lit.
When bounces spike, then. It's a chain with stages, not a switch. Stop sending to the segment that caused it. Suppress every hard bounce, straight away. Let your tool retry the soft ones. And watch your next few sends side by side.
09 · Close · 3:18
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
If your list feels stale, clean it before your next send. Review My Emails finds the dead addresses before they go out. Worried about a blocklist? Our free blocklist directory explains each one. Clean your first 1,000 free at reviewmyemails dot com slash get started. Up next... is double opt-in mandatory?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.006.011-bounces-dont-flip-a-block-switch.md
00 · Do bounce rates directly cause blocking? (hook)
The myth
the title question, Lora, large: "Do bounce rates directly cause blocking?" A big switch labelled BLOCK sits under it. A bounce slip drops on the switch, and the switch does not move. Three numbered chips, the VO's words: 1 what leads to a block · 2 one send or a pattern · 3 three moves for the moment your bounces spike.
none yet. The switch that does not flip is the point. Reveals: (1) the question, (2) the slip lands and the switch holds, (3) the three chips.
concept bounce (the envelope handed straight back with a reason slip, M-15, M-18).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Hard and soft don't weigh the same
Hard and soft
a one-beat callback to playlist 1: the door closing for good and the envelope back at the same door, small, side by side. They slide onto a balance scale. On the left pan, a coral slip on bo.unce@coral-cove.invalid and one on sunk@shipwreck.invalid. On the right pan, two amber soft bounce slips. The left pan sinks hard. Gloss cards: hard bounce · permanent, the address does not work and will not start working. soft bounce · temporary, the server said not right now.
the tilt of the scale. The same count of slips on each side, and the hard side sinks. Weight, not count, is the comparison. Reveals: (1) the playlist 1 callback, (2) the hard slips, (3) the soft slips, (4) the scale tips.
concepts hard-bounce (the door closing for good, M-15, M-14) and soft-bounce (the envelope back to the same door, M-15, M-14, M-31), called back from playlist 1, not re-taught. The gloss cards carry playlist 1's own lines. The balance scale: no picture yet.
03 · The chain, not the switch
What leads to a block
chip 1 lights. The switch from scene 00 fades for good. In its place a chain builds link by link, left to right: bounces, signal, reputation, and the last link hooks onto the mailbox provider's gate, still wide open. The reputation link carries the score gauge, its needle drifting down. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
a count of links, three, then the gate. The distance from the first link to the gate is the point: it is never one step. Reveals: (1) to (3) one link per click, (4) the gate, (5) the gauge needle drops.
concept sender-reputation (the score gauge, M-33) and throttling (the gate, M-18, M-15). The chain: no picture yet. This chain and gate are the video's one picture from here to the recap.
04 · The block comes in stages
The stages
the same chain, held still. Only the gate at its end changes, narrowing one step per click, with one small label each: slowed · more to spam · closed for now · closed for good. Gloss card: throttling · a server slowing down how fast it accepts your mail.
the width of the gate, four steps narrower, from open to shut. Reveals: (1) to (4) one narrowing per click.
concept throttling (the gate narrowing, M-18, M-15). No staircase.
05 · One bad send, or a pattern
Almanac ids in this scene: 015.001.015, 015.011.001, 015.011.005, 021.006.011
One send or a pattern
chip 2 lights. A row of send bars, one per campaign. First pose: one tall coral bar in a row of short ones. Second pose: every bar tall. The gauge from scene 03 barely moves in the first pose and sinks in the second. Third pose: a new segment block snaps onto the list, and the next bar shoots up, with an arrow back to the block labelled where did these come from?
bar height is the share that bounced, with no axis labels and no numbers. One tall bar against a row of tall bars is the whole comparison. Reveals: (1) one tall bar, (2) all tall, (3) the new segment and its spike.
concept sender-reputation (M-33). The send bars: no picture yet (same as the bounce playlist's deferral bars).
06 · Three moves, right now
Three moves
chip 3 lights. Three move cards stack, each with a teal tick as it is said. Card 1: the new segment block unplugs from the list. Card 2: the coral slips drop into the suppress pot, lid closes. Card 3: the amber slips loop back once, twice, and the ones still amber drop into the pot.
a count of moves, 3. Reveals: (1) move 1, (2) move 2, (3) move 3.
concept suppression-list (the pot with its lid, M-23, M-24), soft-bounce (M-15, M-14, M-31).
no retry count, the tool decides (R2, R6, Q sweep 2026-09-30: "a few attempts" read as a count). C5 in the bounce playlist.
07 · Then watch, and let it recover
Almanac ids in this scene: 021.006.011
Before the next send
the new segment block from scene 05, all its dots the same teal before the send. The send goes out, and a patch of dots turns coral as the bars rise. Then the same block, rewound, with the coral dots found and lifted out before the send.
the same segment twice, once found after, once before. Reveals: (1) the uniform block, (2) the send and the coral patch, (3) the rewind, found before.
the send bars and segment block from scene 05.
no "weeks", no "months" (C20). The answer's percentage check is left out (scene 05 GAP), replaced by "come back down".
021.006.011 "An 8% spike after adding a purchased list segment is a real problem. Not necessarily because of the number itself, but because of what it tells mailbox providers about your list practices." (the 8% is not voiced) / "The main risk is continuing to send to bad addresses while hoping the situation fixes itself."
T6, the pivot before the pitch (R15 shape). No rate voiced (the GAP after scene 05 stays).
08 · Recap
The recap
the chain and its gate from scene 03, small, the row of tall bars, the three move cards. All three chips lit.
the chain, held.
callbacks only.
09 · Close
Clean your list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/directory, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is about addresses only. Nothing implies it lifts a block, repairs reputation on its own, or fixes SPF, DKIM, DMARC or a blocklist listing. Scene 07 already says recovery comes from sending clean over time. The next-video line assumes the PM orders the c-myths batch as drafted. Totals: 11 scenes. 585 spoken words (recounted 2026-09-30, Q sweep). About 3:40 at 166 words a minute, about 3:53 with scene breaks. Every scene is 20 to 70 words (S2).
V028Is double opt-in mandatory?
waiting on YTOpen questions for YT
- The legal answer (scene 02), HOLD Settled by R7: one sentence, no law named. OFF hold. GAP-C is not voiced here.
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C21 (ledger): how many signups never confirm.
- Framing checks: "for most senders" in the hook (row 1), "keep a record" instead of "you need to" (scene 08), and whether the "skip it" scene may drop the answer's US framing (row 12).
- "No picture yet" visuals: the two paths from one form, the timestamp stamp, the fading dots at the gate, the signup record card, the pale map.
- Episode number and the next-video title: in the Myths series, set by the Video Studio PM.
00 · Is double opt-in mandatory? (hook) · 0:00
On screen: the title question, Lora, large: "Is double opt-in mandatory?" Under it, a signup form with a confirm-your-email gate after it. Three numbered chips, the VO's words: 1 what the click proves · 2 what it costs · 3 the record you keep.
Is double opt-in mandatory? Sally Send has heard it is, everywhere, full stop. So have plenty of senders. The legal answer is short. For most senders, the bigger question isn't legal. It's practical. This one covers three things. What the click proves. What it costs. And the record you keep, whether you use it or not.
01 · Brought to you by, woven in · 0:21
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails checks every address on your list before you send, however your subscribers joined, one click or two.
02 · The legal part · 0:29
On screen: the signup gate from scene 00, with one card beside it: documented consent. No law name, no map, no country on screen.
Legally? Technically no, the big consent laws ask for documented consent, not a confirmation email. Which makes the practical part the real question.
03 · What double opt-in is · 0:37
On screen: Wren's address, wren@mailbox.example, typed into the Double Opt-In Donuts signup form. Two paths split. Top, single opt-in: the dot drops straight onto the list. Bottom, double opt-in: the dot waits amber at the gate, a confirmation email flies out, a click lands, and the dot turns green and joins the list. Gloss cards: double opt-in · asking a second time, by email, before anyone is added. single opt-in · adding someone the moment they sign up, with nothing sent to confirm.
Here's the difference. With double opt-in, a new signup gets a confirmation link, and only joins your list once they click it. With single opt-in, they're in the moment they hit submit.
04 · What the click proves · 0:53
On screen: chip 1 lights. At the gate, wren@mailbx.invalid waits. Its confirmation email goes out, comes back coral, and the typo never joins the list. Then Wren's green dot gets a small stamp: a clock and a tick, confirmed, with the date in mono.
What does that one click prove? More than you'd think. It filters out typos and fake addresses before they reach your list, without checking a thing. A mistyped address can't click a link it never got. And it gives you a timestamped click, like a signature in a guest book, proof that a real person wanted your emails. That matters if you ever face a spam complaint.
05 · Why the click helps your delivery · 1:17
On screen: the confirmed dots on the list. Each one flips as mail arrives, showing opened or clicked. The door at the far end of the road, with its gate, watches the flips.
There's a second half to that. People who confirmed tend to open, click, and rarely complain. And that engagement is what mailbox providers watch. So the click is worth more than clean data.
06 · The honest cost · 1:29
On screen: chip 2 lights. A row of signup dots walks up to the gate. Most pass and turn green. Some stop amber and fade. The ones that fade get small tags: typo, lost interest. Then two stacks side by side: a shorter green stack labelled confirmed, a taller grey stack labelled forgot they signed up, and the green stack's opened flips outnumber the grey stack's.
Now the honest tradeoff. Your list grows more slowly, because some people never click the link. Mostly, they're typos and people whose interest was already gone. And fewer subscribers who confirmed they want you almost always beat a bigger list of people who forgot they signed up.
07 · Skip it, and pay later · 1:48
On screen: the single opt-in path from scene 03. Dots drop straight onto the list, and a few of them are coral. Over time the coral ones grow in number, and a small bounce slip and a small complaint hand appear beside the list.
Skip double opt-in, and nothing stops the junk at the door. Typos, fake addresses, addresses typed in by someone else. So your list hygiene suffers over time. Expect more bounces and more complaints, unless you clean regularly.
08 · The record you keep either way · 2:01
On screen: chip 3 lights. A signup card fills in line by line, mono: when, where, what they were told, what they agreed to. Then Wren's confirmed stamp from scene 04 lands in the corner of the card.
One thing people overlook. Even if you skip double opt-in, keep a record of every signup. When and where they signed up. What they were told. And what they agreed to. Where do you check? Export your contacts, and look for a signup date and a source against every one. The confirmation click just makes that guest book clean, and hard to dispute.
09 · Recap · 2:25
On screen: the gate, the two stacks, the signup card. All three chips lit.
The practical call, then. Decide on double opt-in for practical reasons, not fear. If you skip it, clean regularly, because the junk gets in at the door. And either way, export your contacts and check every one has a signup date, a source, and what they agreed to.
10 · Close · 2:43
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the 021.002.018 myth video, no subscribe ask.
If your list has picked up dead weight, check it before your next send. Review My Emails tells you what to keep, watch or drop, and the same check runs at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. Up next... myth. Double opt-in completely prevents list quality issues. True or false?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.007.014-is-double-opt-in-mandatory.md
00 · Is double opt-in mandatory? (hook)
The myth
the title question, Lora, large: "Is double opt-in mandatory?" Under it, a signup form with a confirm-your-email gate after it. Three numbered chips, the VO's words: 1 what the click proves · 2 what it costs · 3 the record you keep.
none yet. The gate after the form is the object the whole video holds still. Reveals: (1) the question, (2) the form and its gate, (3) the three chips.
concept opt-in (a hand raised at the door before the envelope is sent, M-14, M-07).
no chip promises the legal answer (H6). The legal part is scene 02's one sentence (R7).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The legal part
Almanac ids in this scene: 021.007.014
The legal part
the signup gate from scene 00, with one card beside it: documented consent. No law name, no map, no country on screen.
one card. Reveals: (1) the card.
concept opt-in (M-14, M-07), the gate held.
R7 (YT, 2026-09-29): ONE sentence, no law named. The GAP is closed and the video comes OFF hold. The second sentence is the Almanac's own hand-off, not a legal claim. The Germany exception and GAP-C (Germany or "Germany or Austria") are not voiced, so GAP-C does not reach this video.
021.007.014 "Technically, no... None of those laws specifically require a confirmation email. They require valid, documented consent." / "Outside Germany, the real question isn't legal. It's practical."
03 · What double opt-in is
Almanac ids in this scene: 008.003.006
What it is
Wren's address, wren@mailbox.example, typed into the Double Opt-In Donuts signup form. Two paths split. Top, single opt-in: the dot drops straight onto the list. Bottom, double opt-in: the dot waits amber at the gate, a confirmation email flies out, a click lands, and the dot turns green and joins the list. Gloss cards: double opt-in · asking a second time, by email, before anyone is added. single opt-in · adding someone the moment they sign up, with nothing sent to confirm.
one dot, two paths. The only difference is the wait at the gate. Reveals: (1) the form, (2) the single path, (3) the double path, the click, the dot turns green.
concept opt-in (M-14, M-07). A callback: the two paths from one form are the 008.003.006 short's own frame, reused, not redrawn. The gloss lines stay one line each.
the 008.003.006 short owns single versus double opt-in. This scene points back to it in its own words and does not repeat the short's lines.
04 · What the click proves
Almanac ids in this scene: 021.007.014
What the click proves
chip 1 lights. At the gate, wren@mailbx.invalid waits. Its confirmation email goes out, comes back coral, and the typo never joins the list. Then Wren's green dot gets a small stamp: a clock and a tick, confirmed, with the date in mono.
a count of proofs, two. One dot stopped at the gate, one dot stamped. Reveals: (1) the typo waits, (2) it never gets in, (3) Wren's stamp.
concept opt-in (M-14, M-07). The timestamp stamp: no picture yet.
this scene uses 021.007.014's own two proofs (typos filtered, a timestamped click), not the short's "real, reachable, intentionally subscribed" stamps.
"a spam complaint" only. The answer's "or a GDPR inquiry" is a legal line and waits on the gdpr row.
05 · Why the click helps your delivery
Why it helps
the confirmed dots on the list. Each one flips as mail arrives, showing opened or clicked. The door at the far end of the road, with its gate, watches the flips.
the count of flips that land opened or clicked, shown as dots turning, with no rate labelled. Reveals: (1) the flips, (2) the provider's door watching.
concepts engagement-signal (the envelope flipping to show opened or not) and mailbox-provider (M-14, M-18).
no inbox placement promise. "what mailbox providers watch", never "gets you into the inbox". No complaint rate figure (the sibling's figure is left out).
one line pointing back to the short's deliverability shot, in new words. The short's "completely different signal" run is not repeated.
06 · The honest cost
What it costs
chip 2 lights. A row of signup dots walks up to the gate. Most pass and turn green. Some stop amber and fade. The ones that fade get small tags: typo, lost interest. Then two stacks side by side: a shorter green stack labelled confirmed, a taller grey stack labelled forgot they signed up, and the green stack's opened flips outnumber the grey stack's.
dots that fade at the gate, with no share labelled (C21). Then stack height is list size, and the flips inside each stack are engagement. The shorter stack wins on flips. Reveals: (1) dots through the gate, (2) the ones that fade and their tags, (3) the two stacks, (4) the flips.
concept list-decay (the dot grid, green going grey) reused for the grey stack. The fading dots at the gate: no picture yet.
no drop-off share (C21). "Almost always", never "always".
who doesn't confirm is the short's objection shot, named in one line. The new idea here is this answer's own "fewer confirmed beat a bigger forgotten list".
07 · Skip it, and pay later
If you skip it
the single opt-in path from scene 03. Dots drop straight onto the list, and a few of them are coral. Over time the coral ones grow in number, and a small bounce slip and a small complaint hand appear beside the list.
the count of coral dots on the list, growing one per reveal. No rate labelled. Reveals: (1) dots drop in, some coral, (2) the coral count grows, (3) the bounce slip and the complaint hand.
concepts bounce (the envelope handed back with a slip, M-15, M-18) and complaint-rate (the hand raised to report, M-48, M-25), no rate shown.
08 · The record you keep either way
The record you keep
chip 3 lights. A signup card fills in line by line, mono: when, where, what they were told, what they agreed to. Then Wren's confirmed stamp from scene 04 lands in the corner of the card.
a count of lines on the card, four, filling one per reveal. Reveals: (1) to (4) one line per click, (5) the stamp.
no registry row for a consent record. Proposed: this card. Needs a registry row if YT likes it.
"keep a record", never "the law requires". The answer calls this "the minimum for any decent consent audit trail", which is voiced as a practice, not a legal duty. YT to confirm the framing.
09 · Recap
The recap
the gate, the two stacks, the signup card. All three chips lit.
the two stacks, held.
callbacks only.
10 · Close
Almanac ids in this scene: 021.002.018
Check what's on your list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the 021.002.018 myth video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean is about addresses only. It does not create consent, prove consent, or make a list compliant anywhere, and it never stands in for double opt-in. It fixes no reputation, SPF, DKIM, DMARC or blocklist problem. The next video is 021.002.018, which owns "confirmation doesn't stop time" (batch E review, point 3, S6). This video's old scene 09 on that idea is cut, and the close points forward to it instead. The PM confirms the series order. Totals: 11 scenes. 489 spoken words (recounted 2026-09-30, Q sweep). About 3:08 at 166 words a minute, about 3:21 with scene breaks. Every scene is 20 to 70 words (S2).
V029Myth: Double opt-in completely prevents list quality issues. True or False?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- The sunset window (scene 05): the answer gives 90 to 180 days.
- The YouTube title: the Almanac question is a true-or-false line.
- "No picture yet" visuals: the confirmed stamp, the interest line peaking at the click.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Clean for good? (hook) · 0:00
On screen: the title, Lora, large: "Myth: Double opt-in completely prevents list quality issues." Under it, Wren's green dot passes the signup gate and a confirmed stamp lands on it. On "No", the dot starts to grey under the stamp, and the stamp stays put. Three numbered chips, the VO's words: 1 what that click protects you from · 2 the three problems it can't stop · 3 what to do after someone confirms. Chips 2 and 3 grey.
Sally Send turned on double opt-in. Every subscriber clicked confirm. So her list is clean for good, right? No. Double opt-in doesn't completely prevent list quality issues. Here's why, in three parts. What that click protects you from. The three problems it can't stop. And what to do after someone confirms.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails shows you what's gone stale on your list before you send, however carefully your subscribers joined in the first place.
02 · What the click protects you from · 0:26
On screen: chip 1 lights. At the signup gate, three dots stop and fade: typo, fake, impulse. Wren's dot passes, green. Gloss card: double opt-in · asking a second time, by email, before anyone is added.
Start with what that click protects you from. Double opt-in is one of the best things you can do for list quality. It protects you from fake addresses, typos, and people who signed up on impulse and forgot straight away. So your bounce rate stays lower, and you've got proof they said yes. It's a photo of that person, on the day they joined.
03 · Three problems it can't stop · 0:50
On screen: chip 2 lights. Three cards, one per problem, each holding one green dot with its confirmed stamp. Time runs along the bottom, and each dot greys on its card, stamp still on: a dot greying after one envelope, kai@driftwood-goods.example greying, and a dot holding a gift tag that greys and walks off. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
Open question: A fourth problem, role addresses.
- Option A, voice the main answer's fourth problem
- Option B, the sibling's side
A photo doesn't age. People do. Three problems show up after the click. People who confirmed, then went cold after the welcome email. Addresses that worked at signup, and were abandoned later. And people who only wanted the freebie or the discount. Enough of those, and your sender reputation takes a hit, even though you did everything right.
04 · Use the moment they confirm · 1:12
On screen: chip 3 lights. A line graph of interest over time with no axis numbers. It peaks at the confirm click, and a row of welcome envelopes sits right under the peak. Then one dot that never opens gets an amber flag early on the timeline.
What's the follow-up? Start with the welcome. The confirmation click is the peak of someone's interest. Don't waste it on one bland email. Send a strong welcome series. And track engagement from day one. Where? In your email marketing tool, sort subscribers by the date they confirmed, and look at who has never opened since. Act on those early.
05 · Ask, then let go · 1:34
On screen: a wall of subscriber cards, each with the same green confirmed stamp and a small photo. Time passes, the stamps stay green. Then a send goes out, and some cards come back coral, their photos still smiling.
Your list won't show you one thing. Every one of those addresses still carries its confirmed stamp. The ones that were abandoned later look exactly like the ones still in use. Someone changed jobs, or switched providers, and the photo on file never changed. You only find out when you send.
06 · Recap · 2:15
On screen: the stamped dots going grey, the three cards, the question envelope. All three chips lit.
Put that together. Keep double opt-in, it's the best start there is. Send a real welcome series. Check from day one who never opens. Ask the quiet ones if they still want to hear from you. And let go of the ones who don't answer.
07 · Close · 2:32
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
If you're not sure how stale your list has become, check it before your next send. Review My Emails sorts what's worth keeping, and the check is called RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... do email warmup tools build real reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.018-double-opt-in-not-forever-myth.md
00 · Clean for good? (hook)
Almanac ids in this scene: 021.007.014
The myth
the title, Lora, large: "Myth: Double opt-in completely prevents list quality issues." Under it, Wren's green dot passes the signup gate and a confirmed stamp lands on it. On "No", the dot starts to grey under the stamp, and the stamp stays put. Three numbered chips, the VO's words: 1 what that click protects you from · 2 the three problems it can't stop · 3 what to do after someone confirms. Chips 2 and 3 grey.
one dot, one stamp. The stamp holds still, the dot's colour is the one thing that changes. Reveals: (1) the title, (2) the stamp lands, (3) the dot starts to grey, (4) the three chips.
concept opt-in (a hand raised at the door, M-14, M-07), the signup gate from the 021.007.014 script. The stamp that does not keep the dot green is the myth picture and the thumbnail (M2). No TRUE or FALSE boxes.
the turn is "No." (M1). The other script in this batch uses "Here's the catch."
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What the click protects you from
Almanac ids in this scene: 021.007.014
What the click protects
chip 1 lights. At the signup gate, three dots stop and fade: typo, fake, impulse. Wren's dot passes, green. Gloss card: double opt-in · asking a second time, by email, before anyone is added.
a count of what the gate stops, three kinds, each fading at the gate. Reveals: (1) to (3) one faded dot per kind, (4) Wren passes.
concept opt-in (M-14, M-07). double-opt-in is gloss tier. The gate from 021.007.014.
"proof they said yes if anyone ever asks" states no law and no legal duty.
03 · Three problems it can't stop
Almanac ids in this scene: 008.003.002, 021.002.018
Three problems it can't stop
chip 2 lights. Three cards, one per problem, each holding one green dot with its confirmed stamp. Time runs along the bottom, and each dot greys on its card, stamp still on: a dot greying after one envelope, kai@driftwood-goods.example greying, and a dot holding a gift tag that greys and walks off. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
a count of problems, three, every one carrying a confirmed stamp that stops none of them greying. No rate on screen (ledger C13). Reveals: (1) time starts, (2) to (4) one card per click, each dot greying on it.
concept list-decay (dots going grey, M-25, M-22) on each card. One scene, one picture that changes (batch E review, point 2).
04 · Use the moment they confirm
What to do after
chip 3 lights. A line graph of interest over time with no axis numbers. It peaks at the confirm click, and a row of welcome envelopes sits right under the peak. Then one dot that never opens gets an amber flag early on the timeline.
the height of the interest line, highest at the click. The welcome series sits under the peak, not after the slope. Reveals: (1) the peak, (2) the welcome row, (3) the early flag.
engagement-signal (M-15, M-12). The interest line: no picture yet.
05 · Ask, then let go
Almanac ids in this scene: 021.002.018
Before you send
a wall of subscriber cards, each with the same green confirmed stamp and a small photo. Time passes, the stamps stay green. Then a send goes out, and some cards come back coral, their photos still smiling.
the same stamp on every card, then the few that return. Reveals: (1) the wall, (2) time passes, (3) the send and the coral returns.
concept list-cleaning (the dot grid, M-25), drawn as cards. No picture yet for the photo cards.
no day count on the window (see Open for YT).
021.002.018 "Someone who confirmed their subscription two years ago might have changed jobs, switched email providers, or simply lost interest." / "Addresses that were valid at signup but became inactive or abandoned over time".
T6, the pivot before the pitch (R15 shape). C27 (role addresses) is not voiced.
06 · Recap
The recap
the stamped dots going grey, the three cards, the question envelope. All three chips lit.
the stamped grey dots, held.
callbacks only.
07 · Close
Almanac ids in this scene: 021.009.007
See what's gone stale
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean sorts addresses. It does not re-engage anyone, create consent, or replace the welcome series, the re-engagement or the sunset policy. It fixes no reputation, SPF, DKIM, DMARC or blocklist problem. The next-video line names 021.009.007, the other script in this batch. Totals: 9 scenes. 463 spoken words (recounted 2026-09-30, Q sweep). About 2:53 at 166 words a minute, about 3:04 with scene breaks. Every scene is 20 to 70 words (S2).
V030Do email warmup tools build real reputation?
checkedOpen questions for YT
- Ledger RULE-1: the warmup answers 021.009.007 and 010.007.002 recommend the tools, against the hard content rule.
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Warmup pool gloss: no registry row exists.
- "No picture yet" visuals: the dashboard, the ring of inboxes, the history bar, the two tick timelines.
- Episode number and the next-video title: in the Myths series, set by the Video Studio PM.
00 · Do warmup tools build real reputation? (hook) · 0:00
On screen: the title question, Lora, large: "Do email warmup tools build real reputation?" Under it, Sally's dashboard: an opens line climbing, complaints 0. A REPUTATION stamp tries to land on the dashboard and slides off. Three numbered chips: 1 what they do · 2 why providers see through it · 3 where real reputation comes from.
Do email warmup tools build real reputation? Sally Send has a brand new sending address. A warmup tool switches on, and soon her dashboard shows healthy opens and zero complaints. So her reputation is built, right? Only on paper. Three questions unpack it. What those tools do. Why mailbox providers see through them. And where the reputation that lasts comes from.
01 · Brought to you by, woven in · 0:22
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Real reputation comes from real readers, and Review My Emails checks that the addresses on your list are real ones.
02 · What a warmup tool does · 0:31
On screen: chip 1 lights. Sally's inbox joins a ring of faceless grey inboxes. Envelopes loop around the ring. Each one flips to opened, then clicked, then a small arrow lifts one out of a spam tray. Every flip is grey, not green. Gloss card: warmup pool · other users' inboxes that open and click each other's mail automatically.
Start with what a warmup tool does. It puts your inbox into a warmup pool, a network of other people using the same service. Your address sends to them, and their inboxes open it, click it, and even pull it out of spam, all automatically. You do the same for them. It's a rehearsal with an audience paid to clap. Engagement, made, not earned.
03 · History is not reputation · 0:54
On screen: one picture. The score gauge, reputation, and under it a thin bar, history, growing under Sally's address. The needle holds still the whole time the bar grows.
And it does something. A new address with some sending history looks less cold than one with none at all. But that's infrastructure history. It isn't the reputation that keeps you in the inbox. Those two aren't the same thing, and mixing them up leads to real deliverability problems.
04 · Why providers see through it · 1:12
On screen: chip 2 lights. Two timelines, one above the other. Top, warmup pool: grey click ticks, evenly spaced, the same few inboxes repeating. Bottom, people: green ticks scattered, some bunched, some far apart, many different faces. A magnifying glass passes over the top line, and its ticks fade to half weight.
Why doesn't it count for more? Because mailbox providers are increasingly wise to it. A small pool of addresses, the same ones again and again, all clicking at similar times. That doesn't look like people. People are messy. Some providers discount warmup traffic in their models.
05 · Where real reputation comes from · 1:29
On screen: chip 3 lights. Marina and Finn at their doors. Marina's envelope flips green, opened, then replied. Finn adds Sally to a small contacts card. The gauge needle climbs, a step per green flip. Gloss card: positive engagement · opens, clicks, replies, and moving your mail to the inbox.
Where does real reputation come from? The strongest signal is the one no pool can fake. A reply. Someone opens your email because they wanted it, and writes back. They add you to their contacts. They don't hit spam. Replies count for a lot, because they can't be faked by an image loading on its own. That's the real audience, and no tool can manufacture it.
06 · What builds reputation that lasts · 1:54
On screen: Sally's new address, its small history bar from the pool. The first real send goes out to her list, and a scatter of coral returns hits the bar, which dips with each one. The list itself looked uniform beforehand.
The dashboard won't show you what comes next. When the rehearsal ends, your first real sends go out on a brand new address, with no track record to cushion them. Every dead address on that list is a hard bounce, landing on the newest thing you own. And you can't tell which ones are dead by looking.
07 · Recap · 2:34
On screen: the grey ring, the two timelines, Marina's green reply. All three chips lit.
Here's the takeaway. Treat a warmup tool's numbers as rehearsal, not reviews. Send to your real audience, people who gave you permission. Get your authentication in place. Start with the readers most likely to open and reply. And watch the replies, because those are the ones that count.
08 · Close · 2:53
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next video, 021.002.005 "Do purchased lists ever work?", no subscribe ask.
Before you build up any new address, make sure the list you're sending to is real. Review My Emails checks every address first. Stuck on one right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... do purchased lists ever work?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.009.007-warmup-tools-not-real-reputation-myth.md
00 · Do warmup tools build real reputation? (hook)
Almanac ids in this scene: 021.002.013
The myth
the title question, Lora, large: "Do email warmup tools build real reputation?" Under it, Sally's dashboard: an opens line climbing, complaints 0. A REPUTATION stamp tries to land on the dashboard and slides off. Three numbered chips: 1 what they do · 2 why providers see through it · 3 where real reputation comes from.
none yet. The stamp that will not stick is the point. Reveals: (1) the question, (2) the dashboard, (3) the stamp slides off, (4) the three chips.
concept sender-reputation (the score gauge, M-33) with the dashboard in front of it.
no tool named. The turn is "Only on paper." (M1, varied: "Here's the catch" stays with 021.002.013 only).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What a warmup tool does
What they do
chip 1 lights. Sally's inbox joins a ring of faceless grey inboxes. Envelopes loop around the ring. Each one flips to opened, then clicked, then a small arrow lifts one out of a spam tray. Every flip is grey, not green. Gloss card: warmup pool · other users' inboxes that open and click each other's mail automatically.
a ring of identical inboxes, envelopes looping round it. Grey flips, never green, because no person chose them. Reveals: (1) Sally joins the ring, (2) the envelopes loop, (3) the flips, (4) the spam rescue.
concept engagement-signal (the envelope flipping, M-15, M-12), drawn grey. The ring: no picture yet, proposed as a mechanism drawing, never a product (rule 9). warmup pool has no registry row. Proposed as a gloss row.
03 · History is not reputation
History is not reputation
one picture. The score gauge, reputation, and under it a thin bar, history, growing under Sally's address. The needle holds still the whole time the bar grows.
a growing bar under a still needle. One gauge, one thing changing. Reveals: (1) the gauge, (2) the history bar grows beneath it, needle still.
concept sender-reputation (M-33). The history bar: no picture yet.
describes what the tools do, never suggests using them. "looks less cold" is the answer's "looks better than a cold IP with no history", voiced neutrally.
04 · Why providers see through it
Why providers see through it
chip 2 lights. Two timelines, one above the other. Top, warmup pool: grey click ticks, evenly spaced, the same few inboxes repeating. Bottom, people: green ticks scattered, some bunched, some far apart, many different faces. A magnifying glass passes over the top line, and its ticks fade to half weight.
tick spacing. Even and repeating against scattered and varied is the whole comparison. No counts, no times. Reveals: (1) the pool line, (2) the people line, (3) the glass, the pool ticks fade.
concept mailbox-provider (the door with its gate, M-14, M-18) holding the glass. The two timelines: no picture yet.
05 · Where real reputation comes from
Where real reputation comes from
chip 3 lights. Marina and Finn at their doors. Marina's envelope flips green, opened, then replied. Finn adds Sally to a small contacts card. The gauge needle climbs, a step per green flip. Gloss card: positive engagement · opens, clicks, replies, and moving your mail to the inbox.
green flips from named people, and the needle moving one step per flip. Compare the still needle in scene 03, the same gauge. Reveals: (1) Marina opens, (2) Marina replies, (3) Finn adds the contact, (4) the needle climbs.
concepts engagement-signal (M-15, M-12), sender-reputation (M-33). positive-engagement is gloss tier.
06 · What builds reputation that lasts
Almanac ids in this scene: 005.008.001, 018.006.004, 021.008.005, 021.009.007
Before the first real send
Sally's new address, its small history bar from the pool. The first real send goes out to her list, and a scatter of coral returns hits the bar, which dips with each one. The list itself looked uniform beforehand.
a thin history bar, dented by the first real bounces. Reveals: (1) the thin bar, (2) the send, (3) the coral hits and the dip.
concept sender-reputation (the score gauge, M-33).
"build it up gradually" is warming up the address with real readers (021.008.005, 018.006.004), never a tool. No volumes, no week counts.
005.008.001 "Every message you send to a dead domain is a hard bounce." / 021.009.007 "A new IP that suddenly has good open rates and no complaints looks better than a cold IP with no history at all." "No track record to cushion them" is framing on "infrastructure history, not reputation".
T6, the pivot before the pitch (R15 shape).
07 · Recap
The recap
the grey ring, the two timelines, Marina's green reply. All three chips lit.
the two timelines, held.
callbacks only.
08 · Close
Almanac ids in this scene: 021.002.005
Start with real readers
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next video, 021.002.005 "Do purchased lists ever work?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed, the pots carry no counts.
concept list-cleaning (M-25, M-23, M-24).
the clean checks addresses. It does not build reputation, replace warming up, or fix SPF, DKIM, DMARC or a blocklist. The next video is named by its Almanac question word for word (S8, added in the Q sweep 2026-09-30). Totals: 10 scenes. 522 spoken words (recounted 2026-09-30, Q sweep). About 3:12 at 166 words a minute, about 3:24 with scene breaks. Every scene is 20 to 70 words (S2).
V031Do purchased lists ever work?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- Three reasons, not four. The trap reason is cut (held word).
- "No picture yet" visuals: the two counters, the terms sheet.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Do purchased lists ever work? (hook) · 0:00
On screen: the title question, Lora, large: "Do purchased lists ever work?" Sally's small green list. A big grey block of dots slides in beside it, labelled 50,000. A counter above reads list size, jumps, and a second counter, opens, does not move at all. Three numbered chips: why nobody opens · what it costs you · what grows a list that lasts.
Do purchased lists ever work? Sally's list is small. A seller offers her fifty thousand addresses, ready to send tonight. Instant list size. What's the harm? It isn't the shortcut it looks like. Let's go through three things. Why nobody opens. What it costs you. And what grows a list that lasts.
01 · Brought to you by, woven in · 0:18
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
If you've inherited a list you're not sure about, Review My Emails checks every address on it before you send.
02 · The grain of truth · 0:27
On screen: the grey block and Sally's small green list side by side. The camera zooms in on the grey block until single dots are visible. None of them has a face.
Let's be fair about why it's tempting. A bigger list feels like more reach, and it's there tonight instead of next year. But the size isn't the problem. Who's on it is. Picture walking into a party and handing your business card to everyone in the room, whether they asked for it or not.
03 · Nobody on that list asked · 0:46
On screen: chip 1 lights. On Sally's own list, each green dot has a small raised hand behind it, the hand that asked. The grey block has no hands at all. Sally's envelope reaches the grey dots, and a few hands go up, this time to report. Gloss card: opt-in · a person actively asking to receive your mail, rather than being added without being asked.
Why doesn't anyone open? Because nobody at that party asked for your card. They never opted in. Your email arrives from a name they've never seen. They have zero reason to open it. And they have every reason to hit report spam, which is the party guest complaining to the host.
04 · The complaints hit everyone · 1:05
On screen: chip 2 lights. The score gauge above Sally's domain. Each report hand pulls the needle down a notch. Then the dim spreads from the grey block across to Sally's green list, and Marina's and Finn's envelopes start dropping into the spam tray too. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
What does it cost you? Here's what people miss. Even a small number of spam complaints hurts your sender reputation. Mailbox providers track complaints closely. And once they climb, your deliverability starts to suffer across your entire sending domain. Not just for those addresses. For EVERYONE you send to.
05 · The data is old · 1:23
On screen: chip 2 stays lit. The grey block ages. Dots go coral one at a time, and sunk@shipwreck.invalid is one of them. A pile of bounce slips grows beside the block, and the tray arrow slides one step away from the inbox.
There's a second problem. Purchased lists are usually old. Addresses that worked two years ago have been abandoned since. So hard bounces pile up fast. And a high bounce rate tells inbox providers your list hygiene is poor. They use that signal to push your mail further from the inbox.
06 · Your email tool will likely stop you · 1:41
On screen: chip 2 stays lit. The sending desk. A terms sheet on the desk, one line lit: no purchased lists. The bounce slips and report hands reach the desk, and the desk's lamp goes out.
Your email marketing tool will likely step in too. Most reputable ones ban purchased lists in their terms, and when complaints or bounces spike, they can suspend your account. So the list that was meant to grow your reach can cost you your domain's reputation AND your account, at the same time.
07 · What grows a list that lasts · 2:01
On screen: Sally's fifty thousand as a dot grid, every dot the same teal. A scan line passes over it and some dots turn coral: made up · scraped · abandoned. Before the scan, nothing told them apart.
On a bought list, every address looks the same. But some were made up, or scraped. Some worked two years ago and were abandoned since. Nothing on the page tells you which. You find out when they bounce, and by then the damage is done.
08 · Recap · 2:36
On screen: the grey block with no hands, the dim spreading, the green list growing. All three chips lit.
Instead, then. Don't buy the list, however cheap or ready it looks. Grow through real opt-ins, even slowly. And if you've already sent to a bought list, or inherited one, stop, and check it before the next send.
09 · Close · 2:52
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
Already sent to a list like that? Check it before you send anything else. RME Clean, our list check, sorts what's worth keeping from what isn't. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... can I use multiple SPF records?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.005-purchased-lists-dont-work-myth.md
00 · Do purchased lists ever work? (hook)
The myth
the title question, Lora, large: "Do purchased lists ever work?" Sally's small green list. A big grey block of dots slides in beside it, labelled 50,000. A counter above reads list size, jumps, and a second counter, opens, does not move at all. Three numbered chips: why nobody opens · what it costs you · what grows a list that lasts.
two counters. One jumps, one stays still. The still one is the myth failing (M2). Reveals: (1) the question, (2) the grey block arrives, (3) the size counter jumps, (4) the opens counter holds, (5) the chips.
concept list-hygiene (the house held up by people, M-09, M-07, M-10), with the grey block as a floor of people who are not there.
the chip words are the VO promise, word for word (H5). The turn is varied per video (M1). 50,000 is an example size with no source claim, and no rate is shown.
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The grain of truth
Almanac ids in this scene: 021.002.001
Why it's tempting
the grey block and Sally's small green list side by side. The camera zooms in on the grey block until single dots are visible. None of them has a face.
zoom in to prove the detail (N3). The block is big from far away and empty up close. Reveals: (1) side by side, (2) the zoom.
list-hygiene floor as scene 00.
M4, the grain of truth first. Calls back 021.002.001 (bigger lists) in one line, it does not repeat it.
03 · Nobody on that list asked
Why nobody opens
chip 1 lights. On Sally's own list, each green dot has a small raised hand behind it, the hand that asked. The grey block has no hands at all. Sally's envelope reaches the grey dots, and a few hands go up, this time to report. Gloss card: opt-in · a person actively asking to receive your mail, rather than being added without being asked.
raised hands. On the green list, every dot has one. On the grey block, none, until the report hands. Reveals: (1) the green hands, (2) the grey block with none, (3) the report hands go up.
concept opt-in (a hand raised at the door, M-14, M-07), then complaint-rate (the few who raise a hand to report, M-48, M-25).
04 · The complaints hit everyone
What it costs you
chip 2 lights. The score gauge above Sally's domain. Each report hand pulls the needle down a notch. Then the dim spreads from the grey block across to Sally's green list, and Marina's and Finn's envelopes start dropping into the spam tray too. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
the needle drops one notch per hand, then the dim crosses from grey to green. No rate on the gauge (N6). Reveals: (1) the needle drops, (2) the dim spreads, (3) Marina's and Finn's mail hits the tray.
concepts sender-reputation (the score gauge, M-33) and inbox-placement (the trays, M-37, M-18).
no figure for "climb". The In short's threshold is left out (N6). One caps word (V4).
05 · The data is old
What it costs you
chip 2 stays lit. The grey block ages. Dots go coral one at a time, and sunk@shipwreck.invalid is one of them. A pile of bounce slips grows beside the block, and the tray arrow slides one step away from the inbox.
the count of coral dots rising, and the slip pile growing with it. No rate. Reveals: (1) the block ages, (2) coral dots, (3) the slip pile, (4) the tray arrow slides.
concepts list-decay (dots going grey, M-25, M-22) drawn coral, and hard-bounce (the door closing for good, M-15, M-14).
the answer's "recycled by providers, or turned into spam traps" is cut, held word.
06 · Your email tool will likely stop you
What it costs you
chip 2 stays lit. The sending desk. A terms sheet on the desk, one line lit: no purchased lists. The bounce slips and report hands reach the desk, and the desk's lamp goes out.
two losses at once, the gauge from scene 04 and the desk lamp. Reveals: (1) the terms line, (2) the spike reaches the desk, (3) the lamp goes out.
concept esp (the sending desk, M-02, M-12).
"email marketing tool", never "ESP" (V5). No tool named, though the answer names three.
07 · What grows a list that lasts
Almanac ids in this scene: 005.006.008, 021.002.005
Before you send
Sally's fifty thousand as a dot grid, every dot the same teal. A scan line passes over it and some dots turn coral: made up · scraped · abandoned. Before the scan, nothing told them apart.
one uniform grid, then the few that were never what they seemed. Reveals: (1) the uniform grid, (2) the scan, (3) the coral dots with their tags.
concept list-cleaning (the dot grid, M-25).
005.006.008 "The address was fabricated (data append, purchased list, scraped contact)" / 021.002.005 "Purchased lists are usually old. Addresses that were valid two years ago are now abandoned" / "Hard bounces pile up fast".
T6, the pivot before the pitch (R15 shape). Spam traps are not voiced (hard content rules).
08 · Recap
The recap
the grey block with no hands, the dim spreading, the green list growing. All three chips lit.
the two counters, held.
callbacks only (S5).
09 · Close
Check what you've got
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
a clean checks addresses. It never turns a bought list into people who asked, never creates consent, and never makes a purchased list safe to send. The close speaks only about an inherited list you're unsure of, as the answer does, and never about buying one. Totals: 11 scenes. 502 spoken words (recounted 2026-09-30, Q sweep). About 3:11 at 166 words a minute, about 3:25 with scene breaks. Every scene is 20 to 70 words (S2).
V032Can I use multiple SPF records?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C23 (ledger): "DNS only allows one SPF record" against "DNS itself imposes no cap".
- Include gloss: no registry row.
- "No picture yet" visuals: the ten-slot lookup counter.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Can I use multiple SPF records? (hook) · 0:00
On screen: the title question, Lora, large: "Can I use multiple SPF records?" Three sending desks line up behind the gate at inkwell-tide.example. Each desk pins its own guest list to the gate. Three lists hang there, and the gate does not open. Three numbered chips: why two records fail · how to fit every sender into one · the limit to watch.
Can I use multiple SPF records? Sally Send's domain has its own mail server, an email marketing tool, and a help desk, all sending as it. So each one gets its own SPF record, right? That's the one move that breaks it. Three things to know. Why two records fail. How to fit every sender into one. And the limit to watch.
01 · Brought to you by, woven in · 0:22
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Your SPF record is yours to fix, and the addresses on your list are what we check at Review My Emails, before you send.
02 · The guest list, in one line · 0:31
On screen: one sending desk slides up to the gate. A light runs down one guest list, finds the desk's name, and the gate opens, teal. Gloss card: SPF · a record at your domain listing which servers are authorized to send mail on its behalf.
Quick reminder. SPF is the guest list your domain publishes. It names the servers allowed to send as you. At the gate, the receiving server checks the sender against that list.
03 · Why two records fail · 0:42
On screen: chip 1 lights. Two guest lists pinned at the same gate. A light flicks from one to the other, then goes out. The gate stays shut and turns coral, stamped in plain words: SPF fails.
Why can't each tool bring its own list? Because a domain gets one SPF record. Publish two, and the receiving server doesn't pick the better one. It sees a conflict, and SPF fails entirely.
04 · What it breaks · 0:55
On screen: all three desks now wait at the shut gate, each envelope stamped coral. Beside the gate, the DMARC instruction card has two slots, SPF and DKIM. The SPF slot goes dark. Gloss card: DMARC · a policy on top of SPF and DKIM saying what a receiving server should do when a message fails.
And it isn't just the new tool that fails. SPF fails for every message from your domain, even the senders that were fine yesterday. Your DMARC check loses its SPF path too, so it leans on DKIM alone. Mail that should pass can end up looking unauthorized.
05 · How it happens · 1:12
On screen: a DNS case file for inkwell-tide.example opens. One SPF line sits in it. A second line is written in below it by a different hand. Nobody looks up.
This happens more often than you'd think. A new tool comes along, someone adds its own record, and nobody checks what's already there. Nobody did anything silly. It just piles up. So check what's there now. Our free SPF checker shows your record, and whether it's valid, in about thirty seconds.
06 · One list with everyone on it · 1:30
On screen: chip 2 lights. The two lists fold into one. Three names now sit on a single guest list, one line per desk. A light reads it once, and the gate opens for all three desks, teal. Gloss card: include · a line inside your SPF record that brings in one sending service's servers.
What's the fix? One record, with everyone on it. You combine every sender into a single SPF record. Each one gets its own line inside that record, called an include. Receiving servers check it once, and get the full picture.
07 · The limit to watch · 1:45
On screen: the guest list from scene 06, crowded, a lookup counter reading 11. One tool's name is struck off, with a small tag only replies in its own screen. The counter drops. Then another name moves across to a second, smaller list labelled notifications. subdomain, and the counter drops again.
There's a way back under. Not every tool needs to be on the guest list. Some only let you reply from inside their own screen, and never send as you at all. Check which ones send. And some senders move a tool to a subdomain, with its own record, so the main list stays short.
08 · Recap · 2:22
On screen: the two lists put down, the single list with three names, the ten-slot counter. All three chips lit.
Your to-do list is short. Run the free SPF checker on your domain today. If there are two records, merge them into one, with an include for each sender. Take off the tools that never send as you. And keep the lookup count under ten.
09 · Close · 2:38
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
One record, every sender on it, and the free SPF checker after every new tool. That record stays yours to fix. Review My Emails looks after the list you send to. Stuck on one right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... do hyperlinks always reduce deliverability?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.003.005-one-spf-record-myth.md
00 · Can I use multiple SPF records? (hook)
The myth
the title question, Lora, large: "Can I use multiple SPF records?" Three sending desks line up behind the gate at inkwell-tide.example. Each desk pins its own guest list to the gate. Three lists hang there, and the gate does not open. Three numbered chips: why two records fail · how to fit every sender into one · the limit to watch.
three lists in one hand, and a gate that stays shut. The myth is the gate that won't open (M2). Reveals: (1) the question, (2) three desks, (3) three lists handed over, (4) the gate stays shut, (5) the chips.
concept spf (a guest list held at the gate, M-18, M-15).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The guest list, in one line
Almanac ids in this scene: 003.001.001
What SPF is
one sending desk slides up to the gate. A light runs down one guest list, finds the desk's name, and the gate opens, teal. Gloss card: SPF · a record at your domain listing which servers are authorized to send mail on its behalf.
one list, one match, one open gate. Reveals: (1) the desk arrives, (2) the finger finds the name, (3) the gate opens.
concept spf (M-18, M-15). Callback to 003.001.001 (S6).
03 · Why two records fail
Why two records fail
chip 1 lights. Two guest lists pinned at the same gate. A light flicks from one to the other, then goes out. The gate stays shut and turns coral, stamped in plain words: SPF fails.
a count of lists at one gate. One opens it. Two shut it. Reveals: (1) the second list pinned, (2) both put down, (3) the gate shuts, coral, stamped SPF fails.
concept spf (M-18, M-15). The SPF fails stamp is a label on the registry picture, not new art. The spec's word "permerror" is never shown or spoken (P6).
"a domain gets one SPF record" names no source for the rule, so it takes no side in C23 (G2). The answer's "DNS only allows one SPF record" and the siblings' RFC are both left out. Only the answer's own reason is voiced: the receiver sees a conflict and SPF fails.
04 · What it breaks
What it breaks
all three desks now wait at the shut gate, each envelope stamped coral. Beside the gate, the DMARC instruction card has two slots, SPF and DKIM. The SPF slot goes dark. Gloss card: DMARC · a policy on top of SPF and DKIM saying what a receiving server should do when a message fails.
three desks, three coral stamps, not one. Then two slots on the card, one going dark. Reveals: (1) all three stamped, (2) the DMARC card, (3) the SPF slot goes dark.
concepts spf (M-18, M-15) and dmarc (the instruction card beside the gate, M-18, M-35).
no inbox claim. The sibling's reputation line ("can't get their record right") is cut. The last line is the answer's own ("can end up looking unauthorized"), "can" kept (V12).
05 · How it happens
How it happens
a DNS case file for inkwell-tide.example opens. One SPF line sits in it. A second line is written in below it by a different hand. Nobody looks up.
one line, then two, in the same file. Reveals: (1) the file with one line, (2) the second line written in.
concept dns (a row of case files, one per domain, M-20, M-02).
V8, never at the viewer. "Nobody did anything silly" is our line, it states no fact.
06 · One list with everyone on it
How to fit every sender into one
chip 2 lights. The two lists fold into one. Three names now sit on a single guest list, one line per desk. A light reads it once, and the gate opens for all three desks, teal. Gloss card: include · a line inside your SPF record that brings in one sending service's servers.
three names on one list. The count of lists goes from two to one while the count of senders stays three. Reveals: (1) the fold, (2) three names on one list, (3) the gate opens for all three.
concept spf (M-18, M-15). include has no registry row. Proposed as a gloss row.
no record syntax in VO or on screen (P7). The example record goes in the description.
07 · The limit to watch
Almanac ids in this scene: 003.001.014, 003.001.015, 021.003.005
The limit to watch
the guest list from scene 06, crowded, a lookup counter reading 11. One tool's name is struck off, with a small tag only replies in its own screen. The counter drops. Then another name moves across to a second, smaller list labelled notifications. subdomain, and the counter drops again.
the lookup count falling as names come off. Reveals: (1) the crowded list and its counter, (2) the struck name, (3) the move to a subdomain list.
the guest list from scene 02. No new registry picture.
"ten" is a spec limit every sibling agrees on (003.001.015, 003.001.014), not a rate or a target (N6). Spoken "ten", shown 10 (N4). The nested lookups, the tools that only reply, and the subdomain route go to the description (P7, S2).
021.003.005 "check whether any of your tools actually send email on your behalf or just let you reply from their interface. Not every integration needs to be in your SPF record. Second, some senders move certain tools to subdomains... and give each subdomain its own SPF record, which keeps the lookup count manageable."
T3, the one twist, and T9 (how to get under the limit). The counter's 11 is illustrative, not a threshold (N6), and pairs with the Almanac's own limit of ten.
08 · Recap
The recap
the two lists put down, the single list with three names, the ten-slot counter. All three chips lit.
the single list, held.
callbacks only (S5).
09 · Close
Send to a list that's real
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
says out loud that cleaning does not fix SPF. The free SPF checker goes in the description. Totals: 11 scenes. 494 spoken words (recounted 2026-09-30, Q sweep). About 3:03 at 166 words a minute, about 3:16 with scene breaks. Every scene is 20 to 70 words (S2).
V033Do hyperlinks always reduce deliverability?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C24 (ledger): does link count matter at all?
- Two more flags, each named by one answer only. Not a GAP, they disagree with nothing.
- Tracking domain gloss: no registry row.
- "No picture yet" visuals: the clicks meter, the envelope with link tags, the redirect hops, the tracking gateway.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Do hyperlinks always reduce deliverability? (hook) · 0:00
On screen: the title question, Lora, large: "Do hyperlinks always reduce deliverability?" Sally's newsletter, links being snipped out one at a time with small scissors. A clicks meter beside it drops with each snip. A delivered better stamp tries to land and slides off. Three numbered chips: what filters look at · the links that raise flags · how many links to use.
Do hyperlinks always reduce deliverability? Someone told Sally Send that links hurt. So she trimmed them, one by one. Now her emails look sparse, and fewer people click. Did it help? Not the way she hoped. Three things sort it out. What filters look at in a link. The links that raise flags. And how many links to use.
01 · Brought to you by, woven in · 0:21
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Links are one side of your email and the addresses are the other, the side we check at Review My Emails before you send.
02 · The grain of truth · 0:30
On screen: Sally's envelope, now carrying its links back as small tags along its edge. One tag at the far end turns coral. The rest stay teal.
There's a grain of truth in it. Some links do hurt. But it's the link, not the fact that there's a link. Links don't hurt deliverability. Bad links do.
03 · What filters look at · 0:40
On screen: chip 1 lights. The sorting arm at the gate picks up Sally's envelope and follows each tag along a thin line to its door. subject-line-salon.example: a known door, teal. lighthouse-letterpress.example: teal. Gloss card: spam filter · the system at the receiving end that decides whether your message reaches the inbox, another folder, or nowhere.
What does a spam filter look at? It doesn't punish you for including links. It follows them. Every link is a reference you give about yourself, and the filter calls your references. Where does each one go? What's that destination's reputation? A link to your own product page, or a helpful article, is completely normal. Reputation follows the destination, not just the sender.
04 · The links that raise flags · 1:03
On screen: chip 2 lights. Three more tags on the envelope, each followed to its door. Door one: a book held open at it, the destination's name found inside, coral. Door two: a fresh sign, registered last week, coral. Door three: the line loops through four empty doorways before it arrives anywhere, coral.
Which links raise flags? Four kinds. A link to a domain with a poor reputation, or one on a blocklist. A link to a brand new domain with no history. A link that hides where it's going, behind a shortener or a long chain of redirects. And link text that says one thing and points somewhere else. It doesn't matter how clean the rest of your email is.
05 · How many links to use · 1:28
On screen: chip 3 lights. Two envelopes side by side: a newsletter with several teal tags, and a receipt with two teal tags. Neither carries a number. Each tag gets a small tick as it earns its place.
How many links should you use? As many as the email needs, no more. A newsletter with a few links to articles fits right in. A receipt with one or two action links makes sense. Just make sure every link earns its place, and points somewhere you trust.
06 · Stuffing hurts, through engagement · 1:46
On screen: an envelope crowded with tags. A reader opens it and closes it without clicking. The score gauge beside the door edges down one notch. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
Now, stuffing an email with links just to fill space does hurt. It hurts engagement. And low engagement is what wears down your sender reputation over time.
07 · Check your tracking domain · 1:56
On screen: a test email in an inbox. A cursor hovers a link, and a small address strip appears: first a tracking subdomain on a reserved .example domain, then an arrow on to the real page. The first part lights.
Where do you see it? Send yourself a test email, and hover over a link, or copy it. The address it shows first, before your real page, is your tracking domain. If it's a subdomain you set up yourself, check it was configured the way your tool asks. Most big tools handle it for you.
08 · Recap · 2:40
On screen: the envelope with its tags, the three coral doors, the tracking gateway. All three chips lit.
Back to Sally's email. Put back the links your email needs. Point each one somewhere you trust, with link text that matches. Drop shorteners and long redirect chains. And send yourself a test, to check the tracking domain every link passes through first.
09 · Close · 2:56
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
Links work best when they reach real people who want to click. Review My Emails checks that the addresses behind those clicks are real. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... can you get deliverability issues from clean lists?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.004.017-links-dont-hurt-bad-links-do-myth.md
00 · Do hyperlinks always reduce deliverability? (hook)
The myth
the title question, Lora, large: "Do hyperlinks always reduce deliverability?" Sally's newsletter, links being snipped out one at a time with small scissors. A clicks meter beside it drops with each snip. A delivered better stamp tries to land and slides off. Three numbered chips: what filters look at · the links that raise flags · how many links to use.
the clicks meter dropping one notch per snip, and the stamp that won't stick (M2). Reveals: (1) the question, (2) the snips and the falling meter, (3) the stamp slides off, (4) the chips.
concept spam-filter (a sorting arm at the gate, M-18, M-37), waiting beside the envelope.
H5, the VO promise and the chips are the same words. Sally is sympathetic, just following advice (V8).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · The grain of truth
Where the myth comes from
Sally's envelope, now carrying its links back as small tags along its edge. One tag at the far end turns coral. The rest stay teal.
one coral tag among teal ones. The envelope holds still, one tag changes (P2). Reveals: (1) the tags return, (2) one turns coral.
concept spam-filter (M-18, M-37). The envelope with link tags: no picture yet, proposed.
M4, the grain of truth first. The grain of truth is said plainly.
03 · What filters look at
What filters look at
chip 1 lights. The sorting arm at the gate picks up Sally's envelope and follows each tag along a thin line to its door. subject-line-salon.example: a known door, teal. lighthouse-letterpress.example: teal. Gloss card: spam filter · the system at the receiving end that decides whether your message reaches the inbox, another folder, or nowhere.
lines from the envelope to doors. Each door's colour is its reputation. Reveals: (1) the arm picks up the envelope, (2) the first line to a teal door, (3) the second line to a teal door.
concept spam-filter (M-18, M-37). Doors from mailbox-provider's street (M-14).
04 · The links that raise flags
The links that raise flags
chip 2 lights. Three more tags on the envelope, each followed to its door. Door one: a book held open at it, the destination's name found inside, coral. Door two: a fresh sign, registered last week, coral. Door three: the line loops through four empty doorways before it arrives anywhere, coral.
a count of flagged kinds, three, one coral door per reveal. The redirect chain is drawn as its hops, so the length is the problem. Reveals: (1) the listed door, (2) the new door, (3) the looping chain.
concepts spam-filter (M-18, M-37) and blocklist (the book held open at the gate, M-18, M-20) for door one.
no blocklist named (the answers name one). "Three kinds" is the count of kinds both answers share, not a claim that there are only three (V9).
05 · How many links to use
How many links to use
chip 3 lights. Two envelopes side by side: a newsletter with several teal tags, and a receipt with two teal tags. Neither carries a number. Each tag gets a small tick as it earns its place.
tags per envelope, different on each, and no number printed. The comparison is fit, not count (N6). Reveals: (1) the newsletter, (2) the receipt, (3) the ticks.
concept spam-filter (M-18, M-37), the envelope with tags.
no link count voiced or shown. This is C24. Both answers agree on "as many as the email needs".
06 · Stuffing hurts, through engagement
Where too many links do hurt
an envelope crowded with tags. A reader opens it and closes it without clicking. The score gauge beside the door edges down one notch. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
the gauge needle edges down one notch per unread, crowded send. Reveals: (1) the crowded envelope, (2) opened and closed, (3) the needle edges down.
concepts engagement-signal (the envelope that stays face down, M-15, M-12) and sender-reputation (M-33).
takes no side in C24 (G2). Whether a filter counts links is not voiced. Only the line both answers support is said: stuffing hurts engagement, and engagement wears down reputation.
07 · Check your tracking domain
Almanac ids in this scene: 021.004.017
Check your tracking domain
a test email in an inbox. A cursor hovers a link, and a small address strip appears: first a tracking subdomain on a reserved .example domain, then an arrow on to the real page. The first part lights.
two hops, one lit. Reveals: (1) the hover, (2) the two-hop strip, (3) the tracking hop lights.
no registry picture for links. Proposed: the address strip.
"email tool", never "ESP" (V5). The answer's named tools are left out.
021.004.017 "if you use link tracking through your ESP, make sure the tracking domain is properly set up and has a good reputation of its own... Most major ESPs... handle this automatically, but it's worth confirming if you've set up custom click tracking." Hovering to read the link is how-to framing, not an Almanac fact.
T2, where and how. Scene 07 split so each stays under 70 words (S2).
08 · Recap
The recap
the envelope with its tags, the three coral doors, the tracking gateway. All three chips lit.
the tags and their doors, held.
callbacks only (S5).
09 · Close
Send to people who click
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
the clean checks addresses. It does not fix a flagged link, a tracking domain, or any content reputation. It fixes no SPF, DKIM, DMARC or blocklist problem. Totals: 11 scenes. 537 spoken words (recounted 2026-09-30, Q sweep). About 3:18 at 166 words a minute, about 3:31 with scene breaks. Every scene is 20 to 70 words (S2).
V034Can you get deliverability issues from clean lists?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C25 (ledger): spam-trigger phrases in 021.002.016 against the spammy-words myth 021.001.001.
- Content as a factor: left out to keep four pillars.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Can you get deliverability issues from clean lists? (hook) · 0:00
On screen: the title question, Lora, large: "Can you get deliverability issues from clean lists?" Sally's list, every dot green, a clean stamp on it. An inbox stamp tries to land on the next campaign and slides off. Three numbered chips: only one pillar · the three that can still crack · what to check next.
Can you get deliverability issues from clean lists? Sally Send's list came back spotless. Every address checked. So the next campaign lands in the inbox, right? Not on its own. Three parts to the answer. Why a clean list is only one pillar. The three that can still crack. And what to check next.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails cleans lists for a living, and we'll be the first to tell you a clean list isn't the whole story.
02 · Only one pillar · 0:27
On screen: chip 1 lights. The four pillars from the 002.001.002 video build under a roof labelled inbox, with the same four mono labels: authentication, sender reputation, engagement, list hygiene. The list hygiene pillar lights teal with Sally's clean stamp. The other three stay unlit.
A clean list is important. But it's only one piece. Deliverability rests on four pillars. Authentication. Sender reputation. Engagement. And list hygiene. Cleaning your list fixes the fourth. If one of the other three cracks, the whole thing wobbles.
03 · Authentication can crack · 0:41
On screen: the ship from scene 03, papers now on board. Then a real envelope's header sheet opens, three lines lit: spf= · dkim= · dmarc=. One of them reads fail in coral although the papers are there. The sheet drops into a panel labelled email header analyzer, which lists the three results as pass or fail.
Set up isn't the same as passing. Your records can all be there, and still fail on a real message. So check it on a real one. Send yourself an email, open its full headers, and look for the SPF, DKIM and DMARC results. Our free Email Header Analyzer reads them out for you, pass or fail.
04 · Reputation can crack · 1:23
On screen: the sender reputation pillar, with the score gauge on it. The needle sits low, and a long tail of past sends trails behind it. Sally's clean stamp lands on the list, and the needle doesn't move. The pillar cracks. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
The second: sender reputation. If your domain or your sending address has a troubled history, that baggage travels with you. A cleaned list won't reset months of complaints. Mailbox providers look at long term signals, not just your latest send.
05 · Engagement can crack · 1:37
On screen: the engagement pillar. Sally's green dots stay green, deliverable, but each envelope that reaches them stays face down. The pillar cracks. The roof now tilts three notches.
The third: engagement. Even with every address deliverable, if people haven't opened your emails in a long time, mailbox providers treat that silence as a signal. A clean list of cold subscribers is still a cold list.
06 · What to check next · 1:51
On screen: chip 3 lights. Three check cards, one per cracked pillar, each ticking as it is said: authentication passing, domain reputation, quiet subscribers. Each tick repairs its pillar to teal. The roof levels.
If your list is clean but delivery still feels off, check the other three. Authentication, on a real message, like we just did. Your domain's reputation, and our free blocklist checker shows whether you're listed anywhere that matters. And who hasn't opened in a long time. That's worth handling on its own.
07 · Recap · 2:10
On screen: the four pillars, all teal, under a level roof. All three chips lit.
Your four checks, then. Clean the list, because it's necessary. Then check authentication on a real message, not just in your settings. Run the free blocklist check. And look at who has gone quiet. Four pillars, four checks.
08 · Close · 2:24
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The list hygiene pillar lights. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.003 "Will inboxes stop using open rates?", no subscribe ask.
The list is the pillar Review My Emails fixes, checking every address before you send. The other three are yours, and our free tools help, the Email Header Analyzer and the blocklist checker. To see who's still engaged, there's RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... will inboxes stop using open rates?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.016-clean-list-still-spam-myth.md
00 · Can you get deliverability issues from clean lists? (hook)
The myth
the title question, Lora, large: "Can you get deliverability issues from clean lists?" Sally's list, every dot green, a clean stamp on it. An inbox stamp tries to land on the next campaign and slides off. Three numbered chips: only one pillar · the three that can still crack · what to check next.
a clean list, and a stamp that won't stick (M2). Reveals: (1) the question, (2) the clean list, (3) the stamp slides off, (4) the chips.
concept list-hygiene (the house held up by people, M-09, M-07, M-10).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Only one pillar
Almanac ids in this scene: 002.001.002
Only one pillar
chip 1 lights. The four pillars from the 002.001.002 video build under a roof labelled inbox, with the same four mono labels: authentication, sender reputation, engagement, list hygiene. The list hygiene pillar lights teal with Sally's clean stamp. The other three stay unlit.
four pillars, one lit. One of four is not enough to hold the roof. Reveals: (1) the four pillars, (2) list hygiene lights, (3) the other three stay unlit.
the four pillars from the 002.001.002 script (S6, P5). No new art.
M4, the grain of truth first (a clean list is important). The four words are the 002.001.002 words exactly.
03 · Authentication can crack
Almanac ids in this scene: 021.002.016
Authentication can crack
the ship from scene 03, papers now on board. Then a real envelope's header sheet opens, three lines lit: spf= · dkim= · dmarc=. One of them reads fail in coral although the papers are there. The sheet drops into a panel labelled email header analyzer, which lists the three results as pass or fail.
three results on one message, one failing despite the papers. Reveals: (1) papers on board, (2) the header lines, (3) the one fail, (4) the analyzer panel.
no registry row for headers. Proposed: the header sheet with three lines lit, reused from the bounces playlist's retries video.
no second analogy (S4, P3). SPF, DKIM and DMARC are named, not taught (S6).
021.002.016 "Check your email headers to confirm authentication is actually passing end to end, not just configured. Our email header analyzer makes that easy."
T3 (the one twist), T2 (where and how) and T7 (our tool).
04 · Reputation can crack
Reputation travels with you
the sender reputation pillar, with the score gauge on it. The needle sits low, and a long tail of past sends trails behind it. Sally's clean stamp lands on the list, and the needle doesn't move. The pillar cracks. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
the gauge needle stays put when the list gets cleaned. The history, not the latest send, sets it. The unmoved needle is the whole scene (S2). Reveals: (1) the low needle and its tail, (2) the clean stamp, needle unmoved, (3) the crack.
the sender reputation pillar with concept sender-reputation (the score gauge, M-33).
the volume-spike line is cut, one idea per scene (S2). Trap words in the answer ("spam trap hits") are left out.
05 · Engagement can crack
A clean list of cold subscribers
the engagement pillar. Sally's green dots stay green, deliverable, but each envelope that reaches them stays face down. The pillar cracks. The roof now tilts three notches.
green dots, face-down envelopes. Deliverable and unread at the same time. Reveals: (1) the envelopes arrive, (2) they stay face down, (3) the crack, three notches.
the engagement pillar with concept engagement-signal (the envelope that stays face down, M-15, M-12).
"deliverable", never "valid" (V6). The answer's "cold lists need warming" is not voiced, to keep warmup out of the video (RULE-1 is about tools, but the line invites the question).
06 · What to check next
What to check next
chip 3 lights. Three check cards, one per cracked pillar, each ticking as it is said: authentication passing, domain reputation, quiet subscribers. Each tick repairs its pillar to teal. The roof levels.
a count of checks, three, one per pillar. The roof's tilt goes back one notch per tick. Reveals: (1) to (3) one card per click, each pillar repairing, (4) the roof levels.
the four pillars, callback (S5).
three checks voiced, three cards (N4). The header check sits inside "passing end to end", and the header tool goes in the description (P7). The answer's "6+ months" is voiced as "a long time" (the answer's own words in scene 05), so no invented or target figure (V9, N6). The free tools go in the description (S8).
07 · Recap
The recap
the four pillars, all teal, under a level roof. All three chips lit.
four pillars, held.
callbacks only (S5).
08 · Close
Almanac ids in this scene: 021.013.003
Start with the pillar we fix
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The list hygiene pillar lights. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.003 "Will inboxes stop using open rates?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
one of four pillars lit, the one we fix. No share claimed.
concept list-cleaning (M-25, M-23, M-24) over the pillars.
says out loud that the clean fixes one pillar, and names the other three as the viewer's. Nothing implies cleaning fixes SPF, DKIM, DMARC, reputation or a blocklist. The next video is batch H's first, the Almanac question word for word (Video PM, 2026-09-29). Totals: 10 scenes. 455 spoken words (recounted 2026-09-30, Q sweep). About 2:48 at 166 words a minute, about 3:00 with scene breaks. Every scene is 20 to 70 words (S2).
V035Will inboxes stop using open rates?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C32 (ledger): how certain the Almanac is about what providers measure.
- Apple named on screen. The answer and the registry gloss name Apple's setting.
- "No picture yet" visuals: the two windows onto one inbox.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Will inboxes stop using open rates? (hook) · 0:00
On screen: the title question, Lora, large: "Will inboxes stop using open rates?" Sally's dashboard with an open counter. A thin line runs from the counter to the provider's door, labelled used to filter?, and the line snaps, because it was never connected (M2). Three numbered chips: whose number an open rate is · what the inbox sees instead · what to watch now.
Will inboxes stop using open rates? Sally Send's open numbers stopped making sense, and she's worried Gmail will stop trusting them too. Turns out, they never did. It comes down to three things. Whose number an open rate is. What the inbox sees instead. And what to watch now.
01 · Brought to you by, woven in · 0:17
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Your opens start with real people at real addresses, and Review My Emails checks every one of those addresses before you send.
02 · Whose number an open rate is · 0:26
On screen: chip 1 lights. Two windows onto the same inbox. Left, your dashboard, with the open counter. Right, the provider's view, blank for now. The counter sits only in the left window.
Whose number is an open rate? Yours. It was always a marketer's number, not a provider's. Mailbox providers never used your open rate to filter your mail. They never needed it. It's their platform, so they can see what their own users do. So there's nothing for them to stop using.
03 · What the inbox sees instead · 0:39
On screen: chip 2 lights. The right window fills with a row of messages. Sally's email to opal.rate@mailbox.example opens, and its row lights read. A second message is deleted unread. A third moves to a folder. A fourth gets the spam button. Each action lights a small mark in the provider's view. Gloss card: tracking pixel · a tiny hidden image in your email, and when it loads, your tool counts an open (backed by 021.001.018 "a tiny 1x1 transparent image embedded in your email.").
What does the inbox see instead? Picture a shop. The provider is inside, watching who picks things up. You're outside, looking in through the window. They see whether someone reads a message. How quickly they delete it. Whether they move it to a folder, hit the spam button, or never touch it at all. They don't need a tracking pixel, the hidden image that counts your opens.
04 · What Apple changed · 1:03
On screen: fog rolls over the left window only. The open counter climbs on its own inside the fog. The right window stays clear, and the read mark on Opal's row stays visible there. Gloss card: Mail Privacy Protection · an Apple setting that loads images for the reader, so an open can no longer be read as a person opening it.
Apple's Mail Privacy Protection changed your view, not theirs. Apple loads the images for the reader, so your email tool records an open that may not be a person. But Apple still knows exactly what that reader did. It fogged your window. The shop owner inside can see just as well as before.
05 · What to watch now · 1:24
On screen: chip 3 lights. Three small tiles stack in Sally's clear dashboard: clicks, replies, complaints. The fogged open counter shrinks to a corner.
What should you watch? The signals that show real intent. Where? In your tool's report for each campaign, the clicks and replies, not the opens. Clicks show someone wanted to act. Replies show someone wanted to talk. And complaints show you've pushed too far.
06 · Send mail people want · 1:45
On screen: the right window, Opal's row lighting read, then clicked. The score gauge beside the door edges up. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
The providers keep watching what their users do, on their side, where you'll never see it. Your job is to send email people want, and trust that fewer spam reports and more clicks follow. That's what protects your sender reputation.
07 · Recap · 2:00
On screen: the two windows, one fogged, one clear. All three chips lit.
What changes for you? Stop judging a campaign by its opens. Read the clicks and replies in each campaign's report. Watch your complaints. And put your effort into sending mail people want, because the shop owner is watching what they do with it.
08 · Close · 2:16
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
What your report can't show you, behind all that fog, is who's still engaged. RME Insights shows you that, and Review My Emails checks every address before you send. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... does high open rate guarantee good deliverability?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.013.003-inboxes-never-used-your-opens-myth.md
00 · Will inboxes stop using open rates? (hook)
The myth
the title question, Lora, large: "Will inboxes stop using open rates?" Sally's dashboard with an open counter. A thin line runs from the counter to the provider's door, labelled used to filter?, and the line snaps, because it was never connected (M2). Three numbered chips: whose number an open rate is · what the inbox sees instead · what to watch now.
a line from the counter to the door that was never attached. Reveals: (1) the question, (2) the counter, (3) the line snaps, (4) the chips.
concept open-rate (the open counter climbing, M-30, M-19) and mailbox-provider (the door, M-14, M-18).
the turn is "Turns out, they never did." (M1, varied, not used elsewhere in the Myths series). Sally is sympathetic (V8).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Whose number an open rate is
Whose number it is
chip 1 lights. Two windows onto the same inbox. Left, your dashboard, with the open counter. Right, the provider's view, blank for now. The counter sits only in the left window.
one counter, and it lives in one window only. Reveals: (1) the two windows, (2) the counter sits left, (3) the right window stays without it.
concept open-rate (M-30, M-19) in the left window.
03 · What the inbox sees instead
Almanac ids in this scene: 021.001.018
What the inbox sees instead
chip 2 lights. The right window fills with a row of messages. Sally's email to opal.rate@mailbox.example opens, and its row lights read. A second message is deleted unread. A third moves to a folder. A fourth gets the spam button. Each action lights a small mark in the provider's view. Gloss card: tracking pixel · a tiny hidden image in your email, and when it loads, your tool counts an open (backed by 021.001.018 "a tiny 1x1 transparent image embedded in your email.").
a count of actions the provider sees, five marks, and none of them needed the sender's counter. Reveals: (1) read, (2) deleted, (3) moved, (4) reported, (5) never touched.
concept engagement-signal (the envelope flipping to show what happened, M-15, M-12) in the right window.
"whether someone reads a message" is the answer's body wording. "read time" from the In short is not voiced (V12, C32).
04 · What Apple changed
Almanac ids in this scene: 021.006.001
What Apple changed
fog rolls over the left window only. The open counter climbs on its own inside the fog. The right window stays clear, and the read mark on Opal's row stays visible there. Gloss card: Mail Privacy Protection · an Apple setting that loads images for the reader, so an open can no longer be read as a person opening it.
one window fogged, one clear. The counter climbing in the fog is the registry picture. Reveals: (1) fog on the left, (2) the counter climbs alone, (3) the right window stays clear.
concept mail-privacy-protection (the open counter climbing while the inbox stays shut, M-30, M-37). One-line callback to the 021.006.001 short (S6).
"may not be a person" keeps to the answer's "false open" without a share (N6).
05 · What to watch now
What to watch now
chip 3 lights. Three small tiles stack in Sally's clear dashboard: clicks, replies, complaints. The fogged open counter shrinks to a corner.
a count of signals, three, one tile per reveal. No rate on any tile (N6). Reveals: (1) to (3) one tile per click, (4) the open counter shrinks. Q7: the VO says three, conversions and unsubscribes stay in the Almanac answer.
concept engagement-signal (M-15, M-12). Tiles are labels on it, not new art.
06 · Send mail people want
What protects you
the right window, Opal's row lighting read, then clicked. The score gauge beside the door edges up. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
the gauge needle rising one step per real action. Reveals: (1) Opal's row lights read and clicked, (2) the needle rises.
concept sender-reputation (the score gauge, M-33).
the answer's "actually want" is voiced as "want" (V10).
07 · Recap
The recap
the two windows, one fogged, one clear. All three chips lit.
the two windows, held.
callbacks only (S5).
08 · Close
Send to real readers
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
the clean checks addresses. It does not fix open tracking, engagement or reputation. The next video is named by its Almanac question word for word (S8). Totals: 9 scenes. 422 spoken words (recounted 2026-09-30, Q sweep). About 2:36 at 166 words a minute, about 2:47 with scene breaks. Every scene is 20 to 70 words (S2).
V036Does high open rate guarantee good deliverability?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- "No picture yet" visuals: the row of truth gauges.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Does high open rate guarantee good deliverability? (hook) · 0:00
On screen: the title question, Lora, large: "Does high open rate guarantee good deliverability?" Sally's dashboard with one tall open bar, no number on it. A guaranteed stamp tries to land on the bar and slides off (M2). Beside it, Sally's envelope drops into the spam tray. Three numbered chips: why a high open rate can hide trouble · the signals that tell the truth · what to check.
Does high open rate guarantee good deliverability? Sally Send's open rate looks great, and her emails keep landing in spam. Something doesn't add up. Three things unpick it. Why a high open rate can hide trouble. The signals that tell the truth. And what to check.
01 · Brought to you by, woven in · 0:17
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some of those signals start with the list itself, which is where Review My Emails checks every address before you send.
02 · Why a high open rate can hide trouble · 0:25
On screen: chip 1 lights. The tall open bar splits into two stacked parts. The bottom part stays teal, people. The top part turns grey, machines, and three small labels land on it: privacy loading, security scanners, bots.
A chunk of that open rate was never a person. Opens get inflated in ways you can't control. Apple's privacy feature loads your email through its own servers. Security scanners at company mail gateways fire the tracking image. So do bots. It's a packed room where half the audience are mannequins. It looks full. Nobody's listening.
03 · Complaints and clicks · 0:47
On screen: chip 2 lights. Beside the open bar, a row of small gauges appears, one at a time. The first, complaints, with a few raised hands. The second, clicks against opens: a short teal bar next to the tall grey-topped open bar.
What tells the truth instead? Start with complaints. High opens don't cancel out high complaints. Then clicks. Clicks are much harder to fake than opens, because a mannequin doesn't click. If your opens are high and your clicks are low, that's a sign your open rate is inflated.
04 · Replies, unsubscribes and bounces · 1:05
On screen: three more gauges join the row: replies, with Rhea's envelope coming back, unsubscribes, with a small spike, and hard bounces, with a coral slip. The open bar stays tall throughout, and none of the gauges move with it.
Replies count too. A real person writing back is one of the strongest positive signals you can get. A spike in unsubscribes tells you something about fit. And hard bounces tell you the list has quality problems, even while the opens look fine.
05 · Where your mail lands · 1:20
On screen: the sixth gauge, placement. Sally's envelope drops through the trays at three doors: one inbox, one promotions, one spam. Gloss card: inbox placement · where an accepted message actually lands, which is the inbox, another tab, the spam folder, or nowhere visible.
And the closest thing to a direct check? Inbox placement. A placement test shows whether your emails hit the inbox, spam or promotions at different providers. Whatever your open rate says.
06 · What to check · 1:31
On screen: chip 3 lights. The dashboard, all green. A lens lifts one email and turns it over, and its header lines show one coral fail next to DKIM. The dashboard stays green the whole time.
What do you check? Your authentication, more than most senders realise. If SPF, DKIM and DMARC aren't set up right, providers can filter your mail even when engagement looks fine. And those failures are invisible in your email tool's dashboard. So open the full headers of one of your own emails, or paste them into our free Email Header Analyzer. It shows whether each check is passing.
07 · Recap · 1:56
On screen: the split open bar, the row of gauges, the coral header line. All three chips lit.
Here's where to look now. Stop reading opens as proof. Put your clicks next to your opens, and watch your complaints. Treat a reply as the best sign you'll get. And check one of your own emails in the Email Header Analyzer, to see if authentication is passing.
08 · Close · 2:13
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
Bounces are the one signal on that list that starts with the addresses, and that's the part Review My Emails checks before you send. Mail landing in spam right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... is using Re: in the subject line a good tactic?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.006.008-high-opens-no-guarantee-myth.md
00 · Does high open rate guarantee good deliverability? (hook)
The myth
the title question, Lora, large: "Does high open rate guarantee good deliverability?" Sally's dashboard with one tall open bar, no number on it. A guaranteed stamp tries to land on the bar and slides off (M2). Beside it, Sally's envelope drops into the spam tray. Three numbered chips: why a high open rate can hide trouble · the signals that tell the truth · what to check.
one tall bar and one envelope in the spam tray, side by side. The bar's height doesn't match where the mail went. Reveals: (1) the question, (2) the tall bar, (3) the stamp slides off, (4) the spam tray, (5) the chips.
concept open-rate (the open counter, then who was a person, M-30, M-19) and inbox-placement (the trays, M-37, M-18).
no open rate figure on screen or in VO (N6). The turn is "Something doesn't add up." (M1, varied, and the answer's own words).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · Why a high open rate can hide trouble
Almanac ids in this scene: 021.006.001
Why it can hide trouble
chip 1 lights. The tall open bar splits into two stacked parts. The bottom part stays teal, people. The top part turns grey, machines, and three small labels land on it: privacy loading, security scanners, bots.
one bar split into people and machines, with no share printed (N6). The grey part is the inflation. Reveals: (1) the split, (2) to (4) one machine label per click.
concept open-rate (the zoom out showing which opens were a person, M-30, M-19). One-line callback to the 021.006.001 short (S6).
"a chunk" is our plain word for the answer's "a meaningful chunk". No share voiced (V12).
03 · Complaints and clicks
The signals that tell the truth
chip 2 lights. Beside the open bar, a row of small gauges appears, one at a time. The first, complaints, with a few raised hands. The second, clicks against opens: a short teal bar next to the tall grey-topped open bar.
a short click bar next to a tall open bar. The gap between them is the tell. Reveals: (1) the complaints gauge, (2) the click bar, (3) the gap.
concepts complaint-rate (the few who raise a hand to report, M-48, M-25) and open-rate.
no complaint figure (N6). The answer's "This is the one that gets you blocklisted" is not voiced (V12, the siblings say complaints feed blocklists among other signals, not alone).
04 · Replies, unsubscribes and bounces
More signals that tell the truth
three more gauges join the row: replies, with Rhea's envelope coming back, unsubscribes, with a small spike, and hard bounces, with a coral slip. The open bar stays tall throughout, and none of the gauges move with it.
a row of six gauges, none of them tied to the open bar's height. Reveals: (1) replies, (2) unsubscribes, (3) hard bounces.
concepts engagement-signal (M-15, M-12) and hard-bounce (the door closing for good, M-15, M-14).
no bounce figure (N6). "one of the strongest positive signals" is the answer's own words.
05 · Where your mail lands
Where your mail lands
the sixth gauge, placement. Sally's envelope drops through the trays at three doors: one inbox, one promotions, one spam. Gloss card: inbox placement · where an accepted message actually lands, which is the inbox, another tab, the spam folder, or nowhere visible.
three doors, three trays, one envelope per door. Where it lands is the answer, not the bar. Reveals: (1) door one, inbox, (2) door two, promotions, (3) door three, spam.
concept inbox-placement (the trays, M-37, M-18).
"actually" sits in the registry gloss card text, not the VO. No placement promise.
06 · What to check
Almanac ids in this scene: 021.006.012
What to check
chip 3 lights. The dashboard, all green. A lens lifts one email and turns it over, and its header lines show one coral fail next to DKIM. The dashboard stays green the whole time.
a green dashboard and one coral line underneath it. The dashboard doesn't change, only the header does. Reveals: (1) the green dashboard, (2) the lens turns the email, (3) the coral line.
concept email-header (the envelope turning to show the lines on its back). One-line callback to the 021.006.012 short on engagement against authentication (S6).
07 · Recap
The recap
the split open bar, the row of gauges, the coral header line. All three chips lit.
the split bar and the row of gauges, held.
callbacks only (S5).
08 · Close
Real opens start with real addresses
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
the clean checks addresses, which is the bounce signal. It does not fix complaints, inflated opens, authentication or placement. The next video is named by its Almanac question word for word (S8), with the quote marks around Re: dropped for speech. Totals: 9 scenes. 422 spoken words (recounted 2026-09-30, Q sweep). About 2:36 at 166 words a minute, about 2:47 with scene breaks. Every scene is 20 to 70 words (S2).
V037Is using “Re:” in the subject line a good tactic?
waiting on YTOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- The legal line Settled by R9: one sentence at the end of scene 04, no law named.
- "No picture yet" visuals: the hanging thread line, the trust meter, the level scale.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Is using "Re:" in the subject line a good tactic? (hook) · 0:00
On screen: the title question, Lora, large: "Is using "Re:" in the subject line a good tactic?" Marina's inbox. A subject line slides in: Re: your order. A thread line tries to connect it to an earlier message, and there is no earlier message, the line hangs in the air (M2). Three numbered chips: what the trick buys you · what it costs · what works better.
Is using Re: in the subject line a good tactic? Sally Send has seen it in her own inbox. Re, your order. Re, following up. Except she never sent anything. It works, right? Briefly, yes. Three things show the rest. What the trick buys you. What it costs. And what works better.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
An honest subject line deserves an honest list, and Review My Emails checks every address on it before you send.
02 · What the trick buys you · 0:27
On screen: chip 1 lights. An opens bar beside Marina's inbox jumps up once, no number on it.
Start with what it buys you. Yes, you might see a short term bump in opens, because people think they're looking at a reply. It's like a stranger in the street greeting you as an old friend. You stop, for a second. That's the part that's true.
03 · What it costs, part one: trust · 0:44
On screen: chip 2 lights. Marina opens it, the page is a sale, not a reply. A trust meter beside her drains. Two small counters tick up: complaints, a raised hand, and unsubscribes. The opens bar from scene 02 sinks back down. The score gauge by the provider's door edges lower. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
And what does it cost? The moment someone opens it and realises there's no old friend, that trust is gone. Spam complaints go up. Unsubscribes spike. And mailbox providers pay close attention to complaint rates. A handful of extra opens isn't worth your sender reputation.
04 · What it costs, part two: filters know it · 1:00
On screen: the sorting arm at the gate picks up the envelope, reads Re: on it, finds the same pattern in its own notebook, and sends the envelope to the spam tray before Marina ever sees it. Gloss card: spam filter · the system at the receiving end that decides whether your message reaches the inbox, another folder, or nowhere.
The trick may never even get its moment. Spam filters have seen it for years. Many flag a fake Re: in bulk email as a known deceptive pattern. So your email may not even reach the inbox. And in some places, a fake reply in the subject line breaks the law on deceptive headers.
05 · What works better · 1:21
On screen: chip 3 lights. Hedda rewrites the subject line: Re: your order becomes Your spring order window opens Friday. Marina opens it, and the trust meter fills instead of draining. A small scale: subject on one side, email on the other, level.
What works better? The honest path. A subject line that says what's inside, speaks to something the reader cares about, or creates real curiosity, not fake urgency. Here's a simple test. Imagine opening the email yourself. Did you get what the subject promised? Then run it through our free subject line tester. It checks for the patterns filters flag, deceptive prefixes included.
06 · Reputation is built message by message · 1:44
On screen: the score gauge from scene 03, climbing one small step per honest send.
Your reputation is built one message at a time. And every fake Re: chips away at it. Honest subject lines win over time.
07 · Recap · 1:52
On screen: the short jump, the long drain, the level scale. All three chips lit.
The honest version, then. Take Re: off anything that isn't a real reply. Write the subject your email delivers on. Open it as if you were the reader, and check the promise holds. And test the line before you send it.
08 · Close · 2:08
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
Honest subject lines win over time, so let the free subject line tester catch the tricks before a filter does. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... do spam filters count exclamation points?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.004.014-fake-re-subject-line-myth.md
00 · Is using "Re:" in the subject line a good tactic? (hook)
Almanac ids in this scene: 021.006.011
The myth
the title question, Lora, large: "Is using "Re:" in the subject line a good tactic?" Marina's inbox. A subject line slides in: Re: your order. A thread line tries to connect it to an earlier message, and there is no earlier message, the line hangs in the air (M2). Three numbered chips: what the trick buys you · what it costs · what works better.
a reply thread with nothing to reply to. Reveals: (1) the question, (2) the subject line, (3) the hanging thread line, (4) the chips.
concept email (one envelope travelling to a door), with the thread line drawn from it.
the turn is "Briefly, yes." (M1, varied, "Half right" is taken by 021.006.011): there is a short bump, which is the grain of truth (M4).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What the trick buys you
What the trick buys you
chip 1 lights. An opens bar beside Marina's inbox jumps up once, no number on it.
one short jump. Reveals: (1) the bar jumps.
concept open-rate (the open counter climbing, M-30, M-19).
M4, the grain of truth first. "might" keeps to the answer's "you might see" (V12).
03 · What it costs, part one: trust
What it costs
chip 2 lights. Marina opens it, the page is a sale, not a reply. A trust meter beside her drains. Two small counters tick up: complaints, a raised hand, and unsubscribes. The opens bar from scene 02 sinks back down. The score gauge by the provider's door edges lower. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
the opens bar's short jump against the trust meter's long drain. Reveals: (1) the open and the drain, (2) complaints tick up, (3) unsubscribes tick up, (4) the opens bar sinks, (5) the gauge edges lower.
concepts complaint-rate (the few who raise a hand, M-48, M-25) and sender-reputation (the score gauge, M-33).
04 · What it costs, part two: filters know it
Almanac ids in this scene: 020.010.011, 021.004.014
Filters have seen it
the sorting arm at the gate picks up the envelope, reads Re: on it, finds the same pattern in its own notebook, and sends the envelope to the spam tray before Marina ever sees it. Gloss card: spam filter · the system at the receiving end that decides whether your message reaches the inbox, another folder, or nowhere.
the envelope never reaches the inbox, so the opens bar never even jumps. Reveals: (1) the arm reads Re:, (2) the pattern match, (3) the spam tray.
concept spam-filter (the sorting arm at the gate, M-18, M-37).
"Many flag" and "may not" keep to the answer's own "Many" and "may" (V12).
R9 (YT, 2026-09-29): the legal line follows R7, one sentence, no law named. It closes scene 04's VO. The GAP is closed.
021.004.014 "Under CAN-SPAM, it's actually illegal. The law prohibits deceptive header information, and a fake 'Re:' qualifies." / 020.010.011 "CAN-SPAM... sets the legal floor (no materially deceptive headers or subjects)".
05 · What works better
Almanac ids in this scene: 020.010.011
What works better
chip 3 lights. Hedda rewrites the subject line: Re: your order becomes Your spring order window opens Friday. Marina opens it, and the trust meter fills instead of draining. A small scale: subject on one side, email on the other, level.
the trust meter, drained in scene 03, now filling. The level scale is the test. Reveals: (1) the rewrite, (2) Marina opens, (3) the meter fills, (4) the level scale.
concept engagement-signal (the envelope flipping to opened, M-15, M-12). The scale: no picture yet.
the test is 020.010.011's alignment standard, in plain words. The example subject line is ours, it claims no fact.
06 · Reputation is built message by message
Message by message
the score gauge from scene 03, climbing one small step per honest send.
one step per send. Reveals: (1) the steps.
concept sender-reputation (M-33).
07 · Recap
The recap
the short jump, the long drain, the level scale. All three chips lit.
the jump and the drain, held.
callbacks only (S5).
08 · Close
Send to people who want it
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
the clean checks addresses. It does not fix a subject line, complaints or reputation. The next video is named by its Almanac question word for word (S8). Totals: 9 scenes. 397 spoken words (recounted 2026-09-30, Q sweep). About 2:28 at 166 words a minute, about 2:39 with scene breaks. Every scene is 20 to 70 words (S2).
V038Do spam filters count exclamation points?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C25 add (ledger): 021.004.008 names FREE as a trigger phrase, 021.004.001 says it is not one.
- "No picture yet" visuals: the fading tally counter, the scale at the gate, the TV frame.
- Episode number: in the Myths series, set by the Video Studio PM.
00 · Do spam filters count exclamation points? (hook) · 0:00
On screen: the title question, Lora, large: "Do spam filters count exclamation points?" A subject line types in: Spring bouquets are here! A cursor hovers over the ! and deletes it. A small tally counter above the gate, labelled ! count, stays at zero and then fades away, because there is no such counter (M2). Three numbered chips: what filters weigh · when punctuation matters · how to write.
Do spam filters count exclamation points? The florist writes, spring bouquets are here! Then deletes the exclamation point, to be safe. Mostly false. Three quick parts. What filters weigh. When punctuation matters. And how to write.
01 · Brought to you by, woven in · 0:13
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Your punctuation is yours to choose, and the list is ours to check, every address, before you send, at Review My Emails.
02 · What filters weigh · 0:21
On screen: chip 1 lights. A scale at the gate. Three heavy blocks land on it: reputation, authentication, engagement. Then one exclamation point drops on, a single grain, and the scale doesn't move. Gloss card: spam score · a running total a filter builds from many small signals, which decides where the message lands.
Start with what filters weigh. Your sender reputation. Your authentication. How engaged your audience is. Those count far more than punctuation. A spam score is a set of scales, with those three as the heavy weights. An exclamation point is a grain of sand on the same scales. Using a few for real enthusiasm is completely normal.
03 · When punctuation matters · 0:42
On screen: chip 2 lights. A second subject line: BUY NOW!!! ACT FAST!!!. On the scale, a heap of small grains lands together: all caps, !!!, made-up urgency, repetition. Together they tip the scale, coral.
When does punctuation matter? Not on its own, only in company. Picture a subject line that's all capitals, three exclamation points after every phrase, the word free, and urgency you made up. The exclamation points aren't the problem. It's the whole package, and filters recognise that pattern.
04 · The infomercial test · 1:00
On screen: the BUY NOW!!! subject line on a small TV screen with a flashing price sticker. The !!! fade out, and the sticker keeps flashing. The scale stays tipped.
Here's the honest line to watch. If your email reads like a late night infomercial, it isn't the exclamation points doing the damage. It's everything around them.
05 · How to write · 1:10
On screen: chip 3 lights. The florist's subject line comes back with its one exclamation point. The three heavy blocks from scene 02 glow teal. The scale settles, level.
How should you write? Like yourself. Use the punctuation that fits your voice. Then test it. Our free subject line tester flags the patterns worth fixing, before you send. And put your energy into the heavy weights on the scales. Steady engagement, clean authentication, and content people want to open.
06 · Recap · 1:29
On screen: the scale: one grain, three blocks, then the heap. All three chips lit.
Keep your voice, then. Stop deleting exclamation points out of fear. Keep the capitals, the made-up urgency and the stacked marks out of the same line. Run your subject lines through the free tester. And spend the effort on engagement and authentication.
07 · Close · 1:44
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
Write like yourself, and let the free subject line tester flag the patterns worth fixing. The heaviest weight, engagement, starts with real addresses, and RME Clean checks every one before you send. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... does domain reputation reset every year?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.004.008-exclamation-points-myth.md
00 · Do spam filters count exclamation points? (hook)
The myth
the title question, Lora, large: "Do spam filters count exclamation points?" A subject line types in: Spring bouquets are here! A cursor hovers over the ! and deletes it. A small tally counter above the gate, labelled ! count, stays at zero and then fades away, because there is no such counter (M2). Three numbered chips: what filters weigh · when punctuation matters · how to write.
a tally counter that isn't there. Reveals: (1) the question, (2) the subject line, (3) the delete, (4) the counter fades, (5) the chips.
concept spam-filter (the sorting arm at the gate, M-18, M-37).
the turn is "Mostly false." (M1, varied, it is the answer's own verdict).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · What filters weigh
What filters weigh
chip 1 lights. A scale at the gate. Three heavy blocks land on it: reputation, authentication, engagement. Then one exclamation point drops on, a single grain, and the scale doesn't move. Gloss card: spam score · a running total a filter builds from many small signals, which decides where the message lands.
three blocks and one grain on the same scale. Weight is size. Reveals: (1) to (3) one block per click, (4) the grain, (5) the scale holds still.
concept spam-filter (M-18, M-37) holding the scale. spam-score is gloss tier. The scale: no picture yet, proposed.
03 · When punctuation matters
Almanac ids in this scene: 021.004.001
When punctuation matters
chip 2 lights. A second subject line: BUY NOW!!! ACT FAST!!!. On the scale, a heap of small grains lands together: all caps, !!!, made-up urgency, repetition. Together they tip the scale, coral.
one grain did nothing in scene 02. A heap of them tips the scale. The count of signals together is the point, not the count of marks. Reveals: (1) the subject line, (2) the heap lands, (3) the scale tips.
concept spam-filter (M-18, M-37), the same scale.
the answer's example includes "FREE GIFT" and "trigger phrases like FREE". The word is left out on screen and in the VO (C25, and 021.004.001 says "free" is not a trigger).
04 · The infomercial test
The honest test
the BUY NOW!!! subject line on a small TV screen with a flashing price sticker. The !!! fade out, and the sticker keeps flashing. The scale stays tipped.
remove the marks and the scale doesn't come back. Reveals: (1) the TV, (2) the marks fade, (3) the scale stays tipped.
the same scale (P3). The TV frame: no picture yet.
one analogy, the answer's own (S4).
05 · How to write
How to write
chip 3 lights. The florist's subject line comes back with its one exclamation point. The three heavy blocks from scene 02 glow teal. The scale settles, level.
the one grain back on the scale, and the scale level. Reveals: (1) the ! returns, (2) the blocks glow, (3) the scale settles.
the same scale (P3).
"Like yourself" is the answer's "Write naturally", in a word the checker allows (V10).
06 · Recap
The recap
the scale: one grain, three blocks, then the heap. All three chips lit.
the scale, held.
callbacks only (S5).
07 · Close
Send to people who open
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
the clean checks addresses. It does not fix content, authentication or reputation, and it does not create engagement. The next video is named by its Almanac question word for word (S8). Totals: 8 scenes. 336 spoken words (recounted 2026-09-30, Q sweep). About 2:06 at 166 words a minute, about 2:16 with scene breaks. Every scene is 20 to 70 words (S2). Short cut (R12): removed in the taste pass. The video now runs past 2:00, so no Short cut is made from it.
V039Does domain reputation reset every year?
checkedOpen questions for YT
- Brought-to-you-by wording Settled by R1 (YT, 2026-09-29): scene 01 is a bridge line written for this video.
- C33 (ledger): recovery takes six to twelve months (021.005.013) or four to eight weeks (012.012.005).
- "No picture yet" visuals: the wall calendar, the send timeline under the gauge.
- Episode number and next-video title: in the Myths series, set by the Video Studio PM.
00 · Does domain reputation reset every year? (hook) · 0:00
On screen: the title question, Lora, large: "Does domain reputation reset every year?" Sally's score gauge, the needle low. A wall calendar flips to January 1. The needle does not move (M2). Three numbered chips: how reputation builds · what moves it · what brings it back.
Does domain reputation reset every year? Sally Send had a rough year of sending, and she's counting down to January, hoping for a fresh start. There's no such date. The answer comes in three parts. How reputation builds. What moves it. And what brings it back.
01 · Brought to you by, woven in · 0:16
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every send adds to your record, which is why at Review My Emails we check every address on your list before you send.
02 · How reputation builds · 0:24
On screen: chip 1 lights. A timeline of sends runs under the gauge, one tick per send, with no year markers. Each good send nudges the needle up a hair, each bad send knocks it down. Then a lease document with an end date slides in and is crossed out. Gloss card: domain reputation · the part of your reputation that belongs to your domain name.
Start with how reputation builds. Continuously. There's no annual reset and no scheduled forgiveness. Think of it like a credit score, not a lease. A lease ends on a date and you walk away clean. A credit score just keeps a running record. Good sending builds it over months and years. Bad sending damages it.
03 · What moves it · 0:44
On screen: chip 2 lights. Four small weights hang from the needle: complaints, bounces, engagement, blocklist history. The calendar from scene 00 flips again, and none of the weights fall off.
What moves it? Spam complaints. Bounce rates. Engagement, like opens, clicks, replies and deletes. And your history on blocklists. None of these clear on a schedule. They're a record of what you've done.
04 · Recent sends count more · 0:56
On screen: the timeline under the gauge. The last stretch of sends glows brighter than the old ones, and the needle follows the bright stretch more than the dim one.
One nuance. Providers weigh history differently. Gmail gives more weight to recent behaviour than to old behaviour. So a clean recent stretch after a rough year gets noticed sooner there. But sooner still isn't a calendar reset.
05 · Going quiet isn't a fresh start · 1:10
On screen: the timeline goes blank for a stretch. The good ticks from the early timeline dim one by one while nothing new is added. The needle sinks a little.
What if you just stop sending for a while, and let it cool off? That isn't a fresh start either. When a domain goes quiet, the trust you built fades, because providers weigh recent engagement far more than the past. A credit score doesn't improve because you stopped using the card.
06 · What brings it back · 1:30
On screen: chip 3 lights. Four cards stack beside the gauge: authentication, list hygiene, suppress the unengaged, watch complaints. The timeline fills with clean ticks and the needle climbs, one step per tick, never jumping.
What brings it back? Consistent clean sending. Authentication that passes. Good list hygiene. Suppressing contacts who don't engage. And watching your complaint rate. Where? The biggest mailbox provider offers a free reputation dashboard that shows your reputation over time. Recovery takes sustained good sending, and the worse the damage, the longer it takes.
07 · Recap · 1:49
On screen: the calendar page and the still needle, then the climbing needle. All three chips lit.
Start this week, not in January. Check your authentication passes. Suppress the contacts who don't engage. Keep sending, steadily and cleanly, rather than going quiet. And watch the reputation dashboard, send by send.
08 · Close · 2:03
On screen: gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next video, 021.003.013 "Does SPF alignment mean the same as DKIM alignment?", no subscribe ask.
List hygiene is one part of the way back, and it's the part Review My Emails handles. Worried about a blocklist? Our free blocklist directory explains each one. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... does SPF alignment mean the same as DKIM alignment?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.005.013-reputation-never-resets-myth.md
00 · Does domain reputation reset every year? (hook)
Almanac ids in this scene: 021.002.018
The myth
the title question, Lora, large: "Does domain reputation reset every year?" Sally's score gauge, the needle low. A wall calendar flips to January 1. The needle does not move (M2). Three numbered chips: how reputation builds · what moves it · what brings it back.
a calendar page turning and a needle standing still. Reveals: (1) the question, (2) the low needle, (3) the calendar flips, (4) the needle holds, (5) the chips.
concept sender-reputation (the score gauge, M-33).
the turn is "There's no such date." (M1, varied: "No." is taken by 021.002.018, and the calendar is the picture).
01 · Brought to you by, woven in
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
02 · How reputation builds
How reputation builds
chip 1 lights. A timeline of sends runs under the gauge, one tick per send, with no year markers. Each good send nudges the needle up a hair, each bad send knocks it down. Then a lease document with an end date slides in and is crossed out. Gloss card: domain reputation · the part of your reputation that belongs to your domain name.
the needle moves once per send, never once per year. Reveals: (1) the timeline, (2) good sends nudge up, (3) a bad send knocks down, (4) the lease crossed out.
concept sender-reputation (M-33). domain-reputation is gloss tier.
one analogy, the answer's own (S4). "months and years" is the answer's wording for building, not for recovery.
03 · What moves it
What moves it
chip 2 lights. Four small weights hang from the needle: complaints, bounces, engagement, blocklist history. The calendar from scene 00 flips again, and none of the weights fall off.
a count of weights, four, and none dropping when the page turns. Reveals: (1) to (4) one weight per click, (5) the page flips, the weights stay.
concepts complaint-rate (M-48, M-25), bounce (M-15, M-18), engagement-signal (M-15, M-12), blocklist (the book held open at the gate, M-18, M-20), each drawn small on the gauge.
the answer's fifth input, "spam trap hits", is a held word and is left out. "None of these" refers to the four named.
04 · Recent sends count more
Recent sends count more
the timeline under the gauge. The last stretch of sends glows brighter than the old ones, and the needle follows the bright stretch more than the dim one.
brightness is weight. Recent sends drawn brighter, so they pull harder on the needle. Reveals: (1) the recent stretch brightens, (2) the needle leans toward it.
concept sender-reputation (M-33).
no "three months" or "months" voiced (the answer's example length sits beside C33).
05 · Going quiet isn't a fresh start
Almanac ids in this scene: 012.001.010
Going quiet
the timeline goes blank for a stretch. The good ticks from the early timeline dim one by one while nothing new is added. The needle sinks a little.
the empty stretch on the timeline, and the old good ticks dimming. Reveals: (1) the blank stretch, (2) the old ticks dim, (3) the needle sinks.
concept sender-reputation (M-33). reputation-decay is gloss tier.
012.001.010 says quiet erodes "accumulated sender trust". The script never says quiet erases bad history, which no answer claims. The answer's day counts are left out (V9).
06 · What brings it back
What brings it back
chip 3 lights. Four cards stack beside the gauge: authentication, list hygiene, suppress the unengaged, watch complaints. The timeline fills with clean ticks and the needle climbs, one step per tick, never jumping.
the needle climbs one step per clean send. No time labels on the timeline (C33). Reveals: (1) to (4) one card per click, (5) the clean ticks, the climb.
concepts sender-reputation (M-33) and suppression-list (the pot with its lid, M-23, M-24) for card 3.
no recovery length (C33). "the worse the damage, the longer it takes" is the answer's "sometimes longer depending on how bad the damage was", which every recovery sibling agrees with.
07 · Recap
The recap
the calendar page and the still needle, then the climbing needle. All three chips lit.
the needle, held.
callbacks only (S5).
08 · Close
Almanac ids in this scene: 021.003.013
Start with the list
gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next video, 021.003.013 "Does SPF alignment mean the same as DKIM alignment?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/directory, named in the VO above.
the dot grid pours into the three pots. No share is shown or claimed.
concept list-cleaning (M-25, M-23, M-24).
"one part of the way back", never the whole of it. The clean does not reset or repair reputation, fix authentication or clear a blocklist history. The next video is named by its Almanac question word for word (S8, added in the Q sweep 2026-09-30, it was the batch's last). Totals: 9 scenes. 385 spoken words (recounted 2026-09-30, Q sweep). About 2:19 at 166 words a minute, about 2:30 with scene breaks. Every scene is 20 to 70 words (S2). Short cut (R12): removed in the taste pass. The video now runs past 2:00, so no Short cut is made from it.
V046Does SPF alignment mean the same as DKIM alignment?
checkedOpen questions for YT
- Episode number: in the Myths series, set by the Video Studio PM.
- C35: , DKIM "survives forwarding intact" (021.003.013) against "body modification breaks the DKIM signature" (021.003.004).
- F1: (plain gloss "where bounces go") and F2 (new dial piece).
00 · Does SPF alignment mean the same as DKIM alignment? (hook) · 0:00
On screen: the title question, Lora, large: "Does SPF alignment mean the same as DKIM alignment?" Two tags, SPF alignment and DKIM alignment, slide toward each other to merge into one. They don't merge. They stop side by side, still two. Three numbered chips: what each one checks · why DMARC needs only one · the one that travels with the email.
Does SPF alignment mean the same as DKIM alignment? Sally Send keeps seeing the word alignment, once next to SPF and once next to DKIM. Same word, so it's one check with two names, right? Same word. Different check. Three parts to this. What each one checks. Why DMARC needs only one. And the one that travels with the email.
01 · Brought to you by, woven in · 0:21
On screen: no cut away, no ad break. The two tags hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
At Review My Emails we check addresses, and before any of that matters, your mail has to prove who sent it.
02 · One letter, three labels · 0:29
On screen: chip 1 lights. One letter, held still. Three labels appear on it, one per click: front From: sally@send-more.example, back return address, and a seal. Gloss card: alignment · the check that the domain a reader sees in the From line matches the domain that actually passed the authentication.
What's being checked? Picture your email as a letter. On the front, the name your subscriber sees, your From address. On the back, a return address, where bounces go. And a seal, your DKIM signature, stamped with a domain. Alignment asks one question. Does the name on the front match the one it's checked against?
03 · SPF alignment: the front against the back · 0:49
On screen: an arrow draws from the back label to the front. The back label fills in: Return-Path: …@mail.send-more.example. The front: From: sally@send-more.example. The arrow waits, neither teal nor coral yet (scene 06 settles it).
First, SPF alignment. It compares the front with the back. The return address has a few names, the envelope sender, or the return path. It's the domain SPF checks. Say Sally's mail goes out from mail dot send more dot example, but her From line says send more dot example. For SPF alignment to hold, SPF has to pass on the right domain.
04 · DKIM alignment: the front against the seal · 1:12
On screen: a second arrow draws, from the seal to the front. The seal reads d=send-more.example. The arrow turns teal. Both arrows now point at the one front label.
DKIM alignment works differently. It compares the front with the seal. Every DKIM signature carries a d equals tag, the domain that signed it. If the seal says send more dot example, and the From says sally at send more dot example, that's aligned. Two different labels, checked against the same front.
05 · The twist: a perfect seal that doesn't count · 1:31
On screen: the seal swaps to d=[your tool's domain], with a small signature valid tick beside it. The arrow to the front turns coral anyway. Caption: valid signature · not aligned.
The seal can be perfect and still not count. If the domain on the seal doesn't match the From, DKIM alignment fails, even when the signature itself is technically valid. The receiving side isn't only asking, is this seal real? It's asking, whose seal is it?
06 · How close is close enough? · 1:49
On screen: the scene 03 arrow comes back. A dial on the letter reads relaxed: the arrow turns teal. The dial clicks to strict: the same arrow turns coral. Gloss card: organisational domain · the main domain a subdomain hangs off.
How close is close enough? That's the mode. In relaxed mode, the default, the two domains only need to share the same organisational domain. So mail dot send more dot example lines up with send more dot example. In strict mode, they have to match exactly. Strict is tighter, and more fragile if you send from subdomains.
07 · Why DMARC needs only one · 2:10
On screen: chip 2 lights. The back arrow turns coral, labelled forwarded then tool's own return path. The seal arrow stays teal. A DMARC card beside the letter needs one teal arrow, gets it, and ticks pass.
Do you need both to line up? No. DMARC only needs one of the two to align and pass. And SPF alignment fails often, with forwarded email, or when your email marketing tool uses its own return path domain. When that happens, DKIM alignment can carry the whole thing on its own.
08 · The one that travels with the email · 2:29
On screen: chip 3 lights. The letter is picked up and re-posted from a second post box. The back label smudges, coral. The seal rides along untouched, teal. Then a second trip: this forwarder stamps a footer onto the letter, and the seal cracks, coral.
Why can DKIM carry it? Forwarding posts the letter again, from a new place, and that breaks SPF almost every time. The seal travels with the letter. So as long as nobody changes what's inside on the way, DKIM gets through. A forwarder that adds a footer or a banner breaks the seal too. That's why leaning on SPF alone is risky.
09 · Where to check it · 2:51
On screen: a real envelope's header sheet opens, the three lines lit one per click: From: · Return-Path: · DKIM-Signature: … d=. Each pairs with its label on the letter. The sheet drops into a panel labelled email header analyzer, which marks each alignment teal or coral.
How do you know which one lines up for you? Open the headers of a real email you sent. Find the From. Find the return path. Find the d equals tag in the DKIM signature. Do the domains match yours? Our free Email Header Analyzer does that reading for you, and shows exactly what's aligned and what's not.
10 · Recap · 3:13
On screen: the letter, both arrows teal. All three chips lit.
Your move. Send yourself an email. Check both alignments, not just pass or fail. If only SPF lines up, get DKIM set up and aligned with your own domain, because that's the one that travels with the email.
11 · Close · 3:27
On screen: the aligned letter lands on a doorstep. Zoom out: a street of doors, some lit, some dark. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.003.006 "Do I need BIMI to pass DMARC?", no subscribe ask.
One test email and the free Email Header Analyzer will show you which alignment holds. Your DNS stays yours. Review My Emails checks the addresses you send to. Stuck on alignment right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... do I need BIMI to pass DMARC?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.003.013-spf-vs-dkim-alignment-myth.md
00 · Does SPF alignment mean the same as DKIM alignment? (hook)
The myth
the title question, Lora, large: "Does SPF alignment mean the same as DKIM alignment?" Two tags, SPF alignment and DKIM alignment, slide toward each other to merge into one. They don't merge. They stop side by side, still two. Three numbered chips: what each one checks · why DMARC needs only one · the one that travels with the email.
two tags that won't merge into one (M2). Reveals: (1) the question, (2) the two tags slide, (3) they stop apart, (4) the chips.
concept alignment (two labels sliding until they line up or don't). The tags that won't merge are the myth, then they retire.
01 · Brought to you by, woven in
no cut away, no ad break. The two tags hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · One letter, three labels
What each one checks
chip 1 lights. One letter, held still. Three labels appear on it, one per click: front From: sally@send-more.example, back return address, and a seal. Gloss card: alignment · the check that the domain a reader sees in the From line matches the domain that actually passed the authentication.
one letter, three labels. Every check in this video is an arrow between two of them, and one end is always the front. Reveals: (1) the letter, (2) the From, (3) the return address, (4) the seal, (5) the gloss.
concept alignment (two labels on the same envelope). Registry pieces for spf (the guest list) and dkim (the seal) are the labels' small marks.
SPF, DKIM and DMARC are named, not taught (S6). The gloss is the registry line.
03 · SPF alignment: the front against the back
SPF alignment
an arrow draws from the back label to the front. The back label fills in: Return-Path: …@mail.send-more.example. The front: From: sally@send-more.example. The arrow waits, neither teal nor coral yet (scene 06 settles it).
one arrow, back to front. Reveals: (1) the arrow, (2) the return path domain, (3) the From domain.
the letter from scene 02, back label lit.
the answer's own example, on demo domains (V7). The verdict for a subdomain waits for the mode in scene 06, so this scene takes no side (G2).
04 · DKIM alignment: the front against the seal
a second arrow draws, from the seal to the front. The seal reads d=send-more.example. The arrow turns teal. Both arrows now point at the one front label.
two arrows, one target. That picture is the answer to the title. Reveals: (1) the second arrow, (2) d=send-more.example, (3) teal, (4) both arrows on the front.
the letter, seal lit.
05 · The twist: a perfect seal that doesn't count
the seal swaps to d=[your tool's domain], with a small signature valid tick beside it. The arrow to the front turns coral anyway. Caption: valid signature · not aligned.
one tick and one coral arrow on the same seal. Valid and not aligned at once. Reveals: (1) the seal's domain changes, (2) the valid tick, (3) the arrow goes coral.
the letter, seal lit. Same object, one status changes (P2).
06 · How close is close enough?
Almanac ids in this scene: 021.003.013
the scene 03 arrow comes back. A dial on the letter reads relaxed: the arrow turns teal. The dial clicks to strict: the same arrow turns coral. Gloss card: organisational domain · the main domain a subdomain hangs off.
one arrow, one dial, two positions. The dial changes the verdict, the domains don't change. Reveals: (1) the arrow, (2) relaxed, teal, (3) strict, coral, (4) the gloss.
the letter, with a two-position dial. New piece, proposed for the registry.
021.003.013 "In relaxed mode (the default), the domains just need to share the same organizational domain... In strict mode, the domains must match exactly. Strict mode is tighter but also more fragile if you're using subdomains for sending."
07 · Why DMARC needs only one
Why DMARC needs only one
chip 2 lights. The back arrow turns coral, labelled forwarded then tool's own return path. The seal arrow stays teal. A DMARC card beside the letter needs one teal arrow, gets it, and ticks pass.
one of two. The DMARC card counts arrows and needs one. Reveals: (1) the back arrow goes coral, (2) the two reasons, (3) the seal arrow holds teal, (4) DMARC ticks pass.
the letter, and the dmarc instruction card from the registry pinned beside it.
08 · The one that travels with the email
Almanac ids in this scene: 021.003.004, 021.003.013
The one that travels with the email
chip 3 lights. The letter is picked up and re-posted from a second post box. The back label smudges, coral. The seal rides along untouched, teal. Then a second trip: this forwarder stamps a footer onto the letter, and the seal cracks, coral.
one trip, one label lost, one label kept. A second trip that changes the letter loses both. Reveals: (1) the re-post, (2) the back label smudges, (3) the seal stays teal, (4) the footer trip, the seal cracks.
021.003.013 "Email forwarding breaks SPF almost every time. DKIM travels with the message, so it survives forwarding intact." and 021.003.004 "any body modification (footers, banners) breaks the DKIM signature too." The VO says only what both agree on (G3), see flag F4 (C35).
the letter. Forwarding is the letter re-posted, so the simile carries (T10). 021.003.004 owns forwarding in full, this scene points forward to it in one line of the description.
09 · Where to check it
Almanac ids in this scene: 021.002.016, 021.003.013
Where to check it
a real envelope's header sheet opens, the three lines lit one per click: From: · Return-Path: · DKIM-Signature: … d=. Each pairs with its label on the letter. The sheet drops into a panel labelled email header analyzer, which marks each alignment teal or coral.
three lines on one real message, two verdicts. Reveals: (1) the header sheet, (2) to (4) one line per click, (5) the analyzer panel.
the header sheet from the Myths clean-list video (021.002.016, scene 03b), reused (S5).
021.003.013 "the free Email Header Analyzer at RME will show you exactly what's aligned and what's not."
header names only as the answer gives them (MAIL FROM or return path, the d= tag in the DKIM-Signature header, the From header). No terminal commands (P7).
10 · Recap
The recap
the letter, both arrows teal. All three chips lit.
two arrows, one front, both teal.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.003.006
Who's at the other end
the aligned letter lands on a doorstep. Zoom out: a street of doors, some lit, some dark. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.003.006 "Do I need BIMI to pass DMARC?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
one letter, a street of doors. Zoom out to show scale (N3). No share claimed.
concept list-cleaning (M-25, M-23, M-24).
"Your DNS stays yours": nothing implies cleaning fixes SPF, DKIM or DMARC. Totals: 12 scenes. 623 spoken words (recounted 2026-09-30, Q sweep). About 3:53 at 166 words a minute, a little longer with scene breaks. Every scene is 20 to 70 words (S2).
V047Do I need BIMI to pass DMARC?
checkedOpen questions for YT
- Episode number: , set by the Video Studio PM.
- C36: , a contradiction on whether DMARC enforcement lifts deliverability directly (003.004.009 against 021.003.002).
00 · Do I need BIMI to pass DMARC? (hook) · 0:00
On screen: the title question, Lora, large: "Do I need BIMI to pass DMARC?" An inbox row, Sally Send, with an empty logo circle. A DMARC pass tick tries to wait for the logo before it lands. It doesn't wait. It lands, logo circle still empty. Three numbered chips: what DMARC does on its own · what BIMI asks for first · what to set up, in order.
Do I need BIMI to pass DMARC? Sally Send keeps seeing brands with their logo right next to their name in the inbox, and she figures that logo must be part of passing. It's the other way round. In three steps, then. What DMARC does on its own. What BIMI asks for first. And what to set up, in order.
01 · Brought to you by, woven in · 0:21
On screen: no cut away, no ad break. The inbox row holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails cleans lists, and just like a clean list, a logo in the inbox is something you earn in the right order.
02 · What DMARC does on its own · 0:31
On screen: chip 1 lights. A DMARC instruction card pinned at a gate. Two envelopes arrive with send-more.example written on them. One has the matching seal and goes through. The other's seal doesn't match, and the card turns it away. Gloss card: email spoofing · sending mail that claims to come from a domain it does not come from.
Start with DMARC. It's your domain's authentication policy. It tells receiving servers what to do when an email fails the SPF and DKIM alignment checks, where the domain that passed has to match your From. It works completely on its own. And it's what protects your domain from being spoofed.
03 · What BIMI is · 0:49
On screen: the inbox row from the hook. The logo fills the circle beside Sally Send. Gloss card: BIMI · a specification that displays a sender's verified logo next to their messages in supported inboxes. A small label under it: for the reader, not the filter.
And BIMI? It's a separate layer on top. BIMI lets your brand logo appear next to your sender name, in inboxes that support it, like Gmail and Yahoo Mail. It's a visual trust signal. Not an authentication check.
04 · A race and a trophy · 1:03
On screen: a track with a finish line labelled DMARC. A runner crosses it, and a trophy labelled BIMI waits on a stand past the line. An arrow draws from the trophy back to the line, one way only. No arrow comes back.
Think of it like a race and a trophy. DMARC is the race. BIMI is the trophy. You can finish the race and never collect a trophy. But nobody hands you the trophy until you've crossed the line. BIMI is the reward for getting your authentication in order, not a requirement to get there.
05 · What BIMI asks for first · 1:22
On screen: chip 2 lights. A three-step dial on the finish line: none · quarantine · reject. At none the line is dashed, coral, and a forged envelope carries Sally's logo through. The dial clicks to quarantine, then reject: the line goes solid teal and the forged envelope stops. A small certificate card, VMC, clips onto the trophy. Gloss card: enforcement · a DMARC policy that acts on failing mail, quarantine or reject, rather than only watching.
Where's the finish line? DMARC at enforcement. That means a policy of quarantine or reject. At none, DMARC only watches, and mail that doesn't line up still reaches the inbox. So a forger using your domain would get your logo right next to their phishing email. That's why BIMI won't show at none. And most mailbox providers also want a Verified Mark Certificate before they'll show it.
06 · The twist: skipping it changes nothing · 1:47
On screen: the trophy is lifted off its stand. The DMARC pass tick and the gate from scene 02 don't move. Then the trophy goes back, and a small arrow points from it down to the finish line: the lift comes from there.
Skipping BIMI changes nothing about DMARC. Not your pass rate. Not your domain protection. Not one bit. And the logo doesn't lift your inbox placement on its own either. When senders with a logo do better, it comes from the work BIMI made them do first.
07 · What to set up, in order · 2:04
On screen: chip 3 lights. Three numbered steps on the track: 1 DMARC · 2 enforcement · 3 BIMI, if you want it. Step 3 has a dotted outline.
What's the order? Set up DMARC first. Get it to enforcement. Then decide whether BIMI is worth the effort for your brand. It usually is. But it's optional.
08 · Where to read yours · 2:15
On screen: a DMARC record drops into a panel labelled DMARC parser. The policy value lights: p=none, and the runner's marker sits before the line. The value flips to p=quarantine, then p=reject, and the marker moves past the line.
And where are you on that track right now? Our free DMARC parser reads what's in your record today. Look for the policy. If it says none, you're watching, not protecting yet. If it says quarantine or reject, you've crossed the line, and the trophy is yours to go after.
09 · Recap · 2:33
On screen: the track, the runner past the line, the trophy on its stand. All three chips lit.
Start with your record. Read your DMARC record today. If it isn't at enforcement, that's the job, not the logo. Finish the race first. The trophy can wait, and it's yours to choose.
10 · Close · 2:45
On screen: the inbox row with Sally's logo, then zoom out to a list of rows, some with a person at the other end, some empty. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.014 "Are role-based emails (info@, sales@) always bad?", no subscribe ask.
Read your record in the free DMARC parser, get it to enforcement, and the logo becomes yours to go after. Review My Emails keeps the list behind it clean. Set up authentication for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... are role based emails, info at and sales at, always bad?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.003.006-bimi-not-needed-for-dmarc-myth.md
00 · Do I need BIMI to pass DMARC? (hook)
The myth
the title question, Lora, large: "Do I need BIMI to pass DMARC?" An inbox row, Sally Send, with an empty logo circle. A DMARC pass tick tries to wait for the logo before it lands. It doesn't wait. It lands, logo circle still empty. Three numbered chips: what DMARC does on its own · what BIMI asks for first · what to set up, in order.
a pass that doesn't need the logo (M2). Reveals: (1) the question, (2) the empty logo, (3) the tick lands anyway, (4) the chips.
concept bimi (the inbox row, logo beside the message).
01 · Brought to you by, woven in
no cut away, no ad break. The inbox row holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What DMARC does on its own
Almanac ids in this scene: 003.003.001, 021.003.013
What DMARC does on its own
chip 1 lights. A DMARC instruction card pinned at a gate. Two envelopes arrive with send-more.example written on them. One has the matching seal and goes through. The other's seal doesn't match, and the card turns it away. Gloss card: email spoofing · sending mail that claims to come from a domain it does not come from.
two envelopes, one card, one turned away. No logo anywhere on screen. Reveals: (1) the card, (2) the envelopes, (3) one through, one turned away, (4) the gloss.
concepts dmarc (the instruction card beside the gate) and spoofing (a second envelope with the same name and a seal that does not match). The seal is the one from 021.003.013 (S6 callback).
DMARC is named, not taught (S6, 003.003.001). "Alignment" is a one-line callback.
03 · What BIMI is
the inbox row from the hook. The logo fills the circle beside Sally Send. Gloss card: BIMI · a specification that displays a sender's verified logo next to their messages in supported inboxes. A small label under it: for the reader, not the filter.
one row, one logo. It changes what a reader sees and nothing else. Reveals: (1) the row, (2) the logo fills, (3) the gloss, (4) the label.
concept bimi.
04 · A race and a trophy
Almanac ids in this scene: 021.003.006, 021.003.007
a track with a finish line labelled DMARC. A runner crosses it, and a trophy labelled BIMI waits on a stand past the line. An arrow draws from the trophy back to the line, one way only. No arrow comes back.
one arrow, one direction. BIMI needs DMARC, DMARC needs nothing from BIMI. Reveals: (1) the track, (2) the runner crosses, (3) the trophy, (4) the one-way arrow.
new piece, proposed: the finish line and trophy. It is the Almanac's own picture (021.003.006 "the reward", 021.003.007 "the trophy").
05 · What BIMI asks for first
What BIMI asks for first
chip 2 lights. A three-step dial on the finish line: none · quarantine · reject. At none the line is dashed, coral, and a forged envelope carries Sally's logo through. The dial clicks to quarantine, then reject: the line goes solid teal and the forged envelope stops. A small certificate card, VMC, clips onto the trophy. Gloss card: enforcement · a DMARC policy that acts on failing mail, quarantine or reject, rather than only watching.
three steps on one dial. The logo can only light on two of them. Reveals: (1) the dial, (2) none, the forger gets the logo, (3) quarantine and reject, the forger stops, (4) the VMC card, (5) the gloss.
the finish line from 04 with the dial on it. dmarc-policies (monitor, quarantine, reject) is the registry concept for the three steps.
66 words, under the 70 cap (S2). "VMC" is named once and left at that (P6: a word needing more than a line gets its own video).
06 · The twist: skipping it changes nothing
Almanac ids in this scene: 021.003.002, 021.003.007
the trophy is lifted off its stand. The DMARC pass tick and the gate from scene 02 don't move. Then the trophy goes back, and a small arrow points from it down to the finish line: the lift comes from there.
take the trophy away, nothing on the track changes. Reveals: (1) the trophy lifts off, (2) the tick holds, (3) the arrow to the line.
the track and trophy from 04.
no claim that enforcement itself lifts placement (that sits against 021.003.002, "Do DKIM and DMARC improve inbox placement automatically?"). Only the prerequisites line from 021.003.007 is voiced.
07 · What to set up, in order
What to set up, in order
chip 3 lights. Three numbered steps on the track: 1 DMARC · 2 enforcement · 3 BIMI, if you want it. Step 3 has a dotted outline.
three steps, the third one optional. Reveals: (1) to (3) one step per click.
the track from 04.
08 · Where to read yours
Almanac ids in this scene: 003.004.009, 021.003.006
a DMARC record drops into a panel labelled DMARC parser. The policy value lights: p=none, and the runner's marker sits before the line. The value flips to p=quarantine, then p=reject, and the marker moves past the line.
one value on one record places you on the track. Reveals: (1) the record, (2) the parser panel, (3) p=none, before the line, (4) quarantine or reject, past it.
the track from 04, with the parser panel.
021.003.006 "our free DMARC Parser can help you read what's actually in your record today." 003.004.009 "At p=none, you're running in monitoring mode, learning what's happening to your mail but not blocking anything."
the tag name p= is shown, not taught. No record syntax beyond it (P7).
09 · Recap
The recap
the track, the runner past the line, the trophy on its stand. All three chips lit.
one line crossed, one trophy optional.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 021.002.014
Who sees the logo
the inbox row with Sally's logo, then zoom out to a list of rows, some with a person at the other end, some empty. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.014 "Are role-based emails (info@, sales@) always bad?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
one row, then many. Zoom out to show scale (N3). No share claimed.
concept list-cleaning (M-25, M-23, M-24).
nothing implies cleaning sets up DMARC or BIMI. The next video's question is word for word, with "info@" and "sales@" spoken as "info at" and "sales at". Totals: 11 scenes. 515 spoken words (recounted 2026-09-30, Q sweep). About 3:11 at 166 words a minute, a little longer with scene breaks. Every scene is 20 to 70 words (S2).
V048Are role-based emails (info@, sales@) always bad?
checkedOpen questions for YT
- Episode number: , set by the Video Studio PM.
- F2: , a soft mismatch on how email marketing tools treat role addresses (021.002.014 against 005.007.002).
00 · Are role-based emails (info@, sales@) always bad? (hook) · 0:00
On screen: the title question, Lora, large: "Are role-based emails (info@, sales@) always bad?" Sally's list, a column of info@, sales@, support@ rows. A big DELETE ALL stamp swings down at them and stops in mid air. Three numbered chips: why they cause trouble · when they're fine · how to decide, one by one.
Are role based emails, info at and sales at, always bad? Sally Send's list has dozens of them. Info at. Sales at. Support at. Someone told her to delete every single one. Depends who's reading. Here's what to weigh, in three parts. Why they cause trouble. When they're fine. And how to decide, one by one.
01 · Brought to you by, woven in · 0:19
On screen: no cut away, no ad break. The role rows hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
At Review My Emails we sort role addresses into keep, monitor and suppress when we clean a list, so let's look at what sits behind them.
02 · One door, a crowd behind it · 0:28
On screen: chip 1 lights. A street of three doors, each labelled info@. Behind the first, one mailbox slot, lit. Behind the second, five slots lighting in turn. Behind the third, an empty hallway and a pile of post. No people drawn (T11). Gloss card: role address · an address tied to a job rather than a person, like info@ or support@.
What is one? A role address goes to a job or a department, not a person. Info at, sales at, support at, billing at, no reply at. Picture one front door with people behind it. Some doors, one person owns. Some, a rotating team of five. And some, nobody opens at all.
03 · Nobody owns the decision to open · 0:47
On screen: an envelope slides under the five-person door. It passes from hand to hand, and nobody opens it. It ends face down on a desk. A small gauge beside the street drifts down one notch.
That's the real risk. Not the format of the address. What happens on the other end. When your email lands behind a shared door, nobody owns the decision to open it. Nobody opens because they meant to. Nobody clicks because they're interested. So engagement stays low, and quiet subscribers drag your sender reputation down over time, whether they bounce or not.
04 · The stranger behind sales@ · 1:09
On screen: the sales@ door opens on one lit mailbox slot. Your envelope lands. The small unsubscribe link at the bottom stays dark, and a large spam button lights instead. The button's light travels back up the street to the gauge.
And there's the complaint side. Say sales at filters down to a busy sales manager who never signed up for your emails. They're more likely to hit mark as spam than go looking for the unsubscribe link. One person tidying their inbox becomes your deliverability problem.
05 · The twist: two doors you never knock on · 1:26
On screen: two more doors at the end of the street, abuse@ and postmaster@, each with a coral suppress tag already on it. The abuse@ door opens a crack on a desk labelled abuse desk, a stack of complaint files on it.
Two role addresses aren't a judgement call at all. Abuse at, and postmaster at. Always suppress them. Abuse at is where an abuse desk usually reads, the team that investigates complaints about spam. So a marketing email there lands with the people whose job is spam complaints.
06 · When they're fine · 1:44
On screen: chip 2 lights. The support@ door: a ticket goes out through it, and a confirmation comes back to the same door, teal. Then an info@ door with a handshake icon beside it, teal.
When are they fine? Transactional email, for a start. If a customer opens a support ticket from support at their company, the confirmation goes right back there. That's the right door. And some B2B mail too. If info at is the contact your sales team got in a real conversation, it might reach exactly the right person. Context matters.
07 · How to decide: what it does, what you send · 2:06
On screen: chip 3 lights. A four-line checklist appears beside the street, the first two lines lighting as said: ever opened or clicked? · what are you sending?.
How do you decide, one by one? Ask four questions. First, has it ever opened or clicked anything? If it's sat on your list with zero engagement, treat it like any other quiet contact. Second, what are you sending? A reply to a request is fine. A promotional newsletter to a scraped info at is something else.
08 · How to decide: where it came from, what domain · 2:27
On screen: the last two checklist lines light: how did it get here? · what domain is it on?. Then two rows on one company: finn@saltmarsh-outfitters.example and admin@saltmarsh-outfitters.example, and one more, info@megaphone.invalid. Each gets its history column: opens, clicks, source.
Third, how did it get on your list? One that signed up through a real form is different from one lifted off a trade show spreadsheet. And fourth, what domain is it on? A healthy, active domain is a much softer risk than one that hasn't sent or received real email in years. Your email marketing tool shows each address's history, so start there.
09 · Recap · 2:50
On screen: the three rows get their verdicts: finn@ teal keep, admin@ amber monitor, info@megaphone.invalid coral suppress. The two end doors, abuse@ and postmaster@, stay coral. All three chips lit.
Here's the rule of thumb. Don't delete them all, and don't keep them all. Judge each role address by what it does, not by its name. Watch the metrics. If it doesn't open, doesn't click, and doesn't interact over a reasonable window, suppress it. It's not personal. It's list hygiene.
10 · Close · 3:08
On screen: the third door from scene 02, the empty hallway, the pile of post growing. Then the dot grid pours into the three verdict pots. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.001.018 "Myth: Removing the tracking pixel improves inbox placement. True or False?", no subscribe ask.
Hardest to spot are the doors nobody opens. They don't bounce. They just sit there, filling up. Finding those is Review My Emails' job. Run a list through RME Clean and you get back a file of what to keep, monitor and suppress. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... myth. Removing the tracking pixel improves inbox placement. True or false?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.014-role-based-emails-myth.md
00 · Are role-based emails (info@, sales@) always bad? (hook)
The myth
the title question, Lora, large: "Are role-based emails (info@, sales@) always bad?" Sally's list, a column of info@, sales@, support@ rows. A big DELETE ALL stamp swings down at them and stops in mid air. Three numbered chips: why they cause trouble · when they're fine · how to decide, one by one.
a stamp that won't come down (M2). Reveals: (1) the question, (2) the role rows, (3) the stamp stops, (4) the chips.
concept role-address, then the stamp retires.
01 · Brought to you by, woven in
no cut away, no ad break. The role rows hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · One door, a crowd behind it
Almanac ids in this scene: 005.007.009
Why they cause trouble
chip 1 lights. A street of three doors, each labelled info@. Behind the first, one mailbox slot, lit. Behind the second, five slots lighting in turn. Behind the third, an empty hallway and a pile of post. No people drawn (T11). Gloss card: role address · an address tied to a job rather than a person, like info@ or support@.
three doors, the same name, and behind them one, five and zero people. Reveals: (1) the street, (2) one, (3) five, (4) zero, (5) the gloss.
concept role-address (one door, a crowd behind it, nobody who owns it).
the gloss is the registry line trimmed at its first clause, the same trim as 005.007.009 (P5, S6).
03 · Nobody owns the decision to open
an envelope slides under the five-person door. It passes from hand to hand, and nobody opens it. It ends face down on a desk. A small gauge beside the street drifts down one notch.
five people, zero opens. The needle moves one notch. Reveals: (1) the envelope under the door, (2) hand to hand, (3) face down, (4) the needle drops.
the door from 02, with engagement-signal (the envelope that stays face down) and sender-reputation (the score gauge, M-33) as small marks.
04 · The stranger behind sales@
the sales@ door opens on one lit mailbox slot. Your envelope lands. The small unsubscribe link at the bottom stays dark, and a large spam button lights instead. The button's light travels back up the street to the gauge.
one person, one press, one signal back to you. Reveals: (1) the lit slot, (2) the envelope lands, (3) unsubscribe stays dark, (4) the spam button lights, (5) the signal travels back.
the door from 02.
05 · The twist: two doors you never knock on
Almanac ids in this scene: 021.002.014, 023.017.001
two more doors at the end of the street, abuse@ and postmaster@, each with a coral suppress tag already on it. The abuse@ door opens a crack on a desk labelled abuse desk, a stack of complaint files on it.
two doors, no decision, both coral. Reveals: (1) the two doors, (2) the coral tags, (3) the abuse desk behind one.
the street from 02. postmaster is a registry concept (the person or team who looks after a mail system's technical health, at a mailbox provider or on the sending side), shown as a label only, not glossed.
021.002.014 "abuse@ or postmaster@ should always be suppressed per RFC 2142" and 023.017.001 "An email abuse desk is the team or automated system that receives and investigates complaints about misuse of email infrastructure, including spam... typically reachable at abuse@domain per RFC 2142."
the RFC number is not voiced (P7). No trap word anywhere near these doors (held word).
06 · When they're fine
When they're fine
chip 2 lights. The support@ door: a ticket goes out through it, and a confirmation comes back to the same door, teal. Then an info@ door with a handshake icon beside it, teal.
two teal doors, each with a reason next to it. Reveals: (1) the ticket out, (2) the confirmation back, (3) the handshake door.
the street from 02.
07 · How to decide: what it does, what you send
How to decide, one by one
chip 3 lights. A four-line checklist appears beside the street, the first two lines lighting as said: ever opened or clicked? · what are you sending?.
four questions, two lit. Reveals: (1) the checklist, (2) question one, (3) question two.
the street from 02, with the checklist.
no inactive window in days or months (the answer's "three months" would add another number to ledger C30, V9). "Scraped" is the answer's own word.
08 · How to decide: where it came from, what domain
the last two checklist lines light: how did it get here? · what domain is it on?. Then two rows on one company: finn@saltmarsh-outfitters.example and admin@saltmarsh-outfitters.example, and one more, info@megaphone.invalid. Each gets its history column: opens, clicks, source.
four questions, all lit. Three rows, three histories. Reveals: (1) question three, (2) question four, (3) the rows, (4) the history columns.
the checklist, then the three rows (T2, where to look).
09 · Recap
The recap
the three rows get their verdicts: finn@ teal keep, admin@ amber monitor, info@megaphone.invalid coral suppress. The two end doors, abuse@ and postmaster@, stay coral. All three chips lit.
three rows, three different verdicts. The name did not decide any of them.
callbacks only (S5). Verdict pots from the list-cleaning concept.
10 · Close
Almanac ids in this scene: 021.001.018
The doors nobody opens
the third door from scene 02, the empty hallway, the pile of post growing. Then the dot grid pours into the three verdict pots. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.001.018 "Myth: Removing the tracking pixel improves inbox placement. True or False?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
one door, zero people, a growing pile. Then the pots.
the door from 02, then concept list-cleaning (M-25, M-23, M-24).
the clean sorts addresses. It does not promise a role address will engage, and says nothing about reputation repair. Totals: 11 scenes. 586 spoken words (recounted 2026-09-30, Q sweep). About 3:33 at 166 words a minute, a little longer with scene breaks. Every scene is 20 to 70 words (S2).
V049Myth: Removing the tracking pixel improves inbox placement. True or False?
waiting on YTOpen questions for YT
- C34, the GAP after scene 06. 021.001.018 "Spam filters don't penalize pixels.
- Episode number: , set by the Video Studio PM.
- F2: , a new registry concept, tracking-pixel, and the bell picture.
00 · Myth: Removing the tracking pixel improves inbox placement. True or False? (hook) · 0:00
On screen: the title, Lora, large: "Myth: Removing the tracking pixel improves inbox placement. True or False?" Sally's email, a toggle beside it: tracking pixel: on. It flips to off. A spam filter gate beside the email doesn't move. The toggle's flip does nothing to it. Three numbered chips: what the pixel does · where the myth comes from · what you lose without it.
Myth. Removing the tracking pixel improves inbox placement. True or false? Sally Send read that spam filters hate tracking pixels, so she's about to switch hers off. False. Here's what the filter weighs instead. Three things cover it. What the pixel does. Where the myth comes from. And what you lose without it.
01 · Brought to you by, woven in · 0:19
On screen: no cut away, no ad break. Sally's email holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails cleans lists every day, and the tiniest thing in your email turns out to be one of the most misunderstood.
02 · What the pixel does · 0:27
On screen: chip 1 lights. Sally's email, full size. A magnifier finds one clear dot at the bottom, labelled 1 × 1. The email opens, the dot loads, and an opened tick lands in a small report panel. Gloss card: tracking pixel · a tiny invisible image in your email that counts an open when it loads.
What is a tracking pixel? A tiny image, one pixel by one, transparent, tucked into your email. When someone opens the message, their email client loads that image, and the load counts as an open. That's how your email marketing tool knows someone opened your campaign. Nearly every marketing email sent today has one.
03 · A bell over the door · 0:47
On screen: the email becomes a shop door with the dot as a small bell above it. The door opens, the bell rings, and a sound line runs to a shopkeeper labelled you.
It works like a little bell over a shop door. Someone opens the door, the bell rings, and you hear it. You, the shopkeeper. The bell is there so you know who came in. It was put up for you, and nobody else.
04 · Where the myth comes from · 1:03
On screen: chip 2 lights. The bell over the door. A small privacy tag lights beside it, teal. A thin line divides the screen: privacy on one side, deliverability on the other. The bell sits on the privacy side.
Where does the myth come from? Probably from the privacy conversation. Privacy advocates point out, rightly, that pixels let senders know when and where you opened an email, sometimes without you realising. That's a fair point. It's just a separate one from deliverability.
05 · Apple's answer was a privacy one · 1:18
On screen: the mail-privacy-protection picture from 021.013.003, called back: the open counter climbing on its own while the inbox beside it stays shut. It sits on the privacy side of the line.
Apple even added Mail Privacy Protection, which gets around pixel tracking by loading the images automatically. That's a privacy feature, not a deliverability one. It changes what you can see, not where your email lands.
06 · What the filter weighs · 1:34
On screen: outside the shop, the filter's checklist has four lines, lighting teal one per phrase: sender reputation · authentication · complaint rate · engagement. The bell is not on the list. A small image address label hangs off the bell, grey.
Open question: Do spam filters weigh the pixel at all?.
What does a spam filter look at? Your sender reputation. Your authentication records. Your complaint rates. Your engagement patterns. A tracking pixel is an image address, and it isn't on that list.
07 · The twist: what you lose · 1:46
On screen: chip 3 lights. The bell is taken down. Inside the shop, a column of subscriber rows loses its last opened column, which fades to blank. The quiet rows, which were marked, lose their marks. Gloss card: engagement segmentation · choosing who to send to by what they have done with your mail before.
Taking the pixel out can work against you. Without it, you lose your open data. And that data feeds your engagement segmentation, which does affect deliverability. So it gets harder to spot the people who've gone quiet, and to suppress them.
08 · It blinds you, not the inbox · 2:01
On screen: outside, the filter's checklist is still full, engagement lit. Inside, a you label sits in a room where the bell used to ring, and the bell's sound lines are gone.
And notice who that hurts. The inbox never needed your pixel. It's their platform, so they still see what people do. Pulling the pixel doesn't hide anything from them. It only hides it from you.
09 · What to do · 2:14
On screen: two doors side by side, one with a bell, one without, both teal. Under each, the same line: find the quiet ones · suppress them.
What should Sally do? If she has privacy reasons to skip tracking, that's a completely valid choice. She just shouldn't expect her inbox placement to budge because of it. Either way, the job doesn't change. Keep finding the people who've gone quiet, and suppress them.
10 · Recap · 2:31
On screen: the bell over the door, the sound line reaching you, the filter's checklist beside it. All three chips lit.
The short of it. The pixel is your bell. Take it down, and you hear less, and that's the part people miss. Whatever you choose, keep watching who's gone quiet, and suppress the ones who stay that way.
11 · Close · 2:45
On screen: the subscriber rows from scene 07, their marks coming back. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.008.010 "Can volume reduction fix poor sender reputation?", no subscribe ask.
The part you can't see on your own is who's gone quiet. RME Insights shows you who's still engaged, and Review My Emails checks every address before you send. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... can volume reduction fix poor sender reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.001.018-tracking-pixel-removal-myth.md
00 · Myth: Removing the tracking pixel improves inbox placement. True or False? (hook)
The myth
the title, Lora, large: "Myth: Removing the tracking pixel improves inbox placement. True or False?" Sally's email, a toggle beside it: tracking pixel: on. It flips to off. A spam filter gate beside the email doesn't move. The toggle's flip does nothing to it. Three numbered chips: what the pixel does · where the myth comes from · what you lose without it.
a switch that flips and a gate that doesn't notice (M2). Reveals: (1) the title, (2) the toggle flips, (3) the gate stays still, (4) the chips.
new, proposed: the toggle and the filter gate. The toggle retires after the hook.
01 · Brought to you by, woven in
no cut away, no ad break. Sally's email holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What the pixel does
What the pixel does
chip 1 lights. Sally's email, full size. A magnifier finds one clear dot at the bottom, labelled 1 × 1. The email opens, the dot loads, and an opened tick lands in a small report panel. Gloss card: tracking pixel · a tiny invisible image in your email that counts an open when it loads.
one dot, one pixel square, inside a whole email. The size is the point. Reveals: (1) the email, (2) the magnifier finds the dot, (3) it loads, (4) the tick in the report, (5) the gloss.
new, proposed: the magnified dot. The report panel is the open-rate counter (M-30).
03 · A bell over the door
the email becomes a shop door with the dot as a small bell above it. The door opens, the bell rings, and a sound line runs to a shopkeeper labelled you.
one bell, one listener. The line reaches you and stops. Reveals: (1) the door and bell, (2) the door opens, (3) the sound reaches you.
the bell over the door, new, proposed. It carries the video (T10).
framing only. The fact under it is scene 02's "that's how your email marketing tool knows". No filter is drawn in this scene, so it takes no side on the scene 06 GAP (G2).
04 · Where the myth comes from
Where the myth comes from
chip 2 lights. The bell over the door. A small privacy tag lights beside it, teal. A thin line divides the screen: privacy on one side, deliverability on the other. The bell sits on the privacy side.
one line, two sides, the bell on one. Reveals: (1) the bell, (2) the privacy tag, (3) the dividing line.
the bell over the door.
M4, the grain of truth first. The privacy concern is called fair.
05 · Apple's answer was a privacy one
Almanac ids in this scene: 021.013.003
the mail-privacy-protection picture from 021.013.003, called back: the open counter climbing on its own while the inbox beside it stays shut. It sits on the privacy side of the line.
the counter climbs, the inbox stays shut. Same picture as before, no new art. Reveals: (1) the callback, (2) it lands on the privacy side.
concept mail-privacy-protection (M-30, M-37), callback only (S6). Not glossed again.
the callback to the open rates video is cut in the Q sweep (Q5). The line glosses Mail Privacy Protection on its own.
06 · What the filter weighs
Almanac ids in this scene: 007.001.009, 010.013.008, 021.001.018
outside the shop, the filter's checklist has four lines, lighting teal one per phrase: sender reputation · authentication · complaint rate · engagement. The bell is not on the list. A small image address label hangs off the bell, grey.
four lines on the list, zero of them the pixel. Reveals: (1) to (4) one line per click, (5) the bell stays grey.
the bell over the door, with the filter's checklist.
07 · The twist: what you lose
What you lose without it
chip 3 lights. The bell is taken down. Inside the shop, a column of subscriber rows loses its last opened column, which fades to blank. The quiet rows, which were marked, lose their marks. Gloss card: engagement segmentation · choosing who to send to by what they have done with your mail before.
one column gone, the quiet rows can't be told apart. Reveals: (1) the bell comes down, (2) the column fades, (3) the marks go, (4) the gloss.
the bell over the door, then the subscriber rows. engagement-signal envelopes as the row marks.
08 · It blinds you, not the inbox
Almanac ids in this scene: 021.013.003
outside, the filter's checklist is still full, engagement lit. Inside, a you label sits in a room where the bell used to ring, and the bell's sound lines are gone.
same four lines outside, one blank column inside. Reveals: (1) the filter's list, unchanged, (2) the silent room.
the bell over the door, callback (S5).
021.013.003 "They don't need your tracking pixel for any of that. It's their platform." and "The signal just got hidden from you, not from the inbox."
09 · What to do
two doors side by side, one with a bell, one without, both teal. Under each, the same line: find the quiet ones · suppress them.
two choices, one job. Reveals: (1) the two doors, (2) the shared line.
the bell over the door.
10 · Recap
The recap
the bell over the door, the sound line reaching you, the filter's checklist beside it. All three chips lit.
one bell, one listener, four lines, the bell not among them.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.008.010
Who's gone quiet
the subscriber rows from scene 07, their marks coming back. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots. Then the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.008.010 "Can volume reduction fix poor sender reputation?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the marks return to the quiet rows. No share claimed.
concept list-cleaning (M-25, M-23, M-24).
no placement promise. Cleaning checks addresses, and says nothing about the pixel. Totals: 12 scenes. 492 spoken words (recounted 2026-09-30, Q sweep). About 3:05 at 166 words a minute, a little longer with scene breaks. Every scene is 20 to 70 words (S2).
V050Can volume reduction fix poor sender reputation?
waiting on YTOpen questions for YT
- Episode number: , set by the Video Studio PM.
- F1: , whether any of the answer's numbers should be voiced (each meets a ledger entry or the threshold rule).
00 · Can volume reduction fix poor sender reputation? (hook) · 0:00
On screen: the title question, Lora, large: "Can volume reduction fix poor sender reputation?" A volume dial labelled send less turns down. A reputation gauge beside it doesn't follow the dial. Three numbered chips: what mailbox providers grade · how to cut, and how to come back · what sending less can't fix.
Can volume reduction fix poor sender reputation? Sally Send's opens are sinking, complaints are creeping up, and she's wondering if she should just send less. Yes. But not for the reason you think. Three things, in order. What mailbox providers grade. How to cut, and how to come back. And what sending less can't fix.
01 · Brought to you by, woven in · 0:20
On screen: no cut away, no ad break. The dial and gauge hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
At Review My Emails the list is our job, and in this one, who you send to matters a lot more than how many.
02 · What mailbox providers grade · 0:27
On screen: chip 1 lights. A set of scales. Teal weights drop onto the left pan, labelled one per phrase: opens · clicks · replies. Coral weights onto the right: deleted unread · spam reports · ignored. The scale tips toward coral, because Sally's list is heavy on the right.
What do mailbox providers grade? Not volume alone. Gmail and Outlook grade you on a ratio. Positive signals, opens, clicks and replies, against negative ones, deletions without opening, spam reports, and being ignored. Picture a set of scales, good on one side, bad on the other.
03 · The twist: fewer weights, better tilt · 0:44
On screen: weights lift off the scale. Most come off the coral pan. A few teal ones come off too. The scale has fewer weights now, and it tips toward teal. A small counter under it reads the total going down while the tilt goes up.
When you shrink your list down to only your most engaged subscribers, that ratio improves fast. There's less mail on the scale than before. But most of what came off was on the bad side. So with fewer weights, it tips the right way. It's who's left that matters, not how many.
04 · Why that works · 1:05
On screen: a stack of unsent envelopes on the side, coral, each with a small not sent tag. None of them reaches the scale.
Why does that help? You're not hiding the bad sends. You're stopping them, while you fix the problems underneath. Every email that would have been ignored, or reported, just doesn't go out. So it can't count against you.
05 · How to cut · 1:18
On screen: chip 2 lights. Sally's list as a grid of dots. A small slice at the top, the recent openers and clickers, lights teal. Only that slice gets envelopes. Three small signal lights beside the scale: opens · complaints · bounces, each turning steady.
How do you cut? Start with your best slice, the people who've opened or clicked recently. Send only to them for a while. And watch your reputation signals the whole time. Opens holding up, complaints low, bounces low. Those are signs things are steadying.
06 · Where to watch it · 1:35
On screen: the lit slice splits by provider, and the Gmail part glows. A dashboard panel labelled Google Postmaster Tools opens beside the scale, a domain reputation line on it. As the scale tips teal, the line rises.
Where do you watch it? If Gmail is the one putting you in spam, focus your reduced sends on your Gmail addresses first. Then watch Google Postmaster Tools, where your domain reputation score moves. That's real feedback, not guesswork.
07 · How to come back · 1:49
On screen: the next band of dots below the slice lights, then the scale is watched. It holds teal. Then the next band. Each band waits for the scale to hold before the next one lights.
And when do you widen again? Once those signals hold steady for a couple of weeks. Then bring back the next group slowly, and watch again before you go further. You're earning trust back one engaged group at a time.
08 · What sending less can't fix · 2:03
On screen: the next band of dots, waiting. A few of its dots go dark before it lights. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The band pours into the three verdict pots, the dark dots into suppress.
One more thing before you widen. The people you bring back haven't heard from you in a while, and some of those addresses have died while you waited. You can't see which from the scale. So check that group before you mail it.
09 · Recap · 2:39
On screen: the scales tipping teal, the lit slice, the bands waiting their turn, the floor repaired. All three chips lit.
Your plan, then. Cut to your most engaged. Watch the signals, starting with the provider that's hurting most. Widen slowly, one group at a time. And fix the cause while you've got the breathing room.
10 · Close · 2:53
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.007.006 "Does unsubscribing mean data deletion?", no subscribe ask.
Review My Emails checks that group for you before it goes back out. Worried about a blocklist? Our free blocklist directory explains each one. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... does unsubscribing mean data deletion?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.008.010-volume-reduction-reputation-myth.md
00 · Can volume reduction fix poor sender reputation? (hook)
Almanac ids in this scene: 021.005.013
The myth
the title question, Lora, large: "Can volume reduction fix poor sender reputation?" A volume dial labelled send less turns down. A reputation gauge beside it doesn't follow the dial. Three numbered chips: what mailbox providers grade · how to cut, and how to come back · what sending less can't fix.
a dial that turns and a needle that doesn't follow it (M2). Reveals: (1) the question, (2) the dial turns down, (3) the needle stays, (4) the chips.
the volume dial is the myth and retires. The gauge is sender-reputation (M-33), a callback from 021.005.013.
01 · Brought to you by, woven in
no cut away, no ad break. The dial and gauge hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What mailbox providers grade
What mailbox providers grade
chip 1 lights. A set of scales. Teal weights drop onto the left pan, labelled one per phrase: opens · clicks · replies. Coral weights onto the right: deleted unread · spam reports · ignored. The scale tips toward coral, because Sally's list is heavy on the right.
the tilt is the ratio. Six kinds of weight, and the scale leans the way the heavier pan pulls. Reveals: (1) the scales, (2) the teal weights, (3) the coral weights, (4) the tilt.
new, proposed: the scales. The weights reuse positive-engagement and negative-engagement (registry lines, no pictures yet).
03 · The twist: fewer weights, better tilt
weights lift off the scale. Most come off the coral pan. A few teal ones come off too. The scale has fewer weights now, and it tips toward teal. A small counter under it reads the total going down while the tilt goes up.
the total drops and the tilt improves at the same time. That's the whole idea (N1). Reveals: (1) the hand, (2) mostly coral comes off, (3) a few teal, (4) the tilt swings teal, (5) the counter.
the scales.
04 · Why that works
Almanac ids in this scene: 021.008.010
a stack of unsent envelopes on the side, coral, each with a small not sent tag. None of them reaches the scale.
the coral stack that never reaches the pan. Reveals: (1) the stack, (2) the tags, (3) the scale untouched by them.
the scales, with engagement-signal envelopes (M-15, M-12).
021.008.010 "You're not hiding the bad sends. You're just stopping them while you fix the underlying problems."
"just doesn't go out... can't count against you" is the plain sum of "stopping them" and the ratio. No new claim.
05 · How to cut
How to cut, and how to come back
chip 2 lights. Sally's list as a grid of dots. A small slice at the top, the recent openers and clickers, lights teal. Only that slice gets envelopes. Three small signal lights beside the scale: opens · complaints · bounces, each turning steady.
one slice of the grid, lit. No share of the list is drawn as a figure. Reveals: (1) the grid, (2) the slice lights, (3) envelopes to the slice only, (4) the three lights.
the dot grid (list-hygiene pieces), beside the scales.
no percentage of the list, no day window, no week count, no target rate. The slice is drawn small, not measured.
06 · Where to watch it
the lit slice splits by provider, and the Gmail part glows. A dashboard panel labelled Google Postmaster Tools opens beside the scale, a domain reputation line on it. As the scale tips teal, the line rises.
one provider's slice, one line on one dashboard. The line follows the tilt. Reveals: (1) the provider split, (2) the Gmail slice, (3) the dashboard, (4) the line rises with the tilt.
the scales, with a dashboard panel. No real screenshot (brand system, demo data only).
07 · How to come back
the next band of dots below the slice lights, then the scale is watched. It holds teal. Then the next band. Each band waits for the scale to hold before the next one lights.
one band per step, and the scale checked between each. Reveals: (1) the first band, (2) the scale holds, (3) the next band.
the dot grid and the scales.
"a couple of weeks" is the answer's own phrase for the hold, not a recovery time (C33 is recovery length and stays unvoiced). No tier size.
08 · What sending less can't fix
Before you widen
the next band of dots, waiting. A few of its dots go dark before it lights. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The band pours into the three verdict pots, the dark dots into suppress.
a few dots go dark in a waiting band. No share claimed, no decay rate (C13). Reveals: (1) the band, (2) the dots go dark, (3) the gloss, (4) the pots.
the dot grid, then concept list-cleaning (M-25, M-23, M-24).
the answer's "spam traps" is a held word and is not voiced. "Content triggering filters" is voiced in the answer's own words, no trigger-word list (C25 stays unvoiced).
the clean checks addresses in the band. Nothing says it repairs reputation.
09 · Recap
The recap
the scales tipping teal, the lit slice, the bands waiting their turn, the floor repaired. All three chips lit.
fewer weights, the right tilt, a solid floor.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 021.007.006
Start with the next group
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.007.006 "Does unsubscribing mean data deletion?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/directory, named in the VO above.
the scales, teal, behind the CTA.
callbacks only. Totals: 12 scenes. 509 spoken words (recounted 2026-09-30, Q sweep). About 3:07 at 166 words a minute, a little longer with scene breaks. Every scene is 20 to 70 words (S2).
V051Does unsubscribing mean data deletion?
checkedOpen questions for YT
- Episode number: , set by the Video Studio PM.
00 · Does unsubscribing mean data deletion? (hook) · 0:00
On screen: the title question, Lora, large: "Does unsubscribing mean data deletion?" A file card, una.subscribe@pearl-diver.invalid. An unsubscribe click lands on it. A shredder beside it switches on, waits for the card, and the card doesn't go in. Three numbered chips: what an unsubscribe asks for · what a deletion request asks for · the one record worth keeping.
Does unsubscribing mean data deletion? Someone hits unsubscribe on Sally Send's newsletter, and her first thought is, now I have to delete everything I know about them. Two different requests. Here are three things to separate. What an unsubscribe asks for. What a deletion request asks for. And the one record worth keeping.
01 · Brought to you by, woven in · 0:18
On screen: no cut away, no ad break. The card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Even a list freshly cleaned by Review My Emails still has to remember who said no, and that's where this starts.
02 · What an unsubscribe asks for · 0:25
On screen: chip 1 lights. The card, filled in: name, email, purchases. A coral sticker lands on its corner: do not email. Everything else on the card stays.
What does an unsubscribe ask for? It's a marketing opt out. It says, stop sending me emails. That's it. You still have their data. Their name, their address, their purchase history. You just can't use it to send them marketing anymore.
03 · Why you keep the address · 0:40
On screen: the stickered card slides into a drawer labelled suppression list. A fresh import sheet arrives with una.subscribe@pearl-diver.invalid on it. The drawer's sticker lights, and the send to that row stops. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
In fact, you often need to keep their address, on a suppression list, so you don't accidentally email them again. A new import, a synced list, and there they are. The sticker is what stops the next send from going out.
04 · What a deletion request asks for · 0:55
On screen: chip 2 lights. A second, different form arrives on the card, labelled delete my data. It sits beside the unsubscribe click, not on top of it. No law name, no date anywhere on screen.
Deletion is a separate request. Privacy laws give people a right to have their personal data erased, and it's something they have to specifically ask for. It doesn't happen on its own when they unsubscribe.
05 · Two requests, on their own · 1:08
On screen: three cards in a row. The first has only the sticker. The second has only the deletion form. The third has both.
The two can happen on their own. Someone might unsubscribe and never ask for deletion. That's common. Someone might ask for deletion without ever unsubscribing. Less common, but it happens. Or both, at the same time.
06 · Where their data lives · 1:21
On screen: the card's copies appear in four boxes, one per phrase: email marketing tool · CRM · database · other tools. Each copy goes into the shredder in turn.
And if a deletion request does come in, take it seriously. You'd typically remove their data from your email marketing tool, your CRM, your database, and any other tools you use. Not just the one you happened to open.
07 · The twist: the shredder takes the sticker too · 1:35
On screen: the suppression drawer, closed. Beside it, a list of cards, a few of them blank, no name, no one behind them. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots, the blank cards into suppress.
Your suppression list keeps out the people who said no. What it can't catch are the addresses where nobody's left to say anything at all. They don't unsubscribe. They just sit there, taking your mail.
08 · Recap · 2:09
On screen: the three cards from scene 05, each handled: sticker kept, card shredded across four boxes, one slip kept. All three chips lit.
Two requests, two jobs. Treat an unsubscribe as stop sending, and keep the address on your suppression list. Treat a deletion request as its own job, across every tool. And decide on purpose what happens to that do not contact line, rather than losing it by accident.
09 · Close · 2:26
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.015 "Do all bounces mean invalid addresses?", no subscribe ask.
Those silent addresses are what Review My Emails checks for, every one, before you send. Not sure how your suppression data holds up across tools? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... do all bounces mean invalid addresses?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.007.006-unsubscribe-not-deletion-myth.md
00 · Does unsubscribing mean data deletion? (hook)
Almanac ids in this scene: 008.004.009
The myth
the title question, Lora, large: "Does unsubscribing mean data deletion?" A file card, una.subscribe@pearl-diver.invalid. An unsubscribe click lands on it. A shredder beside it switches on, waits for the card, and the card doesn't go in. Three numbered chips: what an unsubscribe asks for · what a deletion request asks for · the one record worth keeping.
a shredder that switches on and gets no card (M2). Reveals: (1) the question, (2) the card, (3) the click, (4) the shredder waits, (5) the chips.
new, proposed: the file card and the shredder. The unsubscriber is the one from 008.004.009.
01 · Brought to you by, woven in
no cut away, no ad break. The card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What an unsubscribe asks for
What an unsubscribe asks for
chip 1 lights. The card, filled in: name, email, purchases. A coral sticker lands on its corner: do not email. Everything else on the card stays.
one card, one sticker, nothing removed. Reveals: (1) the filled card, (2) the sticker, (3) the lines stay.
the file card.
03 · Why you keep the address
Almanac ids in this scene: 008.004.009, 021.007.006
the stickered card slides into a drawer labelled suppression list. A fresh import sheet arrives with una.subscribe@pearl-diver.invalid on it. The drawer's sticker lights, and the send to that row stops. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
one address on two sheets, one send stopped. Reveals: (1) the drawer, (2) the import, (3) the sticker lights, (4) the send stops, (5) the gloss.
the file card in a drawer. The registry's suppression-list pot is named in the gloss, not drawn, so the card stays the one picture (P3). 008.004.009 owns the pot.
021.007.006 "you often need to keep their email address on a suppression list so you don't accidentally email them again." 008.004.009 "Even if a suppressed address shows up in a new import, a purchased data set (not that you'd do that), or a synced CRM segment, the suppression check catches it before anything goes out."
04 · What a deletion request asks for
What a deletion request asks for
chip 2 lights. A second, different form arrives on the card, labelled delete my data. It sits beside the unsubscribe click, not on top of it. No law name, no date anywhere on screen.
two forms, two different requests, one card. Reveals: (1) the deletion form, (2) it sits apart from the unsubscribe.
the file card.
the legal part is the second sentence only. No law named, no window. The first and third sentences are the answer's practical point, not law.
05 · Two requests, on their own
three cards in a row. The first has only the sticker. The second has only the deletion form. The third has both.
three cards, three combinations. Reveals: (1) sticker only, (2) form only, (3) both.
the file card, three times.
06 · Where their data lives
the card's copies appear in four boxes, one per phrase: email marketing tool · CRM · database · other tools. Each copy goes into the shredder in turn.
four copies of one card, four trips to the shredder. Reveals: (1) to (4) one box per click, each copy shredded.
the file card and the shredder (T2, where the data sits).
no window for how fast (the answer's day count is law timing, R7). "Not just the one you happened to open" is the plain point of the answer's list of four places.
07 · The twist: the shredder takes the sticker too
The ones nobody can answer
the suppression drawer, closed. Beside it, a list of cards, a few of them blank, no name, no one behind them. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress. The dot grid pours into the three verdict pots, the blank cards into suppress.
the drawer for the people who said no, the pots for the addresses that can't. Reveals: (1) the drawer, (2) the blank cards, (3) the gloss, (4) the pots.
the file card, then concept list-cleaning (M-25, M-23, M-24).
"some companies keep" is the answer's own weight. The script does not say the viewer should, and says nothing about what the law allows here (R7, one sentence only, used in 04).
cleaning checks addresses. It does not handle unsubscribes or deletion requests, and the VO does not say it does. "They just sit there, taking your mail" is the registry's risky-address gloss, "An address that takes your mail without bouncing and never does anything with it" (Q sweep 2026-09-30).
08 · Recap
The recap
the three cards from scene 05, each handled: sticker kept, card shredded across four boxes, one slip kept. All three chips lit.
two requests, two different jobs, one line decided on purpose.
callbacks only (S5).
"decide on purpose" leaves the choice with the viewer. It does not advise keeping or deleting the line (R7).
09 · Close
Almanac ids in this scene: 021.002.015, 021.003.013
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.015 "Do all bounces mean invalid addresses?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the card, kept right, behind the CTA.
callbacks only.
the batch's first, 021.003.013, word for word (S8). Totals: 11 scenes. 448 spoken words (recounted 2026-09-30, Q sweep). About 2:40 at 166 words a minute, a little longer with scene breaks. Every scene is 20 to 70 words (S2).
V064Do all bounces mean invalid addresses?
checkedNo open questions are written in this script.
00 · Do all bounces mean invalid addresses? (hook) · 0:00
On screen: the title question, Lora, large: "Do all bounces mean invalid addresses?" A stack of returned parcels on Sally's desk. A big coral delete all button, her cursor on it. The button presses, and the parcels don't move (M2). Three numbered chips: the two kinds of bounce · what your tool does with the temporary ones · the bounce that's about you.
Do all bounces mean invalid addresses? Sally Send opens the report from last night's campaign. A column of bounces, and her finger is already on delete all. Hold that delete. Three things before you press it. The two kinds of bounce. What your tool does with the temporary ones. And the bounce that's about you.
01 · Brought to you by, woven in · 0:18
On screen: no cut away, no ad break. The stack holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
At Review My Emails we clean lists, and every bounce comes back with a reason attached, if you know where to look.
02 · Two kinds of bounce · 0:25
On screen: chip 1 lights. One parcel lifts off the stack. The stack splits into two piles, each parcel with a blank note waiting to be filled in.
What does a bounce tell you? Just that the email didn't deliver right now. That doesn't always mean the address is gone for good. There are two different kinds of bounce, and mixing them up is where people get into trouble.
03 · The permanent one · 0:40
On screen: the left pile. A coral note stamps onto a parcel: no such address, and the label reads bo.unce@coral-cove.invalid. It slides off the list. Gloss card: hard bounce · a bounce that is permanent. The address does not work and will not start working.
The first kind is a hard bounce. It's permanent. The address doesn't exist, or the domain is gone. It's the parcel that comes back stamped, no such address. Trying again won't change that answer. So you act on it straight away. Remove it from your active list, and don't retry.
04 · The temporary one · 0:57
On screen: the right pile. An amber note on a parcel: nobody home, trying again, label marina@tidewell-supply.example. Three small reasons tick in beside it, one per phrase: server down · slowing you down · greylisting. Gloss cards, one after the other: soft bounce · a bounce that is temporary. The address exists but could not take the message this time. greylisting · a receiving server turning a message away the first time and accepting it when a real sender tries again.
The second kind is a soft bounce. The address is real, but something got in the way. A server that's down for a while. The receiving end slowing you down. Or greylisting, where a server turns away a sender it doesn't recognise the first time, and waits to see if they come back. The address isn't bad. The timing just wasn't right.
05 · Where you read which one it was · 1:20
On screen: a bounce log row opens from each parcel. The first digit of each code lights: 5xx · mailbox does not exist under the coral note, 4xx · greylisted, try again later under the amber one. A pointer lands on the first digit, then on the words after it.
Where do you see which kind you got? Open the bounce message your tool keeps for that address. It carries a code. A code starting with a five is a permanent failure. A code starting with a four is a temporary one. That first digit is your first clue.
06 · What your tool does with the temporary ones · 1:36
On screen: chip 2 lights. The amber parcel goes back out on a courier loop, and comes back to the pile. On the next loop it is delivered, and the note turns teal: delivered.
What happens to a soft bounce next? Most email marketing tools retry it on their own. If it gets through, great. If it doesn't, the message expires. That's normal, and it doesn't mean the address is dead. So don't step in yet. Let the retry do its job.
07 · When temporary stops being temporary · 1:52
On screen: a second amber parcel keeps coming back, campaign after campaign, each return adding a faint mark on its note. A dotted line on the pile reads your tool's setting. No number on the line.
When does a soft bounce count as a dead address? That's a policy decision, not a technical one. Each tool sets its own line, and yours probably has one already. It's worth finding out where it sits. An address that keeps soft bouncing, campaign after campaign, isn't behaving like a live address anymore.
08 · The twist: a bounce that's about you · 2:12
On screen: chip 3 lights. A third parcel lands with a coral note, but this note reads refused: sender, label finn@saltmarsh-outfitters.example. Its log row starts with a 5. The pointer moves from the digit to the words after it. The address on the label stays teal. Gloss card: block bounce · a bounce where the server refused the message on reputation grounds rather than because the address is bad.
Some bounces aren't about the address at all. The server is refusing the mail because of you. That's a block bounce, and it can carry a code starting with a five, just like a hard one. The address may be fine. Your sending reputation might not be.
09 · Why telling them apart matters · 2:32
On screen: the parcels fade. A new parcel goes out to catch-all and never returns. No note, no log row, nothing. Gloss card: catch-all domain · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos. Then the dot grid pours into the three verdict pots.
Cleaning won't lift a block, that's about your sending. But the addresses that worry me most never bounce at all. On a catch-all domain, even a made up name gets accepted, so no bounce comes back to warn you.
10 · Recap: read the code, not the count · 3:04
On screen: the three parcels from scenes 03, 04 and 08, each with its note and its log row, each handled: off the list, back on the loop, a flag on Sally's sending. All three chips lit.
Read the code, then, not just the count. Remove a hard bounce the first time. Let your tool retry a soft one, and find out where it draws the line. And when the server is refusing you, not the address, look at your sending, not your list.
11 · Close · 3:20
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.007 "Can suppression lists be shared legally?", no subscribe ask.
Those silent addresses are what Review My Emails checks for, every one, before you send. Not sure what your bounces are telling you? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... can suppression lists be shared legally?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.015-not-every-bounce-is-invalid-myth.md
00 · Do all bounces mean invalid addresses? (hook)
The myth
the title question, Lora, large: "Do all bounces mean invalid addresses?" A stack of returned parcels on Sally's desk. A big coral delete all button, her cursor on it. The button presses, and the parcels don't move (M2). Three numbered chips: the two kinds of bounce · what your tool does with the temporary ones · the bounce that's about you.
one stack of returned parcels, one button that doesn't clear them. Reveals: (1) the question, (2) the stack, (3) the button, (4) nothing moves, (5) the chips.
new, proposed: the returned parcel with a courier's note.
01 · Brought to you by, woven in
no cut away, no ad break. The stack holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29). "With a reason attached" is the registry's bounce gloss.
02 · Two kinds of bounce
The two kinds of bounce
chip 1 lights. One parcel lifts off the stack. The stack splits into two piles, each parcel with a blank note waiting to be filled in.
one stack, two piles. Reveals: (1) one parcel, (2) the split into two piles.
the returned parcel.
03 · The permanent one
the left pile. A coral note stamps onto a parcel: no such address, and the label reads bo.unce@coral-cove.invalid. It slides off the list. Gloss card: hard bounce · a bounce that is permanent. The address does not work and will not start working.
one parcel, one coral note, one address off the list. Reveals: (1) the note, (2) the address, (3) it leaves the list, (4) the gloss.
the returned parcel. Registry hard-bounce line, owned by V002, called back not re-taught.
04 · The temporary one
the right pile. An amber note on a parcel: nobody home, trying again, label marina@tidewell-supply.example. Three small reasons tick in beside it, one per phrase: server down · slowing you down · greylisting. Gloss cards, one after the other: soft bounce · a bounce that is temporary. The address exists but could not take the message this time. greylisting · a receiving server turning a message away the first time and accepting it when a real sender tries again.
one parcel, one amber note, three reasons. Reveals: (1) the note, (2) to (4) one reason per click, (5) and (6) the glosses.
the returned parcel. Registry lines for soft-bounce and greylisting.
the full mailbox is left out of this list on purpose. It is the channel's most used example.
05 · Where you read which one it was
a bounce log row opens from each parcel. The first digit of each code lights: 5xx · mailbox does not exist under the coral note, 4xx · greylisted, try again later under the amber one. A pointer lands on the first digit, then on the words after it.
two log rows, one digit each that decides the pile. Reveals: (1) the coral row, (2) its 5, (3) the amber row, (4) its 4.
the returned parcel with its log row (T2, where it sits). Registry smtp-reply-code.
no full code syntax in VO. The description carries none either.
06 · What your tool does with the temporary ones
What your tool does with the temporary ones
chip 2 lights. The amber parcel goes back out on a courier loop, and comes back to the pile. On the next loop it is delivered, and the note turns teal: delivered.
one parcel, one loop, one note that changes colour. No clock, no count on screen (R2). Reveals: (1) the loop, (2) back again, (3) delivered.
the returned parcel.
07 · When temporary stops being temporary
a second amber parcel keeps coming back, campaign after campaign, each return adding a faint mark on its note. A dotted line on the pile reads your tool's setting. No number on the line.
one parcel, returns stacking up against a line whose number you look up. Reveals: (1) the returns, (2) the dotted line, (3) the note fades from amber toward coral.
the returned parcel.
R2 and R6. No count, no window. "Each tool sets its own line" is R6's "it depends on the tool", and the answer's "Your ESP probably has a default threshold already".
08 · The twist: a bounce that's about you
The bounce that's about you
chip 3 lights. A third parcel lands with a coral note, but this note reads refused: sender, label finn@saltmarsh-outfitters.example. Its log row starts with a 5. The pointer moves from the digit to the words after it. The address on the label stays teal. Gloss card: block bounce · a bounce where the server refused the message on reputation grounds rather than because the address is bad.
a 5 on the code, a teal address underneath. The digit says permanent, the words say it's you. Reveals: (1) the parcel, (2) its 5, (3) the words, (4) the address stays teal, (5) the gloss.
the returned parcel. Registry block-bounce, owned by V012 ("What is a block bounce?").
C37 add. See the gloss check, row 10.
09 · Why telling them apart matters
the parcels fade. A new parcel goes out to catch-all and never returns. No note, no log row, nothing. Gloss card: catch-all domain · a domain that says yes to every address at it, real or not, so a check cannot tell people from typos. Then the dot grid pours into the three verdict pots.
a parcel that never comes back, then the pots. Reveals: (1) the block note stays with Sally's sending, (2) the parcel that never returns, (3) the gloss, (4) the pots.
the returned parcel, then concept list-cleaning (M-25, M-23, M-24). Registry catch-all, owned by V026.
The ones that never come back
cleaning checks addresses. It does not fix a block or a reputation, and the first sentence says so.
10 · Recap: read the code, not the count
The recap
the three parcels from scenes 03, 04 and 08, each with its note and its log row, each handled: off the list, back on the loop, a flag on Sally's sending. All three chips lit.
three notes, three different jobs.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.002.007
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.007 "Can suppression lists be shared legally?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the three notes, read right, behind the CTA.
callbacks only.
021.002.007, word for word (S8), episode 22 of this batch. Totals: 13 scenes. 603 spoken words (recounted 2026-09-30, Q sweep). About 3:40 at 166 words a minute. Every scene is 20 to 70 words (S2).
V065Can suppression lists be shared legally?
checkedNo open questions are written in this script.
00 · Can suppression lists be shared legally? (hook) · 0:00
On screen: the title question, Lora, large: "Can suppression lists be shared legally?" Two shop counters side by side: Sally Send and Anchor & Oar Books. An envelope slides out from Sally's counter across the gap, and stops halfway, held in mid air (M2). Three numbered chips: what's worth sharing · how to hand it over · what the other side may do with it.
Can suppression lists be shared legally? Sally Send and a partner shop are running a campaign together. Someone who unsubscribed from Sally six months ago is on the partner's list too. Sally wants to warn them. Then she freezes. Is she allowed to hand that over? Yes. With care. Three steps. What's worth sharing. How to hand it over. And what the other side may do with it.
01 · Brought to you by, woven in · 0:22
On screen: no cut away, no ad break. The envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails cleans lists, and the list of people who said no is the one a sender should never lose track of.
02 · Why share it at all · 0:29
On screen: the envelope opens. Inside, a sheet with three kinds of row, one per phrase: unsubscribed (una.subscribe@pearl-diver.invalid), complained, hard bounced. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
Why share it at all? A suppression list is a record of addresses you've promised not to contact again. People who unsubscribed, complained, or hard bounced. Sharing it with a partner can serve a real purpose. It protects those people from being emailed when they've asked not to be.
03 · The legal part, in one line · 0:46
On screen: a single signed sheet slides between the two counters, two signatures, and a line that reads why we share: honour opt outs. No law name, no clause numbers anywhere on screen.
Is it allowed? Here's the legal part, in one line. Yes, it can be shared, as long as the two companies sign a written agreement and write down why they're sharing, before anything is sent.
04 · What's worth sharing · 0:58
On screen: chip 1 lights. A fuller sheet appears first, with name and purchases columns. Those two columns fold away, and only the address column goes into the envelope. Then each address turns into a short fingerprint string. Gloss card: hash · a unique fingerprint made from a piece of data.
What goes in the envelope? The email addresses, and nothing else. No names, no purchase history, no other detail about the person. A suppression check only needs the address itself. And where you can, share them hashed. A hash is a unique fingerprint made from each address.
05 · How to hand it over · 1:18
On screen: chip 2 lights. The envelope gets a teal seal and travels along a closed tube between the counters. Beside it, a plain paper attachment tries the same trip and gets a coral cross.
How does it travel? Securely. An encrypted file transfer, or a shared suppression feed through your email marketing tool. Not an email attachment with a plain list inside. And the other company handles that data with the same care you do.
06 · Check your platform first · 1:34
On screen: the two counters sit under one roof, labelled same platform. The envelope and the tube fade. A settings panel opens with a toggle, shared suppression, and flips on. No product names.
And if you're both on the same platform, check there first. Some email marketing tools support shared suppression lists, or unsubscribe settings across the whole account, which removes the manual handoff entirely. Look in your account settings before you go the manual route.
07 · The twist: it has to stay a do not send list · 1:50
On screen: chip 3 lights. The envelope arrives at the partner's counter, stamped in coral: for suppression only. A copy arrow reaches for it from a new campaign list, and the stamp stops it. A second arrow tries to lay it over another sheet, and the stamp stops that too. A small lock shows who can open it.
The list is only safe while it stays a do not send list. So the other side may use it for one thing, suppression. Not to build a new sending list. Not to match it against other data they hold. Write that into the agreement, and limit who on their side can open it.
08 · When to ask for help · 2:10
On screen: the partner's own list scrolls behind the envelope, some rows greyed. The dot grid pours into the three verdict pots, the grey rows into suppress.
Your shared list tells a partner who said no. It can't tell them which of their own addresses stopped working long ago. Those look fine on paper, and nobody finds out until the mail goes out.
09 · Recap · 2:39
On screen: the envelope's journey, replayed: addresses only, fingerprints, the seal, the signed sheet, the coral stamp. All three chips lit.
Before the file leaves, then. Share the addresses and nothing else, hashed where you can. Send them through a secure channel, or a shared feed on your platform. Get the agreement in writing first. And make sure the list stays a do not send list on the other side.
10 · Close · 2:55
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.007.005 "Is one-click unsubscribe optional?", no subscribe ask.
Checking every address before anyone sends is Review My Emails' job. Already sending with partners? Ask us about our partner programme. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... is one-click unsubscribe optional?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.007-sharing-suppression-lists-myth.md
00 · Can suppression lists be shared legally? (hook)
The myth
the title question, Lora, large: "Can suppression lists be shared legally?" Two shop counters side by side: Sally Send and Anchor & Oar Books. An envelope slides out from Sally's counter across the gap, and stops halfway, held in mid air (M2). Three numbered chips: what's worth sharing · how to hand it over · what the other side may do with it.
one envelope, stopped between two counters. Reveals: (1) the question, (2) the two counters, (3) the envelope held out, (4) it stops, (5) the chips.
new, proposed: the two counters and the envelope.
01 · Brought to you by, woven in
no cut away, no ad break. The envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · Why share it at all
the envelope opens. Inside, a sheet with three kinds of row, one per phrase: unsubscribed (una.subscribe@pearl-diver.invalid), complained, hard bounced. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
one sheet, three kinds of row. Reveals: (1) the sheet, (2) to (4) one row kind per click, (5) the gloss.
the envelope. Registry suppression-list, owned by V007, named in the gloss, not redrawn.
03 · The legal part, in one line
a single signed sheet slides between the two counters, two signatures, and a line that reads why we share: honour opt outs. No law name, no clause numbers anywhere on screen.
one sheet, two signatures, one reason. Reveals: (1) the sheet, (2) the two signatures, (3) the reason line.
the counters.
the legal part is the third sentence only. No law named. "Why we share: honour opt outs" is the answer's purpose, "honoring prior opt-outs".
04 · What's worth sharing
What's worth sharing
chip 1 lights. A fuller sheet appears first, with name and purchases columns. Those two columns fold away, and only the address column goes into the envelope. Then each address turns into a short fingerprint string. Gloss card: hash · a unique fingerprint made from a piece of data.
three columns shrink to one, and one column turns into fingerprints. Reveals: (1) the full sheet, (2) names fold away, (3) purchases fold away, (4) addresses only, (5) fingerprints, (6) the gloss.
the envelope.
the Almanac says to hash where possible but no answer explains why a hash helps a shared suppression list. The VO says what a hash is, and stops there.
05 · How to hand it over
How to hand it over
chip 2 lights. The envelope gets a teal seal and travels along a closed tube between the counters. Beside it, a plain paper attachment tries the same trip and gets a coral cross.
two ways across, one sealed, one crossed out. Reveals: (1) the seal, (2) the tube, (3) the plain attachment, (4) the cross.
the envelope.
06 · Check your platform first
the two counters sit under one roof, labelled same platform. The envelope and the tube fade. A settings panel opens with a toggle, shared suppression, and flips on. No product names.
the handoff disappears, one toggle replaces it. Reveals: (1) one roof, (2) the envelope fades, (3) the panel, (4) the toggle.
the counters (T2, where to look).
07 · The twist: it has to stay a do not send list
What the other side may do with it
chip 3 lights. The envelope arrives at the partner's counter, stamped in coral: for suppression only. A copy arrow reaches for it from a new campaign list, and the stamp stops it. A second arrow tries to lay it over another sheet, and the stamp stops that too. A small lock shows who can open it.
one stamp, two uses refused, one lock. Reveals: (1) the stamp, (2) the copy stopped, (3) the match stopped, (4) the lock.
the envelope.
08 · When to ask for help
the partner's own list scrolls behind the envelope, some rows greyed. The dot grid pours into the three verdict pots, the grey rows into suppress.
the envelope for the people who said no, the pots for the addresses that stopped working. Reveals: (1) the envelope, (2) the grey rows, (3) the pots.
the envelope, then concept list-cleaning (M-25, M-23, M-24).
no legal detail. It points to a person who gives it, which is what the answer does.
What a shared list can't tell them
cleaning checks addresses. It does not share, store or honour opt-outs for anyone, and the VO does not say it does.
09 · Recap
The recap
the envelope's journey, replayed: addresses only, fingerprints, the seal, the signed sheet, the coral stamp. All three chips lit.
four checks on one envelope.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 021.007.005
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.007.005 "Is one-click unsubscribe optional?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: partner programme · 15%, named in the VO above.
the sealed envelope behind the CTA.
callbacks only.
021.007.005, word for word (S8), episode 23 of this batch. Totals: 12 scenes. 524 spoken words (recounted 2026-09-30, Q sweep). About 3:10 at 166 words a minute. Every scene is 20 to 70 words (S2).
V066Is one-click unsubscribe optional?
checkedNo open questions are written in this script.
00 · Is one-click unsubscribe optional? (hook) · 0:00
On screen: the title question, Lora, large: "Is one-click unsubscribe optional?" Sally's email, drawn as a room. One small exit sign inside, at the bottom. A subscriber presses it, and a second door appears behind it, please confirm. The subscriber is still in the room (M2). Three numbered chips: the two ways out · who has to add the button · the step that breaks it.
Is one-click unsubscribe optional? Sally Send has an unsubscribe link at the bottom of every email. It opens a page that asks people to confirm, and she figures that's plenty. Not anymore. Three things to check. The two ways out. Who has to add the button. And the step that breaks it.
01 · Brought to you by, woven in · 0:18
On screen: no cut away, no ad break. The room holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Lists stay healthier when leaving takes one click, and healthy lists are exactly what Review My Emails looks after for you.
02 · Two ways out · 0:25
On screen: chip 1 lights. The room gets a second exit: a button on the outside wall, labelled header. The sign inside stays, labelled body link. Gloss card: email header · the lines above the message that say where it came from, where it is going and what happened on the way.
How many ways out does one email have? Two, and they're not the same thing. One lives in the technical part of your email, the header. The other is the visible link inside the email, usually sitting quietly at the bottom.
03 · The button on the outside · 0:40
On screen: the outside button, seen from the reader's inbox: a small unsubscribe control beside Sally's name, not inside her email. wren@mailbox.example taps it once, and walks straight out. The header line appears under it, List-Unsubscribe, then its second line, List-Unsubscribe-Post. Gloss card: List-Unsubscribe header · a header that puts an unsubscribe control in the reader's own inbox.
The first is the List-Unsubscribe header. Set up correctly, with a second line that points to an address on your side, it lets the mailbox provider show a one-click unsubscribe button right in its own interface. No landing page. No confirmation step. Just instant removal.
04 · Why it stopped being optional · 1:00
On screen: the outside button gets a teal ring and a small date tag, 2024. A dotted line under it reads bulk senders, with no number on it.
Why isn't it optional? Since 2024, Gmail and Yahoo require that one-click button from bulk senders. If you're sending at that volume and you don't have it, you're already at risk of deliverability problems.
05 · Who has to add the button · 1:14
On screen: chip 2 lights. Two rooms side by side. The first has the outside button fitted automatically, a small added for you tag. The second, labelled developer platform, has a bare outside wall, and a toolbox beside it.
Who puts that button there? Most of the big email marketing tools add the header for you, by default, when you use their standard sending. You don't need to configure anything extra. But if you send through a developer level platform, you'll need to add it yourself.
06 · The sign inside, and the one legal line · 1:33
On screen: the body link, first as tiny grey text almost lost at the bottom, then at a readable size. No law name, no day count anywhere on screen.
And the sign inside still matters. Separately, the big anti-spam and privacy laws already require a visible unsubscribe link in the body of your email. It needs to be visible. Hiding it in tiny grey text is not a strategy worth testing.
07 · Why you need both · 1:50
On screen: the room with both exits lit teal. One subscriber leaves by the outside button. Another, reading the email itself, leaves by the sign inside.
Which one do you need? Both. The header handles the mailbox provider side. The body link handles the legal side, and the readers who open your email directly, rather than through the provider's own buttons.
08 · The endpoint does the work · 2:05
On screen: chip 3 lights. The tap on the outside button sends a line into Sally's system, and a row disappears from her list at once: wren@mailbox.example, gone.
What happens after the click? The button calls an address on your side, and that address has to do the removal. It has to process it immediately, and without any extra steps.
09 · The twist: the confirm page · 2:19
On screen: Sally's please confirm door from the hook, now behind the outside button. The teal ring on the button turns coral. A small label: not one click.
A button that goes to a preferences page, asking the reader to confirm again, doesn't count as one click under Gmail and Yahoo's rules. That's Sally's page from the start. And yes, that difference has caught people out.
10 · Where to check yours · 2:37
On screen: the room, quiet. A few seats hold grey envelopes that never move toward either exit. Gloss card: risky address · an address that takes your mail without bouncing and never does anything with it. The dot grid pours into the three verdict pots, the grey envelopes into monitor and suppress.
One click takes someone off your list the moment they ask. But some addresses never ask. They take your mail and never do anything with it, and they never leave on their own.
11 · Recap · 3:09
On screen: the room with both exits lit, the confirm door removed. All three chips lit.
Your checklist. Keep both exits. Check on a test send that the header is there, especially if you send through a developer platform. And take out any confirm step behind the button, so one click means out.
12 · Close · 3:24
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.010.008 "Do email marketing tools control inbox placement?" (the Almanac question with "email marketing tools" for its abbreviation, S8, V5), no subscribe ask.
Finding those before you send is Review My Emails' job. Want to see your own headers? Our Email Header Analyzer is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... do email marketing tools control inbox placement?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.007.005-one-click-unsubscribe-not-optional-myth.md
00 · Is one-click unsubscribe optional? (hook)
The myth
the title question, Lora, large: "Is one-click unsubscribe optional?" Sally's email, drawn as a room. One small exit sign inside, at the bottom. A subscriber presses it, and a second door appears behind it, please confirm. The subscriber is still in the room (M2). Three numbered chips: the two ways out · who has to add the button · the step that breaks it.
one room, one exit that leads to another door. Reveals: (1) the question, (2) the room, (3) the exit sign, (4) the second door, (5) the chips.
new, proposed: the email as a room with exits.
01 · Brought to you by, woven in
no cut away, no ad break. The room holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · Two ways out
The two ways out
chip 1 lights. The room gets a second exit: a button on the outside wall, labelled header. The sign inside stays, labelled body link. Gloss card: email header · the lines above the message that say where it came from, where it is going and what happened on the way.
one room, two exits. Reveals: (1) the outside button, (2) the inside sign, (3) the gloss.
the room. Registry email-header.
03 · The button on the outside
the outside button, seen from the reader's inbox: a small unsubscribe control beside Sally's name, not inside her email. wren@mailbox.example taps it once, and walks straight out. The header line appears under it, List-Unsubscribe, then its second line, List-Unsubscribe-Post. Gloss card: List-Unsubscribe header · a header that puts an unsubscribe control in the reader's own inbox.
one tap, one person out, zero pages. Reveals: (1) the inbox control, (2) the tap, (3) out, (4) the two header lines, (5) the gloss.
the room. Registry list-unsubscribe.
the header names appear on screen as labels only. No syntax, no endpoint format.
04 · Why it stopped being optional
Almanac ids in this scene: 019.007.002
the outside button gets a teal ring and a small date tag, 2024. A dotted line under it reads bulk senders, with no number on it.
one date, one group of senders. Reveals: (1) the ring, (2) the date, (3) the dotted line.
the room.
the volume that makes you a bulk sender is not voiced. 019.007.002 owns it, and the description links it.
05 · Who has to add the button
Who has to add the button
chip 2 lights. Two rooms side by side. The first has the outside button fitted automatically, a small added for you tag. The second, labelled developer platform, has a bare outside wall, and a toolbox beside it.
two rooms, one button fitted, one wall bare. Reveals: (1) the fitted room, (2) the bare room, (3) the toolbox.
the room. No product names.
06 · The sign inside, and the one legal line
the body link, first as tiny grey text almost lost at the bottom, then at a readable size. No law name, no day count anywhere on screen.
one sign, grey then readable. Reveals: (1) the grey sign, (2) it grows.
the room.
the second sentence is the one legal sentence. No law named, no timing.
07 · Why you need both
the room with both exits lit teal. One subscriber leaves by the outside button. Another, reading the email itself, leaves by the sign inside.
two exits, two kinds of reader, both out. Reveals: (1) both lit, (2) one out by the button, (3) one out by the sign.
the room.
08 · The endpoint does the work
The step that breaks it
chip 3 lights. The tap on the outside button sends a line into Sally's system, and a row disappears from her list at once: wren@mailbox.example, gone.
one tap, one row gone, no wait. Reveals: (1) the tap, (2) the line in, (3) the row goes.
the room.
09 · The twist: the confirm page
Sally's please confirm door from the hook, now behind the outside button. The teal ring on the button turns coral. A small label: not one click.
one extra door, one ring that turns coral. Reveals: (1) the door returns, (2) the ring turns, (3) the label.
the room. The hook's second door, called back.
10 · Where to check yours
the room, quiet. A few seats hold grey envelopes that never move toward either exit. Gloss card: risky address · an address that takes your mail without bouncing and never does anything with it. The dot grid pours into the three verdict pots, the grey envelopes into monitor and suppress.
exits for the people who ask, pots for the addresses that never will. Reveals: (1) the grey envelopes, (2) the gloss, (3) the pots.
the room, then concept list-cleaning (M-25, M-23, M-24). Registry risky-address, owned by V022.
The ones that never ask
cleaning checks addresses. It does not add headers or process unsubscribes, and the VO does not say it does.
11 · Recap
The recap
the room with both exits lit, the confirm door removed. All three chips lit.
two exits, zero extra doors.
callbacks only (S5).
12 · Close
Almanac ids in this scene: 021.010.008
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.010.008 "Do email marketing tools control inbox placement?" (the Almanac question with "email marketing tools" for its abbreviation, S8, V5), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/email-headers, named in the VO above.
the room with both exits lit, behind the CTA.
callbacks only.
021.010.008, word for word except the abbreviation, swapped for "email marketing tools" (S8), episode 24 of this batch. Totals: 14 scenes. 543 spoken words (recounted 2026-09-30, Q sweep). About 3:20 at 166 words a minute. Every scene is 20 to 70 words (S2).
V067Do email marketing tools control inbox placement?
checkedNo open questions are written in this script.
00 · Do email marketing tools control inbox placement? (hook) · 0:00
On screen: the title question, Lora, large: "Do email marketing tools control inbox placement?" A delivery van labelled your email marketing tool. Sally shakes a finger at it. Its driver lifts a steering wheel, then points down the road at a building (M2). Three numbered chips: what your tool does · who decides where it lands · what's in your hands.
Do email marketing tools control inbox placement? Sally Send picked a tool, set everything up, and hit send. Half her list landed in Promotions, and some of it in spam. So she blames the tool. Fair instinct. But they carry it. Someone else sorts it. Let's take three things. What your tool does. Who decides where it lands. And what's in your hands.
01 · Brought to you by, woven in · 0:20
On screen: no cut away, no ad break. The van holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Your list is one of the few parts of this journey that sits fully in your hands, and it's the part Review My Emails cleans.
02 · What your tool does · 0:27
On screen: chip 1 lights. The van's jobs tick in, one per phrase: sending setup · IP addresses · bounces · out the door. The van pulls away from Sally's building. Gloss card: email marketing tool · the tool you send with, such as a marketing platform. It is not the same as the provider your reader receives mail with.
What does your email marketing tool do? It transmits your mail. That's its job. It runs the sending setup, manages the IP addresses, processes bounces, and makes sure your message leaves the building.
03 · Who decides where it lands · 0:42
On screen: chip 2 lights. The van stops at a building with a front desk, mailbox provider. The van hands over the envelope and waits outside. The desk has four trays: inbox · spam · Promotions · Junk. Gloss card: mailbox provider · the service your reader receives mail with. It decides where your message lands.
And when it arrives? The moment your email reaches Gmail, Outlook or Yahoo, it's those providers who decide where it goes. Inbox, spam, Promotions, Junk. That call is theirs, not your tool's.
04 · What the desk is looking at · 0:58
On screen: a scorecard on the desk, headed Sally Send. Four lines fill in, one per phrase: reputation · authentication · engagement · content. The van, outside, has no pen. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
What is the desk looking at? Signals it has gathered about you as a sender, over time. Your sender reputation. Whether your authentication records are set up properly. How your subscribers have been engaging with your mail lately. And whether your content looks like something their readers want. Your tool has no say in any of that.
05 · The twist: the company your tool keeps · 1:22
On screen: the van again, now shown carrying envelopes from many senders, Sally's among them. First version: the others are tidy, and the desk waves the van through. Second version: a few coral envelopes from other senders, and the desk slows the whole van, Sally's envelope included.
Your tool can still move your odds, just not directly. A good one keeps its shared IP pools clean and enforces sending standards across its platform. A poorly run one, known for hosting spammy senders, can drag your results down, even if you're doing everything right. Frustrating, but real.
06 · So is a new tool the answer? · 1:44
On screen: Sally swaps vans. The new van pulls up at the same front desk, and the same scorecard is lifted from the drawer.
Is the answer a new tool, then? If your inbox placement is struggling right now, no. A new van still stops at the same desk. No tool, however good, can stand in for the fundamentals.
07 · What's in your hands · 1:58
On screen: chip 3 lights. Sally holds five cards, one per phrase: authentication · engagement · list hygiene · complaints · consistency. Each one slides onto the desk's scorecard.
What's in your hands? Your authentication records, SPF, DKIM and DMARC. Your subscribers' engagement. Your list hygiene. Your complaint rates. And how consistently you send. Those signals tell mailbox providers whether your mail is worth letting through.
08 · Where to start · 2:17
On screen: the list hygiene card lifts from the row. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress, and saying why for each one. The dot grid pours into the three verdict pots. The other four cards stay on the desk, untouched.
List hygiene is the one card on that desk we handle. We check every address before you send, and sort your list into keep, monitor and suppress. It won't fix your authentication or your complaints. Those stay yours.
09 · Recap · 2:52
On screen: the van, the desk, the four trays and Sally's five cards, side by side. All three chips lit.
Stop blaming the van for the sorting. Know that a well run tool gives you better conditions, and a poorly run one can hold you back. Then work backwards through the signals that are yours, and fix the one pulling you down.
10 · Close · 3:08
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.002 "Can AI-generated content hurt deliverability?", no subscribe ask.
Want to check your DMARC record first? Our DMARC Parser is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... can AI generated content hurt deliverability?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.010.008-tools-dont-control-inbox-placement-myth.md
00 · Do email marketing tools control inbox placement? (hook)
The myth
the title question, Lora, large: "Do email marketing tools control inbox placement?" A delivery van labelled your email marketing tool. Sally shakes a finger at it. Its driver lifts a steering wheel, then points down the road at a building (M2). Three numbered chips: what your tool does · who decides where it lands · what's in your hands.
one van, one finger pointed at the wrong place. Reveals: (1) the question, (2) the van, (3) Sally blames it, (4) the driver points on, (5) the chips.
new, proposed: the van and the front desk.
01 · Brought to you by, woven in
no cut away, no ad break. The van holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What your tool does
What your tool does
chip 1 lights. The van's jobs tick in, one per phrase: sending setup · IP addresses · bounces · out the door. The van pulls away from Sally's building. Gloss card: email marketing tool · the tool you send with, such as a marketing platform. It is not the same as the provider your reader receives mail with.
four jobs, one van leaving. Reveals: (1) to (4) one job per click, (5) the van leaves, (6) the gloss.
the van. Registry esp line.
03 · Who decides where it lands
Who decides where it lands
chip 2 lights. The van stops at a building with a front desk, mailbox provider. The van hands over the envelope and waits outside. The desk has four trays: inbox · spam · Promotions · Junk. Gloss card: mailbox provider · the service your reader receives mail with. It decides where your message lands.
one handover, four trays, one hand on the choice. Reveals: (1) the desk, (2) the handover, (3) the four trays, (4) the gloss.
the front desk. Registry mailbox-provider line.
04 · What the desk is looking at
a scorecard on the desk, headed Sally Send. Four lines fill in, one per phrase: reputation · authentication · engagement · content. The van, outside, has no pen. Gloss card: sender reputation · how much the receiving side trusts you, built from how people have treated your mail so far.
one scorecard, four lines, none written by the van. Reveals: (1) the card, (2) to (5) one line per click, (6) the gloss.
the front desk. Registry sender-reputation.
05 · The twist: the company your tool keeps
the van again, now shown carrying envelopes from many senders, Sally's among them. First version: the others are tidy, and the desk waves the van through. Second version: a few coral envelopes from other senders, and the desk slows the whole van, Sally's envelope included.
one van, many senders, one mood at the desk. Reveals: (1) many senders on board, (2) a clean van waved through, (3) a van with coral envelopes, (4) the whole van slowed.
the van.
the answer's "shared IP pools" and "A poorly run ESP with a reputation for hosting spammy senders can drag down your results even if you're doing everything right (which is frustrating, but real)."
06 · So is a new tool the answer?
Sally swaps vans. The new van pulls up at the same front desk, and the same scorecard is lifted from the drawer.
two vans, one desk, one scorecard. Reveals: (1) the swap, (2) the same desk, (3) the same card.
the van and the desk. Calls back the older short V952 in one picture, not in its words.
07 · What's in your hands
What's in your hands
chip 3 lights. Sally holds five cards, one per phrase: authentication · engagement · list hygiene · complaints · consistency. Each one slides onto the desk's scorecard.
five cards, all in Sally's hand, none in the van. Reveals: (1) to (5) one card per click, (6) they reach the desk.
the front desk.
SPF, DKIM and DMARC are named, not taught. Their own videos own them.
08 · Where to start
Almanac ids in this scene: 021.013.014
the list hygiene card lifts from the row. Gloss card: list cleaning · sorting a whole list into keep, monitor and suppress, and saying why for each one. The dot grid pours into the three verdict pots. The other four cards stay on the desk, untouched.
one card of five. Reveals: (1) the card lifts, (2) the gloss, (3) the pots, (4) the other four stay.
the front desk, then concept list-cleaning (M-25, M-23, M-24).
021.013.014 "You can check your DMARC record with our free DMARC Parser if you want to make sure yours is reading cleanly."
The card we can help with
cleaning checks addresses. It does not fix authentication, complaints or reputation, and the VO says so.
09 · Recap
The recap
the van, the desk, the four trays and Sally's five cards, side by side. All three chips lit.
one van, one desk, five cards in Sally's hand.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 021.013.002
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.002 "Can AI-generated content hurt deliverability?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/dmarc-parser, named in the VO above.
the desk with Sally's cards, behind the CTA.
callbacks only.
021.013.002, word for word (S8), episode 25 of this batch. Totals: 12 scenes. 487 spoken words (recounted 2026-09-30, Q sweep). About 3:00 at 166 words a minute. Every scene is 20 to 70 words (S2).
V068Can AI-generated content hurt deliverability?
checkedNo open questions are written in this script.
00 · Can AI-generated content hurt deliverability? (hook) · 0:00
On screen: the title question, Lora, large: "Can AI-generated content hurt deliverability?" Sally's email as a letter, a small byline sticker in the corner: written by AI. A magnifying glass from the filter hovers over the sticker and slides right past it, down to the reader (M2). Three numbered chips: what filters weigh · how AI copy can still cost you · how to use it safely.
Can AI generated content hurt deliverability? Sally Send asked an AI tool to write this week's campaign, and now she's wondering if the spam filters can tell. Filters don't read the byline. Three things to cover. What filters weigh. How AI copy can still cost you. And how to use it safely.
01 · Brought to you by, woven in · 0:17
On screen: no cut away, no ad break. The letter holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
However an email gets written, it still needs real people on the other end, and Review My Emails checks that they're there.
02 · What filters weigh · 0:24
On screen: chip 1 lights. The byline sticker greys out. Under the letter, a row of four reader reactions fills in, one per phrase: open · click · delete unread · report. Gloss card: engagement signal · what a person does with your mail, opening it, clicking it, replying, or nothing at all.
Can a filter tell who wrote it? No. Spam filters don't care whether a human or a tool wrote your copy. What they care about is how your recipients respond. Opens, clicks, deletions without reading, and spam reports.
03 · Where the risk sits · 0:40
On screen: chip 2 lights. The letter's text comes into focus. The reaction row under it holds still, waiting.
That's the good news. And it's also the catch. The risk with AI isn't that it's AI. It's what it tends to produce, and how people respond to that.
04 · Fluent, but vague · 0:52
On screen: Sally's letter in an inbox of other letters that all read alike, the same smooth lines. The reader's eye slides past them all. One hand reaches for report.
AI is good at fluent, confident sounding text. It's not always good at specific, relevant, human feeling text. If your emails sound like every other AI email in someone's inbox, people start skimming past them. Or worse, they hit mark as spam out of frustration.
05 · How it plays out · 1:10
On screen: the reaction row under the letter changes, step by step, one per sentence: the click marker empties, then the open marker, then the letter for the next campaign slides one tray lower, toward spam.
Here's how that plays out. You ask for a promotional email. You get back something polished but vague. You send it. People open it, read two sentences, and close it without clicking. Your clicks slide. Your opens follow. Filters notice. And your next campaign goes to more spam folders.
06 · The twist: it isn't the tool · 1:32
On screen: six of Sally's letters in a row, each opening with the same line, highlighted. Their byline stickers flip at random between AI and Sally. The reaction rows under all six fade the same way.
The AI didn't cause that directly. The generic copy did. And a person can write generic copy too. If your last six campaigns all open with, we're so excited to share, that pattern dulls engagement over time, whoever wrote it.
07 · How to use it safely · 1:52
On screen: chip 3 lights. The AI draft arrives with draft 1 on it. Sally's red pen goes through it. Beside it, two prompts, one short and blank, one full of detail about the boat owner. The detailed one produces a letter that looks nothing like the lookalikes.
How do you use it without falling into that trap? Treat AI as a first draft, not a finished product. Get the structure out fast, then edit for your audience and your brand's own voice. And feed it context. A welcome email for a first time boat owner who just read your guide to tidal navigation beats, write a welcome email.
08 · Test it, on the right number · 2:14
On screen: Sally's list splits in two. Half gets AI draft, half gets edited. Under each, two bars: opens, and clicks out of those opens. The pointer skips the opens bar and lands on the second. Gloss card: click to open rate · of the people who opened, how many clicked something. No numbers on the bars.
Then test it. Split a send between the AI draft and a version you've edited heavily. Look at click to open rate, not just opens. Of the people who opened, how many clicked. That's where the quality difference usually shows up. Compare it from campaign to campaign, not against a target.
09 · Could that change? · 2:34
On screen: the reaction row under a handful of letters stays blank, whatever the copy says. Gloss card: risky address · an address that takes your mail without bouncing and never does anything with it. The dot grid pours into the three verdict pots, the blank rows into monitor and suppress.
And the best edited copy still can't win a reaction from an address nobody reads. Those take your mail and never do anything with it, and no amount of editing changes that.
10 · Recap · 3:08
On screen: the letter, the red pen, the detailed prompt, the six repeated lines crossed through, the click to open bars. All three chips lit.
In practice. Use AI for the first draft, never the last. Give it real context. Watch for the same opening line, campaign after campaign. And test the edited version against the raw one, on clicks, not opens.
11 · Close · 3:24
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.014 "Will AI email scoring replace sender reputation?", no subscribe ask.
Finding those before you send is Review My Emails' job. Not sure what's dragging your engagement down? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... will AI email scoring replace sender reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.013.002-ai-copy-filters-dont-read-bylines-myth.md
00 · Can AI-generated content hurt deliverability? (hook)
The myth
the title question, Lora, large: "Can AI-generated content hurt deliverability?" Sally's email as a letter, a small byline sticker in the corner: written by AI. A magnifying glass from the filter hovers over the sticker and slides right past it, down to the reader (M2). Three numbered chips: what filters weigh · how AI copy can still cost you · how to use it safely.
one sticker, one glass that never stops on it. Reveals: (1) the question, (2) the letter, (3) the sticker, (4) the glass slides past, (5) the chips.
new, proposed: the letter with a byline sticker, and the row of reader reactions.
01 · Brought to you by, woven in
no cut away, no ad break. The letter holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What filters weigh
What filters weigh
chip 1 lights. The byline sticker greys out. Under the letter, a row of four reader reactions fills in, one per phrase: open · click · delete unread · report. Gloss card: engagement signal · what a person does with your mail, opening it, clicking it, replying, or nothing at all.
one grey sticker, four reactions that count. Reveals: (1) the sticker greys, (2) to (5) one reaction per click, (6) the gloss.
the letter. Registry engagement-signal.
03 · Where the risk sits
How AI copy can still cost you
chip 2 lights. The letter's text comes into focus. The reaction row under it holds still, waiting.
one letter, one waiting row. Reveals: (1) the text sharpens, (2) the row waits.
the letter.
04 · Fluent, but vague
Sally's letter in an inbox of other letters that all read alike, the same smooth lines. The reader's eye slides past them all. One hand reaches for report.
a row of lookalike letters, one reader skimming, one report. Reveals: (1) the lookalikes, (2) the skim, (3) the report.
the letter.
05 · How it plays out
the reaction row under the letter changes, step by step, one per sentence: the click marker empties, then the open marker, then the letter for the next campaign slides one tray lower, toward spam.
clicks down, then opens down, then one tray lower. Reveals: (1) polished and vague, (2) sent, (3) two sentences read, (4) clicks slide, (5) opens follow, (6) the next letter drops a tray.
the letter (T1, the mechanism).
no rate on screen. The markers move, no number is shown.
06 · The twist: it isn't the tool
six of Sally's letters in a row, each opening with the same line, highlighted. Their byline stickers flip at random between AI and Sally. The reaction rows under all six fade the same way.
six letters, one repeated line, the same fade whatever the sticker says. Reveals: (1) six letters, (2) the repeated line, (3) the stickers flip, (4) the same fade.
the letter.
07 · How to use it safely
How to use it safely
chip 3 lights. The AI draft arrives with draft 1 on it. Sally's red pen goes through it. Beside it, two prompts, one short and blank, one full of detail about the boat owner. The detailed one produces a letter that looks nothing like the lookalikes.
one draft, one edit, two prompts. Reveals: (1) draft 1, (2) the edit, (3) the short prompt, (4) the detailed prompt, (5) the letter that stands out.
the letter.
08 · Test it, on the right number
Almanac ids in this scene: 004.002.005
Sally's list splits in two. Half gets AI draft, half gets edited. Under each, two bars: opens, and clicks out of those opens. The pointer skips the opens bar and lands on the second. Gloss card: click to open rate · of the people who opened, how many clicked something. No numbers on the bars.
two halves, two bars each, one bar that matters. Reveals: (1) the split, (2) the opens bars, (3) the pointer skips them, (4) the click to open bars, (5) the gloss.
the letter (T2, what to read and where).
no rate shown. "Not against a target" follows 004.002.005's "campaign-to-campaign comparison rather than absolute benchmarking".
09 · Could that change?
the reaction row under a handful of letters stays blank, whatever the copy says. Gloss card: risky address · an address that takes your mail without bouncing and never does anything with it. The dot grid pours into the three verdict pots, the blank rows into monitor and suppress.
letters with blank reaction rows, then the pots. Reveals: (1) the blank rows, (2) the gloss, (3) the pots.
the letter, then concept list-cleaning (M-25, M-23, M-24). Registry risky-address, owned by V022.
"could shift" and "hasn't happened in a meaningful way yet" are the answer's own weight. No forecast beyond it.
The readers your copy can't reach
cleaning checks addresses. It does not write or fix copy, and does not promise engagement or inbox placement.
10 · Recap
The recap
the letter, the red pen, the detailed prompt, the six repeated lines crossed through, the click to open bars. All three chips lit.
four moves on one letter.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.013.014
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.014 "Will AI email scoring replace sender reputation?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the letter, with a full reaction row, behind the CTA.
callbacks only.
021.013.014, word for word (S8), episode 26 of this batch. Totals: 13 scenes. 548 spoken words (recounted 2026-09-30, Q sweep). About 3:21 at 166 words a minute. Every scene is 20 to 70 words (S2).
V069Will AI email scoring replace sender reputation?
waiting on YTNo open questions are written in this script.
00 · Will AI email scoring replace sender reputation? (hook) · 0:00
On screen: the title question, Lora, large: "Will AI email scoring replace sender reputation?" The front desk from episode 24, Sally's scorecard on it. A robot hand reaches in to swap the card for a blank one, and the card stays put. Instead a lens slides down over it (M2). Three numbered chips: what the scorecard holds · what AI adds · what that means for you.
Will AI email scoring replace sender reputation? Sally Send keeps hearing that AI is changing how email gets filtered, and she's wondering if everything she's built up is about to count for nothing. Same scorecard. Sharper eyes. Three things to look at. What the scorecard holds. What AI adds. And what that means for you.
01 · Brought to you by, woven in · 0:19
On screen: no cut away, no ad break. The desk holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A clean list is one line on that scorecard you get to write yourself, and Review My Emails checks every address on it.
02 · What the scorecard holds · 0:26
On screen: chip 1 lights. Sally's scorecard, five lines filling in one per phrase: complaints · bounces · engagement · authentication · volume consistency. The card feeds the desk's sorting into its trays.
What's on the scorecard today? Data signals. Spam complaint rates. Bounce rates. Engagement patterns. Authentication records. And how consistent your sending volume is. Those feed the models mailbox providers use to decide where your email lands. That's been the backbone of deliverability for years.
03 · Is it being replaced? · 0:45
On screen: the lens settles over the card. The five lines stay exactly where they were. A small tag on the lens: on top, not instead.
Is AI throwing that card out? No. AI scoring isn't replacing sender reputation. It's layered on top of it, making the system smarter, and harder to game.
04 · What AI adds: sooner, and more at once · 0:56
On screen: chip 2 lights. Without the lens, the complaints line fills slowly until it hits a line and a flag pops. With the lens, the flag pops much earlier, on the first odd wobble. Then the lens widens and takes in all five lines together.
What does it add? Better pattern recognition, and faster adaptation. Instead of waiting for complaints to pass a line and trigger a flag, AI models can spot unusual sending behaviour much earlier. And they can weigh more signals at once.
05 · Quality, not just quantity · 1:14
On screen: the engagement line under the lens. The amount stays the same, but its texture changes, smooth marks turning into identical, stamped ones. The lens rings them coral.
And it looks closer. It can notice when a sender's engagement suddenly changes in quality, not just quantity. Or when content patterns shift in ways that look suspicious. The judgement gets finer, not blunter.
06 · What that means for you: no shortcut in · 1:30
On screen: chip 3 lights. A brand new scorecard, almost empty, under the lens. The lines fill in one small step at a time.
What does that mean for you? First, new senders still get looked at closely. AI doesn't fast track trust. You still build a track record gradually. There's no shortcut there.
07 · The twist: real reactions count for more · 1:43
On screen: the engagement line splits into two strands under the lens. The hollow strand, bots and silent addresses, fades to grey. The real strand, people opening and clicking, thickens teal.
If AI gets better at spotting hollow engagement, like opens inflated by bots or by inactive addresses, then real reactions from real people count for more, not less. So keeping your list clean, and sending to people who want your emails, matters even more.
08 · Authentication, and where to check it · 2:03
On screen: the authentication line under the lens. A message without it gets a coral ring at once. Then Sally's DMARC record opens beside the card, read out line by line, each line ticking teal.
Authentication stays non negotiable. SPF, DKIM and DMARC aren't going away, and AI systems flag unauthenticated mail faster. You can check your DMARC record with our free DMARC Parser, and make sure yours is reading cleanly.
09 · Gaming it gets harder · 2:20
On screen: the grey hollow strand from scene 07, traced back to a handful of addresses on Sally's list. Gloss card: risky address · an address that takes your mail without bouncing and never does anything with it. The dot grid pours into the three verdict pots, the grey addresses into monitor and suppress.
Keeping your list clean is the line we help with. We check every address before you send, and flag the ones that take your mail and never do anything with it. It won't fix your authentication or your complaints. Those stay yours.
10 · Recap · 2:49
On screen: Sally's scorecard under the lens, four lines lit teal one per phrase: wanted mail · clean list · authentication · complaints. All three chips lit.
Nothing new, then, just done more carefully. Which is either reassuring, or mildly annoying. Send to people who want your emails. Keep your list clean. Authenticate your domain. And watch your complaint rates.
11 · Close · 3:09
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.010.012 "Can email marketing tools fix blocklist issues?" (the Almanac question with "email marketing tools" for its abbreviation, S8, V5), no subscribe ask.
Want a quick first look at how your reputation is doing? Our Blocklist Checker is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... can email marketing tools fix blocklist issues?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.013.014-ai-scoring-sharper-eyes-myth.md
00 · Will AI email scoring replace sender reputation? (hook)
The myth
the title question, Lora, large: "Will AI email scoring replace sender reputation?" The front desk from episode 24, Sally's scorecard on it. A robot hand reaches in to swap the card for a blank one, and the card stays put. Instead a lens slides down over it (M2). Three numbered chips: what the scorecard holds · what AI adds · what that means for you.
one card that doesn't get swapped, one lens that arrives. Reveals: (1) the question, (2) the desk and card, (3) the swap that fails, (4) the lens, (5) the chips.
the front desk and scorecard (episode 24), plus a new lens.
01 · Brought to you by, woven in
no cut away, no ad break. The desk holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What the scorecard holds
What the scorecard holds
chip 1 lights. Sally's scorecard, five lines filling in one per phrase: complaints · bounces · engagement · authentication · volume consistency. The card feeds the desk's sorting into its trays.
one card, five lines. Reveals: (1) to (5) one line per click, (6) the trays.
the scorecard. No gloss card: sender-reputation was glossed in episode 24 and is called back by the picture (S6).
03 · Is it being replaced?
the lens settles over the card. The five lines stay exactly where they were. A small tag on the lens: on top, not instead.
the same five lines, one lens over them. Reveals: (1) the lens settles, (2) the lines unchanged, (3) the tag.
the scorecard.
04 · What AI adds: sooner, and more at once
What AI adds
chip 2 lights. Without the lens, the complaints line fills slowly until it hits a line and a flag pops. With the lens, the flag pops much earlier, on the first odd wobble. Then the lens widens and takes in all five lines together.
one flag, raised later then sooner, then five lines read at once. Reveals: (1) the slow fill, (2) the late flag, (3) the lens, (4) the early flag, (5) the wide read.
the scorecard.
no number on the line. The answer names "complaint thresholds" and gives no figure.
05 · Quality, not just quantity
the engagement line under the lens. The amount stays the same, but its texture changes, smooth marks turning into identical, stamped ones. The lens rings them coral.
the same amount, a different texture, one ring. Reveals: (1) the line, (2) the texture changes, (3) the ring.
the scorecard (T4, quality not amount).
06 · What that means for you: no shortcut in
What that means for you
chip 3 lights. A brand new scorecard, almost empty, under the lens. The lines fill in one small step at a time.
one new card, filling in small steps. Reveals: (1) the empty card, (2) the lens, (3) the steps.
the scorecard.
07 · The twist: real reactions count for more
the engagement line splits into two strands under the lens. The hollow strand, bots and silent addresses, fades to grey. The real strand, people opening and clicking, thickens teal.
one line split in two, one strand fading, one growing. Reveals: (1) the split, (2) hollow fades, (3) real grows.
the scorecard.
08 · Authentication, and where to check it
the authentication line under the lens. A message without it gets a coral ring at once. Then Sally's DMARC record opens beside the card, read out line by line, each line ticking teal.
one line, one fast flag, one record read. Reveals: (1) the line, (2) the fast ring, (3) the record, (4) the ticks.
the scorecard (T2, where to look). Tool named (T7).
09 · Gaming it gets harder
the grey hollow strand from scene 07, traced back to a handful of addresses on Sally's list. Gloss card: risky address · an address that takes your mail without bouncing and never does anything with it. The dot grid pours into the three verdict pots, the grey addresses into monitor and suppress.
the grey strand traced to its addresses, then the pots. Reveals: (1) the trace, (2) the gloss, (3) the pots.
the scorecard, then concept list-cleaning (M-25, M-23, M-24). Registry risky-address, owned by V022.
the answer's "or warming lists artificially" is left out on purpose.
Where hollow engagement comes from
cleaning checks addresses. It does not fix authentication, complaints or reputation, and the VO says so. No placement promise.
10 · Recap
The recap
Sally's scorecard under the lens, four lines lit teal one per phrase: wanted mail · clean list · authentication · complaints. All three chips lit.
four lines, same card, same lens.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.010.012
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.010.012 "Can email marketing tools fix blocklist issues?" (the Almanac question with "email marketing tools" for its abbreviation, S8, V5), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/blacklist-checker, named in the VO above.
the scorecard under the lens, lit, behind the CTA.
callbacks only.
021.010.012, the next untaken myth in the queue. Not drafted yet (flag F1). Totals: 13 scenes. 480 spoken words (recounted 2026-09-30, Q sweep). About 3:00 at 166 words a minute. Every scene is 20 to 70 words (S2).
V094Can email marketing tools fix blocklist issues?
checkedNo open questions are written in this script.
00 · Can email marketing tools fix blocklist issues? (hook) · 0:00
On screen: the title question, Lora, large: "Can email marketing tools fix blocklist issues?" The gate, with the blocklist book held open at it, send-more.example on one line in coral. Beside the gate, Sally's support ticket goes into the van from episode 24. The van drives up to the book, and the line stays coral (M2). Three numbered chips: what your tool can do · what only you can do · the steps, in order.
Can email marketing tools fix blocklist issues? Sally Send's campaign came back with a message naming a blocklist. So she opens a support ticket, and waits for her tool to sort it out. They can point at it. They can't sign the form. Here's how it splits. What your tool can do. What only you can do. And the steps, in order.
01 · Brought to you by, woven in · 0:20
On screen: no cut away, no ad break. The gate holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails is behind this one, and as list cleaners we'll say it first, cleaning never takes anyone off a blocklist.
02 · Whose book is it? · 0:27
On screen: the book closes to show its cover, a plain operator badge with no name. Beside it, a stack of three things fans out: rules · evidence · form. The van stays at the kerb. Gloss card, for a viewer arriving from search: blocklist · a published list of sending IPs or domains flagged for spam, which receiving servers check before accepting mail.
Whose book is it, then? Blocklist operators are independent organisations. Their own rules, their own evidence bar, and their own delisting forms. Your email marketing tool isn't a party to that conversation. You are.
03 · What your tool can do · 0:42
On screen: chip 1 lights. Four cards come out of the van, one per phrase: names the list · shares what worked · pauses sending · rare: its own servers. The fourth card is dimmer than the rest. Gloss card: email marketing tool · the tool you send with, such as a marketing platform. It is not the same as the provider your reader receives with.
And your tool? Four useful things it can do. Tell you which blocklist flagged you, usually from the bounce message. Share what they've seen work for other senders on that list. Pause your sending, so you stop digging the hole deeper. And in rare cases, contact the list for its own shared servers.
04 · When your tool does call · 1:02
On screen: the dim card brightens. The van's own line in the book, shared servers, gets a phone call and clears. Sally's line, send-more.example, stays coral.
That last card needs a closer look. If the listing is against your tool's own shared servers, they may contact the blocklist themselves. But that's them protecting their own setup. It isn't fixing your domain's reputation.
05 · What only you can do · 1:17
On screen: chip 2 lights. The removal form slides out beside the book. One field, labelled your domain or IP, with send-more.example typed into it. The van's pen hovers and has nowhere to write. Gloss card: delisting · asking a blocklist to remove you, after fixing whatever put you on it.
What can't they do? File your delisting request. Prove your list is clean. Or vouch for how people signed up. The removal form has a field for your domain, or your server's address. Not your tool's. The big lists say it plainly. Only the sender, or their network, can ask.
06 · Step one: find the name · 1:38
On screen: chip 3 lights. A numbered rail appears, five steps, the first lit. Sally's bounce slip, in mono, with no code shown: ... blocked using [the list's name]. A teal box lands on blocked using, then slides right to the name.
Now the steps, in order. One. Find which list flagged you. The bounce message names it. Look for the words blocked using, and the list's name comes right after them.
07 · Step two: the cause first · 1:53
On screen: step two lights. Three cause cards drop beside the book, one per phrase: hacked account · bought or scraped list · broken forwarder. A small counter on the form reads second ask: refused.
Two. Find the cause before you ask for removal. Ask without fixing it, and the big lists won't delist you twice. Common causes. An account that's been taken over and is sending phishing. A bought or scraped list. A forwarder that's set up wrong.
08 · Steps three and four: fix it, then ask honestly · 2:12
On screen: steps three and four light. Each cause card from scene 07 turns teal as its fix lands. Then the form's free text box fills with one specific line, a time and a change, and a read tick appears. A second form with a vague line gets a coral rejected.
Three. Fix it. Change the passwords and keys. Stop sending to the bad part of the list. Tighten how people confirm when they sign up. Four. Send the removal request, and be honest about what happened and what you changed. Vague requests get turned down. Specific ones get read.
09 · Step five: wait · 2:32
On screen: step five lights. Sally's line in the book, and a small timer beside one line in a second book, counting down on its own.
Five. Wait. The book isn't yours to close. And some lists you just have to wait out, because they only let you go when a timer runs out.
10 · Where your tool helps for real · 2:44
On screen: a spam complaint flies from an inbox back to the van. The van takes that reader off Sally's send list. A speech card from Sally to the van: do you remove complainers?
Where does your tool genuinely help? Complaints. When someone marks you as spam, the big mailbox providers send that back to whoever owns the sending server. On a shared server, that's your tool. They should be removing those people for you. Ask them to confirm they do.
11 · One question to ask · 3:04
On screen: three cards under the book: list quality · consent · security. Only the first lifts. The dot grid pours into the three verdict pots. The book's coral line does not change.
Where does a listing come from? Almost always list quality, consent, or a security event. List quality is our part of that. Every address gets checked before you send. It won't take you off a list, fix your consent, or lock your accounts. Consent and security are yours to fix.
12 · Recap · 3:36
On screen: the five-step rail, all lit, with the van beside the complaint card. All three chips lit.
Four moves to keep. Read the bounce for the list's name. Fix the cause before you ask. Fill in the form yourself, honestly. And ask your tool to handle complaints on its side.
13 · Close · 3:52
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.011.004 "Do cookies in email exist?", no subscribe ask.
Want to look up the list that named you? Start at our free blocklist directory. Clean your first 1,000 free at reviewmyemails dot com slash get started. Coming up next... do cookies in email exist?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.010.012-tools-cant-sign-the-delisting-form-myth.md
00 · Can email marketing tools fix blocklist issues? (hook)
The myth
the title question, Lora, large: "Can email marketing tools fix blocklist issues?" The gate, with the blocklist book held open at it, send-more.example on one line in coral. Beside the gate, Sally's support ticket goes into the van from episode 24. The van drives up to the book, and the line stays coral (M2). Three numbered chips: what your tool can do · what only you can do · the steps, in order.
one line in one book that doesn't change. Reveals: (1) the question, (2) the gate and book, (3) the ticket and the van, (4) the line that stays coral, (5) the chips.
registry blocklist (the book held open at the gate), the van (episode 24).
01 · Brought to you by, woven in
no cut away, no ad break. The gate holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29). Said up front for the hard content rule (S10).
02 · Whose book is it?
the book closes to show its cover, a plain operator badge with no name. Beside it, a stack of three things fans out: rules · evidence · form. The van stays at the kerb. Gloss card, for a viewer arriving from search: blocklist · a published list of sending IPs or domains flagged for spam, which receiving servers check before accepting mail.
one book, three things it owns. Reveals: (1) the cover, (2) to (4) one thing per phrase, (5) the van at the kerb, (6) the gloss.
registry blocklist. Bounces part 2 owns the full gloss (S6), and this video re-glosses it in the registry's one line so it stands alone (Q5).
03 · What your tool can do
What your tool can do
chip 1 lights. Four cards come out of the van, one per phrase: names the list · shares what worked · pauses sending · rare: its own servers. The fourth card is dimmer than the rest. Gloss card: email marketing tool · the tool you send with, such as a marketing platform. It is not the same as the provider your reader receives with.
four cards, one dimmer. Reveals: (1) to (4) one card per phrase, (5) the gloss.
the van. Registry esp gloss, voiced as "email marketing tool" (V5, Q5).
04 · When your tool does call
the dim card brightens. The van's own line in the book, shared servers, gets a phone call and clears. Sally's line, send-more.example, stays coral.
two lines, one clears, one doesn't. Reveals: (1) the card, (2) the van's line clears, (3) Sally's line unchanged.
the book at the gate.
05 · What only you can do
What only you can do
chip 2 lights. The removal form slides out beside the book. One field, labelled your domain or IP, with send-more.example typed into it. The van's pen hovers and has nowhere to write. Gloss card: delisting · asking a blocklist to remove you, after fixing whatever put you on it.
one form, one field, one name typed in. Reveals: (1) the form, (2) the field, (3) the gloss, (4) the van's pen with nowhere to go, (5) send-more.example typed in.
the book and the form. Registry delisting (gloss tier, first gloss, this video owns it).
06 · Step one: find the name
The steps, in order
chip 3 lights. A numbered rail appears, five steps, the first lit. Sally's bounce slip, in mono, with no code shown: ... blocked using [the list's name]. A teal box lands on blocked using, then slides right to the name.
one slip, one box that moves once. Reveals: (1) the rail, (2) the slip, (3) the box on the words, (4) the box on the name.
the book at the gate (T2, where to look). No bounce code shown (C26 stays out of this video).
07 · Step two: the cause first
step two lights. Three cause cards drop beside the book, one per phrase: hacked account · bought or scraped list · broken forwarder. A small counter on the form reads second ask: refused.
three causes, one refusal. Reveals: (1) the step, (2) to (4) one card per phrase, (5) the refusal.
the book and the form.
the answer's "spamtrap hit" and "open relay" are not voiced. The first is a trap claim, the second needs its own gloss (P6).
08 · Steps three and four: fix it, then ask honestly
steps three and four light. Each cause card from scene 07 turns teal as its fix lands. Then the form's free text box fills with one specific line, a time and a change, and a read tick appears. A second form with a vague line gets a coral rejected.
three cards turn teal, two forms, one read, one rejected. Reveals: (1) step three, (2) the cards turn, (3) step four, (4) the specific form, (5) the vague form.
the book and the form.
09 · Step five: wait
step five lights. Sally's line in the book, and a small timer beside one line in a second book, counting down on its own.
one line waiting, one timer. Reveals: (1) the step, (2) the line, (3) the timer.
the book at the gate.
the answer's "Most lists clear within 24 hours" is not voiced. Siblings give "days to weeks", "24 to 72 hours" and "a few hours to several days". No window is voiced.
10 · Where your tool helps for real
a spam complaint flies from an inbox back to the van. The van takes that reader off Sally's send list. A speech card from Sally to the van: do you remove complainers?
one complaint, one route back, one removal, one question. Reveals: (1) the complaint, (2) the route to the van, (3) the removal, (4) the question.
the van (T5, the action).
11 · One question to ask
three cards under the book: list quality · consent · security. Only the first lifts. The dot grid pours into the three verdict pots. The book's coral line does not change.
three causes, one lifted, the book unchanged. Reveals: (1) the three cards, (2) the first lifts, (3) the pots, (4) the book, still coral.
the book, then concept list-cleaning (M-25, M-23, M-24).
Where a listing starts
cleaning checks addresses. It does not delist, fix consent or fix security, and the VO says so. A listing is never a reason to suppress a reader. No placement promise.
12 · Recap
The recap
the five-step rail, all lit, with the van beside the complaint card. All three chips lit.
five steps and one van card, as before.
callbacks only (S5).
13 · Close
Almanac ids in this scene: 021.011.004
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.011.004 "Do cookies in email exist?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/directory, named in the VO above.
the book at the gate behind the CTA.
callbacks only.
021.011.004, episode 28 in this batch (V095). Totals: 15 scenes. 603 spoken words (recounted 2026-09-30, Q sweep). About 3:40 at 166 words a minute. Every scene is 20 to 70 words (S2).
V095Do cookies in email exist?
checkedNo open questions are written in this script.
00 · Do cookies in email exist? (hook) · 0:00
On screen: the title question, Lora, large: "Do cookies in email exist?" An envelope from send-more.example. A cookie drops toward it and has nowhere to land, it slides off (M2). Behind the envelope, a faint trail of three crumbs. Three numbered chips: why an email can't hold one · what senders use instead · where cookies come back in.
Do cookies in email exist? One of Sally Send's readers asks her straight out. Are your emails putting cookies on my phone? Sally isn't sure. No cookies. Other crumbs. Let's break it into three. Why an email can't hold a cookie. What senders use instead. And where cookies come back in.
01 · Brought to you by, woven in · 0:18
On screen: no cut away, no ad break. The envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every number in your report starts with the people on your list, and those people are what Review My Emails looks at.
02 · Why an email can't hold one · 0:26
On screen: chip 1 lights. Split screen. Left, a browser window with a cookie jar on its shelf. Right, the same shelf inside the envelope, empty. A small label under the empty shelf: no jar, nothing running.
Why can't it? On a website, your browser keeps a cookie jar. An email app doesn't. There's no jar in there, and nothing running in the background to use one. So an email can't set a cookie, and it can't read one sitting in your inbox.
03 · Is email tracking-free, then? · 0:44
On screen: chip 2 lights. The three crumbs behind the envelope light up teal, one, two, three.
But that doesn't make email a tracking-free zone. Senders have other ways in, and some of them work in a similar way. There are three main ones.
04 · Crumb one: the pixel · 0:55
On screen: the first crumb opens into the magnified dot from episode 18. When the email opens, the dot loads and a line pings out to a server, which ticks opened.
The first you may have met already. The tracking pixel. A tiny image, one pixel by one, that pings a server when it loads, and logs that you opened the email.
05 · Crumb two: the tagged link · 1:08
On screen: the second crumb opens into a link in Sally's email, send-more.example/spring. A cursor hovers, and the full address shows beneath it with a tag on the end, ?s=4821, boxed teal. The box then points to one row in a list of subscribers.
The second is the link itself. Each link can carry a short tag on the end of its address, just for you. So when you click, the sender knows which subscriber it was. Hover over a link before you click, and you can often see it.
06 · Crumb three: fingerprinting · 1:27
On screen: the third crumb opens into the same email drawn three ways, a phone, a laptop, a web inbox, each slightly different. A magnifier reads the differences. Gloss card: fingerprinting · working out someone's device or email app from how their email app shows the message.
The third is fingerprinting. Working out your device or your email app from the way it shows the email. No cookie needed.
07 · Where cookies come back · 1:39
On screen: chip 3 lights. The tagged link from scene 05 is clicked, and the view steps out of the envelope into the browser from scene 02. The cookie jar on its shelf opens.
Cookies do come back, though. The moment you click a link and land on a website, you're in your browser's territory. Normal web cookies apply there, and that site's cookie rules kick in as they normally would.
08 · The crumbs are fading · 1:56
On screen: the open counter climbing on its own while the inbox beside it stays shut. Then the first and third crumbs fade to grey, one per phrase.
And even the crumbs are getting harder to read. Apple Mail's privacy setting loads email images in the background, so the pixel fires whether or not anyone opened the email. IP addresses get masked. Device details disappear.
09 · What that leaves · 2:14
On screen: the three crumbs. Two grey, the tagged link still teal. The cookie from the hook slides off the envelope one more time.
That leaves opens from Apple Mail users, for all practical purposes, unreliable now. Email never had cookies. And the tools it did have are getting harder to rely on too.
10 · What to do with that · 2:30
On screen: Sally's list as one column of rows, each with a fuzzy grey opened tick. An RME Insights panel slides in beside it and sorts the same rows into two groups, still engaged in teal and gone quiet in grey. The pixel crumb from scene 08 stays grey.
What a fuzzy open can't tell you any more is who's still paying attention. That's the question RME Insights is for. It shows you who's still engaged on your list. It won't fix open tracking.
11 · Recap · 3:00
On screen: the envelope with its three crumbs, the jar in the browser, the clicks column outlined. All three chips lit.
Here's the short version. No cookies in email. Pixels, tagged links and fingerprinting do the tracking. Cookies come back once someone clicks through. And when opens get fuzzy, follow the clicks in your report.
12 · Close · 3:14
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.005.006 "Does switching domains reset reputation?", no subscribe ask.
Want that split for your own list? Ask us about RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next up... does switching domains reset reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.011.004-no-cookies-other-crumbs-myth.md
00 · Do cookies in email exist? (hook)
The myth
the title question, Lora, large: "Do cookies in email exist?" An envelope from send-more.example. A cookie drops toward it and has nowhere to land, it slides off (M2). Behind the envelope, a faint trail of three crumbs. Three numbered chips: why an email can't hold one · what senders use instead · where cookies come back in.
one envelope, one cookie that won't land, three crumbs. Reveals: (1) the question, (2) the envelope, (3) the cookie slides off, (4) the crumbs, (5) the chips.
new, proposed: the envelope and the crumbs.
01 · Brought to you by, woven in
no cut away, no ad break. The envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · Why an email can't hold one
Why an email can't hold one
chip 1 lights. Split screen. Left, a browser window with a cookie jar on its shelf. Right, the same shelf inside the envelope, empty. A small label under the empty shelf: no jar, nothing running.
one jar, one empty shelf. Reveals: (1) the browser and jar, (2) the envelope's empty shelf, (3) the label.
the envelope and the crumbs, plus the browser (it returns in scene 07).
03 · Is email tracking-free, then?
What senders use instead
chip 2 lights. The three crumbs behind the envelope light up teal, one, two, three.
three crumbs, lit in order. Reveals: (1) to (3) one crumb per click.
the envelope and the crumbs.
04 · Crumb one: the pixel
the first crumb opens into the magnified dot from episode 18. When the email opens, the dot loads and a line pings out to a server, which ticks opened.
one dot, one ping, one tick. Reveals: (1) the dot, (2) the ping, (3) the tick.
episode 18's magnified dot, callback only. Not glossed again (S6).
05 · Crumb two: the tagged link
the second crumb opens into a link in Sally's email, send-more.example/spring. A cursor hovers, and the full address shows beneath it with a tag on the end, ?s=4821, boxed teal. The box then points to one row in a list of subscribers.
one link, one tag, one row. Reveals: (1) the link, (2) the hover, (3) the tag, (4) the row.
the envelope and the crumbs (T2, where to look). The tag is invented, send-more.example is from the demo-names library.
"Hover over a link... you can often see it" is how to look, not an email fact. It uses the answer's own description of the tag ("query strings appended to URLs").
06 · Crumb three: fingerprinting
the third crumb opens into the same email drawn three ways, a phone, a laptop, a web inbox, each slightly different. A magnifier reads the differences. Gloss card: fingerprinting · working out someone's device or email app from how their email app shows the message.
one email, three ways it shows. Reveals: (1) the three, (2) the magnifier, (3) the gloss.
the envelope and the crumbs. New gloss, proposed for the registry (flag F3).
07 · Where cookies come back
Where cookies come back in
chip 3 lights. The tagged link from scene 05 is clicked, and the view steps out of the envelope into the browser from scene 02. The cookie jar on its shelf opens.
one click, one step out, one jar open. Reveals: (1) the click, (2) the step into the browser, (3) the jar.
the browser from scene 02.
08 · The crumbs are fading
the open counter climbing on its own while the inbox beside it stays shut. Then the first and third crumbs fade to grey, one per phrase.
a counter that climbs with the inbox shut, two crumbs fading. Reveals: (1) the counter, (2) the shut inbox, (3) the pixel crumb greys, (4) the fingerprint crumb greys.
concept mail-privacy-protection, callback only (S6).
09 · What that leaves
the three crumbs. Two grey, the tagged link still teal. The cookie from the hook slides off the envelope one more time.
three crumbs, one still teal. Reveals: (1) the grey two, (2) the teal one, (3) the cookie slides off.
the envelope and the crumbs.
10 · What to do with that
Almanac ids in this scene: 021.013.003
Sally's list as one column of rows, each with a fuzzy grey opened tick. An RME Insights panel slides in beside it and sorts the same rows into two groups, still engaged in teal and gone quiet in grey. The pixel crumb from scene 08 stays grey.
one column of rows, split into two groups, the pixel unchanged. Reveals: (1) the column, (2) the panel, (3) the split, (4) the grey pixel.
the envelope and its crumbs, then the RME Insights panel (as in 021.013.003's close).
no window, no rate. The sibling's "30 to 90 days" and "180 or more days" are not voiced (C30, C46).
Who's still engaged
RME Insights shows engagement. It does not fix tracking or open data, and the VO says so. No placement promise.
11 · Recap
The recap
the envelope with its three crumbs, the jar in the browser, the clicks column outlined. All three chips lit.
three crumbs, one jar, one column.
callbacks only (S5).
12 · Close
Almanac ids in this scene: 021.005.006
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.005.006 "Does switching domains reset reputation?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the envelope and its crumbs behind the CTA.
callbacks only.
021.005.006, episode 29 in this batch (V096). Totals: 14 scenes. 483 spoken words (recounted 2026-09-30, Q sweep). About 2:55 at 166 words a minute. Every scene is 20 to 70 words (S2).
V096Does switching domains reset reputation?
checkedNo open questions are written in this script.
00 · Does switching domains reset reputation? (hook) · 0:00
On screen: the title question, Lora, large: "Does switching domains reset reputation?" Two houses on two streets. The old one, send-more.example, with episode 14's gauge low. The new one with a blank house number and its gauge at zero. A removal van carries three boxes across, and the music notes drift out of them (M2). Three numbered chips: what a new domain resets · what moves with you · what to fix before you switch.
Does switching domains reset reputation? Sally Send's domain has had a rough run, and she's eyeing a shiny new one. Fresh name, fresh start. New street. Same music. Three things to sort before you move. What a new domain resets. What moves with you. And what to fix before you switch.
01 · Brought to you by, woven in · 0:17
On screen: no cut away, no ad break. The boxes hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Whatever domain you send from, your list makes the move with you, and that list is what Review My Emails cleans for you.
02 · What a new domain resets · 0:25
On screen: chip 1 lights. The new house's gauge at zero. A magnifier from the mailbox provider hovers over it, closer than over the old house. Gloss callback in one line: domain reputation · the part of your reputation that belongs to your domain name (episode 14's card).
First, what does a new domain reset? Its reputation starts at zero. Zero reputation, not zero problems. Mailbox providers watch new domains closely. Bring the same bad habits, and you'll burn the new one just as fast.
03 · The neighbourhood · 0:42
On screen: the new house at night. A clock reads 2:00. Music notes pour out of the open boxes. One by one, the neighbours' windows light up, and the new gauge drops.
Think of it like moving to a new neighbourhood. The neighbours don't know you yet. But turn up playing loud music at two in the morning, and you'll have the same reputation problem within a week. The domain isn't the issue. How you send is.
04 · What moves with you: the list · 1:00
On screen: chip 2 lights. The first box, labelled list, carried in coral. Inside, rows of addresses, some greyed and silent.
What comes with you, then? Your list, first. If a stale list burned the old domain, the same list will burn the new one. It's the most common culprit, and it follows you everywhere.
05 · What moves with you: complaints · 1:15
On screen: the second box, complaints. Two buttons, spam and unsubscribe, and a cursor presses spam. Then the box opens onto Sally's signup form.
Your complaints come too. If people hit spam instead of unsubscribe, that's a consent problem, not a domain problem. So look at your signup flow. Make sure people chose to hear from you, and know what they signed up for.
06 · What moves with you: bounces · 1:33
On screen: the third box, bounces. Envelopes to dead addresses come back out of it, stamped, and the magnifier notes each one.
And your bounce handling. Sending to dead addresses tells mailbox providers you're not looking after your list. That signal moves with you, to any domain.
07 · What follows you anyway · 1:46
On screen: the new house has a nameplate with Sally's brand on it, and a faint line runs from it back to the old house. Next door, a shared building with suitcases stacked outside. Both nudge the new gauge down.
And some of the old reputation can follow you, even after the switch. If your brand name is well known as a spam source, or you're on a shared server with its own baggage, a new domain alone won't fully reset how filters see you.
08 · What to fix first: authentication · 2:06
On screen: chip 3 lights. The new house's front door gets three locks, SPF, DKIM, DMARC, fitted before the first envelope leaves. Then the SPF Checker page: the new domain typed in, a result that reads pass. Then the DMARC Generator building one record.
What do you fix before you switch? Authentication, first. It proves your mail came from the domain it says it's from. Set it up on the new domain before a single email goes out. A fresh domain with missing authentication looks suspicious straight away. Our free SPF Checker and DMARC Generator help you check and build it.
09 · Then build up slowly · 2:28
On screen: the list box opens. The dot grid pours into the three verdict pots, and only the keep pot's rows go into the van. The old house stays where it is.
The list is the one box we can help you pack. Each address gets checked before the move, so the dead ones don't make the trip. Your complaints, your authentication and the old domain's history are still yours to fix.
10 · Recap · 3:01
On screen: the three boxes turn teal one per phrase, the three locks click, the growing stack. All three chips lit.
The only real reset is how you send. Before you switch, clean the list. Fix what's driving complaints. Handle your bounces. Authenticate the new domain first. Then build up slowly.
11 · Close · 3:17
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.013 "Will cold email become illegal?", no subscribe ask.
Moving house? Run the new domain through our free SPF Checker first. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next question... will cold email become illegal?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.005.006-new-domain-same-habits-myth.md
00 · Does switching domains reset reputation? (hook)
The myth
the title question, Lora, large: "Does switching domains reset reputation?" Two houses on two streets. The old one, send-more.example, with episode 14's gauge low. The new one with a blank house number and its gauge at zero. A removal van carries three boxes across, and the music notes drift out of them (M2). Three numbered chips: what a new domain resets · what moves with you · what to fix before you switch.
one gauge at zero, three boxes carried in. Reveals: (1) the question, (2) the old house, (3) the new house at zero, (4) the boxes, (5) the chips.
concept sender-reputation (the score gauge, M-33), from episode 14. New, proposed: the two houses and the three boxes.
01 · Brought to you by, woven in
no cut away, no ad break. The boxes hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What a new domain resets
What a new domain resets
chip 1 lights. The new house's gauge at zero. A magnifier from the mailbox provider hovers over it, closer than over the old house. Gloss callback in one line: domain reputation · the part of your reputation that belongs to your domain name (episode 14's card).
one gauge at zero, one magnifier held close. Reveals: (1) the zero, (2) the magnifier, (3) the callback card.
the score gauge (M-33). domain-reputation is gloss tier, owned by episode 14.
03 · The neighbourhood
the new house at night. A clock reads 2:00. Music notes pour out of the open boxes. One by one, the neighbours' windows light up, and the new gauge drops.
one clock, the windows lighting one by one, one needle falling. Reveals: (1) the clock, (2) the notes, (3) the windows, (4) the needle.
the two houses (T10, the answer's own simile).
04 · What moves with you: the list
What moves with you
chip 2 lights. The first box, labelled list, carried in coral. Inside, rows of addresses, some greyed and silent.
one box, some rows grey. Reveals: (1) the box, (2) the rows, (3) the grey ones.
the two houses and the boxes.
05 · What moves with you: complaints
the second box, complaints. Two buttons, spam and unsubscribe, and a cursor presses spam. Then the box opens onto Sally's signup form.
one box, two buttons, one pressed. Reveals: (1) the box, (2) the buttons, (3) the press, (4) the form.
the boxes.
the answer's "above 0.1%" is not voiced (N6).
06 · What moves with you: bounces
the third box, bounces. Envelopes to dead addresses come back out of it, stamped, and the magnifier notes each one.
one box, the returned envelopes. Reveals: (1) the box, (2) the returns, (3) the magnifier's notes.
the boxes.
07 · What follows you anyway
the new house has a nameplate with Sally's brand on it, and a faint line runs from it back to the old house. Next door, a shared building with suitcases stacked outside. Both nudge the new gauge down.
one line back to the old house, one shared building, one needle nudged. Reveals: (1) the nameplate, (2) the line back, (3) the shared building, (4) the nudge.
the two houses. "shared IP" voiced as "shared server".
08 · What to fix first: authentication
Almanac ids in this scene: 001.009.002
What to fix before you switch
chip 3 lights. The new house's front door gets three locks, SPF, DKIM, DMARC, fitted before the first envelope leaves. Then the SPF Checker page: the new domain typed in, a result that reads pass. Then the DMARC Generator building one record.
three locks before one envelope, one check, one record. Reveals: (1) the locks, (2) the first envelope waits, (3) the checker, (4) the generator.
the two houses (T2, where to look). Tools named (T7). Q sweep: authentication is the one new word, glossed in one plain line from 001.009.002 for a viewer arriving from search (Q5). The three locks keep their labels on screen, and the VO names SPF and DMARC only inside the tool names (Q6).
09 · Then build up slowly
the list box opens. The dot grid pours into the three verdict pots, and only the keep pot's rows go into the van. The old house stays where it is.
one box, three pots, one pot carried. Reveals: (1) the box, (2) the pots, (3) the van takes one pot.
concept list-cleaning (M-25, M-23, M-24).
the answer's "4-6 weeks" is voiced only as "weeks, not days".
The box that always makes the move
cleaning checks addresses. It does not fix complaints, authentication or reputation, and the VO says so. No placement promise.
10 · Recap
The recap
the three boxes turn teal one per phrase, the three locks click, the growing stack. All three chips lit.
three boxes, three locks, one stack.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.013.013
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.013.013 "Will cold email become illegal?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/spf-checker, named in the VO above.
the new house, gauge climbing, behind the CTA.
callbacks only.
021.013.013, episode 30 in this batch (V097). Totals: 13 scenes. 488 spoken words (recounted 2026-09-30, Q sweep). About 3:00 at 166 words a minute. Every scene is 20 to 70 words (S2).
V097Will cold email become illegal?
checkedNo open questions are written in this script.
00 · Will cold email become illegal? (hook) · 0:00
On screen: the title question, Lora, large: "Will cold email become illegal?" A road with a painted line across it, and a weathervane on a post beside it. A wall drops toward the line, then stops in mid air and fades (M2). Three numbered chips: why a full ban is unlikely · where the squeeze comes from · the signs to watch.
Will cold email become illegal? A rumour reaches Sally Send's sales desk. A ban is coming, and every first email to a stranger is about to be against the law. Wrong worry. Here's the forecast, in three parts. Why a full ban is unlikely. Where the real squeeze comes from. And the signs to watch.
01 · Brought to you by, woven in · 0:19
On screen: no cut away, no ad break. The road holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Whoever you're writing to, it starts with an address that's real, and checking that is where Review My Emails comes in.
02 · What cold email is, and the line today · 0:27
On screen: gloss card: cold email · mail sent to someone who never asked to hear from you. Then the painted line splits into two stretches of road. On one, a sign honest + easy out. On the other, a sign consent first. No law named, no map, no flag.
First, what we mean. Cold email is mail sent to someone who never asked to hear from you. Nobody has a crystal ball on where it's going. But legally, it already depends on where your reader is, because some places allow a first cold email if you're honest and make it easy to opt out, while others want consent before the first message.
03 · Will it all be banned? · 0:52
On screen: chip 1 lights. The wall from the hook tries once more to land on the line, and the road's traffic, a long queue of business envelopes, holds it up.
Is a full ban coming, then? A complete global ban on cold email is unlikely. The sheer scale of business to business sales makes that a hard political lift in most countries.
04 · Not banned, but harder · 1:08
On screen: the weathervane swings. Two gusts, drawn as arrows, blow from two sides and both push toward the line.
But that doesn't mean things aren't getting harder. The more useful question is which way the wind is blowing. And right now, the squeeze is coming from two directions at once.
05 · Gust one: enforcement · 1:19
On screen: chip 2 lights. The first gust labelled enforcement. The two road signs from scene 02 stay the same, only brighter.
The first is enforcement. Regulators are enforcing the rules they already have, and doing it more aggressively. The signs on the road haven't changed. They're just being applied harder.
06 · The filter doesn't wait · 1:30
On screen: the second gust labelled filters. A cold envelope rolls up to the line, passes the legal signs, and drops into a junk tray before any wall appears. A small gauge beside it reads engagement: low.
The second one surprises people. Inbox providers are building their own filters that treat cold senders harshly, whatever the law says. Outlook and Gmail don't need a regulation to route your cold email to junk. They just need low engagement.
07 · The signs to watch · 1:50
On screen: chip 3 lights. Four coral road signs go up along the road, one per phrase: fines near you · new opt-in rules · filtered, auth clean · complaints rising. The last sign points to the complaints column in Sally's own campaign report.
What do you watch for? Regulators fining businesses in your industry or country for unsolicited email. New rules asking for opt-in consent. Your cold email domain getting filtered even when your authentication is clean. And more complaints from recipients, a practical warning sign before a legal one.
08 · Where it's safest to stand · 2:14
On screen: one stretch of road, lit teal, with three small markers: thoughtful · honest · easy no. Both gusts drop to a breeze there.
Where's the safest place to stand, legally and for deliverability? Sending to people who have a genuine reason to hear from you. Target thoughtfully. Personalise honestly. And make it easy to say no.
09 · Why that also performs · 2:31
On screen: the envelopes on the road lift into the dot grid, which pours into the three verdict pots. The road signs don't change.
And none of that engagement can happen at an address that doesn't exist. Each one on your list gets checked before you send. That won't make a cold email welcome, or legal where it isn't. Those calls are yours.
10 · Recap · 3:01
On screen: the road, the vane, the four coral signs and the teal stretch. All three chips lit.
A full ban is unlikely. The squeeze is real, from regulators and from filters. Watch the four signs. And send only where people have a reason to hear from you.
11 · Close · 3:16
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.007.007 "Can I re-add unsubscribed contacts after a while?", no subscribe ask. Gloss card with the parser line: DMARC · a policy on top of SPF and DKIM saying what a receiving server should do when a message fails, and where to send reports.
Want to be sure your authentication is clean before you blame the filters? Our free DMARC Parser reads your DMARC record. Clean your first 1,000 free at reviewmyemails dot com slash get started. Coming next... can I re-add unsubscribed contacts after a while?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.013.013-cold-email-wrong-worry-myth.md
00 · Will cold email become illegal? (hook)
The myth
the title question, Lora, large: "Will cold email become illegal?" A road with a painted line across it, and a weathervane on a post beside it. A wall drops toward the line, then stops in mid air and fades (M2). Three numbered chips: why a full ban is unlikely · where the squeeze comes from · the signs to watch.
one line, one wall that never lands, one vane. Reveals: (1) the question, (2) the road and line, (3) the wall that fades, (4) the vane, (5) the chips.
new, proposed: the road, the line and the weathervane.
01 · Brought to you by, woven in
no cut away, no ad break. The road holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · What cold email is, and the line today
gloss card: cold email · mail sent to someone who never asked to hear from you. Then the painted line splits into two stretches of road. On one, a sign honest + easy out. On the other, a sign consent first. No law named, no map, no flag.
one line, two stretches of road. Reveals: (1) the gloss, (2) the split, (3) the first sign, (4) the second sign.
the road. Registry cold-email (gloss tier, first gloss, this video owns it).
"But legally... before the first message" is the one legal sentence. No law, no timing, no business-days count.
03 · Will it all be banned?
Why a full ban is unlikely
chip 1 lights. The wall from the hook tries once more to land on the line, and the road's traffic, a long queue of business envelopes, holds it up.
one wall, held up by one long queue. Reveals: (1) the wall, (2) the queue, (3) the wall stays up.
the road.
04 · Not banned, but harder
the weathervane swings. Two gusts, drawn as arrows, blow from two sides and both push toward the line.
one vane, two gusts, one direction. Reveals: (1) the vane, (2) gust one, (3) gust two.
the weathervane (T10, the answer's own simile).
05 · Gust one: enforcement
Where the squeeze comes from
chip 2 lights. The first gust labelled enforcement. The two road signs from scene 02 stay the same, only brighter.
the same two signs, brighter. Reveals: (1) the gust label, (2) the signs brighten.
the road and vane.
the answer's fines line is not voiced. It names a law.
06 · The filter doesn't wait
the second gust labelled filters. A cold envelope rolls up to the line, passes the legal signs, and drops into a junk tray before any wall appears. A small gauge beside it reads engagement: low.
one envelope, past the signs, into one tray. Reveals: (1) the gust, (2) the envelope passes the signs, (3) the junk tray, (4) the gauge.
the road. Registry inbox-placement tray, callback.
07 · The signs to watch
The signs to watch
chip 3 lights. Four coral road signs go up along the road, one per phrase: fines near you · new opt-in rules · filtered, auth clean · complaints rising. The last sign points to the complaints column in Sally's own campaign report.
four signs, one pointing at a column. Reveals: (1) to (4) one sign per phrase, (5) the report column.
the road (T2, where to look). No regulation named on the second sign.
08 · Where it's safest to stand
one stretch of road, lit teal, with three small markers: thoughtful · honest · easy no. Both gusts drop to a breeze there.
one lit stretch, three markers, the gusts calming. Reveals: (1) the stretch, (2) to (4) one marker per phrase, (5) the breeze.
the road (T5, the action).
09 · Why that also performs
the envelopes on the road lift into the dot grid, which pours into the three verdict pots. The road signs don't change.
the envelopes, three pots, the signs unchanged. Reveals: (1) the lift, (2) the pots, (3) the signs, still there.
concept list-cleaning (M-25, M-23, M-24).
A real address first
cleaning checks addresses. It does not make mail wanted or lawful, and the VO says so. No placement promise.
10 · Recap
The recap
the road, the vane, the four coral signs and the teal stretch. All three chips lit.
two gusts, four signs, one lit stretch.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.007.007
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.007.007 "Can I re-add unsubscribed contacts after a while?", no subscribe ask. Gloss card with the parser line: DMARC · a policy on top of SPF and DKIM saying what a receiving server should do when a message fails, and where to send reports.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/dmarc-parser, named in the VO above.
the road behind the CTA.
callbacks only.
021.007.007, episode 31 in this batch (V098). Totals: 13 scenes. 489 spoken words (recounted 2026-09-30, Q sweep). About 3:00 at 166 words a minute. Every scene is 20 to 70 words (S2).
V098Can I re-add unsubscribed contacts after a while?
checkedNo open questions are written in this script.
00 · Can I re-add unsubscribed contacts after a while? (hook) · 0:00
On screen: the title question, Lora, large: "Can I re-add unsubscribed contacts after a while?" A closed door with a coral no card on it. Beside it, a calendar flips six pages. The card stays exactly as it was (M2). Three numbered chips: why the no still stands · what it costs · the one way back.
Can I re-add unsubscribed contacts after a while? Sally Send gave them space. Six months have passed. Maybe they'd be open to hearing from her again. Time doesn't reset a no. Three things worth knowing. Why the no still stands. What it costs to ignore it. And the one way back.
01 · Brought to you by, woven in · 0:19
On screen: no cut away, no ad break. The door holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails cleans the addresses on your list, and the people who asked to leave are a list you keep yourself.
02 · Why the no still stands · 0:27
On screen: chip 1 lights. A permission slip is lifted off the door and replaced by the no card. The calendar flips to a year. The card doesn't fade.
Why doesn't time fix it? When someone unsubscribes, they're withdrawing their permission to email them. That permission doesn't expire, and time doesn't refresh it. Six months later, a year later, it's still a no.
03 · The legal line, in one sentence · 0:43
On screen: one line of text under the door, no law named: permanent · fresh consent only. A stamp waited long enough slides toward the door and doesn't stick.
Legally, the big rules agree that an unsubscribe is permanent, and that only fresh consent brings someone back, so waiting long enough doesn't count.
04 · What it costs: spam reports · 0:56
On screen: chip 2 lights. Sally's envelope slides under the closed door anyway. It comes back out stamped spam. A gauge beside the door, episode 14's, dips.
And it isn't only a compliance risk. It's a deliverability one too. People who've already opted out are unlikely to welcome you back. Spam reports go up, and mailbox providers notice.
05 · Who pays · 1:10
On screen: a row of other doors down the street, all open and teal, Sally's readers who want her mail. The gauge's dip spreads a coral shadow along the whole row.
Here's the part that stings. The hit to your reputation doesn't stay with the people you shouldn't have emailed. It affects everyone else on your list too.
06 · Where re-adds happen by accident · 1:25
On screen: a spreadsheet slides into Sally's email tool, upload. Among its rows, one belongs behind the closed door. It glides onto the send list without a sound.
How does this happen to careful senders? It can happen by accident. During a list upload, or a move to a new system, when an old file brings back people who left.
07 · The fix: the list that says no for you · 1:39
On screen: the same upload runs again, this time past the suppression pot from episode 20, lid closing. The row from scene 06 is caught and stays out. Then the file card from episode 20, in its drawer, address kept · proof. Gloss card, for a viewer arriving from search: suppression list · the addresses you keep on record precisely so you never send to them again.
The fix is a suppression list, kept indefinitely. It's how you make sure nobody slips back in during an upload or a migration. And don't delete people who left without keeping their address on record. You'd lose the proof you honoured their request.
08 · The one way back, before they leave · 2:00
On screen: chip 3 lights. The door opens a crack the moment before the no card lands, showing a small panel: fewer emails · a different kind · leave.
Is there any way back, then? There's a right way to give people a choice. Before they finish unsubscribing, offer a preference center, where they can get fewer emails, or switch to a different kind.
09 · After that, only they can open it · 2:14
On screen: the dot grid pours into the three verdict pots. Beside them, Sally's own suppression pot, with a label only you know who said no. The upload from scene 06 passes Sally's pot first, then ours.
Cleaning helps with part of this. It checks whether each address can take your mail before you send. It can't tell who said no to you. Only your suppression list knows that, which is why your upload passes it first.
10 · Recap · 2:48
On screen: the door with its card, the row of open doors, the pot with its lid, the door opening from their side. All three chips lit.
Time doesn't refresh permission. Emailing people who left costs you with everyone else. The only way back is their own fresh opt in. So keep a suppression list for good, and run every upload past it.
11 · Close · 3:05
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.012.011 "Do inbox placement tools show the full truth?", no subscribe ask.
Worried a past import let people back in? The SOS hotline is free, and we'll look through it with you. Clean your first 1,000 free at reviewmyemails dot com slash get started. The next one asks... do inbox placement tools show the full truth?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.007.007-time-doesnt-reset-a-no-myth.md
00 · Can I re-add unsubscribed contacts after a while? (hook)
The myth
the title question, Lora, large: "Can I re-add unsubscribed contacts after a while?" A closed door with a coral no card on it. Beside it, a calendar flips six pages. The card stays exactly as it was (M2). Three numbered chips: why the no still stands · what it costs · the one way back.
six pages flip, one card unchanged. Reveals: (1) the question, (2) the door and card, (3) the calendar flips, (4) the card still there, (5) the chips.
new, proposed: the door with the no card.
01 · Brought to you by, woven in
no cut away, no ad break. The door holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · Why the no still stands
Why the no still stands
chip 1 lights. A permission slip is lifted off the door and replaced by the no card. The calendar flips to a year. The card doesn't fade.
one slip taken back, one card that stays. Reveals: (1) the slip lifted, (2) the card, (3) the calendar at a year.
the door.
03 · The legal line, in one sentence
one line of text under the door, no law named: permanent · fresh consent only. A stamp waited long enough slides toward the door and doesn't stick.
one line, one stamp that won't stick. Reveals: (1) the line, (2) the stamp slides off.
the door.
this is the one legal sentence. No law, no timing (R10, C14).
04 · What it costs: spam reports
What it costs
chip 2 lights. Sally's envelope slides under the closed door anyway. It comes back out stamped spam. A gauge beside the door, episode 14's, dips.
one envelope under the door, one stamp, one dip. Reveals: (1) the envelope, (2) the stamp, (3) the dip.
the door, and concept sender-reputation (the gauge, M-33).
05 · Who pays
a row of other doors down the street, all open and teal, Sally's readers who want her mail. The gauge's dip spreads a coral shadow along the whole row.
one closed door, a row of open ones, one shadow across all. Reveals: (1) the row, (2) the shadow spreads.
the door and the row.
06 · Where re-adds happen by accident
a spreadsheet slides into Sally's email tool, upload. Among its rows, one belongs behind the closed door. It glides onto the send list without a sound.
one upload, one row slipping back in. Reveals: (1) the upload, (2) the row, (3) it lands on the list.
the door and the upload.
the answer's "accidentally re-add someone during a list upload or a system migration". No count, no share (V9).
07 · The fix: the list that says no for you
the same upload runs again, this time past the suppression pot from episode 20, lid closing. The row from scene 06 is caught and stays out. Then the file card from episode 20, in its drawer, address kept · proof. Gloss card, for a viewer arriving from search: suppression list · the addresses you keep on record precisely so you never send to them again.
one upload, one row caught, one card kept. Reveals: (1) the upload, (2) the pot and the gloss, (3) the catch, (4) the card.
concept suppression-list (the pot with its lid, M-23, M-24) and episode 20's file card, callbacks (S6) (T2, where it does its job).
08 · The one way back, before they leave
The one way back
chip 3 lights. The door opens a crack the moment before the no card lands, showing a small panel: fewer emails · a different kind · leave.
one door, three choices, before the card. Reveals: (1) the crack, (2) the panel, (3) the three choices.
the door. Registry preference-center, callback, glossed in its own video (S6).
09 · After that, only they can open it
the dot grid pours into the three verdict pots. Beside them, Sally's own suppression pot, with a label only you know who said no. The upload from scene 06 passes Sally's pot first, then ours.
three pots of ours, one pot of hers, one upload through both. Reveals: (1) our pots, (2) her pot and label, (3) the upload's route.
concept list-cleaning (M-25, M-23, M-24) and suppression-list.
What cleaning can't see
cleaning checks addresses. It does not know consent, and the VO says so. No placement promise.
10 · Recap
The recap
the door with its card, the row of open doors, the pot with its lid, the door opening from their side. All three chips lit.
one closed door, one pot, one door opened from inside.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.012.011
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.012.011 "Do inbox placement tools show the full truth?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the door behind the CTA.
callbacks only.
021.012.011, episode 32 in this batch (V099). Totals: 13 scenes. 463 spoken words (recounted 2026-09-30, Q sweep). About 2:50 at 166 words a minute. Every scene is 20 to 70 words (S2).
V099Do inbox placement tools show the full truth?
checkedNo open questions are written in this script.
00 · Do inbox placement tools show the full truth? (hook) · 0:00
On screen: the title question, Lora, large: "Do inbox placement tools show the full truth?" A score card, inbox 88, slides into an empty photo frame, and it doesn't fit (M2). The card folds into a compass instead, its needle pointing. Three numbered chips: how the test works · what it can't see · what fills the gaps.
Do inbox placement tools show the full truth? Sally Send runs a placement test, gets a score, and feels like she finally has the answer. A compass, not a photograph. Here's what the score leaves out, in three parts. How the test works. What it can't see. And what fills the gaps.
01 · Brought to you by, woven in · 0:17
On screen: no cut away, no ad break. The compass holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
No test mailbox ever sees the real list you send to, and that real list is the part Review My Emails checks.
02 · How the test works · 0:25
On screen: chip 1 lights. A small panel of mailboxes, each with a provider badge left blank. Sally's envelope copies itself into each. Then each drops into one of the inbox placement trays from episode 12. Gloss card: seedlist testing · sending to a set of test addresses to see where a campaign lands before the real send.
How does the test work? It's called seedlist testing. The tool sends your email to a set of test accounts, called seed accounts, spread across different mailbox providers. Then it checks where each one landed. The inbox. The spam folder. Or somewhere else.
03 · What it can't see: history · 0:44
On screen: chip 2 lights. Beside the small panel, one row from Sally's real list, with a trail of past marks behind it: opened · clicked · replied. The seed mailbox beside it has no trail at all, a clean zero.
It sounds thorough. The catch is what those seed accounts are missing. History. Your real subscribers have opened your emails before, clicked, maybe replied. That history shapes where your mail lands for that person. A seed account starts from zero, every time.
04 · Person by person · 1:04
On screen: three real rows, each sent the same email, land in three different trays. The panel's result is one blended number that matches none of them.
That history matters because mailbox providers make decisions person by person, from each reader's own behaviour. A seed panel gives you an average. Not a picture of each subscriber.
05 · What it can't see: size · 1:19
On screen: zoom out. The small panel shrinks to a dot beside a huge field of inboxes. A few rows at the edge of the field glow, and the panel never reaches them.
The panel is small, too. Most seed panels are small next to your real list. A few dozen accounts standing in for millions of inboxes is always going to miss edge cases.
06 · What it can't see: your mix · 1:32
On screen: Sally's real list as a bar split by where her readers read, one side heavy. The panel's bar beside it split evenly. The two bars don't match.
And it may not look like your audience. Your readers might lean heavily toward corporate Outlook users, or toward Gmail on phones. The seed panel may not match that mix.
07 · What fills the gaps: your own data · 1:46
On screen: chip 3 lights. Sally's own campaign report opens. Three columns light teal, clicks · replies · complaints, split by segment in rows. Then a small bounce line across weeks.
What fills the gaps, then? Your real engagement data. Open your own campaign report and watch your click rates, reply rates and complaint rates, segment by segment. And look at your bounce patterns over time.
08 · What fills the gaps: the provider's own view · 2:03
On screen: a plain dashboard panel, no brand name on it, labelled from real Gmail users, showing a spam rate line and a domain reputation band.
Then add Gmail's own reputation data for senders. It shows your spam rate and domain reputation from actual Gmail users, not seeds. That's real signal.
09 · Is seed testing useless? · 2:17
On screen: the small seed panel from scene 05, then the huge field of Sally's real list beside it. The panel never reaches the field. The field's dots pour into the three verdict pots.
And there's one list no seed panel ever sees. Yours. The addresses you send to are the part we check, each one, before you send. That won't change a placement score, or fix your reputation.
10 · Recap · 2:46
On screen: the compass, the report's three columns and the provider panel slide together into the photo frame, which finally fills. All three chips lit.
Read the three signals together. Seed tests, your real engagement, and the provider's own data give you a much clearer picture than any one of them alone. So never let one score have the final word.
11 · Close · 3:03
On screen: the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.010 "Can B2B senders ignore opt-in laws?", no subscribe ask.
Not sure which signals to lean on for your setup? Our SOS hotline is free, and we'll walk through it with you. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next time... can B2B senders ignore opt-in laws?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.012.011-seed-tests-compass-not-photo-myth.md
00 · Do inbox placement tools show the full truth? (hook)
The myth
the title question, Lora, large: "Do inbox placement tools show the full truth?" A score card, inbox 88, slides into an empty photo frame, and it doesn't fit (M2). The card folds into a compass instead, its needle pointing. Three numbered chips: how the test works · what it can't see · what fills the gaps.
one score that won't fill the frame, one compass. Reveals: (1) the question, (2) the score and frame, (3) the fold into a compass, (4) the chips.
new, proposed: the compass and the empty photo frame. The 88 is an invented score, not a target and not a rate anyone should aim for (N6).
01 · Brought to you by, woven in
no cut away, no ad break. The compass holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
02 · How the test works
How the test works
chip 1 lights. A small panel of mailboxes, each with a provider badge left blank. Sally's envelope copies itself into each. Then each drops into one of the inbox placement trays from episode 12. Gloss card: seedlist testing · sending to a set of test addresses to see where a campaign lands before the real send.
one envelope, one small panel, the trays. Reveals: (1) the panel, (2) the copies, (3) the gloss, (4) the trays.
registry inbox-placement trays (episode 12), callback. Registry seedlist-testing (gloss tier, first gloss, this video owns it).
03 · What it can't see: history
What it can't see
chip 2 lights. Beside the small panel, one row from Sally's real list, with a trail of past marks behind it: opened · clicked · replied. The seed mailbox beside it has no trail at all, a clean zero.
one real row with a trail, one seed with none. Reveals: (1) the real row, (2) its trail, (3) the seed's zero.
the compass and the panel.
04 · Person by person
three real rows, each sent the same email, land in three different trays. The panel's result is one blended number that matches none of them.
three rows, three trays, one average that matches none. Reveals: (1) the three rows, (2) the three trays, (3) the average.
the inbox placement trays.
05 · What it can't see: size
zoom out. The small panel shrinks to a dot beside a huge field of inboxes. A few rows at the edge of the field glow, and the panel never reaches them.
a few dozen dots against a field of millions, the edges unreached. Reveals: (1) the zoom out, (2) the field, (3) the edges.
the panel (N3, zoom out to show scale).
06 · What it can't see: your mix
Sally's real list as a bar split by where her readers read, one side heavy. The panel's bar beside it split evenly. The two bars don't match.
two bars, two different splits. Reveals: (1) her bar, (2) the panel's bar, (3) the mismatch.
the panel. The splits are drawn, never numbered.
07 · What fills the gaps: your own data
What fills the gaps
chip 3 lights. Sally's own campaign report opens. Three columns light teal, clicks · replies · complaints, split by segment in rows. Then a small bounce line across weeks.
three columns, one line over time. Reveals: (1) the report, (2) to (4) one column per phrase, (5) the bounce line.
the compass, with the report (T2, where to look). No rate is shown as a target (N6).
08 · What fills the gaps: the provider's own view
a plain dashboard panel, no brand name on it, labelled from real Gmail users, showing a spam rate line and a domain reputation band.
one panel, two readings. Reveals: (1) the panel, (2) spam rate, (3) domain reputation.
the compass. Registry google-postmaster is internal: the mechanism is shown, never the name.
09 · Is seed testing useless?
the small seed panel from scene 05, then the huge field of Sally's real list beside it. The panel never reaches the field. The field's dots pour into the three verdict pots.
one small panel, one huge field, three pots. Reveals: (1) the panel, (2) the field, (3) the pots.
concept list-cleaning (M-25, M-23, M-24). The catch-all risky-address line was cut in the Q sweep (Q2, not a list topic).
"especially during IP warming" is not voiced (RULE-1 stays clear).
The list no seed sees
cleaning checks addresses. It does not change placement or reputation, and the VO says so. No placement promise.
10 · Recap
The recap
the compass, the report's three columns and the provider panel slide together into the photo frame, which finally fills. All three chips lit.
three signals, one frame filled.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 021.002.010
Start clean
the CTA in teal: Clean your first 1,000 free with reviewmyemails.com/get-started in mono beneath it. End screen: the next Myths video, 021.002.010 "Can B2B senders ignore opt-in laws?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the filled frame behind the CTA.
callbacks only.
021.002.010, the next draftable myth in the queue (flag F1). Not drafted yet. Totals: 13 scenes. 458 spoken words (recounted 2026-09-30, Q sweep). About 2:45 at 166 words a minute. Every scene is 20 to 70 words (S2).
V040What are the recommended bounce classification codes (per RFC 3463)?
waiting on YTOpen questions for YT
- C41 (new): what a full mailbox code says, and how long it gets.
- Registry: "no picture yet" for the log-line form of the slip and the ghost stamp.
00 · Four little codes (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 how the code is built · 2 the four you'll see most · 3 what each one tells you to do. Chips 2 and 3 grey.
Three things answer it. How the code is built. The four you'll see most. And what each one tells you to do.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every one of those codes is an address that didn't take your mail, so Review My Emails checks addresses before they bounce.
02 · How the code is built · 0:40
On screen: one bounce log line, mono, most of it grey: bo.unce@coral-cove.invalid · 550 5.1.1 · The email account that you tried to reach does not exist. A lamp lights 550, then 5.1.1. Then a second line with no dotted code, 550 Requested action not taken, and the lamp settles on 550.
Where do you find it? In your bounce log, on the line next to the failed address. First comes the three-digit code, like five fifty. Right after it, the dotted one. Not every server sends the dotted code. When it's missing, fall back to the three-digit one. It still tells you four or five.
03 · The first one: 5.1.1 · 1:19
On screen: chip 2 lights. The slip's stamp reads 5.1.1. Behind the letter, the door it came from closes. A coral tag lands on the arrow: remove. On the last line, the report zooms out and a cluster of 5.1.1 rows glows together.
Now the four you'll see most. First, five point one point one. Bad destination address. The mailbox doesn't exist. Nobody's there, so there's nothing to wait for. That's a hard bounce. Take the address off, right away. And if you see a lot of them? Your list has aged without a clean, or a signup form is letting bad addresses in.
04 · The second one: 4.2.2 · 1:42
On screen: the stamp rewrites to 4.2.2, amber. The letter goes back to the same door and waits. An amber tag on the arrow: let it retry. Then three sends in a row, the same address, each returned 4.2.2, and the tag turns coral: treat as gone.
Second, four point two point two. Mailbox full, for now. The server is saying try again later. And your sending system does, on its own, so there's nothing for you to do yet. But if the same address keeps coming back full, send after send, stop reading it as busy. Treat it as gone.
05 · The same full mailbox, as a five · 2:03
On screen: the stamp rewrites to 5.2.2, the 5 coral and the 2.2 amber, side by side with a ghost of the 4.2.2 from scene 04. The door behind the letter stays open, a light on inside. The tag on the arrow reads a few more tries, then, after the letter returns full twice more, suppress.
Third, five point two point two. The same full mailbox, but coded as a five. A five says stop. Yet the mailbox is there. It's just full. So most senders don't drop it on the first one. They give it a few more tries, and suppress it only if it stays full. A mailbox that stays full is often an abandoned one.
06 · The fourth one: 5.7.1 · 2:26
On screen: the stamp rewrites to 5.7.1, the 7 lit. A ghost 5.1.1 sits beside it. The remove tag from scene 03 slides toward the arrow, then stops and fades. A new tag lands: read the reason. The words line under the stamp underlines.
Fourth, five point seven point one. Rejected for policy. It looks a lot like five point one point one. Both are fives. But the fix is nothing like it. Five point one point one is about the address. Five point seven point one isn't. So taking the address off fixes nothing. Read the words after it to see whose rule you hit.
07 · What each one tells you to do · 2:49
On screen: chip 3 lights. The four stamps from scenes 03 to 06 in a column, each with its tag, one per click: 5.1.1 → remove (coral) · 4.2.2 → let it retry (amber) · 5.2.2 → a few more tries, then suppress (amber to coral) · 5.7.1 → read the reason (grey). Then the first digits glow together, then the middle digits.
Each one is an instruction. Five point one point one, take it off. Four point two point two, let it retry. Five point two point two, a few more tries, then suppress it if it stays full. Five point seven point one, leave the list alone and read the reason. The first digit says retry or not. The middle one says what next.
08 · Why be this careful · 3:13
On screen: playlist 1's reputation gauge, called back, one notch down as a returned 5.1.1 letter goes out again. Then a small card: reviewmyemails.com/tools/email-headers.
Why be this careful? Because sending again to an address that hard bounced hurts your sender reputation. It tells mailbox providers you're not looking after your list. And if your bounce rate is climbing and you can't tell which codes are behind it, our free Email Header Analyzer helps you read the server's actual reply.
09 · Recap · 3:34
On screen: the four stamps and their tags, the gauge. All three chips lit.
Read it like this. The first digit says retry or stop. The middle one says what kind of problem. Five point one point one, off. Four point two point two, let it retry. Five point two point two, a little more patience. Five point seven point one, the list isn't the problem. Read the second code before you act.
10 · Close · 3:56
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Read the second code before you act, and check the list before it bounces. The check that does it is RME Clean, from Review My Emails. It takes out the five point one point ones before you send. It won't clear a five point seven point one. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is list hygiene automation via bounce mapping?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-020.007.001-rfc-3463-bounce-codes.md
00 · Four little codes (hook)
Almanac ids in this scene: 020.007.001
What are the recommended bounce classification codes?
three numbered chips, the VO's words: 1 how the code is built · 2 the four you'll see most · 3 what each one tells you to do. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept bounce (M-15, M-18), the report as a list of returned letters.
020.007.001 "You're scanning your bounce report and you see codes like 5.1.1 or 4.2.2 next to failed addresses. What do those numbers actually mean, and what are you supposed to do with them?"
H4, H5, split from 00 so each stays under 70 words (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit". 015.001.001 "we'll flag what's safe to send to and what to suppress".
one sentence, 22 words, brand said here and in the close only.
02 · How the code is built
Almanac ids in this scene: 020.007.001, 020.007.002
How the code is built
one bounce log line, mono, most of it grey: bo.unce@coral-cove.invalid · 550 5.1.1 · The email account that you tried to reach does not exist. A lamp lights 550, then 5.1.1. Then a second line with no dotted code, 550 Requested action not taken, and the lamp settles on 550.
one line, two codes lit in order, then a line with only one. Reveals: (1) the line, (2) the three-digit code, (3) the dotted code, (4) the line without it.
the Diagnostic Code slip, as a log line.
020.007.001 "They sit alongside the basic SMTP response codes". 020.007.002 "Not every mail server includes enhanced codes. When they're missing, you fall back to the three-digit SMTP code."
a one-scene callback of playlist 1 video 1 and part 3 video 6 (S6). The standard's name goes in the description (P7), and is only spoken in the hook, because it is the title question (H3).
T2, where it sits and how to read it. The second example line is a demo line on the reserved domain, not a provider's own wording.
03 · The first one: 5.1.1
Almanac ids in this scene: 015.002.026, 020.007.001
The four you'll see most
chip 2 lights. The slip's stamp reads 5.1.1. Behind the letter, the door it came from closes. A coral tag lands on the arrow: remove. On the last line, the report zooms out and a cluster of 5.1.1 rows glows together.
one stamp, one closed door, one tag. Then a cluster of the same stamp. Reveals: (1) the stamp, (2) the door closes, (3) the tag, (4) the cluster.
concept hard-bounce (the door closing for good).
020.007.001 "5.1.1. Bad destination address. The mailbox doesn't exist. This is a hard bounce. Remove the address immediately." 015.002.026 "There's no one there to deliver to. There's no waiting it out." / "If you're seeing a lot of 5.1.1 codes, that's a list hygiene signal. It usually means your list has aged without being cleaned, or you've had a sign-up source bringing in bad addresses."
04 · The second one: 4.2.2
Almanac ids in this scene: 015.003.003, 020.007.001
The four you'll see most
the stamp rewrites to 4.2.2, amber. The letter goes back to the same door and waits. An amber tag on the arrow: let it retry. Then three sends in a row, the same address, each returned 4.2.2, and the tag turns coral: treat as gone.
one stamp, one door, then three returns in a row. Reveals: (1) the stamp, (2) the retry, (3) the tag, (4) the three returns, (5) the tag turns.
concept soft-bounce (the envelope going back to the same door).
020.007.001 "4.2.2. Mailbox full (temporary). The receiving server is saying "try again later." Your sending infrastructure will retry automatically, but if this keeps happening over several days, treat it as a dead address." 015.003.003 "If you see the same address failing with 452 across several campaigns over weeks, that's a signal the account may be abandoned or neglected."
no count and no window (R2, C41). "Send after send" is the answers' "keeps happening" and "across several campaigns", with the days and weeks left out.
05 · The same full mailbox, as a five
Almanac ids in this scene: 015.002.026, 020.007.001
A five that waits
the stamp rewrites to 5.2.2, the 5 coral and the 2.2 amber, side by side with a ghost of the 4.2.2 from scene 04. The door behind the letter stays open, a light on inside. The tag on the arrow reads a few more tries, then, after the letter returns full twice more, suppress.
one condition, two first digits. The coral five over an open, lit door. Reveals: (1) the 5.2.2 stamp beside the ghost 4.2.2, (2) the open door, (3) the tag, (4) the tag turns.
the Diagnostic Code slip. Ghost stamp and lit door: no picture yet.
020.007.001 "5.2.2. Mailbox full (permanent)." / "Treat it like a hard bounce after a few attempts." 015.002.026 "5.2.2 means the mailbox exists, but it's full." / "Because 5.2.2 starts with a 5, it's technically coded as a permanent failure. But in practice, most senders treat it as a soft bounce at first" / "A full mailbox that stays full is often a sign of an abandoned account anyway."
T3, the one twist. "A few" is the answers' own word, no count (R2, V9). C41 is kept out: the script says neither "a real person is there" nor "no recovery expected".
06 · The fourth one: 5.7.1
Almanac ids in this scene: 011.009.012, 020.007.001
The four you'll see most
the stamp rewrites to 5.7.1, the 7 lit. A ghost 5.1.1 sits beside it. The remove tag from scene 03 slides toward the arrow, then stops and fades. A new tag lands: read the reason. The words line under the stamp underlines.
two fives side by side, one tag refused. Reveals: (1) the stamp, (2) the ghost 5.1.1, (3) the remove tag fades, (4) read the reason.
the Diagnostic Code slip. Part 2 video 3's two slips, called back.
020.007.001 "5.7.1. Message rejected for policy reasons." / "One thing to watch: a 5.7.1 is different from a 5.1.1. A 5.1.1 is about the address." / "They both look like permanent failures, but the fix is completely different." 011.009.012 "The bounce text itself is the giveaway."
C26 kept neutral. The answer's "A 5.7.1 is about your reputation or content" and "investigate your sending setup" are not voiced, because 011.009.012 reads the same code as the recipient organisation's own rule. Both answers agree it is not about the address. Part 2 videos 2 and 3 own the rest (S6).
07 · What each one tells you to do
Almanac ids in this scene: 020.007.001
What each one tells you to do
chip 3 lights. The four stamps from scenes 03 to 06 in a column, each with its tag, one per click: 5.1.1 → remove (coral) · 4.2.2 → let it retry (amber) · 5.2.2 → a few more tries, then suppress (amber to coral) · 5.7.1 → read the reason (grey). Then the first digits glow together, then the middle digits.
four stamps, four tags. Reveals: (1) to (4) one row each, (5) the first digits, (6) the middle digits.
the Diagnostic Code slip, four stamps.
020.007.001 "The practical split that matters most is 4.x.x versus 5.x.x. A 4.x.x code is a soft bounce. Your mail server should retry automatically. A 5.x.x code is a hard bounce. Don't retry it." Each row as scenes 03 to 06.
T5, the action.
08 · Why be this careful
Almanac ids in this scene: 020.007.001
What each one tells you to do
playlist 1's reputation gauge, called back, one notch down as a returned 5.1.1 letter goes out again. Then a small card: reviewmyemails.com/tools/email-headers.
one gauge, one notch down. Reveals: (1) the resend, (2) the notch, (3) the card.
concept sender-reputation (the score gauge), email-header.
020.007.001 "Continuing to send to hard-bounce addresses damages your sender reputation and tells mailbox providers you're not managing your list." / "If your bounce rates are climbing and you're not sure which codes are driving it, our free Email Header Analyzer can help you read the actual delivery response from the receiving server."
no bounce-rate number (N6, C4, C16).
09 · Recap
What to remember
the four stamps and their tags, the gauge. All three chips lit.
callbacks only.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 015.002.026
Read the code, then act
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10): it does not fix a policy rejection. Next video named by its Almanac question, "What is “list hygiene automation” via bounce mapping?" (S8). Backed by 015.002.026 "Our list cleaning service is worth a look if that pattern is showing up regularly." Totals: 13 scenes. 690 spoken words (counted 2026-09-30, Q sweep). About 4:09 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V041What is "list hygiene automation" via bounce mapping?
waiting on YTOpen questions for YT
- Registry: a new webhook row, and "no picture yet" for the translation card, the counter dial and the CRM building.
- Tool idea (T7): a suppression-list compare tool, for the PM's idea list.
00 · An afternoon of bounces (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what bounce mapping is · 2 the rules it runs for you · 3 where it stops protecting you. Chips 2 and 3 grey.
We'll go in three steps. What bounce mapping is. The rules it runs for you. And where it stops protecting you.
01 · Brought to you by, woven in · 0:23
On screen: no cut away and no ad break. The stack holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
An afternoon of bounces is an afternoon of dead addresses, and Review My Emails spots them before you ever hit send.
02 · What bounce mapping is · 0:32
On screen: three trays on the desk, labelled one per click: hard (coral) · soft (amber) · block (grey). A letter drops into each. bo.unce@coral-cove.invalid into hard, kai@driftwood-goods.example into soft, and a third letter with 550 5.7.1 into block.
There are three names it files under. Hard, for a permanent failure, like an address that doesn't exist. Soft, for a temporary one, like a full inbox. And block, when the receiving server is refusing your mail on purpose. Once every bounce has a name, the rules can take over.
03 · Rule one: hard · 1:13
On screen: chip 2 lights. The hard tray tips its letter into playlist 2's third verdict pot, and the lid closes. No hand on screen.
Now the rules, and nobody has to click a thing. Rule one. A hard bounce is suppressed on the first one. Sending again to a dead address is never useful, so there's nothing to wait for.
04 · Rule two: soft · 1:27
On screen: Kai's counter is about to hit the dial when a small green spark flies up from an earlier send, an opened tag. The counter freezes, and a grey hold tag lands on the tray.
And there's a pause built in. If that address opened or clicked something recently, many tools hold off before suppressing it. Someone's there, even if the last send bounced. A real reader is worth one more look.
05 · Rule three: block · 2:00
On screen: the block tray. Its letter does not go to the pot. A grey flag pops up on it: look into this. Part 2's block-bounce picture, small, in the corner as a callback.
Rule three. A block bounce usually isn't suppressed at all. It's flagged for someone to look at. Because the problem might be on your side, the way you send, not their address.
06 · What you get · 2:13
On screen: the third pot, called back from playlist 2, filling a little after each send, a small send 1, send 2, send 3 under it. Sally's stack from scene 00 is gone. The clock is still.
What you get is a suppression list that grows by itself, with every campaign you send. No spreadsheet. No afternoon. The addresses that can't take mail stop getting it, and your reputation stops taking those hits. Worth checking which rules your own tool runs, and whether you can change them.
07 · It only protects one tool · 2:32
On screen: the desk from part 3, its lamp lit only on returned letters. Behind it, a long shelf of unsent, unchecked addresses in the dark. One envelope goes through a door marked accepts everything and nothing comes back. Then the checking lamp sweeps the whole shelf at once.
But automation only learns from bounces as they happen. So it can't fix the old addresses you've never checked. And some domains say yes to every address, real or not, so a dead one there usually never bounces at all. For that backlog, a one-time clean is usually the faster fix.
08 · Recap · 3:28
On screen: the card, the three trays, the pot, the dial, the flag, the pipe. All three chips lit.
The whole loop, then. Bounce mapping turns a raw code into a name. Hard, soft or block. Then the rules run. Hard, out on the first one. Soft, out after a run, and your tool sets the run. Block, held for a look. And make sure the suppression reaches your CRM too.
09 · Close · 3:48
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Let the rules run, sync them everywhere, and clean the backlog once. At Review My Emails we clear the dead ones out of that backlog in one pass. A clean won't sync your CRM for you. Checking signups as they come in? That's our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how do I troubleshoot block bounces?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.004.011-bounce-mapping-automation.md
00 · An afternoon of bounces (hook)
Almanac ids in this scene: 015.004.011
What is list hygiene automation via bounce mapping?
three numbered chips, the VO's words: 1 what bounce mapping is · 2 the rules it runs for you · 3 where it stops protecting you. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept bounce (M-15, M-18).
015.004.011 "If you've ever spent an afternoon manually removing bounced addresses from a list, you already understand why list hygiene automation exists."
H4, H5, split from 00 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The stack holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit". 015.001.001 "we'll flag what's safe to send to and what to suppress".
one sentence, 21 words, brand said here and in the close only.
02 · What bounce mapping is
Almanac ids in this scene: 015.004.011
What bounce mapping is
three trays on the desk, labelled one per click: hard (coral) · soft (amber) · block (grey). A letter drops into each. bo.unce@coral-cove.invalid into hard, kai@driftwood-goods.example into soft, and a third letter with 550 5.7.1 into block.
a count of three trays, one letter each. Reveals: (1) to (3) one tray and its letter each.
the desk and its trays.
015.004.011 "classifies each failure into a category (hard, soft, block)" / "Hard bounces (permanent failures, like a non-existent address)" / "Soft bounces (temporary failures, like a full inbox)" / "Block bounces (where the receiving server is actively rejecting your mail)".
"email marketing tool", never "ESP" (V5). The desk and its four steps are a callback (S6).
03 · Rule one: hard
Almanac ids in this scene: 015.004.011
The rules it runs for you
chip 2 lights. The hard tray tips its letter into playlist 2's third verdict pot, and the lid closes. No hand on screen.
one bounce, one lid. Reveals: (1) the tray tips, (2) the lid closes.
concept suppression-list (the third pot, lid closing).
015.004.011 "Hard bounces (permanent failures, like a non-existent address) trigger immediate suppression. Most ESPs do this after the very first hard bounce, because re-sending to a dead address is never useful."
playlist 1 video 3 owns "hard is once" (S6). One line.
04 · Rule two: soft
Almanac ids in this scene: 015.004.007, 015.004.011
The rules it runs for you
Kai's counter is about to hit the dial when a small green spark flies up from an earlier send, an opened tag. The counter freezes, and a grey hold tag lands on the tray.
the counter stopped one short, by one green spark. Reveals: (1) the counter nears the dial, (2) the spark, (3) the hold.
the desk. The engagement spark: concept engagement-signal.
015.004.007 "And if a subscriber has opened or clicked recently, that recent engagement acts as a reason to pause before suppressing. (It's a real signal that someone is there, even if the last send bounced.)"
R6 (YT, 2026-09-29): no fixed count. C9 kept out (015.004.011 "three to five", 015.004.007 "3 and 7").
"many tools" for the answer's plain statement of how tools decide, not "all" (V12).
05 · Rule three: block
Almanac ids in this scene: 015.004.011
The rules it runs for you
the block tray. Its letter does not go to the pot. A grey flag pops up on it: look into this. Part 2's block-bounce picture, small, in the corner as a callback.
one letter that does not move, one flag. Reveals: (1) the letter stays, (2) the flag.
concept block-bounce (gloss tier, no picture yet), called back.
015.004.011 "Block bounces (where the receiving server is actively rejecting your mail) usually get flagged for investigation rather than instant suppression, since the problem might be on your sending side, not the recipient's address."
part 2 video 2 owns "suppressing a block fixes nothing" (S6). "Earlier in the series" is a playlist callback, not a production word (S7). No blocklist named.
06 · What you get
Almanac ids in this scene: 015.004.007, 015.004.011
The rules it runs for you
the third pot, called back from playlist 2, filling a little after each send, a small send 1, send 2, send 3 under it. Sally's stack from scene 00 is gone. The clock is still.
one pot filling, one stack gone. Reveals: (1) to (3) one send each, (2) the stack gone.
concept suppression-list.
015.004.011 "The result is a suppression list that grows automatically with every campaign you send. No spreadsheet, no manual review. The addresses that can't receive mail stop being sent to, and your sender reputation stops taking hits from those repeated failures." 015.004.007 "some let you tune them for your list."
07 · It only protects one tool
Almanac ids in this scene: 004.007.007, 015.004.011, 021.002.013
What it never catches
the desk from part 3, its lamp lit only on returned letters. Behind it, a long shelf of unsent, unchecked addresses in the dark. One envelope goes through a door marked accepts everything and nothing comes back. Then the checking lamp sweeps the whole shelf at once.
a lit desk, a dark shelf. Reveals: (1) the desk, (2) the dark shelf, (3) the door with nothing back, (4) the lamp sweeps.
concept catch-all, part 3's desk.
015.004.011 "If your list has a lot of historical addresses you've never validated, automation alone won't fix the backlog. It only catches future bounces as they happen. For the existing problem, a one-time list clean is usually the faster fix." 021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T2 where, T5 the action. The setup detail (endpoints, payloads) goes in the description (P7).
R15 (YT, 2026-09-29), with T6. "Usually" keeps inside C17.
part 3 video 4 owned "it only ever looks backwards" as its twist. Here it is the pitch's setup, one line, with the old picture (S6).
moved before the recap as 07c (Q3). The only catch-all idea in Bounces part 4 (V040 and V042 dropped theirs). "That's what we do" cut from its last line (Q1).
08 · Recap
What to remember
the card, the three trays, the pot, the dial, the flag, the pipe. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Let the rules run
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the API, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). Next video named by its Almanac question, "How do I troubleshoot block bounces?" (S8). Totals: 15 scenes. 659 spoken words (counted 2026-09-30, Q sweep). About 3:58 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V042How do I troubleshoot block bounces?
waiting on YTOpen questions for YT
- Registry: "no picture yet" for the coral third-party link and the side door.
- Tool idea (T7): no free tool checks every link in an email against blocklists.
00 · Blocked, and the next send is tomorrow (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 read what the block says · 2 check the usual suspects · 3 follow the provider's own way back in. Chips 2 and 3 grey.
Three steps answer it. Read what the block says. Check the usual suspects. And follow the provider's own way back in.
01 · Brought to you by, woven in · 0:23
On screen: no cut away and no ad break. The gate holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A block is about how you send, not who you send to, but Review My Emails still checks every address before you send.
02 · Step one: read what it says · 0:32
On screen: one log line, mono, most of it grey: 550 · Message blocked. Visit postmaster.mailbox.example/sender-help. A lamp moves across it left to right, lighting 550, then Message blocked, then settling on the link.
Here's what that looks like. The code first, like five fifty. Then the reason, in the provider's own words. Then, near the end, a web address. It's easy to skim past. Don't. It's usually the provider telling you exactly where to start.
03 · Step two: the blocklist · 1:09
On screen: chip 2 lights. The second clipboard line: blocklist. A small card: reviewmyemails.com/tools/blacklist-checker, two rows checked, IP and domain. A coral listed mark on one fades to a softer amber fixable.
Step two, the usual suspects. First, a blocklist. If the message names one, go straight to that list's removal process. If it doesn't, run your sending IP and your domain through our free blocklist checker. And don't panic. Being listed doesn't make you a bad sender. It means something flagged your reputation. And that's usually fixable.
04 · Step two: your authentication · 1:30
On screen: the third clipboard line: authentication. Three small record cards, SPF, DKIM, DMARC, each ticked green one per click. Then a card: reviewmyemails.com/tools/spf-checker.
Next suspect, your authentication, the records that prove the mail is yours. A surprising number of blocks trace back to SPF, DKIM or DMARC that's broken or not lined up. Check that every server you send from is in your SPF record, that DKIM is signing correctly, and that DMARC matches your SPF and DKIM domains. Our free SPF checker flags the obvious gaps.
05 · Someone else's link · 1:54
On screen: the fourth clipboard line: every link. Sally's email opens. Her own links glow green. One link near the bottom, to megaphone.invalid, turns coral. The doorman taps it. Beside the gate, Sally's IP and domain cards stay green, and the gate stays shut.
Check every link in the email. Not just your own. Say you link to another company's site, and that site's domain is on a blocklist. Your mail can be blocked for it. Even from a clean IP, with a clean domain. One link you didn't think twice about, and the whole send pays.
06 · Step two: the provider's own view · 2:14
On screen: the fifth clipboard line: their view. Behind the gate, a window opens onto a small panel with two gauges, domain and IP, playlist 1's reputation gauge, twice. Beside it, Sally's own tool dashboard, where those gauges are missing.
Last suspect, your reputation, seen from their side. The big mailbox providers run free sender dashboards. They show how that provider rates your domain and your IP. That's data your email marketing tool's dashboard won't show you. So if the block came from one of them, look there.
07 · Step three: the way back in · 2:32
On screen: chip 3 lights. The last clipboard line: their way back in. The link from scene 02b becomes a door in the wall beside the gate, marked request review. A second envelope tries to squeeze round the side of the gate and bounces off. Sally walks to the door instead.
Step three. Follow the way back in. Most block messages from the big providers come with a fix-it link or a reference code. Follow it. It isn't optional. They run formal ways to ask for the block to be lifted. Try to send around a block instead, and you'll just keep getting blocked.
08 · Read the pattern · 2:53
On screen: the slip from scene 02 slides onto a small card, reviewmyemails.com/tools/email-headers, then a second card, reviewmyemails.com/sos.
Still staring at a message that makes no sense? Drop it into our free Email Header Analyzer. Or bring it to our free SOS hotline. Block bounces are fixable. You just need to know what you're dealing with first.
09 · Recap · 3:25
On screen: the clipboard, every line ticked green. The gate opens a crack. All three chips lit.
In order, then. Read the rejection, and go to the link first. Check the blocklist, your authentication, every link in the email, and the provider's own dashboard. Then follow their way back in, never around. One provider blocking you? Read their message. Several? Look at your reputation.
10 · Close · 3:43
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 3, no subscribe ask.
Work the block in order, and keep the list honest before you send. Keeping it honest is our side of it, here at Review My Emails. Lifting the block is yours. Stuck on a message? Our free SOS hotline is there. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is typo or malformed address capture?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.005.005-troubleshoot-block-bounces.md
00 · Blocked, and the next send is tomorrow (hook)
Almanac ids in this scene: 015.005.005
How do I troubleshoot block bounces?
three numbered chips, the VO's words: 1 read what the block says · 2 check the usual suspects · 3 follow the provider's own way back in. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept block-bounce (gloss tier), part 2's doorman.
015.005.005 "You sent a campaign, checked your stats, and there it is: a block bounce. Your email didn't just fail to deliver. A receiving server actively refused it." / "The bounce message your ESP logs is your starting point, not a dead end."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 015.005.005
no cut away and no ad break. The gate holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.005.005 "Something about your sending reputation, your content, or your infrastructure triggered a rejection." 015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit". 015.001.001 "we'll flag what's safe to send to and what to suppress".
does not say a clean fixes the block (hard content rules).
one sentence, 23 words, brand said here and in the close only.
02 · Step one: read what it says
Almanac ids in this scene: 015.005.005
Read what the block says
one log line, mono, most of it grey: 550 · Message blocked. Visit postmaster.mailbox.example/sender-help. A lamp moves across it left to right, lighting 550, then Message blocked, then settling on the link.
one line, three parts lit in order. Reveals: (1) the line, (2) to (4) one part each.
the slip as a log line. The link is on a reserved domain (V7), never a real provider's page.
015.005.005 "often a URL pointing to the receiving provider's support page" / "Most block messages from major providers include a remediation URL or a reference code."
"email marketing tool", never "ESP" (V5). Playlist 1 video 1 owns how to read the code (S6).
T2, where it sits. "Usually" is kept from the answer's "usually contain" (V12).
03 · Step two: the blocklist
Almanac ids in this scene: 015.005.005
Check the usual suspects
chip 2 lights. The second clipboard line: blocklist. A small card: reviewmyemails.com/tools/blacklist-checker, two rows checked, IP and domain. A coral listed mark on one fades to a softer amber fixable.
two things checked, IP and domain. Reveals: (1) the line, (2) the card, (3) the two rows, (4) the mark softens.
concept blocklist (gloss tier). Part 2 video 2 glossed it, so the gloss card is a callback.
015.005.005 "If the error message mentions a blocklist by name, go straight to that list's removal process. If it doesn't name one, run your sending IP and your domain through a blocklist checker." / "Being listed doesn't mean you're a bad sender. It means something flagged your reputation, and that something is usually fixable. You can use our free blocklist checker to see where you stand right now."
no blocklist is named (the answer names two). The URL is the live tool's own path.
04 · Step two: your authentication
Almanac ids in this scene: 015.005.005
Check the usual suspects
the third clipboard line: authentication. Three small record cards, SPF, DKIM, DMARC, each ticked green one per click. Then a card: reviewmyemails.com/tools/spf-checker.
three records, three ticks. Reveals: (1) the line, (2) to (4) one tick each, (5) the card.
concepts spf, dkim, dmarc, alignment. Part 2 video 2's three record cards, called back.
015.005.005 "A surprising number of block bounces trace back to broken or misconfigured SPF, DKIM, or DMARC." / "Check that all your sending IPs are included in your SPF record, that your DKIM signature is signing correctly, and that DMARC is set up to match your SPF and DKIM domains. Our free SPF checker will flag any obvious gaps."
no gloss cards (Q6): the VO says what the three records do in one plain line, the acronyms sit on the three cards. "Every server you send from" for "all your sending IPs", plainer, same meaning.
05 · Someone else's link
Almanac ids in this scene: 015.005.005
Check the usual suspects
the fourth clipboard line: every link. Sally's email opens. Her own links glow green. One link near the bottom, to megaphone.invalid, turns coral. The doorman taps it. Beside the gate, Sally's IP and domain cards stay green, and the gate stays shut.
many green links, one coral one, and a shut gate. Reveals: (1) the email, (2) the green links, (3) the coral link, (4) the green IP and domain beside a shut gate.
the doorman and the email. The coral link: no picture yet.
015.005.005 "So some block bounces are triggered by content filters rather than IP or domain reputation." / "URLs inside your email that link to a blocklisted domain can all cause a rejection. Check every link you sent. If a third-party URL in your campaign is on a blocklist, even with a clean IP you'll get blocked."
T3, the one twist. "Can be blocked" is softer than the answer's "you'll get blocked", allowed (V12 only forbids tighter). The answer's "Spam-heavy phrases, suspicious formatting" are not voiced (C25).
06 · Step two: the provider's own view
Almanac ids in this scene: 015.005.005
Check the usual suspects
the fifth clipboard line: their view. Behind the gate, a window opens onto a small panel with two gauges, domain and IP, playlist 1's reputation gauge, twice. Beside it, Sally's own tool dashboard, where those gauges are missing.
two gauges on their side, none on hers. Reveals: (1) the line, (2) the window, (3) the two gauges, (4) the empty space on her dashboard.
concept sender-reputation (the score gauge). Concepts google-postmaster and microsoft-snds are in the registry, their names go in the description only.
015.005.005 "Check Google Postmaster Tools for your domain and IP reputation scores." / "These tools are free and give you data that your ESP dashboard won't show you."
no provider named in the VO. The answer's "trap-hit history" is not voiced (no spam-trap claims on marketing surfaces).
07 · Step three: the way back in
Almanac ids in this scene: 015.005.005
The way back in
chip 3 lights. The last clipboard line: their way back in. The link from scene 02b becomes a door in the wall beside the gate, marked request review. A second envelope tries to squeeze round the side of the gate and bounces off. Sally walks to the door instead.
one proper door, one side route that fails. Reveals: (1) the door, (2) the side route fails, (3) Sally at the door.
the doorman and gate. The side door: no picture yet. Concept delisting (gloss tier).
015.005.005 "Most block messages from major providers include a remediation URL or a reference code. Follow that path. It's not optional." / "Google, Microsoft, and Yahoo all have postmaster feedback loops and formal delisting processes. If you try to send around a block without going through remediation, you'll just keep getting blocked."
no provider named in the VO. The answer's "will just keep" stays "will", not tightened.
08 · Read the pattern
Almanac ids in this scene: 015.005.005
The way back in
the slip from scene 02 slides onto a small card, reviewmyemails.com/tools/email-headers, then a second card, reviewmyemails.com/sos.
one slip, two cards. Reveals: (1) the analyzer card, (2) the SOS card.
concept email-header.
015.005.005 "If you're staring at an error message that doesn't make sense, drop it into our Email Header Analyzer or bring it to the SOS hotline. Block bounces are fixable. You just need to know what you're actually dealing with first."
part 2 video 3 owns this for policy bounces (S6), one scene here because the answer adds the reputation reasons. No complaint-rate number (N6).
T7, our tools.
09 · Recap
What to remember
the clipboard, every line ticked green. The gate opens a crack. All three chips lit.
callbacks only. The clipboard full, one gate opening.
callbacks only (S5).
10 · Close
Fix the block, then keep it honest
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). Last video of the series, the next video is the first of "Keeping a list healthy, part 3", named by its Almanac question, "What is typo or malformed address capture?" (S8). Totals: 14 scenes. 647 spoken words (counted 2026-09-30, Q sweep). About 3:54 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V043What is typo or malformed address capture?
waiting on YTOpen questions for YT
- C42 (new): what typo capture means.
- Demo names: two derived forms with no ending, for the library.
- Registry: a signup-form picture, and "no picture yet" for typosquatting.
- Tool idea (T7): a free signup-form checker (paste your form's URL, we say whether it checks addresses).
00 · One letter wrong (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the typos that get in · 2 why they cost you · 3 how to catch them at the form. Chips 2 and 3 grey.
Three things answer it. The typos that get in. Why they cost you. And how to catch them at the form, before they're on your list.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The form holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
One wrong letter at signup makes an address that will never take your mail, and Review My Emails finds those before you send.
02 · The three shapes · 0:40
On screen: chip 1 lights. The one field holds still. The address rewrites itself, one shape per click, the wrong part lit coral: wren@mailbx.invalid (dropped letter) · wren@mailboxexample (no dot) · wren@mailbox (no ending). Under each, faint and green, the right one: wren@mailbox.example.
What do the typos look like? Three shapes, mostly. Letters swapped or dropped in the domain, the part after the at sign. A missing dot before the ending, so two words run together. Or no ending at all. Each one looks almost right. That's the problem. Nobody's eye stops on it.
03 · Why they cost you · 1:06
On screen: chip 2 lights. Sally's envelope to wren@mailbx.invalid leaves, comes back coral, and a small tally lands not on Wren's row but on Sally's own name tag, send-more.example.
And here's why they cost you. When you send, your email marketing tool still tries to deliver. The receiving side can't find the address. That's a hard bounce. And it's recorded against your sending domain. So every typo that gets in becomes a bounce with your name on it.
04 · The easy ones · 1:28
On screen: the returned letter drops into playlist 2's third verdict pot, and the lid closes.
Some typos end right there. The typo domain doesn't exist. The bounce is immediate, and you suppress the address. Annoying. Simple enough.
05 · The twist: a typo domain someone owns · 1:43
On screen: a second envelope goes out to a lookalike domain, drawn only as mailbx with a faint real building behind it, lights on. It does not come back. Then a small blocklist board, and Sally's name tag slides onto it after the third send.
But some typo domains do exist. Someone registered them on purpose, spelled almost like a big mailbox provider, to catch people's slips. That's called typosquatting. And if you keep sending to one of those domains, it can get you listed on a blocklist.
06 · Catch it at the form · 2:07
On screen: under the field, a small line in the brand's body type: Did you mean wren@mailbox.example? The person taps it, the field corrects, the edge turns green, and the button lights.
Here's where it sits. Right under the email field, before the button. The person types, and a small line appears. Did you mean wren at mailbox dot example? One tap, and the right address goes in instead.
07 · The second line · 2:50
On screen: after the form, a confirmation envelope goes out to wren@mailbx.invalid and never arrives. The address fades before reaching the list. A small pair of scales: fewer signups on one side, fewer bad addresses on the other.
There's a second line too. Double opt-in. A mistyped address can't confirm an email it never receives, so it never makes the list. The cost? Fewer people finish signing up. The benefit? A list with a lot fewer bad addresses.
08 · Try your own form · 3:12
On screen: the form fades, and behind it Sally's list scrolls, a few rows glowing coral, mailbx among them. One envelope goes through a door marked accepts everything, and nothing comes back. Then the checking desk lamp sweeps the list.
What about the typos already on your list? No form can catch those. They got in before anything was checking. And on a domain whose server accepts any name at all, a typo usually never bounces. A clean finds both kinds.
09 · Recap · 3:49
On screen: the three shapes, the tally on Sally's tag, the lookalike, the lamp, the suggestion, the envelope that never lands. All three chips lit.
Here's the whole of it. Typos take three shapes, and each looks almost right. Every one that gets in becomes a bounce against your domain. Some typo domains are owned on purpose. Clean the ones already in. Catch new ones at the form, with a real-time check and a did you mean. And let double opt-in be your second line.
10 · Close · 4:08
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Check at the door, and clean what's already inside. Your form is yours to fix. Cleaning takes out the addresses that were never going to work. Want the check at the form? That's our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a parked domain?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.002.014-typo-malformed-address-capture.md
00 · One letter wrong (hook)
Almanac ids in this scene: 005.002.014
What is typo or malformed address capture?
three numbered chips, the VO's words: 1 the typos that get in · 2 why they cost you · 3 how to catch them at the form. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the signup form (no registry row, a form is a plain picture). Concept bounce.
005.002.014 "Typo capture happens when someone makes a small mistake typing their email address at signup and your form accepts it without checking whether the address is real." / "the signup-time process of catching mistyped email addresses before they enter your list".
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.002.014
no cut away and no ad break. The form holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.002.014 "our done-for-you Review My Emails list cleaning identifies malformed and typo addresses in existing lists."
02 · The three shapes
Almanac ids in this scene: 005.002.014
The typos that get in
chip 1 lights. The one field holds still. The address rewrites itself, one shape per click, the wrong part lit coral: wren@mailbx.invalid (dropped letter) · wren@mailboxexample (no dot) · wren@mailbox (no ending). Under each, faint and green, the right one: wren@mailbox.example.
one field, three wrong shapes against one right one. Reveals: (1) to (3) one shape each.
the form. Addresses are the library's typo domain and two forms with no ending (V7).
005.002.014 "The most common patterns: transposing characters in the domain (gmal.com, yahooo.com, outlok.com), missing the period before a TLD (captain@tidalmailio instead of captain@tidalmail.example), or forgetting the top-level domain entirely (captain@tidalmail)."
the answer's real-provider typos are never shown (demo names rule 2). "Ending" for TLD (P6, no new word needed).
03 · Why they cost you
Almanac ids in this scene: 005.002.014
Why they cost you
chip 2 lights. Sally's envelope to wren@mailbx.invalid leaves, comes back coral, and a small tally lands not on Wren's row but on Sally's own name tag, send-more.example.
one bounce, one mark on the sender. Reveals: (1) the envelope out, (2) back coral, (3) the mark on Sally's tag.
concept hard-bounce. Bounces part 3 video 1 owns typos as a hard-bounce cause (S6).
005.002.014 "In each case, your ESP will attempt delivery, receive a hard bounce, and record it against your sending domain."
"email marketing tool", never "ESP" (V5).
04 · The easy ones
Almanac ids in this scene: 005.002.014
Why they cost you
the returned letter drops into playlist 2's third verdict pot, and the lid closes.
one letter, one lid. Reveals: (1) the drop, (2) the lid.
concept suppression-list.
005.002.014 "Some of these typo domains are benign: they simply do not exist, the bounce is immediate, and you can suppress the address."
"some typos" keeps the answer's "some" with no share (V12). The first draft said "most of the time", which the second pass cut as tighter than the Almanac.
05 · The twist: a typo domain someone owns
Almanac ids in this scene: 005.002.014
Why they cost you
a second envelope goes out to a lookalike domain, drawn only as mailbx with a faint real building behind it, lights on. It does not come back. Then a small blocklist board, and Sally's name tag slides onto it after the third send.
one lookalike domain, three sends, one listing. Reveals: (1) the lookalike, (2) the lights on, (3) three sends, (4) the listing.
concept typosquatting (gloss tier). Gloss card: typosquatting · registering a domain that looks almost like a real one, so a reader does not notice. (the registry's own gloss).
005.002.014 "Others are more problematic. Typosquatting domains like gmal.com are registered specifically to catch common Gmail typos." / "Repeatedly sending to a typosquatting domain can trigger a blocklist listing."
the answer's next line about who monitors these domains is not voiced (no spam-trap claims on marketing surfaces). No provider or real domain is named or shown. "Can" kept from the answer (V12).
06 · Catch it at the form
Almanac ids in this scene: 005.002.014
How to catch them at the form
under the field, a small line in the brand's body type: Did you mean wren@mailbox.example? The person taps it, the field corrects, the edge turns green, and the button lights.
one suggestion, one tap, one green edge. Reveals: (1) the suggestion, (2) the tap, (3) green.
the form.
005.002.014 "Some tools offer a "did you mean?" suggestion for common domain typos: "Did you mean captain@gmail.example?""
T2, where it sits and what the viewer sees. The set-up detail goes in the description (P7).
07 · The second line
Almanac ids in this scene: 005.002.014
How to catch them at the form
after the form, a confirmation envelope goes out to wren@mailbx.invalid and never arrives. The address fades before reaching the list. A small pair of scales: fewer signups on one side, fewer bad addresses on the other.
one envelope that never lands, one pair of scales. Reveals: (1) the envelope, (2) the fade, (3) the scales.
concept double-opt-in (gloss tier), a callback from myths video 4 (S6).
005.002.014 "Double opt-in is the second line of defense. A mistyped address cannot confirm the opt-in email it never receives. The cost is a lower signup completion rate. The benefit is a list with meaningfully fewer bad addresses."
no non-confirmation percentage (C21). Myths video 4 owns the rest of double opt-in.
08 · Try your own form
Almanac ids in this scene: 005.002.014, 021.002.013
The ones already in
the form fades, and behind it Sally's list scrolls, a few rows glowing coral, mailbx among them. One envelope goes through a door marked accepts everything, and nothing comes back. Then the checking desk lamp sweeps the list.
a list with a few coral rows, one door with nothing back. Reveals: (1) the list, (2) the coral rows, (3) the door, (4) the lamp.
concept catch-all, the checking desk.
005.002.014 "our done-for-you Review My Emails list cleaning identifies malformed and typo addresses in existing lists." 021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. A test on the viewer's own form, from the answer's own definition.
Q3: moved before the recap. Q2: a list topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
R15 (YT, 2026-09-29), with T6. "Usually" keeps inside C17.
09 · Recap
What to remember
the three shapes, the tally on Sally's tag, the lookalike, the lamp, the suggestion, the envelope that never lands. All three chips lit.
callbacks only.
callbacks only (S5).
10 · Close
Check at the door
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the API, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). Next video named by its Almanac question, "What is a parked domain?" (S8). Totals: 15 scenes, 600 spoken words, about 3:40 of speech and about 4:35 with scene breaks and reveals (counted in Step 4). Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V044What is a parked domain?
waiting on YTOpen questions for YT
- Next-video title: keep or drop "(Revisiting from List Hygiene)" when the close names video 3.
- Registry: "no picture yet" for the slot through the floor and the inspection card.
- Tool idea (T7): a free "where does this domain's mail go?" lookup (MX host, age, parked page).
00 · Deliverable, and silent (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what a parked domain is · 2 how it quietly swallows your mail · 3 how to spot one. Chips 2 and 3 grey.
Three things answer it. What a parked domain is. How it quietly swallows your mail. And how to spot one.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
An address that looks deliverable and isn't is exactly what Review My Emails looks for, before you ever send to it.
02 · What a parked domain is · 0:37
On screen: a small coin drops from the ad page into the owner's hand. The shop's mail slot, meanwhile, gathers dust.
Why would anyone leave a domain like that? Because the ad page pays. The owner gets a small cut of the click money. So they have no reason to care about email at all.
03 · Setup one: no mail server · 1:18
On screen: chip 2 lights. The shop's mail slot is bricked up, as in playlist 2. An envelope bounces off it, coral. A checking lamp beside it flags the address before the send.
What happens to your mail? That depends on how the domain is set up. The simplest one has no mail server at all. No MX record. Your email bounces hard. That's the easy one, because a validator catches it.
04 · The twist: a slot that takes everything · 1:37
On screen: the brick slides out of the slot and the slot widens. An envelope goes in, and a checking lamp outside gets a green yes back. Then the camera drops below the floor: the envelope falls straight through into the dark.
Some parked domains do have a mail server, though. The parking service's own. It accepts every address you send to, real or invented. Then it drops the message. So when a validator asks, the server says yes. The report says deliverable. And the mail goes nowhere.
05 · Why the silence hurts · 2:04
On screen: Sally's list, one small block of rows greyed at zero opens. Playlist 1's reputation gauge drifts down a notch. Two identical grey blocks side by side, one labelled nobody there, the other not interested, and the gauge can't tell them apart.
Why does that hurt? You send. The mail disappears. Your opens drop, because there's nobody there to open. And mailbox providers watch engagement closely. To them, a chunk of your list that never opens looks just like a chunk that doesn't want your mail.
06 · How to spot one, part one · 2:28
On screen: the inspection card grows two lines: a made-up name → yes · opens, ever → none. Both tick amber. The row ossie@kelp-street.example turns from green deliverable to amber parked.
Two more signs. Does the server say yes to any made-up name you try? That's a catch-all. A real mailbox provider says no. And if you've sent there before, has anyone ever opened or clicked? Never, across several sends, is worth acting on.
07 · What to do · 3:17
On screen: Sally's bounce report, clean and empty. Beside it, the silent open column. Then the checking desk lamp sweeps the list and one row gets an amber parked domain tag.
Your bounce report won't help here. These never bounce, so it never shows them. You only see the silence. When we clean a list, we tag parked-domain addresses, so you can suppress them before you send.
08 · Recap · 3:56
On screen: the shop, the coin, the bricked slot, the slot through the floor, the inspection card, the pot. All three chips lit.
In short. A parked domain is owned and unused. With no mail server, it bounces, and a validator catches it. With a parking service's catch-all, it says yes to everything and drops the mail. Spot it by where its mail goes, its age, its website, and silence. Then suppress it.
09 · Close · 4:15
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Look behind the yes, and check the list before you send. An empty domain will never read your mail. Cleaning takes those addresses out. Want the parked ones tagged for you? That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is an email sunset policy?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.008.002-what-is-a-parked-domain.md
00 · Deliverable, and silent (hook)
Almanac ids in this scene: 005.008.002
What is a parked domain?
three numbered chips, the VO's words: 1 what a parked domain is · 2 how it quietly swallows your mail · 3 how to spot one. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept list-cleaning's report row.
005.008.002 "A parked domain is a registered domain that nobody is actually using for real mail or a real site." / "Some of these accept every address as a catch-all, so validators mark them deliverable while the mail disappears."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.008.002
no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.008.002 "At Review My Emails we tag parked-domain addresses in the report so you can suppress them before sending".
02 · What a parked domain is
Almanac ids in this scene: 005.008.002
What a parked domain is
a small coin drops from the ad page into the owner's hand. The shop's mail slot, meanwhile, gathers dust.
one coin in, one slot ignored. Reveals: (1) the coin, (2) the dusty slot.
the shop.
005.008.002 "The domain owner gets a small cut of click revenue from the ad page. They have no reason to care about email."
"earlier in the playlist" is a callback to playlist 2 video 4 (S6, not a production word). No parking company or registrar named.
T1, the why behind the thing.
03 · Setup one: no mail server
Almanac ids in this scene: 005.008.002
How it quietly swallows your mail
chip 2 lights. The shop's mail slot is bricked up, as in playlist 2. An envelope bounces off it, coral. A checking lamp beside it flags the address before the send.
one bricked slot, one bounce, one flag. Reveals: (1) the bricked slot, (2) the bounce, (3) the lamp's flag.
concept dead-domain (M-13), called back. mx-record is a callback from playlist 1 video 5.
005.008.002 "No MX record at all. The domain has web DNS but no mail server. Mail bounces hard. This is the cleanest case because validators catch it."
playlist 2 video 4 owns this case (S6). "That depends on how the domain is set up" keeps the answer's "Three configurations are common" without voicing a count, because the third is held back (see Step 3).
04 · The twist: a slot that takes everything
Almanac ids in this scene: 005.008.002
How it quietly swallows your mail
the brick slides out of the slot and the slot widens. An envelope goes in, and a checking lamp outside gets a green yes back. Then the camera drops below the floor: the envelope falls straight through into the dark.
one green yes, one envelope through the floor. Reveals: (1) the slot opens, (2) the green yes, (3) the fall.
concept catch-all, called back from myths video 1. The slot through the floor: no picture yet.
005.008.002 "MX pointing at a parking provider's catch-all. Every address on the domain accepts mail at the SMTP layer, then the message is dropped or routed to a black hole." / "your validator sees a 250 OK response and labels the address deliverable when it is not."
T3, the one twist. "Some" keeps the answer's In short "Some of these" (V12).
05 · Why the silence hurts
Almanac ids in this scene: 005.008.002
How it quietly swallows your mail
Sally's list, one small block of rows greyed at zero opens. Playlist 1's reputation gauge drifts down a notch. Two identical grey blocks side by side, one labelled nobody there, the other not interested, and the gauge can't tell them apart.
two identical grey blocks, one gauge. Reveals: (1) the grey block, (2) the gauge drifts, (3) the two blocks side by side.
concept sender-reputation, engagement-signal.
005.008.002 "You send. The mail disappears. Your open rate craters because nobody is opening anything on that domain. Mailbox providers like Gmail and Microsoft watch engagement signals closely" / "a chunk of your list that never opens looks identical to a chunk of your list that hates you."
no provider named. "Doesn't want your mail" for "hates you", gentler, same meaning.
06 · How to spot one, part one
Almanac ids in this scene: 005.008.002
How to spot one
the inspection card grows two lines: a made-up name → yes · opens, ever → none. Both tick amber. The row ossie@kelp-street.example turns from green deliverable to amber parked.
five checks, all amber, one row changes colour. Reveals: (1) and (2) one check each, (3) the row changes.
the inspection card.
005.008.002 "If the server accepts every random local-part you throw at it, that is a catch-all. A real mailbox provider rejects" a random address. / "If you have ever sent to the address before and it has never opened or clicked across multiple campaigns, that is a silent hygiene issue worth acting on."
no host or company named. The answer's day count is not voiced ("only recently"), and the terminal command goes in the description (P7).
07 · What to do
Almanac ids in this scene: 005.008.002
The one you never see
Sally's bounce report, clean and empty. Beside it, the silent open column. Then the checking desk lamp sweeps the list and one row gets an amber parked domain tag.
an empty bounce report beside a silent column, then one tag. Reveals: (1) the empty report, (2) the silent column, (3) the tag.
the checking desk, concept list-cleaning.
005.008.002 "Every address on the domain accepts mail at the SMTP layer, then the message is dropped" / "At Review My Emails we tag parked-domain addresses in the report so you can suppress them before sending instead of finding out the hard way through a dead engagement column."
T5, the action.
R15 (YT, 2026-09-29), with T6. Backed by this answer's own catch-all line.
Q3: moved before the recap. Q2: a list topic, the pivot is this topic's own blind spot.
08 · Recap
What to remember
the shop, the coin, the bricked slot, the slot through the floor, the inspection card, the pot. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Look behind the yes
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). Next video named by its Almanac question, "What is an email sunset policy? (Revisiting from List Hygiene)" (S8), with the bracketed note left unspoken (flagged for the PM below). Totals: 14 scenes, 600 spoken words, about 3:46 of speech and about 4:40 with scene breaks and reveals (counted in Step 4). Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V045What is an email sunset policy? (Revisiting from List Hygiene)
waiting on YTOpen questions for YT
- C43 (new): how many inactive subscribers come back.
- Title: drop "(Revisiting from List Hygiene)" from the video title, or keep it.
- Registry: "no picture yet" for the rule card, the window bars, the seasons strip and the dashboard arrows.
00 · Silent, and still sent to (hook) · 0:00
On screen: three numbered chips: 1 what a sunset policy is · 2 why the silent ones cost you · 3 how to set yours. Chips 2 and 3 grey.
Three things answer it. What a sunset policy is. Why the silent ones cost you. And how to set yours.
01 · Brought to you by, woven in · 0:30
On screen: no cut away and no ad break. The bed holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
At Review My Emails, we sort the quiet ones who drifted away from the addresses that never worked at all.
02 · What a sunset policy is · 0:40
On screen: chip 1 lights. A small rule card pinned at the edge of the bed: silent for a set window → win-back → suppress. The grey block gets one last pass of the can, a single drop. Then the can skips it. The plants stay in the soil.
What is it? A written rule. After a set window with no opens, clicks or replies, a subscriber gets one last try, a win-back. Still nothing? They're suppressed from your regular sends. Not deleted. They stay in your database. You just stop sending campaigns they're ignoring. You stop watering the row. You don't dig it up.
03 · Why the silent ones cost you · 1:06
On screen: a small price tag hangs from each grey plant. The tags add up into one receipt at the edge of the bed.
And there's the bill. Most email marketing tools charge by contacts, or by emails sent. So every silent row is someone you're paying to mail, who isn't reading, clicking, or buying.
04 · How to set yours: what counts as silent · 1:48
On screen: chip 3 lights. One grey plant, looked at closely. Above it, two small lights: opened flickers on by itself, with a tiny auto tag, while clicked stays dark. The rule card updates: inactive = no opens AND no clicks. Gloss card: Mail Privacy Protection · a privacy feature that can load an email on its own, so it counts as opened.
How do you set yours? Start with what counts as inactive. Make it no opens AND no clicks. Opens alone aren't reliable anymore. Apple's Mail Privacy Protection can register an open when nobody looked. Clicks are a much cleaner signal.
05 · How long a window · 2:11
On screen: three bars under the bed, one per click, each a length with no number on it: daily short, weekly longer, monthly longest. Each bar has a tiny calendar with fewer or more sends drawn on it.
Then, how long a window? There's no one answer. It depends on how often you send. A daily newsletter can sunset sooner. A brand that sends weekly waits longer. A monthly newsletter waits longer still, because its readers get fewer chances to engage. Set yours by your own sending, not by someone else's number.
06 · The twist: quiet isn't always gone · 2:37
On screen: one row in the bed stays grey through three small seasons drawn along the top, then bursts green in the fourth. A ghost of the watering can shows what would have happened: the row skipped in season three, and never watered in season four.
Quiet isn't always gone, though. Think of a seasonal business. Some customers only show up for one season a year. Sunset them after one quiet quarter, and you cut off people who were always coming back. So the window has to fit your buying cycle too.
07 · The flow, and the button · 2:59
On screen: one grey row, kai@driftwood-goods.example. A small email card opens over it: Still interested in hearing from us? and one teal button, Yes, keep me. Two outcomes, one per click: the button pressed and the row turns green, or no press and the row goes coral, skipped by the can.
Here's the flow. A subscriber goes quiet. You wait out your window. Then a short win-back. The first one asks, still interested? With one clear button. Yes, keep me. If they click, they stay. If they still don't engage, you suppress them. Done.
08 · Not gone for good · 3:24
On screen: a coral row sprouts a new green shoot, a small bought tag on it, and the can starts watering it again. A separate thin line of receipt envelopes keeps flowing to a coral row the whole time.
And you haven't lost them for good. If they come back through a new signup, or a purchase, they're active again. Make sure your system flags them, so they're not still on the quiet path. And if they're customers, keep sending their receipts and order updates. A sunset is for campaigns, not those.
09 · Write it down, then watch · 3:46
On screen: the checking desk lamp sweeps the grey block. Most grey plants stay amber, gone quiet. A few turn out to be paper plants on a door marked accepts everything, and they go coral, never a subscriber.
Before your first win-back, check the soil itself. Not every silent row was a person who drifted away. On some domains, the server takes mail for any name at all, even a made-up one, so a dead address there usually never bounces. It just sits in the bed, silent. A clean tells those apart before you send.
10 · Recap · 4:29
On screen: the bed, the rule card, the two lights, the three bars, the seasons strip, the button, the new shoot. All three chips lit.
The whole policy, in brief. A sunset policy is a written rule for the silent ones. Inactive means no opens and no clicks. The window fits how often you send, and your buying cycle. Check the list, then a short win-back with one clear button. Suppress, never delete, and welcome them back. Then write yours down.
11 · Close · 4:49
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V061, no subscribe ask.
Stop watering the silent rows, and never dig them up. Review My Emails can't win anyone back for you, but it shows you who was never there. Want to see who's gone quiet? That's RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is SMTP handshake validation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-020.014.001-what-is-a-sunset-policy.md
00 · Silent, and still sent to (hook)
Almanac ids in this scene: 020.014.001
What is an email sunset policy?
three numbered chips: 1 what a sunset policy is · 2 why the silent ones cost you · 3 how to set yours. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept re-engagement (the garden bed, M-03, M-04).
020.014.001 "somewhere along the way a chunk of your subscribers just... stopped opening. They're not unsubscribing. They're not complaining (yet). They're just silent. A sunset policy is how you decide what to do with them before they become a real problem."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 020.014.001
no cut away and no ad break. The bed holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
020.014.001 "a list clean can help you separate the genuinely inactive from addresses that are risky to mail at all." Q4: one sentence, 20 words, brand once here and once in the close.
02 · What a sunset policy is
Almanac ids in this scene: 020.014.001
What a sunset policy is
chip 1 lights. A small rule card pinned at the edge of the bed: silent for a set window → win-back → suppress. The grey block gets one last pass of the can, a single drop. Then the can skips it. The plants stay in the soil.
one rule card, one last drop, one skipped block still planted. Reveals: (1) the card, (2) the last drop, (3) the can skips, (4) the plants stay.
concept re-engagement, the garden bed. The rule card: no picture yet.
020.014.001 "An email sunset policy is a documented rule that defines what happens to subscribers after a set period of no engagement (no opens, clicks, or replies)" / "Inactive contacts are routed into a win-back sequence and then suppressed from regular sends, not deleted." / "They stay in your database. They just stop receiving campaigns that they're clearly ignoring."
"win-back" is glossed by the line itself (one last try). The older re-engagement short owns the rest (S6).
03 · Why the silent ones cost you
Almanac ids in this scene: 020.014.001, 020.014.003
Why the silent ones cost you
a small price tag hangs from each grey plant. The tags add up into one receipt at the edge of the bed.
one tag per silent row, summed into one receipt. Reveals: (1) the tags, (2) the receipt.
the garden bed.
020.014.003 "Most ESPs charge by contacts or emails sent." / "That's 20,000 people you're paying to mail" / "And none of them are buying, clicking, or converting."
"email marketing tools", never "ESPs" (V5). The answer's example list and its 40 percent are not voiced, the receipt has no figure (N6).
04 · How to set yours: what counts as silent
Almanac ids in this scene: 020.014.002, 021.006.008
How to set yours
chip 3 lights. One grey plant, looked at closely. Above it, two small lights: opened flickers on by itself, with a tiny auto tag, while clicked stays dark. The rule card updates: inactive = no opens AND no clicks. Gloss card: Mail Privacy Protection · a privacy feature that can load an email on its own, so it counts as opened.
two lights, one of them lying. Reveals: (1) the plant, (2) the auto-lit open, (3) the dark click, (4) the card updates.
concept mail-privacy-protection (called back from V035, named and glossed here, Q5).
020.014.002 ""Inactive" should mean no opens AND no clicks over a defined window. Opens alone are unreliable now that Apple Mail Privacy Protection inflates open rates. Clicks are a much cleaner signal." 021.006.008 "Mail Privacy Protection (MPP) pre-fetches emails through Apple's proxy servers, which registers an open even if the subscriber never actually looked at your email."
Named the way V035 names it, "Apple's Mail Privacy Protection" (Q11, P5), glossed in one line (Q5). One new word in the scene (Q6). Caps on one payoff word only, "AND" (V4).
05 · How long a window
Almanac ids in this scene: 020.014.001, 020.014.002
How to set yours
three bars under the bed, one per click, each a length with no number on it: daily short, weekly longer, monthly longest. Each bar has a tiny calendar with fewer or more sends drawn on it.
three bars, their lengths the only number. Reveals: (1) to (3) one bar each.
the garden bed. The window bars: no picture yet.
020.014.001 "A common sunset window is 90 to 180 days of no engagement, though this varies by how often you send. A daily newsletter might sunset after 60 days. An e-commerce brand sending weekly might wait until the six-month mark." 020.014.002 "12 months is reasonable for low-frequency lists (monthly newsletters, annual event emails). These readers have less opportunity to engage." / "there's no universal answer."
no day or month count voiced or drawn (C30, and its new daily pair). "Can sunset sooner" keeps the answer's "might" (V12).
06 · The twist: quiet isn't always gone
Almanac ids in this scene: 020.014.001, 020.014.002
How to set yours
one row in the bed stays grey through three small seasons drawn along the top, then bursts green in the fourth. A ghost of the watering can shows what would have happened: the row skipped in season three, and never watered in season four.
four seasons, three grey and one green. Reveals: (1) to (3) the grey seasons, (4) the green burst, (5) the ghost can.
the garden bed. The seasons strip: no picture yet.
020.014.001 "The right window depends on your sending frequency and your audience's buying cycle (a seasonal business, for example, shouldn't sunset someone after one quiet quarter)." 020.014.002 "6 months is the sweet spot for most senders. It's long enough to catch seasonal readers".
T3, the one twist. Only the answer's words for the rule, no number (the six months stays in the quote, not the VO).
07 · The flow, and the button
Almanac ids in this scene: 020.014.001, 020.014.002
How to set yours
one grey row, kai@driftwood-goods.example. A small email card opens over it: Still interested in hearing from us? and one teal button, Yes, keep me. Two outcomes, one per click: the button pressed and the row turns green, or no press and the row goes coral, skipped by the can.
one email, one button, two outcomes. Reveals: (1) the email, (2) the button, (3) the green outcome, (4) the coral outcome.
concept re-engagement.
020.014.001 "A subscriber goes quiet. You wait out your defined window. You send a re-engagement or win-back campaign, sometimes a series of two or three emails, to give them a final chance. If they still don't engage, you suppress them. Done." 020.014.002 "Email 1 (soft check-in): "Still interested in hearing from us?" Keep it warm, no pressure. Include a clear "yes, keep me" button."
"a short win-back", no count of emails (C31). T2, what the email looks like.
08 · Not gone for good
Almanac ids in this scene: 020.014.001, 020.014.002
How to set yours
a coral row sprouts a new green shoot, a small bought tag on it, and the can starts watering it again. A separate thin line of receipt envelopes keeps flowing to a coral row the whole time.
one row back to green, one line that never stopped. Reveals: (1) the shoot, (2) the can returns, (3) the receipt line.
the garden bed.
020.014.001 "You haven't lost them permanently. If they come back through a new sign-up or a purchase, they're active again." 020.014.002 "Make sure your system flags these people so you're not accidentally mailing someone who's now engaged as if they're still on the inactive path." / "If they're customers who still need transactional emails (receipts, order updates), keep them on that flow separately."
09 · Write it down, then watch
Almanac ids in this scene: 020.014.001, 020.014.002, 021.002.013
Before the win-back
the checking desk lamp sweeps the grey block. Most grey plants stay amber, gone quiet. A few turn out to be paper plants on a door marked accepts everything, and they go coral, never a subscriber.
one grey block split into two kinds. Reveals: (1) the lamp, (2) the amber ones, (3) the paper plants turn coral.
concept catch-all, the checking desk.
020.014.002 "you can run it through RME Clean first. It'll flag the contacts worth keeping versus the ones that are already gone before you ever send a win-back email." 020.014.001 "a list clean can help you separate the genuinely inactive from addresses that are risky to mail at all." 021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. T2, which numbers to watch. No target rates (N6).
R15 (YT, 2026-09-29), with T6. Q2: a list topic, so the catch-all pivot fits. Q3: moved before the recap. "Usually" keeps inside C17.
10 · Recap
What to remember
the bed, the rule card, the two lights, the three bars, the seasons strip, the button, the new shoot. All three chips lit.
callbacks only.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 005.003.009
Stop watering, don't dig up
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V061, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10), in new words (Q1). S8: last video of part 3, so the next video is the first of part 4, 005.003.009, by its Almanac question word for word. No more "end of this series". Totals: 15 scenes, 667 spoken words, about 4:03 of speech and about 5:00 with scene breaks and reveals (counted in Step 4). Every scene is 20 to 70 words (S2). Over five minutes with breaks, so a Short cut note (Q10). Short cut: scenes 00, 02, 04, 07 and 09 (the silent block, the rule, no opens AND no clicks, the win-back button, write it down). The answer lands by about 1:00 and the action by the end of the cut.
V052What causes hard bounces?
waiting on YTOpen questions for YT
- "No picture yet": the slot row with a gap, the crate, the three source trays.
- Series order: this is video 1 of "Bounces, part 3" in the order the PM gave.
00 · A brand new list (hook) · 0:00
On screen: the title, Lora, large: "What causes hard bounces?" A fresh list card, new · 2 weeks, with a green shine. One letter comes back to it, coral note clipped on, mono 550. Three numbered chips, the VO's words: 1 where they come from · 2 how to tell them apart · 3 how to find the source. Chips 2 and 3 grey.
What causes hard bounces? Sally Send's list is brand new. Two weeks old. So she's sure it can't have any. Then her welcome email comes back. Hard. Here's the thing. A hard bounce isn't just about age. Three answers, in order. Where they come from. How to tell them apart. And how to find the source.
01 · Brought to you by, woven in · 0:21
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Most hard bounces are sitting on a list long before anyone hits send, and that's where Review My Emails finds them.
02 · What the server found · 0:30
On screen: chip 1 lights. Playlist 1's returned letter, small, called back. The clipped note unfolds, mono: 550 no such user. Behind the receiving door, a row of mailbox slots, and the zoom finds the empty gap where this one should be.
What did that server find? A hard bounce is the permanent kind. The letter comes back with a note clipped on, and the note starts with a five. Usually five fifty. The receiving server looked for that mailbox, at that domain, and there was nothing there to take it. Not busy. Not full. Nothing.
03 · Cause one: it was typed wrong · 0:50
On screen: a signup form. The address field fills letter by letter: marnia@tidewell-supply.invalid. The swapped ni is circled in coral. The letter goes out, and comes back with its note rewritten: no one by that name.
Where do they come from? The first place is the signup itself. Someone types their own address and swaps two letters. Marina becomes Marnia. It looks right to them, and to you. But the server looks for Marnia, and nobody by that name ever lived there. Some signups are fake on purpose. Same result.
04 · Cause two: they left · 1:11
On screen: the same letter, a new address: una.subscribe@pearl-diver.invalid. On the far side of the door, a desk with a nameplate. The nameplate is lifted off, the desk is empty. The note is rewritten: moved away.
The second place is time. The person moved on. They left the company, and IT switched the work mailbox off. Or they closed a personal account they didn't want anymore. The address was real when they gave it to you. It just has nobody behind it now. Like a letter to someone who moved away and left no forwarding address.
05 · Cause three: the whole domain went · 1:34
On screen: the letter, a new address: sunk@shipwreck.invalid. The building behind the door fades to an empty lot. Every envelope for that domain turns coral together. The note: the building is gone.
Sometimes it's bigger than one person. The whole domain expired, or the company shut down. Now there's no building at all. Every address at that domain fails the same way, at once. That's a dead domain, a domain with no working mail server. It's the same cause, just all together.
06 · Cause four: the bought list · 1:53
On screen: a crate of envelopes tipped out onto the desk, stamped bought and scraped. A lot of them pass the door and come back coral, in a heap.
And the fourth place is how the list was built. Purchased lists and scraped addresses are full of hard bounces. That's one of the many reasons not to mail them in the first place. Whoever gathered them, the receiving servers only see the addresses that aren't there.
07 · Even a perfect list · 2:11
On screen: Sally's list card, green, held still. A season strip runs along the bottom. As it moves, one green dot after another on the card turns coral, with nobody touching it.
Say you did everything right. No bought lists. Every address typed with care. Your list still grows hard bounces, all on its own. People change jobs. They change providers. The address that loved your emails last spring can be a hard bounce this autumn, and nobody did anything wrong.
08 · How to tell them apart · 2:29
On screen: the three rows from scene 08, each one pulling out a small card: user unknown → list decay, domain not found → how it was collected, and a fourth row slides in, 550 policy → about you, which takes the coral off the subscriber's side and puts it on Sally's.
Then read what each kind points to. Lots of user unknown on an older list? That's normal list decay, people moving on. Domain bounces are usually a signup or list-building problem. And if the words point at a policy block, it isn't the address at all. That one is about you, the sender.
09 · Find the source · 3:10
On screen: chip 3 lights. The heap of coral letters sorts itself into three trays, labelled signup form · import · event list. One tray fills far more than the others, and a small lamp lights over it.
Now find the source. Export your hard bounces and look at where each address came from. The signup form. An import. An event list. Patterns matter. If a big share of them came in through one door, that door has a problem. Fix it there, and the next list stays cleaner.
10 · Why no retry fixes it · 3:29
On screen: one letter goes in through a door marked accepts everything, and the door closes. Hold. Nothing comes back out. Then the checking desk lamp finds the same address and tags it amber, catch-all.
And some never bounce at all. On a domain that says yes to every address, real or made up, a typo usually goes through without a word. No note, nothing to trace, and it stays on your list.
11 · Recap · 4:04
On screen: the four rewritten notes side by side, the three report rows, the tall tray. All three chips lit.
In short, a hard bounce means there's nothing there. It comes from four places. A typo at signup. A person who moved on. A domain that's gone. Or a list you never should have bought. Read the words in your bounce report, and trace the pile back to the door it came through.
12 · Close · 4:24
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 2, no subscribe ask.
Catch them before they bounce. Finding the addresses whose people have already moved on is the job Review My Emails does. It can't stop people moving on. And to catch a typo the moment it's typed, you can check each address at signup, through our API. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how should I handle hard bounces?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-004.004.003-what-causes-hard-bounces.md
00 · A brand new list (hook)
What causes hard bounces?
the title, Lora, large: "What causes hard bounces?" A fresh list card, new · 2 weeks, with a green shine. One letter comes back to it, coral note clipped on, mono 550. Three numbered chips, the VO's words: 1 where they come from · 2 how to tell them apart · 3 how to find the source. Chips 2 and 3 grey.
one new list, one returned letter. The shine goes as the letter lands. Reveals: (1) the list, (2) the letter, (3) the chips.
concept hard-bounce (the returned envelope stamped once, M-15, M-14).
H1 the wrong belief ("new means no hard bounces"), H3 the title word for word, H5 chips = VO.
01 · Brought to you by, woven in
Almanac ids in this scene: 004.004.003
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
004.004.003 "a list validation tool can flag bad addresses at the point of signup or before a send."
one sentence, 21 words, brand said here and in the close only.
02 · What the server found
Almanac ids in this scene: 004.004.003
What a hard bounce says
chip 1 lights. Playlist 1's returned letter, small, called back. The clipped note unfolds, mono: 550 no such user. Behind the receiving door, a row of mailbox slots, and the zoom finds the empty gap where this one should be.
a row of slots with one gap. The gap is the whole bounce. Reveals: (1) the note, (2) the row of slots, (3) the zoom on the gap.
concept hard-bounce (M-15, M-14). The slot row: no picture yet, proposed.
004.004.003 "The server at the receiving end sent back a permanent failure, usually an SMTP 550 error, which translates roughly to 'this address doesn't exist here.'" / "There's no mailbox there to receive it."
one callback line for the five and the hard bounce (S6). Not re-taught.
03 · Cause one: it was typed wrong
Almanac ids in this scene: 004.004.003, 005.006.001
Where they come from
a signup form. The address field fills letter by letter: marnia@tidewell-supply.invalid. The swapped ni is circled in coral. The letter goes out, and comes back with its note rewritten: no one by that name.
one address, two letters swapped. Reveals: (1) the typing, (2) the circle, (3) the note.
concept opt-in (M-14, M-07) for the form, then the returned letter.
004.004.003 "the address was mistyped at signup (captain@deepcurrent.example entered as captian@deepcurrent.example)". 005.006.001 "The address never existed (typo at signup, fake signup)".
the Almanac's own example is on a real-looking ending, so the screen uses a library name on a reserved ending instead (V7). Part 2 video 5 owns broken formats, this is a typo that looks fine.
04 · Cause two: they left
Almanac ids in this scene: 004.004.003, 005.006.003
Where they come from
the same letter, a new address: una.subscribe@pearl-diver.invalid. On the far side of the door, a desk with a nameplate. The nameplate is lifted off, the desk is empty. The note is rewritten: moved away.
one desk, full, then empty. Reveals: (1) the desk with the nameplate, (2) the nameplate lifts, (3) the note.
the returned letter (M-15). The empty desk: hygiene video 1's picture, called back.
004.004.003 "the mailbox was deleted after the person left the company or closed their account." 005.006.003 "Address disabled (551, 553). The account existed but has been disabled by the provider. Common with corporate email when someone leaves a company and IT deactivates the account."
05 · Cause three: the whole domain went
Almanac ids in this scene: 004.004.003, 005.006.003, 005.008.001
Where they come from
the letter, a new address: sunk@shipwreck.invalid. The building behind the door fades to an empty lot. Every envelope for that domain turns coral together. The note: the building is gone.
one domain, every address on it coral at once. Reveals: (1) the building, (2) the empty lot, (3) every envelope turns.
the hygiene playlist's dead domain picture, called back.
004.004.003 "the domain has expired or shut down entirely". 005.006.003 "Expired company domains, mistyped domains (gmial.com), and domains that were never set up for email all produce this error." 005.008.001 "Every message you send to a dead domain is a hard bounce."
one callback line (S6). The dead domain is not re-taught.
06 · Cause four: the bought list
Almanac ids in this scene: 004.004.003
Where they come from
a crate of envelopes tipped out onto the desk, stamped bought and scraped. A lot of them pass the door and come back coral, in a heap.
the heap of returned letters is the share that bounced. No number on it. Reveals: (1) the crate, (2) the letters go, (3) the heap comes back.
the returned letter, many at once. The crate: no picture yet.
004.004.003 "Purchased lists and scraped addresses are full of hard bounces, which is one of the many reasons you shouldn't be mailing to them in the first place."
no share is drawn or spoken for the heap (N6, V9). The last sentence is framing for "full of hard bounces", no new fact (fact-check pass: "Nobody on them asked" cut, it had no Almanac line).
07 · Even a perfect list
Almanac ids in this scene: 004.004.003
Even a perfect list
Sally's list card, green, held still. A season strip runs along the bottom. As it moves, one green dot after another on the card turns coral, with nobody touching it.
a list that loses dots over time with no action. The strip is time, the coral dots are the count. No rate drawn (C13 not voiced). Reveals: (1) the green list, (2) the strip moves, (3) the dots turn.
concept list-decay (one hundred dots going grey), used with coral instead of grey and no meter number.
004.004.003 "Even organically collected lists accumulate invalid addresses over time as people change jobs and providers."
T3, the one twist. "Last spring, this autumn" is framing, not a timing fact.
08 · How to tell them apart
Almanac ids in this scene: 005.006.003
How to tell them apart
the three rows from scene 08, each one pulling out a small card: user unknown → list decay, domain not found → how it was collected, and a fourth row slides in, 550 policy → about you, which takes the coral off the subscriber's side and puts it on Sally's.
three words, three sources. The fourth moves the colour from the address to the sender. Reveals: one card per row, then the fourth row.
the report, and video 1's coral sliding to the sender's side, called back.
005.006.003 "If you're seeing a lot of user-unknown bounces on an older list, that's normal list decay." / "If you're seeing domain-related bounces, that's usually a validation or acquisition problem." / "Permanent policy rejection (550, 554). The receiving server has a permanent block in place for your sending domain or IP."
the policy block is never a reason to suppress the address (hard content rules). One callback line, video 1 owns it (S6). Decay percentage not voiced (C13).
09 · Find the source
Almanac ids in this scene: 005.006.001, 005.006.006
How to find the source
chip 3 lights. The heap of coral letters sorts itself into three trays, labelled signup form · import · event list. One tray fills far more than the others, and a small lamp lights over it.
three trays, one much taller. The height is the count. Reveals: (1) the export, (2) the sort, (3) the tall tray lights.
concept suppression-list style trays. The sorting: no picture yet.
005.006.006 "Export your suppression list quarterly and look at the bounce reasons. Patterns matter. If 40% of your hard bounces come from one acquisition source, that source has a problem." 005.006.001 "a look at your acquisition process to understand where these addresses came from."
"a big share" replaces the Almanac's example "40%" so no number reads as a pass mark (N6). The three sources on screen are examples of where addresses come in, not an Almanac list.
10 · Why no retry fixes it
Almanac ids in this scene: 004.004.003, 005.006.001, 021.002.013
The one you never see
one letter goes in through a door marked accepts everything, and the door closes. Hold. Nothing comes back out. Then the checking desk lamp finds the same address and tags it amber, catch-all.
the count of returned letters is zero. The empty space where a note should land is the picture. Reveals: (1) the letter goes in, (2) nothing returns, (3) the lamp tags it.
concept catch-all (a gate that lets every envelope through without looking).
021.002.013 "it accepts delivery attempts for any address at that domain, even completely made-up ones. So an email sent to madeupname@somecompany.example doesn't bounce." / "validation tools will flag these addresses as 'catch-all' or 'accept-all'".
the handling steps belong to video 2 (005.006.001), pointed forward here (S6).
R15 (YT, 2026-09-29): pivot before the pitch, backed by the catch-all answers only. "Doesn't bounce" is said of a made-up name on a catch-all, as 021.002.013 says it. No count. "Usually" keeps inside C17 (fact-check pass: added).
reworded so it grows out of this video's own typo cause (Q1, Q2) and moved before the recap as 10b (Q3). The only catch-all pivot in Bounces part 3, V053 to V057 use their own topic.
11 · Recap
What to remember
the four rewritten notes side by side, the three report rows, the tall tray. All three chips lit.
callbacks only.
callbacks only (S5).
12 · Close
Almanac ids in this scene: 004.004.003
Check before they bounce
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 2, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: API · check at signup, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (stop decay) and what it does here (S10). Backed by 004.004.003 "a list validation tool can flag bad addresses at the point of signup or before a send. That's something Review My Emails does as part of RME Clean." Totals: 15 scenes. 760 spoken words (counted 2026-09-30, Q sweep). About 4:35 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V053How should I handle hard bounces?
waiting on YTOpen questions for YT
- GAP at 07b: delete the records, or keep them on file (C38).
- C37 at 03b: "is every 5xx removed?", numbered by the PM 2026-09-29.
- "No picture yet": the dark house, the help page card, the price tag, the billing card, the report bar.
00 · Just one more, to be sure (hook) · 0:00
On screen: the title, Lora, large: "How should I handle hard bounces?" Sally's finger over a send again button, and the returned letter beside it, coral note, mono 550 on bo.unce@coral-cove.invalid. On "Don't", the button greys. Three numbered chips, the VO's words: 1 when to remove it · 2 what your tool does for you · 3 what a pile of them is telling you. Chips 2 and 3 grey.
How should I handle hard bounces? Sally Send has one she doesn't believe. So she wants to send it one more time, just to be sure. Don't. One is enough. Here's how, in three parts. When to remove it. What your tool does for you. And what a pile of them is telling you.
01 · Brought to you by, woven in · 0:21
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
The easiest hard bounce to handle is the one you never send, and Review My Emails helps you never send it.
02 · Why one is enough · 0:29
On screen: chip 1 lights. The returned letter from the hook, its note unfolding into three short lines, mono: doesn't exist · domain doesn't take mail · switched off for good. Beside it, the house, windows dark. A second letter hovers at the letterbox, then fades.
Why is one enough? Because a hard bounce is the receiving server telling you, in plain terms, that this won't work. The address doesn't exist. The domain doesn't take mail. Or the mailbox has been switched off for good. No retry changes that answer. It's a letter back from an empty house. You don't post a second one to check.
03 · The rule · 0:52
On screen: a second letter, kai@driftwood-goods.example, note mono 550 5.7.1 with blocklist underlined. It heads for the pot, stops, and the coral slides off Kai's side onto Sally's, as in playlist 1. Kai's dot stays green.
One exception. If the words after the five point at you, a blocklist, spam complaints, your sending, that's a block bounce, a refusal aimed at the sender. The address may be perfectly fine. Suppressing it fixes nothing. Fix what the block is about instead.
04 · The four you'll see · 1:29
On screen: four notes in a row. The first three are small callbacks from video 1, greyed: never existed, deleted, domain expired. The fourth lights up, new: switched off by the provider with two small tags, broke the rules · sat unused.
Which fives do you remove? The four you'll see most. An address that never existed, from a typo or a fake signup. A mailbox deleted when someone left. A domain that expired. And one we haven't met yet. An account the provider itself switched off, for breaking its rules, or for sitting unused.
05 · What your tool does · 1:49
On screen: chip 2 lights. A send going out as a row of envelopes. The one hard-bounced address is lifted out of the row by a small arm, marked suppressed, before the next send leaves.
Do you have to do this by hand? Usually not. Most email marketing tools do it for you. When an address hard bounces, the tool suppresses it, and it won't go out in your future sends. That part is the safety net.
06 · Where to see what yours does · 2:06
On screen: a help page card, bounce handling, with one line highlighted: hard bounce → ?. A chat bubble to support slides in, what happens to a hard bounce?, and gets back a vague a few bounces, which gets a coral strike.
But what does yours do, exactly? Tools handle bounces differently, and the defaults aren't always on your side. So open your tool's bounce documentation and read what it does with a hard bounce. Can't find it? Ask their support. We suppress after a few bounces is not an answer.
07 · Suppressed isn't removed · 2:24
On screen: the billing card, and the hard-bounced contacts lifting off it one by one. The count shrinks.
Open question: Delete the records, or keep them on file?.
Check how your tool treats a suppressed contact. If you're paying per contact, and those records still count, clean the hard-bounced records out.
08 · What a pile of them is telling you · 2:51
On screen: chip 3 lights. The send's bounce report, one bar for hard bounces, grown tall, with no number on it (??). It splits into two tags: stale · never valid. Two small cards slide in: check before the next big send · where did they come from?, the second with video 1's source trays.
Now the last part. What if it isn't one hard bounce, but a pile of them on a single send? That's a signal to take seriously. A real chunk of your list is either stale, or was never valid to begin with. The fix is two things. Check the list before your next big send. And look at where those addresses came from.
09 · Recap · 3:15
On screen: the pot with its lid, the coral sliding to Sally's side, the price tag, the tall bar. All three chips lit.
Your hard bounce routine, then. Remove a hard bounce the first time, no second send. Unless the words point at you, then fix the sending. Check what your tool does with a suppressed contact, and clean out the records if you pay for them. And when a pile shows up, check the list and find the source.
10 · Close · 3:36
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, no subscribe ask.
Better still, find them before the first send. Review My Emails flags most hard bounce candidates before you send, which is a lot gentler on your reputation. That's RME Clean. It won't fix a block, that's about how you send. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is poor sender reputation in bounce messages?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.006.001-how-to-handle-hard-bounces.md
00 · Just one more, to be sure (hook)
How should I handle hard bounces?
the title, Lora, large: "How should I handle hard bounces?" Sally's finger over a send again button, and the returned letter beside it, coral note, mono 550 on bo.unce@coral-cove.invalid. On "Don't", the button greys. Three numbered chips, the VO's words: 1 when to remove it · 2 what your tool does for you · 3 what a pile of them is telling you. Chips 2 and 3 grey.
one returned letter, one button that greys out. Reveals: (1) the letter and the button, (2) the button greys, (3) the chips.
concept hard-bounce (M-15, M-14).
H1 the wrong belief ("send again to confirm") in the viewer's own moment. H3 title word for word. H7 states, no quiz. The turn is "Don't. One is enough", new to the series (M1 spirit).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.006.001
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
005.006.001 "Our list cleaning service will also catch most hard-bounce candidates before you send, which is a lot gentler on your reputation than finding out the hard way."
one sentence, 21 words, brand said here and in the close only.
02 · Why one is enough
Almanac ids in this scene: 005.006.001
When to remove it
chip 1 lights. The returned letter from the hook, its note unfolding into three short lines, mono: doesn't exist · domain doesn't take mail · switched off for good. Beside it, the house, windows dark. A second letter hovers at the letterbox, then fades.
one letter back, a second letter that never goes. Reveals: (1) the three lines, (2) the dark house, (3) the second letter fades.
concept hard-bounce (M-15, M-14). The house: framing, no picture yet.
005.006.001 "The receiving server is telling you clearly: this address doesn't exist, the domain doesn't accept mail, or the mailbox is permanently disabled. There's no retry that changes that answer."
03 · The rule
Almanac ids in this scene: 001.008.007, 005.006.001, 005.006.015, 015.001.001, 015.001.011, 015.005.004
When to remove it
a second letter, kai@driftwood-goods.example, note mono 550 5.7.1 with blocklist underlined. It heads for the pot, stops, and the coral slides off Kai's side onto Sally's, as in playlist 1. Kai's dot stays green.
the same five, the colour moved from the address to the sender. Reveals: (1) the note, (2) the stop at the pot, (3) the coral moves.
video 1's coral sliding to the sender's side, called back. Concept blocklist.
015.005.004 "Block bounces (550 5.7.1 policy rejection ...) mean a valid server refuses your mail based on IP, domain, or content reputation. Suppressing the address fixes nothing." / 005.006.015 "Policy rejection (5.7.0, 5.7.1, 5.7.2, 5.7.26): Reputation, content, or blocklist issue. Don't suppress the address."
a blocklist listing is never a reason to suppress a recipient (hard content rules). One callback line, part 2 video 2 owns it (S6). No blocklist named.
005.006.001 says "removing the address immediately after the first SMTP 5xx failure", and 001.008.007 lists "blocked" among hard bounces that "get suppressed immediately". 015.005.004, 005.006.015 and 015.001.011 say a block or policy rejection is not suppressed. The hard content rule decides the script (G7): blocks are not removed. The Almanac lines are flagged for YT, never edited.
04 · The four you'll see
Almanac ids in this scene: 005.006.001
When to remove it
four notes in a row. The first three are small callbacks from video 1, greyed: never existed, deleted, domain expired. The fourth lights up, new: switched off by the provider with two small tags, broke the rules · sat unused.
a count of four, three called back grey, one new and lit. Reveals: (1) to (3) the callbacks, (4) the new one.
video 1's rewritten notes, called back.
005.006.001 "The address never existed (typo at signup, fake signup)" / "The mailbox was deleted (person left the company, closed their account)" / "The domain expired or shut down" / "The address was disabled by the provider (policy violation, inactivity)".
05 · What your tool does
Almanac ids in this scene: 005.006.001, 005.006.006
What your tool does for you
chip 2 lights. A send going out as a row of envelopes. The one hard-bounced address is lifted out of the row by a small arm, marked suppressed, before the next send leaves.
one row, one gap where the suppressed address was. Reveals: (1) the row, (2) the arm lifts it, (3) the next send leaves without it.
concept suppression-list (M-23, M-24).
005.006.001 "Most ESPs handle this automatically. When an address hard bounces, the platform will suppress it from future sends." 005.006.006 "Auto-suppression is a safety net, not a list hygiene strategy."
"email marketing tool", never "ESP" (V5).
06 · Where to see what yours does
Almanac ids in this scene: 005.006.001, 005.006.006
What your tool does for you
a help page card, bounce handling, with one line highlighted: hard bounce → ?. A chat bubble to support slides in, what happens to a hard bounce?, and gets back a vague a few bounces, which gets a coral strike.
one question, one vague answer struck out. Reveals: (1) the help page, (2) the question, (3) the strike.
no picture yet (the help page card).
005.006.006 "the rules vary and the defaults are not always sender-friendly." / "Open your ESP's bounce documentation and write down the exact soft bounce threshold. If you cannot find it, ask support. 'We suppress after a few bounces' is not an answer." 005.006.001 "Worth checking your specific platform's behavior".
the Almanac line about "soft bounce threshold" is used only for how to ask, the question here is about hard bounces, backed by 005.006.001 "Worth checking your specific platform's behavior". No tool named, no numbers (R2, R6).
07 · Suppressed isn't removed
Almanac ids in this scene: 005.005.001, 005.006.001, 016.005.007
Suppressed isn't removed
the billing card, and the hard-bounced contacts lifting off it one by one. The count shrinks.
the contact count shrinks by the suppressed records. Reveals: (1) the card, (2) the records lift off.
concept suppression-list (M-23, M-24), with a price tag. The tag: no picture yet.
005.006.001 "Worth checking your specific platform's behavior and cleaning the hard-bounced records out entirely if you're paying per contact."
T5, the action that goes with the twist.
08 · What a pile of them is telling you
Almanac ids in this scene: 005.006.001
What a pile is telling you
chip 3 lights. The send's bounce report, one bar for hard bounces, grown tall, with no number on it (??). It splits into two tags: stale · never valid. Two small cards slide in: check before the next big send · where did they come from?, the second with video 1's source trays.
one bar, grown tall, no number. Reveals: (1) the bar, (2) the two tags, (3) the two cards.
the bounce report bar (no picture yet), video 1's trays, called back.
005.006.001 "It means a meaningful chunk of your list is either stale or was never valid to begin with. The fix is validation before the next large send, and a look at your acquisition process to understand where these addresses came from."
the answer's "above 2 percent" is not voiced or drawn. The bar reads ?? so nothing is a target (N6, and C16 and C19 sit on this line).
09 · Recap
What to do
the pot with its lid, the coral sliding to Sally's side, the price tag, the tall bar. All three chips lit.
callbacks only.
callbacks only (S5).
if the GAP at 07b plays without it, the third sentence becomes "Check what your tool does with a suppressed contact." (G2).
10 · Close
Almanac ids in this scene: 015.005.012
Catch them before you send
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not fix (a block) and what it does, in the answer's own words, "most" kept, not tightened (V12, S10). The next title is 015.005.012 word for word, its quote marks dropped in VO only. Totals: 13 scenes. 630 spoken words (counted 2026-09-30, Q sweep). About 3:48 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V054What is "poor sender reputation" in bounce messages?
waiting on YTOpen questions for YT
- "No picture yet": the ledger strip, the line on the gauge, the dashboard card.
- T7 note for the PM: a free reputation check of our own does not exist.
00 · A wall of the same words (hook) · 0:00
On screen: the title, Lora, large: "What is "poor sender reputation" in bounce messages?" A stack of returned letters builds up in front of Sally, each note in mono with the same words: rejected due to poor sender reputation. Three numbered chips, the VO's words: 1 what the words mean · 2 what's behind them · 3 how you climb back. Chips 2 and 3 grey.
Sally Send hits send on her campaign. And instead of deliveries, she gets a wall of bounces that all say the same thing. Poor sender reputation. What is poor sender reputation in bounce messages? We'll unpack it in three. What the words mean. What's behind them. And how you climb back.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Sending to addresses that don't exist drags a reputation down, and Review My Emails flags those addresses before they cost you.
02 · What the words mean · 0:28
On screen: chip 1 lights. Playlist 1's score gauge, small at first, then filling the frame. A ledger strip runs beneath it, one mark per past send, some green, some coral. The needle sits low. Gloss card (the playlist 1 line, re-glossed for a viewer from search, Q5): sender reputation · how mailbox providers score your sending domain, based on how you've sent so far.
What are those words saying? Start with sender reputation, the score mailbox providers keep on your domain and your IP, built up over time from how you've sent. Think of it like a credit score. Every send adds to the record. And this bounce is a provider telling you, pretty directly, that your record has left a bad impression.
03 · It skips the spam folder · 0:50
On screen: the gauge from scene 02, with one line drawn across it. Above the line, Sally's envelope goes through the gate and drops into an amber tray marked spam folder. The needle slips below the line, and the next envelope never reaches the tray. The gate hands it back, coral note clipped on.
You'd expect a bad reputation to land you in spam. But providers draw a line on that score. Drop below it, and they don't just filter your mail. They refuse it, outright, at the door. It never gets as far as the spam folder. And the bounce comes back to tell you why.
04 · Where to read it: your IP or your domain? · 1:11
On screen: gloss card: domain reputation · the part of your reputation that belongs to your domain name. The Domain word from scene 04 held still. Sally's envelopes leave from a new sending building, a different door, and the gate still hands them back. The ledger strip from scene 02 is pinned to every envelope.
Why does it matter which one? Because your domain reputation follows your name. Providers track your domain's signals separately from your IP. So switching to another sending tool doesn't clear it. The record comes with you.
05 · What's behind it: the biggest one · 1:46
On screen: chip 2 lights. The registry's complaint picture: a crowd of readers, and a few hands going up, each one tapping a small spam button. With each hand, the needle on the gauge drops a notch. No count on the crowd.
What's behind the score? The biggest one is complaints. Every time someone marks your mail as spam, that's a direct vote against you. Too many of those, and the needle falls, whatever else you get right.
06 · What piles on top · 2:00
On screen: three weights land on the gauge's needle, one per click: bounces · low engagement · blocklist history. The last one is a faded stamp on the ledger strip, cleared, that still weighs.
Then other things pile on top. Sending to addresses that don't exist, so your bounce rate climbs. Low engagement, people who never open or click. And blocklist history. A past listing still leaves a mark, even after it's been cleared. The record remembers.
07 · One provider, or all of them? · 2:17
On screen: a row of doors, one per provider, as in part 2 video 2. First pose: one door hands back a note. Second pose: every door does, labelled your sending history. Then a small card: reviewmyemails.com/tools/blacklist-checker.
Now check the pattern. The exact wording matters less than this. Is it one provider, or several at once? Several at once means it's your sending history, not a one-off policy. And check whether your domain is on a blocklist. Our free blocklist checker will tell you.
08 · How you climb back: the list and the pace · 2:35
On screen: the ledger strip from scene 02 keeps adding green marks, one per send, and the needle climbs a little with each.
And give it time. That's the frustrating part. You built the score slowly with good sending, and you rebuild it the same way. It just won't happen overnight.
09 · Recap · 3:20
On screen: the gauge with its line, the Diagnostic Code slip with IP and Domain lit, the row of doors, and the four moves as small cards. All three chips lit.
Put together. Poor sender reputation means your score fell below the provider's line, so you're refused, not filtered. Read whether it names your IP or your domain. Check if it's one provider or all of them. Then climb back. The list first, a slower pace, your sender checks, and the dashboards.
10 · Close · 3:40
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
Start the climb with the list. Review My Emails takes one weight off, the addresses that don't exist. A clean won't fix your reputation, and it won't lift a block. Worried about a listing? Our free blocklist checker is the first stop. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a bounce server?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.005.012-poor-sender-reputation-bounce.md
00 · A wall of the same words (hook)
Almanac ids in this scene: 015.005.012
Poor sender reputation
the title, Lora, large: "What is "poor sender reputation" in bounce messages?" A stack of returned letters builds up in front of Sally, each note in mono with the same words: rejected due to poor sender reputation. Three numbered chips, the VO's words: 1 what the words mean · 2 what's behind them · 3 how you climb back. Chips 2 and 3 grey.
a stack of notes, all the same words. The height is the cost. Reveals: (1) the send, (2) the stack builds, (3) the chips.
concept bounce (M-15, M-18), many at once.
015.005.012 "You sent a campaign, and instead of delivery confirmations you got a wall of bounces saying things like 'Rejected due to poor sender reputation'".
H1 the cost first, H2 Sally's own send, H3 the title word for word (its quote marks dropped in VO).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.005.012
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
015.005.012 "Sending to invalid addresses (high bounce rates), hitting spam traps, and having low engagement all pile on top of that."
says the clean touches one feed of the score, never that it fixes reputation (S10).
one sentence, 21 words, brand said here and in the close only.
02 · What the words mean
Almanac ids in this scene: 015.005.012
What the words mean
chip 1 lights. Playlist 1's score gauge, small at first, then filling the frame. A ledger strip runs beneath it, one mark per past send, some green, some coral. The needle sits low. Gloss card (the playlist 1 line, re-glossed for a viewer from search, Q5): sender reputation · how mailbox providers score your sending domain, based on how you've sent so far.
one needle, one ledger of past sends. The needle sits where the ledger put it. Reveals: (1) the gauge, (2) the ledger, (3) the needle settles low.
concept sender-reputation (the score gauge, M-33), called back. The ledger strip: no picture yet.
015.005.012 "Sender reputation is a score (or set of signals) that mailbox providers build up about your domain and IP over time." / "That's an ISP telling you, pretty directly, that your sending history has left a bad impression." / "Think of sender reputation like a credit score with ISPs."
the gloss line is playlist 1's, word for word (P5, S6).
03 · It skips the spam folder
Almanac ids in this scene: 015.005.012
Refused, not filtered
the gauge from scene 02, with one line drawn across it. Above the line, Sally's envelope goes through the gate and drops into an amber tray marked spam folder. The needle slips below the line, and the next envelope never reaches the tray. The gate hands it back, coral note clipped on.
one line on the gauge, two outcomes either side. Reveals: (1) the line, (2) above it, the amber tray, (3) below it, the envelope handed back.
concept sender-reputation (M-33) and concept bounce (M-15, M-18). The line on the gauge: no picture yet.
015.005.012 "When that score drops below their threshold, they don't just filter your email. They reject it outright, and the bounce message tells you why."
T3, the one twist. No number is put on the line (N6, red zone thresholds). "At the door" is framing.
04 · Where to read it: your IP or your domain?
Almanac ids in this scene: 015.005.007, 015.005.008, 015.005.012
Your IP or your domain?
gloss card: domain reputation · the part of your reputation that belongs to your domain name. The Domain word from scene 04 held still. Sally's envelopes leave from a new sending building, a different door, and the gate still hands them back. The ledger strip from scene 02 is pinned to every envelope.
two buildings, one ledger. Reveals: (1) the new building, (2) the envelope handed back, (3) the ledger on every envelope.
the ledger strip (no picture yet), the gate (M-18).
015.005.008 "Because Gmail, Outlook, and Yahoo track domain signals independently of IP, switching ESPs or warming a new IP does not clear it." / "switching ESPs or warming up a new IP won't get you out of it."
"sending tool", never "ESP" (V5). The providers are not named. The answer's "warming a new IP" is not voiced (never recommend warmup tools, and it is not needed for the point).
05 · What's behind it: the biggest one
Almanac ids in this scene: 015.005.012
What's behind it
chip 2 lights. The registry's complaint picture: a crowd of readers, and a few hands going up, each one tapping a small spam button. With each hand, the needle on the gauge drops a notch. No count on the crowd.
a few raised hands, each one a notch. Reveals: (1) the crowd, (2) the hands go up, (3) the needle drops.
concept complaint-rate (out of a hundred people, the few who raise a hand), with no number on it, and sender-reputation (M-33).
015.005.012 "High complaint rates are the biggest one. When too many recipients mark your mail as spam, that's a direct vote against you."
no complaint rate number (N6). "Whatever else you get right" is framing for "the biggest one".
06 · What piles on top
Almanac ids in this scene: 015.005.012
What's behind it
three weights land on the gauge's needle, one per click: bounces · low engagement · blocklist history. The last one is a faded stamp on the ledger strip, cleared, that still weighs.
three weights, the needle lower with each. Reveals: (1) to (3) one weight each.
sender-reputation (M-33), the ledger strip.
015.005.012 "Sending to invalid addresses (high bounce rates), hitting spam traps, and having low engagement all pile on top of that. Past blocklist events also leave a mark, even after the listing is cleared."
the spam trap line is held back (hard content rules). No blocklist named.
07 · One provider, or all of them?
Almanac ids in this scene: 015.005.012
What's behind it
a row of doors, one per provider, as in part 2 video 2. First pose: one door hands back a note. Second pose: every door does, labelled your sending history. Then a small card: reviewmyemails.com/tools/blacklist-checker.
a count of refusing doors, one against all. Reveals: (1) one door, (2) every door, (3) the checker card.
concept mailbox-provider (M-14, M-18) for the doors, called back.
015.005.012 "The exact wording matters less than the pattern. If you're seeing reputation-based rejections from multiple providers at once, the problem is your sending history, not a one-off policy issue." / "If you want to check whether your domain is already on a blocklist, our free blocklist checker takes about 30 seconds."
the doors pose is part 2 video 2's, one callback (S6). No time is voiced for the checker.
08 · How you climb back: the list and the pace
Almanac ids in this scene: 015.005.012
How you climb back
the ledger strip from scene 02 keeps adding green marks, one per send, and the needle climbs a little with each.
one green mark per send, one small lift per mark. Reveals: (1) the marks, (2) the climb.
sender-reputation (M-33), the ledger strip.
015.005.012 "Fixing it takes time (of course, that's the frustrating part)." / "You built it up slowly with good behavior, and you can rebuild it the same way. It just won't happen overnight."
no recovery time is given (C33, C20).
09 · Recap
What to do
the gauge with its line, the Diagnostic Code slip with IP and Domain lit, the row of doors, and the four moves as small cards. All three chips lit.
callbacks only.
callbacks only (S5).
10 · Close
Start with the list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/tools/blacklist-checker, the free blocklist checker, named in the VO above (Q11, the same name as scene 07).
the dot grid into three pots, no counts. On "one weight off", the bounces weight from scene 06 lifts off the needle, and the other two stay.
concept list-cleaning (M-25, M-23, M-24).
says out loud what a clean does not fix (reputation, a block) and the one feed it does touch (S10, hard content rules). The checker line uses the same tool name as scene 07 (Q11). Totals: 14 scenes. 636 spoken words (counted 2026-09-30, Q sweep). About 3:50 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V055What is a bounce server?
waiting on YTOpen questions for YT
- P5 word: the registry calls this concept bounce-processor, the Almanac question says "bounce server".
- "No picture yet": the mailroom desk, the report bins, the timeline.
- T7 idea for the PM: none of our free tools reads bounce reasons.
00 · The report that fills itself in (hook) · 0:00
On screen: the title, Lora, large: "What is a bounce server?" Sally's campaign report, rows filling in by themselves: hard · soft · hard. Behind the report, faint, a pile of returned letters being opened one by one. Three numbered chips, the VO's words: 1 what it does · 2 where you see it · 3 what it can't do. Chips 2 and 3 grey.
What is a bounce server? Sally Send has never heard of hers. Every send, her report just fills itself in. Bounced, hard. Bounced, soft. But somebody read every one of those returned letters. Three questions, then. What it does. Where you see it. And what it can't do.
01 · Brought to you by, woven in · 0:18
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A bounce server only finds out about a bad address after you've sent to it, and Review My Emails catches it before you send.
02 · What it is · 0:28
On screen: playlist 1's notice travelling back to the Return-Path, small, called back. It lands on the desk. Part 2's three chain links, watch · read · match, snap onto the desk's edge.
And where do those letters come from? They're bounce notices, sent back to your Return-Path, the address your failures go to. Watching that inbox, reading each notice, and matching it back to the send all happen at this desk.
03 · Follow a hard one · 1:05
On screen: the letter on the desk, note mono: 550 5.1.1 on bo.unce@coral-cove.invalid. The lamp lights the 5. A stamp comes down, coral, hard, and the address drops into playlist 1's suppress pot.
Follow one letter across the desk. It says five fifty, five point one point one. The address doesn't exist. The clerk reads the five, files it as a hard bounce, and suppresses the address. Straight away. No second try.
04 · Follow a soft one · 1:21
On screen: a second letter lands, note mono: 4.7.0 throttled on marina@tidewell-supply.example, with a small green dot for a real reader. The lamp lights the 4. An amber stamp, soft, and the letter slides onto playlist 1's queue shelf. A small loop arrow runs back to the gate, with no count on it.
Now a different letter. Four point seven point zero. Throttled. The address is fine, the send was just too fast for that server. The clerk files it as soft, and puts the message back in the queue to try again. How long it keeps trying depends on your tool. If it keeps failing, in the end it's treated as hard.
05 · Where you see its work · 1:43
On screen: chip 2 lights. The desk slides behind a wall, out of sight. On the front of the wall, Sally's campaign report, the labels lit one per click: hard · soft · policy. The last one carries a small some tools tag.
Where is it, then? You won't find it. Most senders never touch a bounce server directly. Your email marketing tool runs one behind the scenes. There's no settings panel for it. What you see is its work. Those bounce labels in your campaign reports. Hard, soft, and in some tools, a separate one for policy.
06 · What it lumps together · 2:04
On screen: a crowd of different notes pours into the report, and gets squeezed into two or three bins. Zoom in on one bin labelled hard: inside it, 550 5.7.1 beside 550 5.1.1. The first glows toward Sally's side (sender), the second toward the address.
But look closely at those labels. Your tool squeezes dozens of different reasons into a handful of buckets. So where there's no separate policy label, a block about your sending and a user unknown about the address can sit under the same word. One is a reputation problem. The other is a list problem.
07 · Always after the fact · 2:25
On screen: chip 3 lights. A timeline under the desk. Sally's send leaves on the left. Only later, on the right, the letter lands on the desk. Between the two, playlist 1's reputation gauge has already dropped a notch. The desk lamp lights, too late for that notch.
A bounce server is only ever looking backwards. It can't learn an address is bad until you've sent to it, and it's come back. By the time an address bounces, the damage to your reputation is done. So it's a safety net. Not a plan.
08 · What to do with that · 2:42
On screen: the report from scene 05, the bins opening so each reason shows. Then a second return path onto the desk, a small hand icon on each letter, reported as spam, feeding the same desk. Gloss card: feedback loop · an arrangement where a mailbox provider tells a sender which of their messages were reported.
Two habits help. Check your bounce reports regularly, and read the reasons, not just the labels. And make sure feedback loops are set up. That's when a mailbox provider tells you who hit report spam, so complaints flow back to you, just like bounces do.
09 · Recap · 2:59
On screen: the desk with its two stamps, the report labels, the bins opened, the timeline gap. All three chips lit.
Back to the desk. A bounce server is the clerk. It reads every returned letter, files it hard or soft, and tells your tool to retry or remove. You see its work in your reports. Read the reasons behind the labels. And remember it only ever learns after the send.
10 · Close · 3:18
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, no subscribe ask.
Check before the letters ever go out. With Review My Emails, you check the list first, so fewer letters come back to that desk. It doesn't replace your bounce server. And your bounce server can't tell you who stopped reading. For that, there's RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is a return-path or bounce domain?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-001.008.007-what-is-a-bounce-server.md
00 · The report that fills itself in (hook)
What is a bounce server?
the title, Lora, large: "What is a bounce server?" Sally's campaign report, rows filling in by themselves: hard · soft · hard. Behind the report, faint, a pile of returned letters being opened one by one. Three numbered chips, the VO's words: 1 what it does · 2 where you see it · 3 what it can't do. Chips 2 and 3 grey.
a report that fills, a pile that empties behind it. Reveals: (1) the report fills, (2) the pile behind it, (3) the chips.
concept bounce (M-15, M-18), many at once.
H1 the wrong belief ("it fills itself in"), H3 the title word for word.
01 · Brought to you by, woven in
Almanac ids in this scene: 001.008.007, 005.006.006
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
005.006.006 "By the time an address bounces, the damage to your reputation is done." 001.008.007 "The bounce server reads that NDR, figures out if it's a temporary problem (soft bounce) or permanent failure (hard bounce)".
one sentence, 24 words, brand said here and in the close only.
02 · What it is
Almanac ids in this scene: 001.008.007, 015.001.014
What it does
playlist 1's notice travelling back to the Return-Path, small, called back. It lands on the desk. Part 2's three chain links, watch · read · match, snap onto the desk's edge.
one notice in, three jobs on one desk. Reveals: (1) the notice lands, (2) the three links snap on.
callbacks only, playlist 1 video 5 and part 2 video 1.
001.008.007 "typically using the Return-Path address defined in RFC 5321 to route DSNs back to the sender". 015.001.014 (part 2 video 1) for the three jobs.
Delivery Status Notification, Return-Path and the three jobs are callbacks, no new gloss cards (S6).
03 · Follow a hard one
Almanac ids in this scene: 001.008.007
What it does
the letter on the desk, note mono: 550 5.1.1 on bo.unce@coral-cove.invalid. The lamp lights the 5. A stamp comes down, coral, hard, and the address drops into playlist 1's suppress pot.
one digit read, one stamp, one pot. Reveals: (1) the note, (2) the 5 lights, (3) the stamp, (4) into the pot.
the desk, concept suppression-list (M-23, M-24).
001.008.007 "It reads the SMTP enhanced status code (for example 5.1.1 for a nonexistent mailbox ...), classifies the failure as hard or soft, then suppresses or retries the address." / "Hard bounces (address doesn't exist, domain doesn't exist ...) get suppressed immediately."
"blocked" from the same answer line is not voiced (C37, video 2).
04 · Follow a soft one
Almanac ids in this scene: 001.008.007, 005.006.006, 015.007.004
What it does
a second letter lands, note mono: 4.7.0 throttled on marina@tidewell-supply.example, with a small green dot for a real reader. The lamp lights the 4. An amber stamp, soft, and the letter slides onto playlist 1's queue shelf. A small loop arrow runs back to the gate, with no count on it.
the same desk, the other digit, the other way out. Reveals: (1) the note, (2) the 4 lights, (3) the amber stamp, (4) onto the shelf.
the desk, the queue shelf from playlist 1 video 4 (called back), concept soft-bounce (M-15, M-14, M-31).
005.006.006 "Soft bounces are temporary (421, 4.2.1 mailbox busy, 4.7.0 throttled)." 001.008.007 "classifies it as a soft bounce (temporary), and queues a retry. If the mailbox is still full after several attempts, it gets reclassified as a hard bounce and suppressed." 015.007.004 "vary quite a bit from one platform to the next".
R2 and R6 (YT, 2026-09-29): no retry window and no count. The answer's "retried for a few days" is not voiced.
T4, a throttled send instead of the answer's mailbox full. "Too fast for that server" is the meaning of throttling taught in playlist 1 video 1.
05 · Where you see its work
Almanac ids in this scene: 001.008.007
Where you see it
chip 2 lights. The desk slides behind a wall, out of sight. On the front of the wall, Sally's campaign report, the labels lit one per click: hard · soft · policy. The last one carries a small some tools tag.
one wall, the desk behind it, three labels in front. Reveals: (1) the wall, (2) to (4) one label each.
the campaign report (no picture yet), the desk.
001.008.007 "Most senders never interact with a bounce server directly. Your ESP runs one behind the scenes. When you see 'bounce' labels in your campaign reports, that's the bounce server's work." / "you won't find a 'bounce server settings' panel in your ESP. It's all automatic." / "Some ESPs also track policy failures separately (rejected due to content, blocked by recipient's filters)."
"email marketing tool", never "ESP" (V5). No tool is named (the answer names two, held back).
06 · What it lumps together
Almanac ids in this scene: 005.006.006
Where you see it
a crowd of different notes pours into the report, and gets squeezed into two or three bins. Zoom in on one bin labelled hard: inside it, 550 5.7.1 beside 550 5.1.1. The first glows toward Sally's side (sender), the second toward the address.
many reasons in, a few bins out. Reveals: (1) the pour, (2) the bins, (3) the zoom on two notes in one bin.
the report bins (no picture yet), video 1's coral slide, called back.
005.006.006 "Most ESPs collapse dozens of distinct SMTP reasons into 2-3 buckets. A 550 5.7.1 (blocked by recipient policy) is treated the same as a 550 5.1.1 (user unknown), even though one is a reputation problem and one is a list problem."
not a repeat of playlist 1 video 3's twist (a code read wrong). This is two codes read right and filed together. The block is never a reason to suppress (hard content rules).
07 · Always after the fact
Almanac ids in this scene: 005.006.006
What it can't do
chip 3 lights. A timeline under the desk. Sally's send leaves on the left. Only later, on the right, the letter lands on the desk. Between the two, playlist 1's reputation gauge has already dropped a notch. The desk lamp lights, too late for that notch.
the gap on the timeline between the send and the landing. The notch falls inside the gap. Reveals: (1) the send, (2) the notch drops, (3) the letter lands after it.
the desk, sender-reputation (M-33), the timeline (no picture yet).
005.006.006 "By the time an address bounces, the damage to your reputation is done." / "Automatic bounce processing is a safety net, not a strategy."
T3, the one twist. "Only ever looking backwards" is framing for "by the time an address bounces".
08 · What to do with that
Almanac ids in this scene: 001.008.007, 001.008.008, 005.006.006
What to do
the report from scene 05, the bins opening so each reason shows. Then a second return path onto the desk, a small hand icon on each letter, reported as spam, feeding the same desk. Gloss card: feedback loop · an arrangement where a mailbox provider tells a sender which of their messages were reported.
two streams into one desk, bounces and complaints. Reveals: (1) the bins open, (2) the second stream, (3) the gloss.
the desk, the report. feedback-loop is gloss tier, no picture yet.
001.008.007 "What you CAN do: check your bounce reports regularly, set up feedback loops so complaint data flows back just like bounces do". 005.006.006 "Export your suppression list quarterly and look at the bounce reasons." 001.008.008 "If the mailbox provider participates in a feedback loop (FBL), they send you a notification saying 'this person just complained about your email.'"
the answer's "and run your list through validation if your bounce rate climbs above 2%" is not voiced as a number (N6). Most tools register feedback loops for you (001.008.008 "Most ESPs handle FBL registration and processing automatically"), so "make sure they're set up" is a check, not a build.
09 · Recap
What to remember
the desk with its two stamps, the report labels, the bins opened, the timeline gap. All three chips lit.
callbacks only.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 005.006.006
Check before the desk
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 5, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the dot grid into three pots, no counts. The desk behind gets a thinner pile.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (replace bounce handling) and what it does (S10). Backed by 005.006.006 "Catch engagement decay. Addresses that accept mail but never open are still 'deliverable' to your ESP." and "Do not rely on bounces alone to keep your list clean." "Fewer letters" says the pile gets smaller, with no share promised. Totals: 12 scenes. 587 spoken words (counted 2026-09-30, Q sweep). About 3:32 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V056What is a return-path or bounce domain?
waiting on YTOpen questions for YT
- GAP-I, tool flag: does our SPF checker show return-path alignment, as 009.003.002 says?
- Registry: a new bounce-domain row, and a picture for the turned envelope and the DNS record card.
- Demo name: bounce.send-more.example is a subdomain of Sally's library domain.
00 · An address that isn't hers (hook) · 0:00
On screen: the title, Lora, large: "What is a return-path or bounce domain?" A raw header, mono, most lines greyed. One line lights: Return-Path: <bounce-abc123@[your tool's bounce domain]>. Beside it, Sally's own From: sally@send-more.example, and the two don't match. Three numbered chips, the VO's words: 1 what it is · 2 why it matters for your sender checks · 3 how to make it yours. Chips 2 and 3 grey.
Sally Send opens the raw header of her own email. And near the top, there's an address she's never seen. It isn't hers. What is a return-path, or bounce domain? Three pieces to it. What it is. Why it matters for your sender checks. And how to make it yours.
01 · Brought to you by, woven in · 0:19
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every bounce you get lands at that address, and Review My Emails makes sure far fewer of them ever come back.
02 · Two sender addresses · 0:28
On screen: playlist 1 video 5's two servers talking, called back small. The first line of their conversation writes the return address onto the envelope. Only then do From and Subject follow.
And it's set early. During the conversation between the two mail servers, before your From line or your subject are even sent. It's the first thing on the envelope.
03 · Whose it is, by default · 1:00
On screen: the envelope's return address fills in: [your tool's bounce domain]. A hard-bounced letter comes back to it and drops onto video 4's mailroom desk, inside the tool's building. A soft one loops once around the queue shelf before it comes back.
Whose address is it? By default, not yours. Your email marketing tool sends through its own servers, so the return address is on its domain. Every time a message hard bounces, the notice goes there, and the tool deals with it on its own. Soft bounces usually go through its retries first.
04 · Never to the address they see · 1:20
On screen: a stack of Sally's envelopes, each turned over. Every return address is different in its middle part, bounce-abc123, bounce-…, bounce-…. A returned letter lands on one of them, and a thin line runs from it to one campaign card and one subscriber dot.
Your bounces don't come back to the address your readers see. They go to that long one in the header. Many tools make it up, a new one for each message, so when a bounce comes back it knows exactly which campaign, and which subscriber, it belongs to.
05 · Why it matters: SPF checks the envelope · 1:39
On screen: chip 2 lights. The SPF guest list at the gate, called back. The gate reads the envelope's return address, [your tool's bounce domain], finds it on a list, and a green tick lands on the tool's name. Sally's From on the letter inside gets no tick at all.
Why does it matter whose domain it is? Because SPF, the guest list your domain publishes, is checked against the return address. Not the From. So when your tool's domain is on the envelope, SPF is checking your tool. It can pass. But what passed is their name, not yours.
06 · Why it matters: alignment · 1:58
On screen: two labels on the same envelope, the visible From: send-more.example and the checked [your tool's bounce domain], sliding toward each other and not lining up. An amber SPF: not aligned tag. Then a DKIM seal on the envelope lights green, DKIM: aligned. Gloss card: alignment · the check that the domain a reader sees in the From line matches the domain that passed the authentication.
And that's where DMARC comes in. DMARC looks for alignment. The domain that passed has to match the From domain your readers see. Your tool's name doesn't match yours, so SPF can't count toward a DMARC pass. DKIM can still save you. But it's worth getting both right.
07 · How to make it yours · 2:16
On screen: chip 3 lights. The envelope's return address rewrites itself: bounce.send-more.example. Behind it, one DNS record card, CNAME small in mono, with an arrow to the tool's building, where video 4's desk still sorts the letters. A settings card: Sending domains · Authentication. Gloss card: bounce domain · your own subdomain on the return address, pointed at your tool so it still handles the bounces.
How do you make it yours? Set up a custom bounce domain. A subdomain you control, like bounce dot your brand. You add one record in your DNS that points to your tool's bounce system. Where? Most tools have it in account settings, under sending domains or authentication. And your tool still handles every bounce. You're just putting your name on the envelope.
08 · Check yours · 2:40
On screen: Sally's inbox, one of her own emails opened, show original. The raw header from the hook, the Return-Path line lit, the end of it circled: [your tool's bounce domain] in amber, then (on the after pose) send-more.example in green. A small card: reviewmyemails.com/tools/email-headers.
Check yours today. Send yourself one of your emails, and open its raw header. Find the Return-Path line. Does it end in your domain, or your tool's? Our free Email Header Analyzer pulls the header apart for you. And if an SPF check is failing, a misaligned bounce domain is often why.
09 · Recap · 2:59
On screen: the envelope with its two addresses, the tick on the tool's name, the two labels, then the rewritten bounce.send-more.example. All three chips lit.
The short version. The return-path is the return address on the envelope, where every bounce goes. By default it's your tool's, often a new one for each message. SPF checks it, and DMARC wants it to match your From. Find yours in the raw header, and if it isn't your domain, set up a custom bounce domain.
10 · Close · 3:21
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 6, no subscribe ask.
Put your name on the envelope, and check the list. With Review My Emails, the dead addresses come out first, so fewer bounces come back at all. Your SPF and your alignment are still yours to fix. Set this up for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... are bounce codes standardized across the industry?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-009.003.002-return-path-bounce-domain.md
00 · An address that isn't hers (hook)
What is a return-path or bounce domain?
the title, Lora, large: "What is a return-path or bounce domain?" A raw header, mono, most lines greyed. One line lights: Return-Path: <bounce-abc123@[your tool's bounce domain]>. Beside it, Sally's own From: sally@send-more.example, and the two don't match. Three numbered chips, the VO's words: 1 what it is · 2 why it matters for your sender checks · 3 how to make it yours. Chips 2 and 3 grey.
two addresses on one message, not matching. Reveals: (1) the header, (2) the Return-Path line lights, (3) the From beside it, (4) the chips.
concept email-header (the envelope turning to show the written lines on its back).
H1 the wrong belief ("my email comes from my address"), H2 her own header, H3 title word for word.
01 · Brought to you by, woven in
Almanac ids in this scene: 009.003.002, 015.001.001
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
009.003.002 "This is where undeliverable mail bounces back to". 015.001.001 "we'll flag what's safe to send to and what to suppress".
one sentence, 21 words, brand said here and in the close only.
02 · Two sender addresses
Almanac ids in this scene: 009.003.002, 009.003.003, 009.008.008
What it is
playlist 1 video 5's two servers talking, called back small. The first line of their conversation writes the return address onto the envelope. Only then do From and Subject follow.
an order of three, the return address first. Reveals: (1) the return address, (2) From, (3) Subject.
the conversation picture from playlist 1 video 5, called back.
009.008.008 "It's set during the SMTP conversation, specifically by the MAIL FROM command, before any of the readable headers like From or Subject are even transmitted."
the command name is for the description only (P7).
03 · Whose it is, by default
Almanac ids in this scene: 009.003.002
What it is
the envelope's return address fills in: [your tool's bounce domain]. A hard-bounced letter comes back to it and drops onto video 4's mailroom desk, inside the tool's building. A soft one loops once around the queue shelf before it comes back.
one return address, the tool's. Reveals: (1) the address fills in, (2) the hard one lands on the desk, (3) the soft one loops first.
video 4's mailroom desk, playlist 1 video 4's queue shelf, called back.
009.003.002 "your ESP routes mail through their servers, so by default the return-path is something like bounces.youresp.com. Every time a message hard-bounces, the notification goes to that address and your ESP processes it automatically." / "Soft bounces are temporary (mailbox full, server timeout) and may route through the return-path but typically trigger retry logic before returning a failure."
"email marketing tool", never "ESP" (V5). The answer's example domain is not shown.
04 · Never to the address they see
Almanac ids in this scene: 009.008.008
The address you never see
a stack of Sally's envelopes, each turned over. Every return address is different in its middle part, bounce-abc123, bounce-…, bounce-…. A returned letter lands on one of them, and a thin line runs from it to one campaign card and one subscriber dot.
one return address per envelope, all different. The line picks out one pair. Reveals: (1) the stack turns over, (2) the addresses differ, (3) the line to campaign and subscriber.
the envelope from scene 02, many at once.
009.008.008 "It doesn't bounce back to the address your subscribers see in the From field." / "That long, unique address isn't your actual email. It's a tracking address your ESP generated so it can match the bounce notification back to the right campaign and subscriber." / "use unique Return-Path addresses per message so their systems can automatically process bounces and suppress the right contacts."
T3, the one twist, and T1 (why the address is long).
05 · Why it matters: SPF checks the envelope
Almanac ids in this scene: 009.003.002, 009.008.008
Why it matters for your sender checks
chip 2 lights. The SPF guest list at the gate, called back. The gate reads the envelope's return address, [your tool's bounce domain], finds it on a list, and a green tick lands on the tool's name. Sally's From on the letter inside gets no tick at all.
one tick, on the wrong name. Reveals: (1) the gate reads the back, (2) the tick lands on the tool, (3) Sally's From stays bare.
concept spf (a guest list held at the gate), called back from the SPF video.
009.003.002 "it's what receiving servers use to run your SPF check." / "it means your SPF record is technically aligned to your ESP's domain, not yours." 009.008.008 "So if your ESP sends on your behalf using their own bounce domain, SPF is checking their domain, not yours. That's fine for SPF to pass".
SPF is called back with one line, the SPF video owns it (S6). No SPF record syntax (P7).
06 · Why it matters: alignment
Almanac ids in this scene: 009.003.003, 009.008.008
Why it matters for your sender checks
two labels on the same envelope, the visible From: send-more.example and the checked [your tool's bounce domain], sliding toward each other and not lining up. An amber SPF: not aligned tag. Then a DKIM seal on the envelope lights green, DKIM: aligned. Gloss card: alignment · the check that the domain a reader sees in the From line matches the domain that passed the authentication.
two labels that don't line up, one seal that does. Reveals: (1) the labels slide, (2) the amber tag, (3) the DKIM seal lights.
concept alignment (two labels sliding until they line up or do not), concept dkim (the seal), both from the registry.
009.008.008 "For SPF to contribute to a DMARC pass, the Return-Path domain needs to match your From domain at the organizational level. If your ESP routes bounces through their own domain and you haven't set up a custom bounce domain, SPF alignment will fail under DMARC. DKIM can still save you, but it's worth getting both right." 009.003.003 "When the two domains don't align, DMARC can fail even if SPF passes."
DMARC and DKIM are named, not taught, each has its own video. The gloss drops the registry's word "actually" (V10), meaning unchanged.
07 · How to make it yours
Almanac ids in this scene: 009.003.002
How to make it yours
chip 3 lights. The envelope's return address rewrites itself: bounce.send-more.example. Behind it, one DNS record card, CNAME small in mono, with an arrow to the tool's building, where video 4's desk still sorts the letters. A settings card: Sending domains · Authentication. Gloss card: bounce domain · your own subdomain on the return address, pointed at your tool so it still handles the bounces.
one address rewritten, one record, one arrow. Reveals: (1) the address rewrites, (2) the record and its arrow, (3) the settings card.
the envelope from scene 02, video 4's desk. The DNS record card: no picture yet.
009.003.002 "For DMARC alignment, you'll usually want your return-path on a subdomain you control. Something like bounce.yourbrand.com." / "Setting up a custom bounce domain means adding a CNAME record in your DNS that points to your ESP's bounce processing infrastructure." / "support this in their account settings under sending domains or authentication. The CNAME does the actual routing, so your ESP still handles the bounce processing. You're just claiming the domain for your brand."
the record's exact values go in the description, not the VO (P7). No tool named (the answer names three, held back). "Bounce domain" gets its own gloss because the title uses it.
no bounce-domain row. Proposed as new, with the line above.
08 · Check yours
Almanac ids in this scene: 009.008.008
How to make it yours
Sally's inbox, one of her own emails opened, show original. The raw header from the hook, the Return-Path line lit, the end of it circled: [your tool's bounce domain] in amber, then (on the after pose) send-more.example in green. A small card: reviewmyemails.com/tools/email-headers.
one line, one ending, amber then green. Reveals: (1) the raw header, (2) the circle on the ending, (3) the analyzer card.
concept email-header, called back from the hook.
009.008.008 "When you're troubleshooting authentication failures, checking the Return-Path in your raw headers is one of the first things to do. SPF failures are often just a misaligned or misconfigured bounce domain. You can pull the full headers and check with our free Email Header Analyzer".
T2 (where, and what to look for), T5 (the action), T7 (our tool). "Show original" is the idea of opening the raw header, not a named provider's menu. "Send yourself one" is how to get a raw header of your own mail, framing, not an Almanac fact.
09 · Recap
What to remember
the envelope with its two addresses, the tick on the tool's name, the two labels, then the rewritten bounce.send-more.example. All three chips lit.
callbacks only.
callbacks only (S5).
10 · Close
Your name, and a clean list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: video 6, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: Partner programme · 15%, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says out loud that a clean does not fix SPF or alignment (hard content rules, S10). The partner line follows part 2 video 4's form. Totals: 12 scenes. 595 spoken words (counted 2026-09-30, Q sweep). About 3:35 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V057Are bounce codes standardized across the industry?
waiting on YTOpen questions for YT
- End screen Settled by the Video PM 2026-09-29: playlist 2, "Keeping a list healthy".
- C40: "how far can you trust the enhanced code?", numbered by the PM 2026-09-29.
- Registry: a new enhanced-status-code row.
00 · Three lines, one failure? (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what's standard · 2 what isn't · 3 how to read a bounce anyway. Chips 2 and 3 grey.
Three things answer it. What's standard. What isn't. And how to read a bounce anyway, even when the words don't help.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Whatever words a server uses, a bounce still costs you, which is why Review My Emails checks every address before it can bounce.
02 · What's standard: the first number · 0:39
On screen: chip 1 lights. Playlist 1's Diagnostic Code slip, called back. Its top line is a printed form, the same on every note. Three digits light in their colours, one per click: 2 = delivered (green), 4 = try again later (amber), 5 = stop trying (coral).
Start with what's standard. Every mail server follows the same rules for the three-digit code. A two means it was delivered. A four, a temporary failure, try again later. A five, a permanent failure, stop trying. Every serious mail server respects that. So a five, from anywhere, is permanent.
03 · What's standard: the second layer · 0:57
On screen: the slip's second printed box: 5.1.1. Each digit lights with a small label, one per click: 5 permanent · 1 addressing · 1 bad mailbox. Gloss card: enhanced status code · the longer code like 5.1.1, which adds the category and the exact reason to the first digit.
Then there's a second layer, the enhanced status code. Five point one point one. Read it in three parts. The first digit matches the class, five is permanent. The second is the category, one is addressing. The third is the exact condition, one is a bad mailbox. So on paper, it means the same everywhere.
04 · What isn't: the words · 1:18
On screen: chip 2 lights. The slip's bottom half is handwritten, and it rewrites itself per click: The email account that you tried to reach does not exist · User unknown · …plus the provider's own reference code. The printed 550 5.1.1 above it never moves.
And that's where the standard ends. After the code, every provider writes whatever it wants. One big provider says the email account you tried to reach does not exist. A small company's server just says user unknown. Another adds its own reference codes on top. Same reason. Totally different words.
05 · Why that trips up your tool · 1:37
On screen: video 4's mailroom desk, called back, with a small word-filter on it: does not exist. Three notes come in. The first matches and drops into hard. The other two, Mailbox unavailable and No such user here, slide past the filter into a grey bin marked ?.
Why does that matter? Because a lot of bounce readers match the words, not just the code. Say your tool looks for does not exist. Then a bounce that says mailbox unavailable, or no such user here, slips past it. And you end up with a pile of bounces sitting in an ambiguous bucket.
06 · How to read one: three layers · 1:58
On screen: chip 3 lights. The slip splits into three stacked layers, lit top to bottom, each with a tag: trust it · usually reliable · a hint, not a rule. The handwritten line from scene 04 slides under the printed code and underlines it, rather than replacing it.
How do you read one, then? In layers. First, the three-digit code. Five is hard, four is soft and worth a retry. That part you can trust. Second, the enhanced code, if there is one. That's usually reliable. Third, the words. They're your fastest clue. But a clue. Use them to confirm the code, not to decide on their own.
07 · Vague on purpose · 2:21
On screen: the slip from scene 06. A curtain draws itself across the bottom layer (no hand, T11), leaving only rejected · policy. Then the top digit flickers: a 4, amber, while behind the curtain a coral permanent tag shows through, faintly.
Sometimes the vagueness is on purpose. Some big mailbox providers hide the real reason. If they told every sender exactly which spam signal tripped, spammers would just tune their mail to dodge it. So you get a general category. Sometimes even a soft code, for a problem that won't go away. Even the number isn't always the whole story.
08 · Where to look when it's vague · 2:43
On screen: Sally's tool shows a one-line preview, bounced · policy. Behind it, the full bounce unfolds, most lines grey, one long reply line lit. A small card: reviewmyemails.com/tools/email-headers.
Where do you look when the reason is hidden? Start with the full bounce. The whole reply, buried in the header, sometimes says more than the preview your email marketing tool shows you. Our free Email Header Analyzer pulls it apart for you.
09 · What to do with the grey bin · 2:59
On screen: the grey ? bin from scene 05 tips out. Each note is laid on the three-layer slip from scene 06, and most of them drop into a proper tray once the printed code is read.
And that grey bin of bounces you can't place? Don't leave it. Export the raw bounce lines, the full replies, not just your tool's labels, and read them in layers. If there are a lot of them, that's worth digging into.
10 · Recap · 3:15
On screen: the printed form, the three digits of 5.1.1, the changing handwritten line, the curtain, the header. All three chips lit.
Here's the order. The number is standard, a five is permanent anywhere. The enhanced code is usually reliable. The words are a hint, different at every provider. Read in that order. And when a provider keeps it vague on purpose, open the full reply in the header.
11 · Close · 3:33
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: playlist 2, Keeping a list healthy (Video PM, 2026-09-29), opening on V006, no subscribe ask.
Read the number first, and check the list before it bounces. Review My Emails takes out the addresses that were never going to work. A clean won't make a provider explain itself. Can't place a bounce? Bring it to our free SOS hotline. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what does user unknown mean?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.016.005-are-bounce-codes-standardized.md
00 · Three lines, one failure? (hook)
Almanac ids in this scene: 015.016.005
Are bounce codes standardized?
three numbered chips, the VO's words: 1 what's standard · 2 what isn't · 3 how to read a bounce anyway. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept bounce (M-15, M-18), three at once.
015.016.005 "Some say 550 5.1.1. Some say 550 Mailbox does not exist. One from a corporate server just says User unknown. Are any of these the same thing?" / "the number is standardized. The text is not."
H4, H5, split from 00 so each stays under 70 words (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The previous scene's picture holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29): one spoken sentence that grows out of the topic, woven into the narration, small logo in the corner.
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit". 015.001.001 "we'll flag what's safe to send to and what to suppress".
one sentence, 23 words, brand said here and in the close only.
02 · What's standard: the first number
Almanac ids in this scene: 015.016.005
What's standard
chip 1 lights. Playlist 1's Diagnostic Code slip, called back. Its top line is a printed form, the same on every note. Three digits light in their colours, one per click: 2 = delivered (green), 4 = try again later (amber), 5 = stop trying (coral).
three digits, three colours, one printed form. Reveals: (1) the form, (2) to (4) one digit each.
the Diagnostic Code slip (proposed in playlist 1). smtp-reply-code is gloss tier.
015.016.005 "Every mail server follows SMTP standards that define three code families. A 2xx means delivery succeeded. A 4xx means a temporary failure (try again later). A 5xx means a permanent failure (stop trying). That structure comes from RFC 5321 and every serious mail server respects it."
the four and the five are callbacks from playlist 1 (S6). "Permanent" is said, never "suppress it": a five can be a block (hard content rules). The standard's name goes in the description (P7).
03 · What's standard: the second layer
Almanac ids in this scene: 015.016.005
What's standard
the slip's second printed box: 5.1.1. Each digit lights with a small label, one per click: 5 permanent · 1 addressing · 1 bad mailbox. Gloss card: enhanced status code · the longer code like 5.1.1, which adds the category and the exact reason to the first digit.
one code, three parts lit in order. Reveals: (1) the box, (2) to (4) one digit each.
the Diagnostic Code slip. No registry row for the enhanced code, proposed below.
015.016.005 "a second layer called enhanced status codes ... These look like 5.1.1 and add more detail. The first digit mirrors the SMTP class (5 is permanent), the second points to the category (1 is addressing), and the third is the specific condition (1 is bad destination mailbox). So 550 5.1.1 is technically the same across providers: the address doesn't exist."
"on paper" keeps the answer's "technically" (V12). Playlist 1 video 1's middle-number key is called back, not re-taught (S6).
04 · What isn't: the words
Almanac ids in this scene: 015.016.005
What isn't
chip 2 lights. The slip's bottom half is handwritten, and it rewrites itself per click: The email account that you tried to reach does not exist · User unknown · …plus the provider's own reference code. The printed 550 5.1.1 above it never moves.
one printed line held still, one handwritten line changing three times. Reveals: (1) to (3) one wording each.
the Diagnostic Code slip.
015.016.005 "That's where standardization ends. After the code, providers write whatever they want. Gmail might say 'The email account that you tried to reach does not exist.' A corporate server running its own filtering might just say 'User unknown.' Outlook adds its own proprietary identifiers on top". / "Same underlying reason for rejection, totally different message text."
the providers are not named (the answer names two). The proprietary code is drawn as a placeholder, not the answer's example, so no provider is identified.
05 · Why that trips up your tool
Almanac ids in this scene: 015.016.005
What isn't
video 4's mailroom desk, called back, with a small word-filter on it: does not exist. Three notes come in. The first matches and drops into hard. The other two, Mailbox unavailable and No such user here, slide past the filter into a grey bin marked ?.
one filter, one match, two misses. The grey bin fills. Reveals: (1) the filter, (2) the match, (3) the two misses into the grey bin.
video 4's desk. The grey bin: no picture yet.
015.016.005 "many bounce parsers rely on matching message text, not just the code. If your ESP or your own code is looking for specific phrases like 'does not exist' to classify a bounce, it'll miss rejections that say 'Mailbox unavailable' or 'No such user here.' You end up with a bunch of bounces sitting in an ambiguous bucket."
not a repeat of playlist 1 video 3's twist (a code read wrong). Here the code is ignored and the words don't match.
06 · How to read one: three layers
Almanac ids in this scene: 015.002.025, 015.016.005
How to read a bounce anyway
chip 3 lights. The slip splits into three stacked layers, lit top to bottom, each with a tag: trust it · usually reliable · a hint, not a rule. The handwritten line from scene 04 slides under the printed code and underlines it, rather than replacing it.
three layers, the trust in each one lower than the one above. Reveals: (1) to (3) one layer each, (4) the words underline the code.
the Diagnostic Code slip, in layers.
015.016.005 "Look at the 3-digit SMTP code first. 5xx is a hard bounce. 4xx is soft (and worth retrying before giving up). This part you can trust." / "Check the enhanced code if there is one. 5.1.1 or 5.1.2 tells you why the address failed with more precision. This part is usually reliable." / "Treat the message text as a hint, not a rule. It adds context, but it varies by provider. Use it to confirm what the code already told you, not to make the classification yourself." 015.002.025 (playlist 1) "That's your fastest clue."
the answer's "5xx is a hard bounce" is voiced as "five is hard", and scene 02 already said a five is about permanence, not always the address. This joins the playlist 1 line to this answer, so the two don't read as a contradiction.
07 · Vague on purpose
Almanac ids in this scene: 015.016.005, 015.016.008
Vague on purpose
the slip from scene 06. A curtain draws itself across the bottom layer (no hand, T11), leaving only rejected · policy. Then the top digit flickers: a 4, amber, while behind the curtain a coral permanent tag shows through, faintly.
the three layers, the bottom one covered, the top one showing the wrong colour. Reveals: (1) the curtain, (2) the general category, (3) the amber 4 over a coral tag.
the Diagnostic Code slip. The curtain: no picture yet.
015.016.005 "some providers deliberately obscure rejection reasons. Gmail in particular sometimes returns a soft bounce code for what is effectively a permanent problem, or gives you a vague rejection to avoid revealing how their filtering works. So even the codes aren't always the full story." 015.016.008 "If Gmail told every sender exactly which spam signal triggered a rejection, spammers would just tune their emails to dodge that specific trigger." / "Usually a general category (spam, policy violation, authentication failure)".
T3, the one twist. "Some big mailbox providers" for the answer's named provider. "Sometimes" kept, not tightened (V12).
08 · Where to look when it's vague
Almanac ids in this scene: 015.016.008
Vague on purpose
Sally's tool shows a one-line preview, bounced · policy. Behind it, the full bounce unfolds, most lines grey, one long reply line lit. A small card: reviewmyemails.com/tools/email-headers.
one preview line against the full reply behind it. Reveals: (1) the preview, (2) the full reply, (3) the analyzer card.
concept email-header (the envelope showing the lines on its back).
015.016.008 "Sometimes the full SMTP response buried in the header has more detail than the preview your ESP shows you. Our free Email Header Analyzer can pull that apart quickly."
"email marketing tool", never "ESP" (V5). The answer's other steps (authentication, a provider's dashboard, the blocklist checker) are playlist 1 video 1 and this series' video 3, not repeated (S6).
09 · What to do with the grey bin
Almanac ids in this scene: 005.006.015, 015.016.005
How to read a bounce anyway
the grey ? bin from scene 05 tips out. Each note is laid on the three-layer slip from scene 06, and most of them drop into a proper tray once the printed code is read.
the grey bin empties into the trays. Reveals: (1) the bin tips, (2) the notes read in layers, (3) the trays fill.
the desk and trays from video 4.
005.006.015 "Check whether 'hard bounce,' 'soft bounce,' and 'block' are as granular as you need, or whether you need to export raw bounce logs for deeper analysis." 015.016.005 "If you're seeing a lot of ambiguous bounces you can't classify cleanly, that's worth digging into."
T5, the action.
10 · Recap
What to remember
the printed form, the three digits of 5.1.1, the changing handwritten line, the curtain, the header. All three chips lit.
callbacks only.
callbacks only (S5).
11 · Close
Almanac ids in this scene: 015.016.005
Read it, or ask us
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: playlist 2, Keeping a list healthy (Video PM, 2026-09-29), opening on V006, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). Backed by 015.016.005 "Our SOS hotline is free if you want a second pair of eyes on a specific bounce pattern." Totals: 13 scenes. 622 spoken words (counted 2026-09-30, Q sweep). About 3:45 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V058What is bounce ratio tracking?
waiting on YTOpen questions for YT
- C45: pick option A, B, or keep "plays without it".
- Registry: "no picture yet" for the cake, the export sheet and the trend line.
- Tool idea (T7): a free bounce-export slicer (paste your bounce export, see it by domain, provider and month).
00 · One number, looks fine (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 slice it by provider · 2 slice it by where the address came from · 3 watch it over time. Chips 2 and 3 grey.
Three cuts do it. Slice it by provider. Slice it by where the address came from. And watch it over time.
01 · Brought to you by, woven in · 0:26
On screen: no cut away and no ad break. The grid holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every coral dot in that grid is an address that didn't work, and Review My Emails finds those before your next send.
02 · One number hides things · 0:35
On screen: a small callback card from part 2: bounce rate and hard bounce rate, two lines. Then the grid is drawn as a cake, seen from the top, one even colour. Gloss card: bounce ratio tracking · your bounce rate, cut into slices and watched over time.
Your bounce rate is the share of your mail that comes back, and it's worth keeping hard bounces apart from soft ones, because they tell you different things. Bounce ratio tracking takes that further. You cut the number into slices and watch each slice over time. One number tells you something's wrong. The slices tell you where.
03 · Cut one: by provider · 0:57
On screen: a bounce export, mono, three rows: bo.unce@coral-cove.invalid, sunk@shipwreck.invalid, wren@mailbx.invalid. A lamp lights the part after each @. The rows fold into a small table, one row per domain, a count beside each. Then a tab in a tool menu lights: reports · by domain.
Open question: What a bunch of bounces at one provider points to (C45).
Where do you get this? Your email marketing tool lets you export the bounces, with the address on every row. Take the part after the @. That's the domain. A simple pivot table does the rest. And check your tool's reports first. Many already break bounces down by domain.
04 · Cut two: by where it came from · 1:34
On screen: chip 2 lights. The grid is re-cut into three rows, signup form, import, another app. The import row holds most of the coral. A small arrow points from that row back to a door marked where it came in.
Cut two. Slice by where the address came from. Did this batch come from a signup form, an import, or another app? Source matters, because it tells you where your data problems start. One source keeps sending you addresses that bounce? Fix it there, not after every send.
05 · Cut three, the slow creep · 1:53
On screen: the six-month line gets one sharp spike. The spike opens like a drawer, and inside is one campaign card, new import, its coral dots spilling out.
And a spike? A spike in one campaign usually points to that send. A bad segment, a newly imported list, or a targeting mistake. So isolate that send, and look at where its addresses came from.
06 · Alerts that fit you · 2:24
On screen: the trend line with a soft band drawn around its usual level, labelled your normal. One amber soft-bounce spike pokes out of the band on one day, and a small bell rings. A second, borrowed band, someone else's, sits higher and does not ring.
Now set alerts, but set them to your own normal. A soft bounce spike on a single day can mean you've hit a limit with a big provider. And those limits vary with how much you send and your history. So a number that works for someone else might be noise for you.
07 · Your first run, today · 2:44
On screen: one envelope goes in through a door marked accepts everything, and the door closes. Hold. No coral dot appears in the grid. Then the checking desk lamp finds the same address and tags it amber, catch-all.
But slices only show what comes back. On a domain that says yes to every address, real or made up, a dead one usually never bounces. It never lands in any slice, however you cut it.
08 · Recap · 3:16
On screen: the cake from scene 02, cut three ways at once. All three chips lit.
Pull it together. One number says something's wrong. The slices say where. Slice by provider, and by where the address came from. Watch the line over time, the slow creep as much as the spike. And set alerts to your own normal.
09 · Close · 3:32
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Bounces, part 5, video 2, no subscribe ask.
Slice the number before you trust it, and keep the source clean. Review My Emails finds the addresses no slice will ever show you. A clean won't change how a provider sees you. Want us to do the whole list? That's RME Clean. Or clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how to test bounce handling accuracy?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.015.007-bounce-ratio-tracking.md
00 · One number, looks fine (hook)
Almanac ids in this scene: 015.015.007
What is bounce ratio tracking?
three numbered chips, the VO's words: 1 slice it by provider · 2 slice it by where the address came from · 3 watch it over time. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the dot grid (part 2 video 4).
015.015.007 "you're measuring what fraction of your sent emails bounce, and you're watching that number over time." / "Segment your tracking by domain or ISP."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The grid holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a clean fixes a provider's view of you (hard content rules).
was three sentences, now one of 22 words. Brand said here and in the close only.
02 · One number hides things
Almanac ids in this scene: 015.013.004, 015.015.007
What it is
a small callback card from part 2: bounce rate and hard bounce rate, two lines. Then the grid is drawn as a cake, seen from the top, one even colour. Gloss card: bounce ratio tracking · your bounce rate, cut into slices and watched over time.
one number becomes a cake with layers. Reveals: (1) the callback card, (2) the cake from the top, (3) the gloss card.
the dot grid as a cake. The cake: no picture yet.
015.015.007 "Why track them separately? Because they tell you different things." / "Bounce ratio tracking is simple in concept but powerful in practice". 015.013.004 "Grouping bounces by domain or ISP turns a single bounce rate number into diagnostic signal."
part 2 video 4 owns the rate and the two numbers (S6), one line here.
03 · Cut one: by provider
Almanac ids in this scene: 015.013.004, 015.013.005, 015.015.007
Slice it by provider
a bounce export, mono, three rows: bo.unce@coral-cove.invalid, sunk@shipwreck.invalid, wren@mailbx.invalid. A lamp lights the part after each @. The rows fold into a small table, one row per domain, a count beside each. Then a tab in a tool menu lights: reports · by domain.
three rows fold into a count per domain. Reveals: (1) the export, (2) the part after the @ lit, (3) the table, (4) the reports tab.
an export sheet. No picture yet.
015.013.004 "from each bounced address, pull the part after the @ symbol. That's your domain." / "A simple pivot table grouped by domain is usually enough for the analysis." / "some platforms (including most modern ESPs) provide per-domain bounce breakdowns in their reporting dashboards. Check your ESP's analytics section before building anything custom."
no provider named and no rate voiced (N6). What the thin column means is the GAP below, so the VO stops at "look first" (G2).
T2, where it sits. "Many" is looser than "most modern", allowed (V12 forbids only tighter). Addresses from the demo library, suppress examples on .invalid (V7).
04 · Cut two: by where it came from
Almanac ids in this scene: 015.015.007
Slice it by where the address came from
chip 2 lights. The grid is re-cut into three rows, signup form, import, another app. The import row holds most of the coral. A small arrow points from that row back to a door marked where it came in.
three sources, one holding most of the coral. Reveals: (1) the three rows, (2) the coral bunches in one, (3) the arrow back to the door.
the dot grid, sliced by source.
015.015.007 "Track by list source too. Did this batch come from a web form, an import, or an API? Source matters because it tells you where your data quality issues are." / "Identify which list sources produce clean addresses (form signups might be better than purchased lists)."
"another app" for "an API", plainer. Which row holds the coral is a drawn example, not a claim about imports.
05 · Cut three, the slow creep
Almanac ids in this scene: 015.013.005, 015.015.007
Watch it over time
the six-month line gets one sharp spike. The spike opens like a drawer, and inside is one campaign card, new import, its coral dots spilling out.
one spike, one campaign behind it. Reveals: (1) the spike, (2) the drawer opens, (3) the campaign card.
the trend line.
015.013.005 "Spike in a single campaign: usually a bad segment, a new imported list, or a targeting error. Isolate the send and investigate the source."
T3, the one twist. The two readings come from two answers and do not conflict (a collection change, or aging), so both are voiced. No rate is said (N6).
"usually" is kept from the answer (V12).
06 · Alerts that fit you
Almanac ids in this scene: 015.015.007
Watch it over time
the trend line with a soft band drawn around its usual level, labelled your normal. One amber soft-bounce spike pokes out of the band on one day, and a small bell rings. A second, borrowed band, someone else's, sits higher and does not ring.
one band that fits, one that doesn't. Reveals: (1) the band, (2) the spike, (3) the bell, (4) the borrowed band stays silent.
the trend line.
015.015.007 "A sudden spike in soft bounces on a specific day might mean you hit a reputation threshold with a major ISP. Those thresholds vary by your sending volume and history, so adjust them to your baseline."
the answer's two alert levels are not voiced (N6, C4, C16). "Can mean" keeps the answer's "might mean" (V12).
07 · Your first run, today
Almanac ids in this scene: 015.015.007, 021.002.013
The one you never see
one envelope goes in through a door marked accepts everything, and the door closes. Hold. No coral dot appears in the grid. Then the checking desk lamp finds the same address and tags it amber, catch-all.
a dot that never turns coral. Reveals: (1) the envelope goes in, (2) the grid stays unchanged, (3) the lamp tags it.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. "Tends to jump out" is softer than "immediately", allowed (V12).
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
never says a clean fixes a provider's view of you. The close says so.
moved before the recap as 07b (Q3) and reworded from this video's own slices (Q1, Q2). The only catch-all idea in Bounces part 5 (V059 and V060 dropped theirs).
08 · Recap
What to remember
the cake from scene 02, cut three ways at once. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Slice it, then keep it clean
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Bounces, part 5, video 2, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, the done-for-you clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question, "How to test bounce handling accuracy?" (S8). Totals: 14 scenes. 617 spoken words (counted 2026-09-30, Q sweep). About 3:43 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V059How to test bounce handling accuracy?
waiting on YTOpen questions for YT
- Registry: "no picture yet" for the sorting machine, the tray, the log and the score card.
- Tool idea (T7): the bounce-code lookup idea (YT, R-list) would make scene 07's monthly read faster.
00 · It says it's working (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 send to known outcomes · 2 compare the code with the label · 3 check who got suppressed. Chips 2 and 3 grey.
Three checks will answer it. Send to known outcomes. Compare the code with the label. And check who got suppressed.
01 · Brought to you by, woven in · 0:23
On screen: no cut away and no ad break. The machine holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A sorter only sorts what comes back, so Review My Emails works one step earlier, on the list itself, before you send.
02 · Three ways it breaks quietly · 0:32
On screen: the machine, three quiet faults, one per click: a teal envelope into the coral pot, a coral envelope slipping past the pot back onto the list, and a soft envelope sent down the hard chute. Gloss card, a callback: bounce processor · the part of a sending system that reads bounces and acts on them without a person doing it.
Why test at all? Because a bounce processor that's set up wrong fails in silence. It suppresses good addresses. It lets bad ones through. Or it mixes up a temporary delay with a permanent failure. Nothing flashes red. The errors just stack up, send after send.
03 · Check one: send to known outcomes · 0:50
On screen: four envelopes go in, one per click, each with its expected note: bo.unce@coral-cove.invalid with 5.1.1 · hard, a full mailbox with 4.2.2 · soft, a reputation block with 5.7.x · block, and a no-mail-server domain with a note that reads depends · write it down.
What goes in the tray? An address that doesn't exist. That should come back as a hard bounce. A full mailbox, which should come back soft. A block over reputation. And an address at a domain with no mail server record. What comes back there depends on the receiving side, so write down what came back.
04 · The auto-reply · 1:26
On screen: a fifth envelope, otto.responder@lighthouse-letterpress.example, note not a bounce · keep. It comes back out of the machine with a small away tag. The machine hesitates over the coral pot. Hold.
Put one more in the tray. An address that only ever auto-replies. Mail comes back from it, but it isn't a bounce. The person is there. They're just away. So if your tool suppresses it, you've found a fault that would cost you a real subscriber.
05 · Check two: compare the code with the label · 1:44
On screen: the tray splits in two, sandbox and real. A mailbox on send-more.example is created, then crossed out. Two providers, drawn as plain doors, answer the same envelope, one with soft, one with hard.
One catch. Some tools label sandbox bounces differently from real ones. So run a second pass with real addresses you control, like a mailbox on your own domain that you then delete. Real providers have their own habits. Some send a soft bounce where others send a hard one, for the same problem.
06 · Check three: who got suppressed · 2:22
On screen: a small score card, three lines lit one per click: right label · good ones suppressed · bad ones left on. Each has a tally, drawn from the log above: 4 of 5 · 1 · 0.
Then give it a score. Three questions. How many test bounces got the right label? How many good addresses got suppressed when they shouldn't have? And how many bad ones were left on the list when they should have come off?
07 · Make it a monthly habit · 2:55
On screen: a month calendar, one page turning per click. On each page, a small random scoop of real bounce slips. One slip, from a server drawn as an old grey box, carries an unfamiliar code in mono, and it slides into the wrong chute.
A test only proves the sorter worked that day. So make it a habit. Each month, pull a random handful of real bounces, say fifty to a hundred, and read the raw codes against the labels. Real mail brings odd cases. An old company mail server can send a code your tool has never seen, and it quietly lands in the wrong bucket.
08 · Recap · 3:19
On screen: the sorting machine, every test envelope in its right place, the auto-reply outside the pot. All three chips lit.
The whole test. Feed the sorter bounces you already know the answer to, and include an auto-reply. Put the raw code next to the label. Check who landed on the suppression list. Score it. Then do a small sample every month.
09 · Close · 3:35
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Bounces, part 5, video 3, no subscribe ask.
Test the sorter before you trust its green light. With Review My Emails, the list gets checked first, so there's less for it to sort. If the sorter is set up wrong, that fix is still yours. Log makes no sense? Our free SOS hotline is there. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is an email bounce loop?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.013.001-test-bounce-handling-accuracy.md
00 · It says it's working (hook)
Almanac ids in this scene: 015.013.001
How to test bounce handling accuracy?
three numbered chips, the VO's words: 1 send to known outcomes · 2 compare the code with the label · 3 check who got suppressed. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the sorting machine. No picture yet.
015.013.001 "You set up bounce handling, your ESP says it's working, and you trust it. But how do you actually know it's classifying bounces correctly?"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The machine holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a clean fixes a broken sorter.
was three sentences, now one of 22 words. Brand said here and in the close only.
02 · Three ways it breaks quietly
Almanac ids in this scene: 015.013.001
Why test it
the machine, three quiet faults, one per click: a teal envelope into the coral pot, a coral envelope slipping past the pot back onto the list, and a soft envelope sent down the hard chute. Gloss card, a callback: bounce processor · the part of a sending system that reads bounces and acts on them without a person doing it.
three faults, one light that stays green. Reveals: (1) to (3) one fault each, (4) the light still green.
concept bounce-processor (gloss tier), drawn as the sorting machine.
015.013.001 "A misconfigured bounce processor quietly suppresses valid addresses, lets bad ones through, or mixes up a temporary deferral with a permanent failure. Left unchecked, those errors stack up fast."
"temporary delay" for "temporary deferral", plainer. Part 4 video 2 glossed the processor, so the card is a callback (S6).
03 · Check one: send to known outcomes
Almanac ids in this scene: 015.013.001
Send to known outcomes
four envelopes go in, one per click, each with its expected note: bo.unce@coral-cove.invalid with 5.1.1 · hard, a full mailbox with 4.2.2 · soft, a reputation block with 5.7.x · block, and a no-mail-server domain with a note that reads depends · write it down.
four envelopes, four notes, one note that is a question. Reveals: (1) to (4) one envelope each.
the tray. Codes in mono.
015.013.001 "A non-existent address (expect a hard bounce, typically a 550 5.1.1 "user not found" response)" / "A full mailbox (expect a soft bounce, typically a 452 or 4.2.2 code)" / "A domain with no MX record (expect a DNS failure bounce)" / "A reputation-based rejection (expect a block bounce, usually a 5.7.x code)".
playlist 1 owns the codes (S6), they sit on screen only. The fifth case is scene 04.
R4 (YT, 2026-09-29): a domain with no MX record, "it depends on the receiving side".
04 · The auto-reply
Almanac ids in this scene: 015.013.001
Send to known outcomes
a fifth envelope, otto.responder@lighthouse-letterpress.example, note not a bounce · keep. It comes back out of the machine with a small away tag. The machine hesitates over the coral pot. Hold.
one envelope that comes back but must stay out of the pot. Reveals: (1) the envelope, (2) the away tag, (3) the hover over the pot.
the sorting machine. The demo address is the library's auto-reply address (V7).
015.013.001 "An auto-responder address (this should NOT trigger a suppression)" / "Did the auto-responder trigger a suppression when it shouldn't have?"
T3, the one twist. "They're just away" is the picture of an auto-reply, not a claim about why.
05 · Check two: compare the code with the label
Almanac ids in this scene: 015.013.001, 015.013.002
Compare the code with the label
the tray splits in two, sandbox and real. A mailbox on send-more.example is created, then crossed out. Two providers, drawn as plain doors, answer the same envelope, one with soft, one with hard.
one problem, two different answers. Reveals: (1) the split tray, (2) the deleted mailbox, (3) the two doors answer differently.
the tray. The two doors: part 2 video 3's row of doors, called back.
015.013.001 "Some ESPs classify sandbox bounces differently than production ones, so you may need to run a second pass with real addresses you control (a domain you own where you can delete a mailbox, for example)." 015.013.002 "Some ISPs return soft bounces where others return hard ones for the same underlying problem. Simulation can't capture that diversity."
T2, where the code and the label sit. Which row goes amber is a drawn example.
"some tools" keeps the answer's "Some ESPs" (V12). No provider named.
06 · Check three: who got suppressed
Almanac ids in this scene: 015.013.001
Check who got suppressed
a small score card, three lines lit one per click: right label · good ones suppressed · bad ones left on. Each has a tally, drawn from the log above: 4 of 5 · 1 · 0.
three tallies from the five test rows. Reveals: (1) to (3) one line each.
the score card.
015.013.001 "What percentage of test bounces were labeled the right type?" / "How many valid addresses got suppressed when they shouldn't have?" / "How many invalid addresses were not suppressed when they should have been?"
the answer's false-positive level is not voiced (N6). The tallies match scene 05's drawn log (one amber row of five) and scene 06's one wrongly suppressed soft bounce (N4, N5).
07 · Make it a monthly habit
Almanac ids in this scene: 015.013.001
Make it a habit
a month calendar, one page turning per click. On each page, a small random scoop of real bounce slips. One slip, from a server drawn as an old grey box, carries an unfamiliar code in mono, and it slides into the wrong chute.
one scoop a month, one odd slip. Reveals: (1) the calendar, (2) the scoop, (3) the odd slip, (4) the wrong chute.
the sorting machine.
015.013.001 "One-off testing only tells you your system worked on that day. Build a habit of pulling a random sample of recent bounces (say, 50-100 per month) and reviewing the raw SMTP codes manually against the classifications your ESP assigned." / "A response from a legacy corporate mail server might return a non-standard code your ESP has never seen before and quietly drops into the wrong bucket."
T5, the action. "Say fifty to a hundred" keeps the answer's "say", an example, not a rule (V9). "Can send" keeps "might return" (V12).
08 · Recap
What to remember
the sorting machine, every test envelope in its right place, the auto-reply outside the pot. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Test the sorter, then clean the list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Bounces, part 5, video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question, "What is an email bounce loop?" (S8). Totals: 14 scenes. 629 spoken words (counted 2026-09-30, Q sweep). About 3:47 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V060What is an email bounce loop?
waiting on YTOpen questions for YT
- Registry: "no picture yet" for the answering machines, the bounce log and the forwarding cards.
- End card: the partner programme URL is written as reviewmyemails.com/partner from the team's notes.
00 · The error that answers itself (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 how two servers end up answering each other · 2 why it's rare now · 3 where you'll still find one. Chips 2 and 3 grey.
Three parts to it. How two servers end up answering each other. Why it's rare now. And where you'll still find one.
01 · Brought to you by, woven in · 0:22
On screen: no cut away and no ad break. The log holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Most bounces aren't loops at all, they're addresses that don't work, and Review My Emails weeds those out before you send.
02 · How it starts · 0:30
On screen: chip 1 lights. Two answering machines on one desk, A and B. A coral slip goes from A to B. B's light blinks and an amber slip goes back. A returns a coral slip. The tape between them starts to wind. Gloss card: bounce loop · two mail systems stuck replying to each other's error messages.
How does it start? Server A sends a bounce to server B. Server B has an auto-reply, so it answers the bounce. Server A can't deliver that answer, so it bounces it back. B answers again. That's a bounce loop. Two answering machines, each leaving a message for the other.
03 · Why it's rare now · 0:50
On screen: a message header, mono. A stack of Received: lines grows upward, one per click, a small hop counter beside it ticking 1, 2, 3. Then one line lights amber: Auto-Submitted: auto-replied. B's machine reads it, and its reply button greys out.
What does it look at? Two things in the header. Every server that handles a message adds a received line, so you read them from the bottom up, one per hop. Too many hops, and something's circling. And an automatic reply carries a label saying so. A well-behaved auto-reply won't answer mail that has it.
04 · The fix is silent · 1:27
On screen: the tape between the machines stops mid-wind. A pair of scissors snips it. The slip in the middle, the original message, falls into a bin marked dropped. Neither machine's light blinks. Hold.
When a server spots the loop, it doesn't warn anyone. After two or three rounds on the same path, it stops and drops the message. Silently. So the loop ends, but the message it started with never arrives.
05 · Where you'll still find one: forwarding · 1:42
On screen: machine A gets a new sticker, auto-reply to bounces, drawn in amber. A coral bounce arrives, A answers, B answers the answer. A small shield marked email marketing tool blocks the sticker from sticking. Behind it, a home-built box without the shield keeps winding tape.
The other place is a setup that auto-replies to bounces. If the bounce came from a system that also replies to everything, you've built a loop. Modern email marketing tools won't let you set that up. Home-built sending setups sometimes miss it.
06 · What to do · 2:20
On screen: a checklist card, one line per click: no auto-replies to bounces · no forwarding circles · loop detection on. Then the repeating log from scene 00, with an arrow to check forwarding first. Then a card: reviewmyemails.com/tools/email-headers, the header from scene 03b inside it.
Two rules, then. Never send automatic replies to bounces. Never forward in a circle. If you run your own mail server, check loop detection is on. It usually is. On an email marketing tool, you're most likely fine. Seeing that repeating log? Check forwarding first. Want to see the hops? Our free Email Header Analyzer shows what's being sent.
07 · Recap · 2:42
On screen: the two answering machines, switches on, the tape snipped. All three chips lit.
Short and simple. A bounce loop is two systems answering each other's errors. Servers now spot it and drop the message without a word. When you still see one, it's usually forwarding in a circle, or an auto-reply to a bounce. Check those two first.
08 · Close · 2:59
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 4, no subscribe ask.
Break any circle you find, and keep the list honest. Review My Emails clears out the addresses that bounce for real, before you send. The forwarding rule is still yours to fix. Set up email for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is SMTP handshake validation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-001.001.071-email-bounce-loop.md
00 · The error that answers itself (hook)
Almanac ids in this scene: 001.001.071
What is an email bounce loop?
three numbered chips, the VO's words: 1 how two servers end up answering each other · 2 why it's rare now · 3 where you'll still find one. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
a log. The answering machines arrive in scene 02.
001.001.071 "If you're seeing repeated bounce messages in your logs that look like they're replying to each other".
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The log holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a clean stops a loop.
was three sentences, now one of 21 words. Brand said here and in the close only.
02 · How it starts
Almanac ids in this scene: 001.001.071
How two servers end up answering each other
chip 1 lights. Two answering machines on one desk, A and B. A coral slip goes from A to B. B's light blinks and an amber slip goes back. A returns a coral slip. The tape between them starts to wind. Gloss card: bounce loop · two mail systems stuck replying to each other's error messages.
two machines, one tape that grows by one slip per turn. Reveals: (1) A to B, (2) B answers, (3) A bounces it back, (4) the gloss card.
two answering machines. No picture yet.
001.001.071 "is what happens when two mail servers or automated systems get stuck in an infinite cycle of replying to each other's error messages. Server A sends a bounce to Server B. Server B's auto-responder replies to that bounce. Server A treats that reply as invalid and bounces it back. Server B replies again. And so on."
T10, the simile, carried through the video.
03 · Why it's rare now
Almanac ids in this scene: 001.001.071, 009.010.010, 023.015.005
Why it's rare now
a message header, mono. A stack of Received: lines grows upward, one per click, a small hop counter beside it ticking 1, 2, 3. Then one line lights amber: Auto-Submitted: auto-replied. B's machine reads it, and its reply button greys out.
a stack of hop lines, a count that climbs, one label that stops the reply. Reveals: (1) the header, (2) to (4) one hop each, (5) the label, (6) the button greys.
concept email-header.
001.001.071 "Modern MTAs prevent this by checking the Received header hop count and the RFC 3834 Auto-Submitted field". 023.015.005 "Received headers (read bottom to top) trace every SMTP hop". 009.010.010 "covers automatic responses like out-of-office messages" / "And the rule most autoresponders follow is simple: don't reply to anything with an Auto-Submitted value other than "no." That's what breaks the loop."
"almost never" kept word for word (V12).
T2, where it sits and how to read it. "Well-behaved" keeps "most autoresponders" (V12), not every one.
04 · The fix is silent
Almanac ids in this scene: 001.001.071
Why it's rare now
the tape between the machines stops mid-wind. A pair of scissors snips it. The slip in the middle, the original message, falls into a bin marked dropped. Neither machine's light blinks. Hold.
two or three turns of tape, one snip, one message in the bin. Reveals: (1) the tape stops, (2) the snip, (3) the message falls, (4) no light blinks.
the answering machines.
001.001.071 "After a message bounces 2-3 times along the same path, the server stops processing it and drops it silently." / "dropping the message silently after 2 or 3 loops."
T3, the one twist. "Never arrives" follows from "drops it silently", the dropped message is the one in the loop.
05 · Where you'll still find one: forwarding
Almanac ids in this scene: 001.001.071
Where you'll still find one
machine A gets a new sticker, auto-reply to bounces, drawn in amber. A coral bounce arrives, A answers, B answers the answer. A small shield marked email marketing tool blocks the sticker from sticking. Behind it, a home-built box without the shield keeps winding tape.
one sticker that sticks on one setup and not the other. Reveals: (1) the sticker, (2) the loop starts, (3) the shield, (4) the home-built box.
the answering machines.
001.001.071 "and the bounce itself came from another automated system that replies to everything, you've got a loop. Modern ESPs won't let you set this up, but custom SMTP setups sometimes miss it."
"email marketing tool" for "ESPs" (V5). No tool named (the answer names two). "Home-built sending setups" for "custom SMTP setups", plainer.
06 · What to do
Almanac ids in this scene: 001.001.071, 009.010.010
What to do
a checklist card, one line per click: no auto-replies to bounces · no forwarding circles · loop detection on. Then the repeating log from scene 00, with an arrow to check forwarding first. Then a card: reviewmyemails.com/tools/email-headers, the header from scene 03b inside it.
three rules, one first check, one tool. Reveals: (1) to (3) one rule each, (4) the arrow, (5) the tool card.
the checklist card (part 4 video 3's clipboard, called back). Concept email-header.
001.001.071 "never send automated replies to bounce messages, never forward a mailbox to itself or create circular forwarding chains, and if you're running your own mail server, make sure loop detection is enabled (it usually is by default). If you're using an ESP, you're almost certainly fine." / "check your forwarding rules and any automated reply settings. Most of the time, it's a forwarding misconfiguration rather than a true server-to-server loop." 009.010.010 "can show you exactly what's being sent and whether anything looks off."
T5, the action. T7, our tool.
07 · Recap
What to remember
the two answering machines, switches on, the tape snipped. All three chips lit.
callbacks only.
callbacks only (S5).
08 · Close
Break the circle, then keep it clean
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the partner programme, 15%, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). Last video of the series, the next video is the first of "Keeping a list healthy, part 4", named by its Almanac question, "What is SMTP handshake validation?" (S8). Totals: 12 scenes. 531 spoken words (counted 2026-09-30, Q sweep). About 3:12 at 166 words a minute, plus scene breaks. Every scene is 20 to 70 words (S2).
V061What is SMTP handshake validation?
waiting on YTOpen questions for YT
- GAP-J: the SPF checker link at the end of 005.003.009.
- Registry: the smtp-handshake gloss is "asking the receiving server, without sending, whether a mailbox exists", which is the checker's use.
- Tool idea (T7): no free tool of ours shows a handshake for one address.
00 · It never sent a thing (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what the checker says at the door · 2 what the server answers · 3 when the answer isn't clean. Chips 2 and 3 grey.
Three parts to it. What the checker says at the door. What the server answers. And what happens when the answer isn't clean.
01 · Brought to you by, woven in · 0:27
On screen: no cut away and no ad break. The door holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Asking before you send is the whole idea, and Review My Emails asks about every address on your list before it goes out.
02 · Every email knocks first · 0:37
On screen: chip 1 lights. V008's door, now with a small hatch at eye level (no drawn doorman, T11). An envelope walks up and four speech lines appear one per click, mono: HELO · MAIL FROM · RCPT TO · DATA. The hatch light blinks at each. Gloss card, a callback: SMTP handshake · the short conversation two mail servers have before a message is handed over.
Start with a normal email. Before any message goes in, your mail server has a short conversation with the receiving one. Hello. Who it's from. Who it's for. Then the message itself. That's the SMTP handshake. Think of a doorman checking IDs before he lets your email through the door.
03 · The checker stops before the letter · 1:00
On screen: the same four lines. The checker's probe card walks up instead of an envelope. HELO, MAIL FROM, RCPT TO light one per click. DATA stays grey and a small stop sign drops in front of it. The probe card turns and walks away, nothing handed over.
A checker walks through the same first steps. It says hello. It names a sender. It asks, is there a mailbox by this name? And then it stops. It never gets to the message part. Nothing is sent. The server's replies tell it what it needs.
04 · What the server answers · 1:24
On screen: a magnifying glass passes over bo.unce@coral-cove.invalid and every character ticks green, written properly. Then the probe card walks it to the door and comes back coral, 550.
Why go to the door at all? Because a quick look at the shape of an address only checks that it's written properly. You can have a perfectly formatted address that doesn't exist. Only the server knows that. So a mailbox check asks the one who'd know.
05 · When the answer isn't clean · 2:07
On screen: chip 3 lights. V008's server that plays dead, called back: the door stays shut, a small clock turns, the probe card comes back amber, try later. Then the same list is drawn twice side by side, and three rows differ between the two runs.
But not every server answers plainly. Some say maybe, try later. Some stall on purpose. Why? Because to them, a checker asking at every door looks just like a spammer testing a list before a blast. So they refuse to confirm or deny. That's why the same list, checked twice, can come back different.
06 · The twist: a yes that turns into a bounce · 2:33
On screen: the hatch lights 250 at the probe card, green. The card walks off happy. Then, later, an envelope with the same address goes through the door, and a coral slip comes back out, delayed, on a small later clock.
Some big servers, though, say yes at the door to almost any name you ask about. The no only comes later, after the letter's been handed over, or once it's been queued. So a yes at the door isn't always a yes.
07 · What to do with an unknown · 2:55
On screen: one envelope goes in through a door marked accepts everything, and the door closes. Hold. No slip comes back. Then the checking desk lamp finds the same address and tags it amber, catch-all.
And one kind of door answers yes to any name at all, invented ones included. A dead address there usually never bounces, and a handshake can't tell. When we clean a list, we label those for what they are.
08 · Recap · 3:33
On screen: the door, the hatch, the probe card walking away. All three chips lit.
Here's the short of it. A handshake check walks the first steps of a delivery and stops before the letter. A yes or a no comes back in a blink. Some servers won't say, and some say yes and bounce later. Treat an unknown as caution, not delete, and check it again another day.
09 · Close · 3:50
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 4, video 2, no subscribe ask.
Ask the door before you send, and trust an unknown for what it is. Nobody can promise you the inbox, but a clean takes out addresses that were never going to work. Want the whole list done for you? That's RME Clean. Or clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is engagement- based segmentation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.003.009-smtp-handshake-validation.md
00 · It never sent a thing (hook)
Almanac ids in this scene: 005.003.009
What is SMTP handshake validation?
three numbered chips, the VO's words: 1 what the checker says at the door · 2 what the server answers · 3 when the answer isn't clean. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the results sheet. "Deliverable", never "Valid" (V6).
005.003.009 "Ever wonder how validators actually confirm your email address exists without sending a real message?"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The door holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a check guarantees the inbox.
02 · Every email knocks first
Almanac ids in this scene: 001.001.035
What the checker says at the door
chip 1 lights. V008's door, now with a small hatch at eye level (no drawn doorman, T11). An envelope walks up and four speech lines appear one per click, mono: HELO · MAIL FROM · RCPT TO · DATA. The hatch light blinks at each. Gloss card, a callback: SMTP handshake · the short conversation two mail servers have before a message is handed over.
four lines, four blinks. Reveals: (1) the hatch, (2) to (5) one line each, (6) the gloss card.
concept smtp-handshake (gloss tier). V008's probe card at a door, called back, with a hatch. The doorman is spoken only, never drawn (T11).
001.001.035 "An SMTP handshake is the conversation your mail server has with the receiving server before it can deliver a message." / "checking IDs before letting your email through the door." (the answer's door-guard simile, the one word for the guard left out of this quote, red-zone term) / "Your server connects to the receiving server and says hello (literally, with a command called HELO or EHLO)." / "Then your server announces who the email is from (MAIL FROM), who it's going to (RCPT TO), and finally sends the message content (DATA)."
the gloss card widens the registry's line to the full conversation, since this video owns it. Flagged for the registry in Open.
03 · The checker stops before the letter
Almanac ids in this scene: 005.003.009
What the checker says at the door
the same four lines. The checker's probe card walks up instead of an envelope. HELO, MAIL FROM, RCPT TO light one per click. DATA stays grey and a small stop sign drops in front of it. The probe card turns and walks away, nothing handed over.
three of four lines lit, the fourth never reached. Reveals: (1) to (3) one line each, (4) the stop sign, (5) the card walks away.
the probe card at the door.
005.003.009 "It says hello (HELO), claims it's sending from your domain (MAIL FROM), and asks if a specific mailbox exists (RCPT TO). Then it stops. It doesn't actually send a message. Instead, the server's responses tell the validator everything." / "without ever issuing DATA or sending a message."
T2, the conversation shown line by line and where it stops. "Tell it what it needs" is softer than "tell the validator everything", allowed (V12 forbids only tighter), and it leaves room for scene 05.
04 · What the server answers
Almanac ids in this scene: 005.003.008, 005.003.009
What the server answers
a magnifying glass passes over bo.unce@coral-cove.invalid and every character ticks green, written properly. Then the probe card walks it to the door and comes back coral, 550.
all green on the shape, one coral at the door. Reveals: (1) the glass, (2) the green ticks, (3) the walk to the door, (4) the coral 550.
the probe card at the door. The magnifying glass: V924's syntax check, called back.
005.003.008 "They confirm an address follows the rules defined in RFC 5322" / "But you can have a perfectly formatted address that doesn't exist" / "This is the real deal because the server is the source of truth."
the answer's "20-30%" bounce figure for syntax-only checks is not voiced (N6).
05 · When the answer isn't clean
Almanac ids in this scene: 005.003.008, 005.003.014
When the answer isn't clean
chip 3 lights. V008's server that plays dead, called back: the door stays shut, a small clock turns, the probe card comes back amber, try later. Then the same list is drawn twice side by side, and three rows differ between the two runs.
one amber card, then two runs of one list with three rows that don't match. Reveals: (1) the shut door, (2) the clock, (3) the amber card, (4) the two runs, (5) the rows that differ.
concept throttling (M-18, M-15), V008's gate, called back.
005.003.008 "or says 'Maybe, try again later.'" 005.003.014 "the receiving server can stall, defer, or return a vague temporary error instead of a clean yes or no. That stall is called tarpitting, and it's exactly why the same list run through the same validator twice can return different answers." / "They do it because validation traffic looks identical to a spammer harvesting a list before a blast, so the safest default is to refuse to confirm or deny anything."
V008 glossed "throttled", so no new gloss (S6). No provider named (the answer names four).
06 · The twist: a yes that turns into a bounce
Almanac ids in this scene: 005.003.014
When the answer isn't clean
the hatch lights 250 at the probe card, green. The card walks off happy. Then, later, an envelope with the same address goes through the door, and a coral slip comes back out, delayed, on a small later clock.
one green yes, one coral no, a clock between them. Reveals: (1) the green 250, (2) the card leaves, (3) the envelope goes in, (4) the late coral slip.
the probe card at the door, and the Diagnostic Code slip.
005.003.014 "will accept almost any RCPT TO and only bounce later in the DATA phase or after queue processing, which is a different flavor of the same problem: the syntactic check passes, but you still don't know if the mailbox exists."
T3, the one twist. The provider the answer names is not voiced, "some big servers" instead. "Isn't always a yes" keeps inside what the answer says.
07 · What to do with an unknown
Almanac ids in this scene: 005.003.014, 021.002.013
The one you never see
one envelope goes in through a door marked accepts everything, and the door closes. Hold. No slip comes back. Then the checking desk lamp finds the same address and tags it amber, catch-all.
a blank slip, a count of zero. Reveals: (1) the envelope goes in, (2) nothing back, (3) the lamp tags it.
concept catch-all. Myths video 1 owns it (S6).
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce." / "tools will flag these addresses as "catch-all" or "accept-all" rather than "valid" or "invalid", because they genuinely can't verify the mailbox."
T5, the action. "Recently" stands in for the answer's 90 days, which sits inside C30 (N6, G3).
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a validation topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
08 · Recap
What to remember
the door, the hatch, the probe card walking away. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Ask the door, then keep it clean
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 4, video 2, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, the done-for-you clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question, "What is engagement-based segmentation?" (S8). Totals: 13 scenes, 571 spoken words, about 3:30 of speech and about 4:15 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V062What is engagement-based segmentation?
waiting on YTOpen questions for YT
- C46 and the C30 add: for YT's look.
- Registry: "no picture yet" for the theatre.
- End card: RME Insights has no URL in the team's notes.
00 · Her best fans, in spam (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 sort by what people did, and when · 2 give each group its own send · 3 why the quiet ones cost your best ones. Chips 2 and 3 grey.
Three parts to it. Sort by what people did, and when. Give each group its own send. And why the quiet ones cost your best ones.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The theatre holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Before you sort people by interest, make sure they can get your mail at all, which is what Review My Emails checks.
02 · What you sort by · 0:39
On screen: chip 1 lights. Three small dials beside the stage, one per click: how recently · how often · how far. On "how far", three steps light under one seat: opened · clicked · bought. Gloss card: engagement-based segmentation · choosing who to send to by what they have done with your mail before.
What is it? Engagement-based segmentation splits your list by how people treat your email. Three things. How recently they last did something. How often they do it. And how far they go. Opened, clicked, or bought. Think of your audience. Some lean in. Some drifted off an act ago.
03 · The tiers, and your own clock · 1:03
On screen: one seat, three lights: clicked, replied, bought, all teal. A fourth light, opened, flickers on by itself while the seat stays asleep. A small callback card: the robot opener from the Myths videos.
And what counts as doing something? Lean on clicks, replies and purchases. An open on its own is shaky, because some mail apps load the images in your email automatically, and that's recorded as an open, whether anyone read it or not.
04 · Chip two: a send for each tier, the front rows · 1:48
On screen: the third band gets one clear card, still interested? yes / no, and a few seats light back up. The back band gets one final card, last chance. The seats that stay grey are roped off from the main stage, not removed.
At risk is the group worth a proper win-back. A direct, still interested? With a clear way to say yes. This is the group you can often bring back. The inactive get much less mail. And if one last chance doesn't wake them, take them out of your main sends.
05 · The twist: the back rows cost the front · 2:36
On screen: chip 3 lights. A single gauge above the stage, how people react, averaged across every seat. The grey back rows pull the needle down. Then the front row seats start dropping into the coral spam box from scene 00, one, then two.
The back rows cost the front rows, too. Mailbox providers watch how people react to your mail. Keep sending full campaigns to the inactive, and your average drops. That looks like a list nobody wants. So more of your mail goes to spam. Including the mail to your most engaged subscribers.
06 · The quickest fix · 2:58
On screen: one grey back-row seat. The checking desk lamp swings onto it, and the seat is empty. A tag lands on it, amber, catch-all.
And some of your inactive may not be quiet people at all. On some domains, the server accepts mail for any name, even an invented one, so a dead address there usually never bounces. It just sits in your back row, looking like a sleepy subscriber. A clean finds those.
07 · Recap · 3:37
On screen: the theatre, four bands, the front lit, the back roped off. All three chips lit.
The whole idea, then. Sort by how recently, how often, and how far people go. Lean on clicks. Set the windows to your own rhythm. Check the back row for addresses that were never people. Play to the front rows, win back the ones at risk, and stop performing to seats that stay asleep.
08 · Close · 3:55
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 4, video 3, no subscribe ask.
Sort your list by who's still listening, and stop mailing empty seats. Clicks are up to your content. The seats that were never filled, we take out. Want to see who's still engaged? That's RME Insights. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how do you sync suppression lists across apps?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-006.003.002-engagement-based-segmentation.md
00 · Her best fans, in spam (hook)
Almanac ids in this scene: 006.003.002
What is engagement-based segmentation?
three numbered chips, the VO's words: 1 sort by what people did, and when · 2 give each group its own send · 3 why the quiet ones cost your best ones. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
a theatre audience. No picture yet.
006.003.002 "Sending your full campaign to the inactive tier drags down your average, signals poor list quality, and pushes more mail to spam. Including for your highly engaged subscribers."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The theatre holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a clean raises engagement.
02 · What you sort by
Almanac ids in this scene: 006.003.002
Sort by what people did, and when
chip 1 lights. Three small dials beside the stage, one per click: how recently · how often · how far. On "how far", three steps light under one seat: opened · clicked · bought. Gloss card: engagement-based segmentation · choosing who to send to by what they have done with your mail before.
three dials, three steps. Reveals: (1) to (3) one dial each, (4) the three steps, (5) the gloss card.
concept engagement-segmentation (gloss tier), drawn as the theatre.
006.003.002 "Engagement-based segmentation divides your list by how actively subscribers interact with your email. Recency of last click or open, frequency of interaction over a time window, and depth of engagement (opened only vs. clicked vs. purchased)."
the registry's gloss is used word for word (P5). The older short V930 owns the first split, this video builds the tiers on it (S6).
03 · The tiers, and your own clock
Almanac ids in this scene: 006.003.002, 006.003.003, 006.003.004
Sort by what people did, and when
one seat, three lights: clicked, replied, bought, all teal. A fourth light, opened, flickers on by itself while the seat stays asleep. A small callback card: the robot opener from the Myths videos.
three steady lights, one that lies. Reveals: (1) to (3) the steady lights, (4) the flicker, (5) the callback card.
concept open-rate (rail), the Myths videos' picture.
006.003.004 "Clicks are the defining metric, not opens, because Apple Mail Privacy Protection (since iOS 15) preloads images and records opens whether or not the recipient actually read the message". 006.003.002 "opened only vs. clicked vs. purchased".
"lean on clicks" is what both sides of C46 agree counts. "Shaky" does not say an open never counts. The mail app is not named. The Myths videos own why (S6).
04 · Chip two: a send for each tier, the front rows
Almanac ids in this scene: 006.003.002
Give each group its own send
the third band gets one clear card, still interested? yes / no, and a few seats light back up. The back band gets one final card, last chance. The seats that stay grey are roped off from the main stage, not removed.
a few seats relit, the rest roped off. Reveals: (1) the win-back card, (2) seats relight, (3) the last-chance card, (4) the rope.
the theatre. The last-chance card is part 3 video 3's sunset, called back.
006.003.002 "A dedicated re-engagement campaign is worth running. A direct "still interested?" with a clear opt-in to continue. This is the group you can often recover with the right message." / "Send significantly less to this group. If a sunset campaign (a final "this is your last chance to re-confirm") doesn't revive engagement, suppress them from main sends."
"take them out of your main sends" keeps "suppress them from main sends", not deletion (C38 kept out). Part 3 video 3 owns the sunset, V927 owns re-engagement (S6). "Often" kept (V12).
05 · The twist: the back rows cost the front
Almanac ids in this scene: 006.003.001, 006.003.002
Why the quiet ones cost your best ones
chip 3 lights. A single gauge above the stage, how people react, averaged across every seat. The grey back rows pull the needle down. Then the front row seats start dropping into the coral spam box from scene 00, one, then two.
one average, pulled down by the back, paid for by the front. Reveals: (1) the gauge, (2) the needle drops, (3) the front seats drop.
concept sender-reputation (the score gauge), called back.
006.003.002 "mailbox providers track your engagement rate. Sending your full campaign to the inactive tier drags down your average, signals poor list quality, and pushes more mail to spam. Including for your highly engaged subscribers." 006.003.001 "pushes future sends toward the spam folder for engaged recipients too."
T3, the one twist. Two answers say it, the same way.
06 · The quickest fix
Almanac ids in this scene: 006.003.002, 021.002.013
The one you never see
one grey back-row seat. The checking desk lamp swings onto it, and the seat is empty. A tag lands on it, amber, catch-all.
one seat that was never filled. Reveals: (1) the seat, (2) the lamp, (3) it's empty, (4) the tag.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce." / "They're costing you reputation points without giving anything back."
T5, the action. "Can all improve" is softer than "will all improve", allowed (V12), and it keeps clear of an inbox promise. The answer's "90 days" is not voiced (C30 add).
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a list topic (Keeping a list healthy), so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
07 · Recap
What to remember
the theatre, four bands, the front lit, the back roped off. All three chips lit.
callbacks only.
callbacks only (S5).
08 · Close
Play to the front, clean the back
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Keeping a list healthy, part 4, video 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Insights, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question, "How do you sync suppression lists across apps?" (S8). Totals: 13 scenes, 577 spoken words, about 3:31 of speech and about 4:15 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V063How do you sync suppression lists across apps?
waiting on YTOpen questions for YT
- Next video: named by the Q sweep (2026-09-30): V074, 005.010.002.
- Registry: "no picture yet" for the doors, the toggle and the clock.
- End card: the API has no URL in the team's notes.
00 · Unsubscribed, then mailed anyway (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the four things to sync · 2 the ways to move them · 3 test it, then keep watching it. Chips 2 and 3 grey.
Three parts to it. The four things to sync. The ways to move them. And how to test it, then keep watching it.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The doors hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A do-not-send list only works where every app reads it, and Review My Emails checks the addresses themselves before you send.
02 · Why it matters · 0:38
On screen: chip 1 lights. Four doors now, one doorman at each, each with a copy of the list. One copy gets a new coral name. Thin lines try to reach the other three copies. Two of them stay amber, out of date.
Why does it matter? Your suppression list lives inside each app. So when someone opts out, bounces, or complains in one of them, every other connected app needs to know. Miss it, and that's a compliance problem. Depending on where they live, a legal one too.
03 · The four · 0:59
On screen: four coral cards on the list, one per click: unsubscribe · hard bounce · spam complaint · delete my data. The fourth card carries a small callback tag from the Myths video, unsubscribe ≠ delete.
What has to travel? Four things, without exception. Unsubscribes. Hard bounces. Spam complaints. And requests to have someone's data deleted. That last one is its own kind. Unsubscribing isn't deletion, but a deletion request still has to reach every app.
04 · Way one: live · 1:22
On screen: a small robot arm between two doors, carrying names across one at a time. Then a clock face. At 09:00 a name goes coral on one list. The hand sweeps round. An envelope slips out at 14:00. At 00:00 the export finally lands, too late.
No direct link? An automation tool can bridge the gap. It watches one app for new suppressions and writes them into another. Not always instant, but far better than nothing. For older, closed systems, the fallback is an export every day. Mind the gap, though. Unsubscribe at nine in the morning, sync at midnight, and an email can land in between.
05 · Or one list everyone reads · 2:14
On screen: the four doormen put their copies away. One big board goes up in the middle of the hall, one list, and each doorman glances at it before opening his door. Then the board shrinks to a single field on a contact card, do not send · yes.
Bigger teams often skip the copying. They keep one central list, and every app checks it before it sends. Smaller team? One well-kept field in your sales app that every other app respects can do the same job.
06 · The twist: both ways · 2:33
On screen: a door marked receipts gets a coral slip, hard bounce. A line runs from it back to the email tool door, whose copy turns coral too. Then an arrow runs the other way. A single one-way arrow from scene 04 is crossed out and redrawn as a two-headed one.
Sync has to run both ways, too. Say the app that sends your receipts gets a hard bounce. That address belongs on your marketing list's do-not-send too. And the other way round. It isn't just marketing telling everyone else.
07 · Chip three: test it, then watch it · 2:55
On screen: one envelope goes in through a door marked accepts everything, and the door closes. Hold. No coral slip, and every doorman's list stays the same. Then the checking desk lamp finds the same address and tags it amber, catch-all.
But a sync only passes on what something caught. Some domains never turn an address away, not even a made-up one. So a dead address there usually never bounces, and there's nothing to sync. A clean catches those before any app sends.
08 · Recap · 3:39
On screen: the hall of doors, every copy coral in the same places, the two-headed arrows, the bell quiet. All three chips lit.
Here's the checklist. Four things travel, unsubscribes, hard bounces, complaints, and deletion requests. Move them live if you can, bridged or exported if you can't, or keep one list everyone reads. Run it both ways. Then test it, and watch it.
09 · Close · 3:57
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V074, no subscribe ask.
Make every app hear the no, and prove it with a test. Connecting your apps is your job. Taking out addresses that were never going to work is ours. Building your own connections? Our API checks addresses from your apps too. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... when should I run a re-engagement campaign?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-014.012.009-sync-suppression-lists-across-apps.md
00 · Unsubscribed, then mailed anyway (hook)
Almanac ids in this scene: 014.012.009
How do you sync suppression lists across apps?
three numbered chips, the VO's words: 1 the four things to sync · 2 the ways to move them · 3 test it, then keep watching it. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
doors with doormen. No picture yet.
014.012.009 "Imagine someone unsubscribes from your marketing campaign in" / "but your CRM still has them marked as active. Three days later, an automated follow-up goes out from"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The doors hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a clean syncs anyone's lists. The close says so.
02 · Why it matters
Almanac ids in this scene: 014.012.009
The four things to sync
chip 1 lights. Four doors now, one doorman at each, each with a copy of the list. One copy gets a new coral name. Thin lines try to reach the other three copies. Two of them stay amber, out of date.
four copies, one updated, two stale. Reveals: (1) the four doors, (2) the new name, (3) the lines, (4) the two amber copies.
concept suppression-list (M-23, M-24), one copy per door.
014.012.009 "across platforms means making sure that when someone opts out, bounces, or files a spam complaint in one system, every other connected system knows about it immediately." / "That's a compliance problem, and depending on where your contact lives, it could also be a legal one."
R7 (YT, 2026-09-29): one sentence on the law, no law named.
playlist 2 video 2 owns the suppression list, the gloss is a callback (S6).
03 · The four
Almanac ids in this scene: 014.012.009
The four things to sync
four coral cards on the list, one per click: unsubscribe · hard bounce · spam complaint · delete my data. The fourth card carries a small callback tag from the Myths video, unsubscribe ≠ delete.
a count of four. Reveals: (1) to (4) one card each, (5) the callback tag.
the list card.
014.012.009 "The four types you need to sync, without exception, are unsubscribes, hard bounces, spam complaints, and legal deletion requests (like GDPR erasure)."
no law named (R7). Myths video 20 owns why unsubscribing is not deletion (S6), one line here. The on-screen ≠ is a symbol, not a dash.
04 · Way one: live
Almanac ids in this scene: 014.012.003, 014.012.009
The ways to move them
a small robot arm between two doors, carrying names across one at a time. Then a clock face. At 09:00 a name goes coral on one list. The hand sweeps round. An envelope slips out at 14:00. At 00:00 the export finally lands, too late.
one arm, then one clock with a fifteen-hour gap. Reveals: (1) the arm, (2) the clock, (3) the 09:00 name, (4) the 14:00 envelope, (5) the midnight export.
doors with doormen. The clock: no picture yet.
014.012.009 "can bridge the gap when there's no direct API integration. You can build a flow that watches for new suppressions in one tool and writes them to another. It's not always instant, but it's far better than doing nothing." / "are the fallback for older or more closed systems. Pull a suppression export from each platform daily" / "If someone unsubscribes at 9am and your sync runs at midnight, they could receive an email in between."
T2, where the switch sits. "Email tools and sales apps" for "ESPs and CRMs" (V5).
the two automation tools the answer names are not voiced. The 14:00 envelope is a drawn example inside the answer's window (09:00 to midnight, fifteen hours, N5).
05 · Or one list everyone reads
Almanac ids in this scene: 014.012.009
The ways to move them
the four doormen put their copies away. One big board goes up in the middle of the hall, one list, and each doorman glances at it before opening his door. Then the board shrinks to a single field on a contact card, do not send · yes.
four copies become one board, then one field. Reveals: (1) the copies go away, (2) the board, (3) the glances, (4) the single field.
doors with doormen.
014.012.009 "is what larger teams often build when they're managing multiple sending systems. One central list, all systems check against it before sending." / "For smaller teams, a well-maintained CRM field that every system respects can do the same job."
playlist 2 video 2's "keep your own master file" is the same idea from the other side, not re-taught (S6). The two platforms the answer names are not voiced.
06 · The twist: both ways
Almanac ids in this scene: 014.012.009
The ways to move them
a door marked receipts gets a coral slip, hard bounce. A line runs from it back to the email tool door, whose copy turns coral too. Then an arrow runs the other way. A single one-way arrow from scene 04 is crossed out and redrawn as a two-headed one.
one arrow becomes two. Reveals: (1) the receipts bounce, (2) the line back, (3) the copy turns coral, (4) the two-headed arrow.
doors with doormen.
014.012.009 "First, suppression sync needs to go both ways. If your transactional sender has a hard bounce, that address should be suppressed in your marketing platform too (and vice versa)."
T3, the one twist. "The app that sends your receipts" for "your transactional sender", plainer.
07 · Chip three: test it, then watch it
Almanac ids in this scene: 014.012.007, 014.012.009, 021.002.013
The one you never see
one envelope goes in through a door marked accepts everything, and the door closes. Hold. No coral slip, and every doorman's list stays the same. Then the checking desk lamp finds the same address and tags it amber, catch-all.
a slip that never comes, a list that never changes. Reveals: (1) the envelope goes in, (2) the lists stay still, (3) the lamp tags it.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. T2, the test step by step. "Connections time out" for "APIs time out", plainer.
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a list topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
08 · Recap
What to remember
the hall of doors, every copy coral in the same places, the two-headed arrows, the bell quiet. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 005.010.002
One list, every door
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V074, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the API, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10), in new words (Q1). S8: the next video is V074, 005.010.002, named by the Q sweep (2026-09-30) where the batch left it open. The PM can swap it when it sequences the playlists. Totals: 13 scenes, 565 spoken words, about 3:29 of speech and about 4:15 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V070When should I use real-time validation (e.g., API)?
waiting on YTOpen questions for YT
- GAP-M: the answer's blocklist-checker pointer, for #almanac-to-check.
- Registry: "no picture yet" for the gate, the scale and the storeroom.
- End card: the API has no URL in the team's notes.
00 · The order that never arrived (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what it catches · 2 when it pays for itself · 3 when you can skip it. Chips 2 and 3 grey.
Three parts to it. What a check at the form catches. When it pays for itself. And when you can skip it.
01 · Brought to you by, woven in · 0:30
On screen: no cut away and no ad break. The checkout holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every address that bounces costs you more than one lost email, and Review My Emails checks them before they cost you.
02 · What it catches · 0:41
On screen: chip 1 lights. The form now has a gate between the address field and the list behind it. Four cards try the gate, one per click: typo · bot · junk · throwaway. Each one turns coral and is held at the gate. Gloss card: real-time validation · checking an address the moment someone types it, before it joins your list.
What does it catch? Real-time validation checks each address the moment it's typed, before it reaches your list. Typos. Bots. Junk. Throwaway inboxes. And here's why that moment matters. The person is still there. They can fix a typo on the spot, instead of you finding out later from a bounce.
03 · Where it sits · 1:06
On screen: a zoom on the checkout. A small arrow runs from the address field out to a box marked check, and back. A green tick for one address. Then wren@mailbx.invalid again, and a line of text appears under the field in amber: Please check this address. The customer's cursor fixes it. Last, a tag on the form's corner, supports checks?
Where does it sit? Between typing and the button. Your form sends the address off for a check, and the answer comes straight back. A good one goes through. A bad or risky one gets a message asking them to fix it. One catch, though. Your form has to support it. Most email marketing tools do. Some custom builds don't.
04 · When it pays for itself · 1:30
On screen: chip 2 lights. A balance scale beside the gate. On one pan, one small coin, one check. On the other, four weights, one per click: bounce · complaint · reputation · lost customer. The scale tips towards the weights.
When is it worth it? You pay for every check. So weigh it against what a bad address costs you. A bounce. A complaint. A hit to your reputation. A customer who never hears from you. When that costs more than the check, it pays. Few signups a week, high value each, and bounces already hurting? It pays for itself.
05 · The twist: when you can skip it · 1:57
On screen: chip 3 lights. The gate's queue grows until it runs off screen, and the coin pile beside the scale grows with it. The scale tips back the other way. Then the gate stands aside, and a single sweep passes over the storeroom behind it, once, before a campaign envelope goes out.
The busiest forms are where it can pay least. Taking thousands of signups a day, and already running a solid re- engagement workflow? Then checking the whole list before each campaign is cheaper. You still catch the dead weight. Just without paying for every single signup.
06 · Door or storeroom, or both · 2:22
On screen: the whole picture at once: the gate on the left, the storeroom on the right. A label under each, the door and what's inside. A small arrow from messy list points at the storeroom. A small arrow from new form points at the gate.
One check guards the door. The other audits what's already inside. The door check only sees new signups. The audit cleans what you've already got. Most teams use both. Messy list, or data from an old system? Start with the audit. Building a new form from scratch? Start at the door.
07 · What to do · 2:47
On screen: an address on a domain marked accepts everything walks through the gate with a green tick. It sits in the storeroom. Hold. Nothing comes back. Then the checking desk lamp finds it and tags it amber, catch-all.
Some addresses pass every door, though. A few domains accept mail for any name, even one nobody owns, so a made- up address there usually never bounces, and nothing ever tells you. Those are worth finding on the list you already have.
08 · Recap · 3:28
On screen: the gate with its four held cards, the scale tipped, the sweep over the storeroom. All three chips lit.
The short of it. A check at the form catches typos, bots, junk and throwaways while the person can still fix them. It pays when a bad address costs more than the check. On the busiest forms, a check before each campaign can be cheaper. So write down what one bad address costs you, and pick your door.
09 · Close · 3:44
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Validation, part 1, no subscribe ask.
Weigh the check against the cost, and guard the right place. Your form is one door. A clean sorts the list you already have. Want the check at your door too? Our API runs it on every signup. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how can disposable email domains be identified?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.003.004-when-to-use-real-time-validation.md
00 · The order that never arrived (hook)
Almanac ids in this scene: 005.003.004
When should I use real-time validation?
three numbered chips, the VO's words: 1 what it catches · 2 when it pays for itself · 3 when you can skip it. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the signup gate. No picture yet.
005.003.004 "when the cost of a bad address (bounce, complaint, reputation damage, lost customer) exceeds the per-check API fee" / "at the point of capture (signup forms, checkout, lead magnets, gated content)"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The checkout holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a check fixes reputation. The close says what a clean does.
02 · What it catches
Almanac ids in this scene: 005.003.003, 005.003.004
What it catches
chip 1 lights. The form now has a gate between the address field and the list behind it. Four cards try the gate, one per click: typo · bot · junk · throwaway. Each one turns coral and is held at the gate. Gloss card: real-time validation · checking an address the moment someone types it, before it joins your list.
four kinds, each held at one gate. Reveals: (1) the gate, (2) to (5) one card each, (6) the gloss card.
the signup gate, concept email-validation.
005.003.004 "Real-time API validation catches typos, bots, junk addresses, and disposable email addresses before they hit your CRM." / "you'll catch errors instantly, so people can fix typos on the spot rather than getting a bounce email later." 005.003.003 "This catches problems at capture, when they're fresh and the subscriber can correct them themselves."
"throwaway inboxes" for "disposable email addresses", the word V021 uses. Typo capture is V043's, one word here (S6).
03 · Where it sits
Almanac ids in this scene: 005.003.003
What it catches
a zoom on the checkout. A small arrow runs from the address field out to a box marked check, and back. A green tick for one address. Then wren@mailbx.invalid again, and a line of text appears under the field in amber: Please check this address. The customer's cursor fixes it. Last, a tag on the form's corner, supports checks?
one round trip, one tick, one message, one fix. Reveals: (1) the arrow out, (2) the answer back, (3) the tick, (4) the message, (5) the fix, (6) the tag.
the signup gate, zoomed in (N3).
005.003.003 "Real-time validation runs instantly during a form submission or API call." / "Valid? They proceed. Invalid or risky? You show a message asking them to fix it or re-enter." / "it requires your signup form to support validation checks (most ESPs do, but some custom builds don't)."
T2, where it sits and what the person sees. "Email marketing tools" for "ESPs" (V5). The on-screen message is a drawn example, not a quote.
04 · When it pays for itself
Almanac ids in this scene: 005.003.004
When it pays for itself
chip 2 lights. A balance scale beside the gate. On one pan, one small coin, one check. On the other, four weights, one per click: bounce · complaint · reputation · lost customer. The scale tips towards the weights.
one coin against four weights, the tip is the answer. Reveals: (1) the scale, (2) the coin, (3) to (6) one weight each, (7) the tip.
the balance scale. No picture yet.
005.003.004 "when the cost of a bad address (bounce, complaint, reputation damage, lost customer) exceeds the per-check API fee" / "You pay per-check, so it's not cheap at scale. But if you're collecting only a few hundred addresses a week and your bounce rate is already painful, it pays for itself." / "Are you signing up high-value customers where a bad address costs you more than the validation API?"
no price voiced or shown (the answer's "a fraction of a cent" stays in the Almanac). "Few signups a week" keeps the answer's "a few hundred addresses a week" without a number to read as a target (N6).
05 · The twist: when you can skip it
Almanac ids in this scene: 005.003.004
When you can skip it
chip 3 lights. The gate's queue grows until it runs off screen, and the coin pile beside the scale grows with it. The scale tips back the other way. Then the gate stands aside, and a single sweep passes over the storeroom behind it, once, before a campaign envelope goes out.
a queue too long to count, a coin pile that outweighs the weights, one sweep. Reveals: (1) the queue grows, (2) the coins grow, (3) the scale tips back, (4) the sweep.
the signup gate, then the storeroom.
005.003.004 "Skip it for high-volume signups where bulk validation before each campaign is cheaper." / "You're accepting thousands of signups daily and already have a solid re-engagement workflow? Bulk validation before campaigns is cheaper and catches the dead weight without the per-check bill."
T3, the twist. "A solid way to win back or remove quiet subscribers" glosses "re-engagement workflow" in the line itself (P6).
06 · Door or storeroom, or both
Almanac ids in this scene: 005.003.003
When you can skip it
the whole picture at once: the gate on the left, the storeroom on the right. A label under each, the door and what's inside. A small arrow from messy list points at the storeroom. A small arrow from new form points at the gate.
two places, two starting points. Reveals: (1) the two labels, (2) the messy-list arrow, (3) the new-form arrow.
the signup gate and the storeroom, side by side (P2, the gate holds still).
005.003.003 "It's the difference between guarding the door (real-time) versus auditing what's already inside (bulk)." / "But it only works on new signups" / "Bulk validation cleans historical data" / "Most teams use both." / "If your list is already pretty messy or you're inheriting data from an old system, start with bulk. If you're building a new flow from scratch, start with real-time to prevent the mess in the first place."
T10, the Almanac's own simile, carried from here to the close.
07 · What to do
Almanac ids in this scene: 005.003.004, 021.002.013
The one you never see
an address on a domain marked accepts everything walks through the gate with a green tick. It sits in the storeroom. Hold. Nothing comes back. Then the checking desk lamp finds it and tags it amber, catch-all.
one tick that means nothing, one address that never comes back. Reveals: (1) the tick, (2) the hold, (3) the lamp tags it.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. The arrows on the card are symbols, not dashes.
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a validation topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
08 · Recap
What to remember
the gate with its four held cards, the scale tipped, the sweep over the storeroom. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
The door and the storeroom
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Validation, part 1, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the API, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 12 scenes, 562 spoken words, about 3:30 of speech and about 4:05 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V071How can disposable email domains be identified?
waiting on YTOpen questions for YT
- Next video: named by the Q sweep (2026-09-30): V072, 005.001.011.
- Registry: "no picture yet" for the checking desk with lenses and the results card.
- An idea for the PM (T7, not a tool we have): a free "is this a throwaway domain?" check.
00 · Blocked the famous ones, missed the new one (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the four ways it gives itself away · 2 why you need more than one · 3 what a pile of them tells you. Chips 2 and 3 grey.
Three parts to it. The four ways a throwaway domain gives itself away. Why you need more than one. And what a pile of them tells you.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The form holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Throwaway inboxes don't stay open for long, and Review My Emails finds them on your list before you send to them.
02 · Checking a passport · 0:40
On screen: chip 1 lights. The checking desk. The card from the hook lies on it. Four lenses on a swing arm above it, labelled one per click: known list · how its DNS behaves · how new · its record.
A throwaway inbox is a hotel key card that stops working at checkout. Spotting the domain behind it is more like checking a passport. Is it on the list of known fakes? Does the issuer act oddly? How new is it? And what's its record? Four checks.
03 · Lens one: the known list · 0:59
On screen: the first lens swings over the card. The domain after @ lights up. A long scroll unrolls beside the desk, too many lines to read, hundreds. The top lines stay steady. At the bottom, new lines keep appearing, and a frozen copy of the scroll beside it turns amber, last updated: never.
First, the list of known fakes. Check the part after the at sign against a list of known throwaway services. There are hundreds. The big ones don't change much, so this catches the common ones well. But new services start all the time, so a list that never updates goes stale.
04 · Lens two: how its DNS behaves · 1:23
On screen: the second lens swings over. Three made-up variations of the domain appear, one per click, each on .invalid. Three arrows run from them, and all three land on the same single server box, which turns coral. Gloss card: wildcard DNS · a domain set up to accept mail at any name at all, even ones nobody created.
Second, how the domain behaves. Many throwaway services use wildcard DNS. They'll take mail at any made-up name you invent, not just a fixed set. So a checker tries a few random variations. If every one of them points to the same mail server, that's a strong sign it's throwaway machinery.
05 · Lens three: how new it is · 1:51
On screen: the third lens swings over. A small calendar tag on the card reads registered: 2 weeks ago, and turns amber, worth a look. Beside it, a registration record card with most of its lines blacked out, hidden for privacy.
Third, how new it is. Throwaway services often use brand-new domains, or swap them fast to stay off the lists. A domain registered two weeks ago that's already taking email is worth a look. The domain's registration record helps here. Though privacy rules are hiding more of it than they used to.
06 · Lens four, and why one lens isn't enough · 2:16
On screen: chip 2 lights. The fourth lens swings over, and a short file slides out, history: abuse. Then all four lenses swing over the card together. Each lens alone shows a small gap in its view. Together the gaps close and the card turns coral.
Fourth, its record. Anti-spam groups and validation services keep track of domains with a history of abuse, so an address can be flagged on its domain's past alone. So why all four? Each one misses something. A good check at signup runs every one of them at once.
07 · The twist: a pile of them is a message · 2:43
On screen: a throwaway card goes coral and comes back, as before. Then a card on a domain marked accepts everything goes in and never comes back. Hold. The checking desk lamp finds it and tags it amber, catch-all.
A throwaway at least bounces in the end. Some domains never refuse a name, invented or not. So a made-up address there usually never bounces, and it sits on your list for good. A clean finds those too.
08 · Recap · 3:47
On screen: the desk, all four lenses, the coral card, the arrow back to the freebie. All three chips lit.
In short. A throwaway domain gives itself away four ways. It's on a known list. Its DNS takes any made-up name. It's brand new. Or it has a record. No single check sees all of it. And when a pile of them shows up, trace it back to the freebie that brought them in.
09 · Close · 4:03
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V072, no subscribe ask.
Check with all four, and read the pile as a message. Your freebie is yours to fix. The throwaways already on your list, we find. Not sure what's drawing them in? Our SOS hotline is a free call. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how do hygiene issues affect sender reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.007.024-identifying-disposable-domains.md
00 · Blocked the famous ones, missed the new one (hook)
Almanac ids in this scene: 005.007.024
How can disposable email domains be identified?
three numbered chips, the VO's words: 1 the four ways it gives itself away · 2 why you need more than one · 3 what a pile of them tells you. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
concept disposable-provider, the signup card.
005.007.024 "The challenge is that new disposable services launch frequently, so a static list needs regular updates to stay current."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.007.025, 015.001.001
no cut away and no ad break. The form holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.007.025 "the domain or mailbox exists only for a short window, then stops accepting mail." 015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
no lifetime voiced (C29).
02 · Checking a passport
Almanac ids in this scene: 005.007.024
The four ways it gives itself away
chip 1 lights. The checking desk. The card from the hook lies on it. Four lenses on a swing arm above it, labelled one per click: known list · how its DNS behaves · how new · its record.
a count of four lenses. Reveals: (1) the desk, (2) to (5) one lens each.
the checking desk with lenses. No picture yet.
005.007.024 "Disposable email domains are identified through four overlapping methods" / "they're well-known services (Mailinator, TempMail, Guerrilla Mail, 10MinuteMail), they have unusual DNS behaviors, or they show up in maintained blocklists of known throwaway providers."
T10, the passport. The key card is V021's, called back in one line (S6). The passport is a picture for the four checks, not an Almanac claim.
03 · Lens one: the known list
Almanac ids in this scene: 005.007.024
The four ways it gives itself away
the first lens swings over the card. The domain after @ lights up. A long scroll unrolls beside the desk, too many lines to read, hundreds. The top lines stay steady. At the bottom, new lines keep appearing, and a frozen copy of the scroll beside it turns amber, last updated: never.
a scroll of hundreds, a frozen copy that falls behind. Reveals: (1) the lens, (2) the domain lights, (3) the scroll, (4) new lines appear, (5) the frozen copy goes amber.
the checking desk, lens one.
005.007.024 "check the domain part of every email address against a curated database of known disposable providers. There are hundreds of them. The major ones are stable, so this works well for the common services. The challenge is that new disposable services launch frequently, so a static list needs regular updates to stay current."
T1, why a list alone fails. "The part after the at sign" says "domain part" plainly.
04 · Lens two: how its DNS behaves
Almanac ids in this scene: 005.007.024
The four ways it gives itself away
the second lens swings over. Three made-up variations of the domain appear, one per click, each on .invalid. Three arrows run from them, and all three land on the same single server box, which turns coral. Gloss card: wildcard DNS · a domain set up to accept mail at any name at all, even ones nobody created.
three made-up names, one server. Reveals: (1) the lens, (2) to (4) one variation each, (5) the three arrows meet, (6) the gloss card.
the checking desk, lens two, concept mx-record for the server box.
005.007.024 "Many disposable email services set up wildcard DNS, meaning they'll accept mail at any randomly generated domain name (not just a fixed set). Validation tools can detect wildcard DNS patterns by testing multiple variations of the domain. If all variants resolve to the same mail server, it's likely disposable infrastructure."
T1, T9, what the checker is looking for and why it gives the domain away. "A strong sign" keeps the answer's "likely" (V12).
05 · Lens three: how new it is
Almanac ids in this scene: 005.007.024
The four ways it gives itself away
the third lens swings over. A small calendar tag on the card reads registered: 2 weeks ago, and turns amber, worth a look. Beside it, a registration record card with most of its lines blacked out, hidden for privacy.
one date, two weeks old, one record half hidden. Reveals: (1) the lens, (2) the date, (3) the amber tag, (4) the half-hidden record.
the checking desk, lens three.
005.007.024 "Disposable services often use freshly registered domains or rotate through domains rapidly to evade blocklists. A domain registered two weeks ago that accepts email is a flag worth investigating. Domain registration data (WHOIS) is useful here, though it's increasingly restricted by privacy rules."
"worth a look" keeps the answer's "a flag worth investigating", not a verdict (V12). The In short's 30 to 90 days is not voiced (N6). "WHOIS" stays off the VO, the plain words carry it.
06 · Lens four, and why one lens isn't enough
Almanac ids in this scene: 005.007.024
Why you need more than one
chip 2 lights. The fourth lens swings over, and a short file slides out, history: abuse. Then all four lenses swing over the card together. Each lens alone shows a small gap in its view. Together the gaps close and the card turns coral.
four lenses, four gaps, one covered card. Reveals: (1) the fourth lens, (2) the file, (3) all four together, (4) the gaps close, (5) coral.
the checking desk, all four lenses.
005.007.024 "Anti-spam organizations and email validation providers maintain databases of domains with known high abuse rates. Addresses at these domains get flagged based on the domain's history rather than a real-time check." / "a real-time validation tool at the point of signup is your most effective defense. It checks the domain against all of the above methods simultaneously and flags disposables before they enter your list." / "four overlapping methods"
"Each one misses something" draws the answer's "overlapping" and its stale-list and hidden-record lines, not a new claim. The check at signup is video 1's, called back (S6).
07 · The twist: a pile of them is a message
Almanac ids in this scene: 005.007.024, 005.007.025, 021.002.013
The one you never see
a throwaway card goes coral and comes back, as before. Then a card on a domain marked accepts everything goes in and never comes back. Hold. The checking desk lamp finds it and tags it amber, catch-all.
one card that comes back, one that never does. Reveals: (1) the bounce, (2) the card that stays, (3) the lamp tags it.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce." 005.007.025 "Temporary disposables are a hard bounce waiting to happen."
T2, where to look. T5, the action.
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17. "In the end" keeps the temporary kind only: 005.007.025 says the permanent kind "can receive mail indefinitely", so the line says "a throwaway at least bounces in the end" only of the one in the hook.
Q3: moved before the recap. Q2: a validation topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
08 · Recap
What to remember
the desk, all four lenses, the coral card, the arrow back to the freebie. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 005.001.011
Four lenses, one desk
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V072, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: /sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10), in new words (Q1). S8: the next video is V072, 005.001.011, named by the Q sweep (2026-09-30) where the batch left it open. The PM can swap it when it sequences the playlists. Totals: 13 scenes, 581 spoken words, about 3:34 of speech and about 4:10 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V072How do hygiene issues affect sender reputation?
waiting on YTOpen questions for YT
- Registry: "no picture yet" for the two record cards, the dashboard frame and the checker screen.
- End card: the Q sweep made the free blocklist checker the one tool name (Q11).
00 · New server, same spam folder (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the two records · 2 what wears each one down · 3 the way back. Chips 2 and 3 grey.
Three parts to it. The two records. What wears each one down. And the way back, with where to watch it.
01 · Brought to you by, woven in · 0:30
On screen: no cut away and no ad break. The spam folder holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Bad addresses leave marks on your reputation, and Review My Emails checks every one on your list before you send.
02 · Two records, not one · 0:41
On screen: chip 1 lights. Two record cards slide in side by side: the server (an IP-shaped tag, server B) and the name (send-more.example). Two gloss cards, one per click: IP reputation · the part of your reputation that belongs to the server you send from. Domain reputation · the part of your reputation that belongs to your domain name.
Your reputation isn't one number. It's two. Think of a credit score, only you have two files. IP reputation belongs to the server your mail leaves from. Domain reputation belongs to your name, the domain in your From address. Hygiene problems land on both.
03 · What wears down the server's record · 1:05
On screen: chip 2 lights. Coral marks land on the server card, one per click, hard bounce, hard bounce, complaint. Then the card widens into a shared one with three other senders' names on it, and a mark from one of them lands on Sally's side too. Last, a small separate card, dedicated, with only Sally's name.
What wears down the server's record? Hard bounces, again and again. Spam complaints. Over time, they add up. And here's the part people miss. On a shared server, other senders' marks land on your record too. That's one reason big senders pay for a server of their own.
04 · What wears down the name's record · 1:31
On screen: coral marks land on the name card, one per click, complaints, no opens, no clicks. Then the name card grows a little taller than the server card, and a small label sits above it, counts most.
And the name's record? Lots of complaints, and poor engagement. Mail nobody opens or clicks. Providers tie that pattern to your domain. And the name is now the record that counts most at Gmail and Yahoo. Why? It's harder to game than a server.
05 · The twist: the name follows you · 1:57
On screen: back to the hook's swap. The server card flips to a blank teal one, server B, clean. The name card beside it keeps every coral mark. An envelope from the new server still carries @send-more.example, and the name card's marks ride along with it.
Sally's new server came with a clean record. Her name didn't. Moving to a new server doesn't reset your domain's reputation. The marks travel with the name, to every server you'll ever send from.
06 · Why the way back is slow · 2:18
On screen: chip 3 lights. The name card. A long strip of small teal ticks starts to fill beside it, one tick at a time, too slowly to count. The coral marks fade a little only as the strip grows.
What's the way back? First, the honest part. If your reputation is already hurt, cleaning your list won't fix it overnight. Providers need to see good behaviour held for weeks or months before they trust you again. There's no shortcut.
07 · What helps fastest · 2:40
On screen: an envelope goes in through a door marked accepts everything, and the door closes. Hold. No bounce comes back. On the name card, a faint no opens mark appears anyway. Then the checking desk lamp finds the address and tags it amber, catch-all.
Not every bad address leaves a mark you can see, though. Some domains accept any name you send to, even one nobody owns. A made-up address there usually never bounces. It just sits on your list, never opening a thing. A clean finds those.
08 · Recap · 3:44
On screen: the two record cards, the coral marks, the shared card, the clean server card beside the marked name, the strip of teal ticks. All three chips lit.
In a sentence or two. You have two records. The server's, worn down by bounces and complaints, and shared with your neighbours. And the name's, worn down by complaints and poor engagement. A new server won't clear the name. Only steady, clean sending does, so start with the addresses you send to.
09 · Close · 4:00
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Reputation, part 1, no subscribe ask.
Look after the name, because it follows you everywhere. Cleaning can't repair a reputation. It stops bad addresses adding new marks. Worried about a blocklist? Start with our free blocklist checker. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what's the difference between complaint feedback versus bounce feedback?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.001.011-hygiene-issues-sender-reputation.md
00 · New server, same spam folder (hook)
Almanac ids in this scene: 005.001.011
How do hygiene issues affect sender reputation?
three numbered chips, the VO's words: 1 the two records · 2 what wears each one down · 3 the way back. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the two record cards, not yet shown. The server box.
005.001.011 "Moving to a new sending IP does not reset it." / "Your sender reputation is not one number. It is two: your IP reputation and your domain reputation."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.001.011, 015.001.001
no cut away and no ad break. The spam folder holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.001.011 "Consistent hard bounces, spam complaints, and spam trap hits from a given IP degrade its reputation over time." 015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
"a mark" stays general, the answer ties bounces to the server's record (scene 03). Nothing says a check fixes reputation. The close says so.
02 · Two records, not one
Almanac ids in this scene: 005.001.011
The two records
chip 1 lights. Two record cards slide in side by side: the server (an IP-shaped tag, server B) and the name (send-more.example). Two gloss cards, one per click: IP reputation · the part of your reputation that belongs to the server you send from. Domain reputation · the part of your reputation that belongs to your domain name.
a count of two cards. Reveals: (1) the server card, (2) its gloss, (3) the name card, (4) its gloss.
concepts ip-reputation and domain-reputation, the two record cards.
005.001.011 "Your sender reputation is not one number. It is two: your IP reputation and your domain reputation. Hygiene issues weaken both" / "IP reputation reflects the history of the server that sends your mail." / "Domain reputation is tied to your From address and sending domain."
T10, V039's credit score carried on as two files (S6, one line).
03 · What wears down the server's record
Almanac ids in this scene: 005.001.011
What wears each one down
chip 2 lights. Coral marks land on the server card, one per click, hard bounce, hard bounce, complaint. Then the card widens into a shared one with three other senders' names on it, and a mark from one of them lands on Sally's side too. Last, a small separate card, dedicated, with only Sally's name.
marks that add up, one card shared four ways, one card of her own. Reveals: (1) to (3) one mark each, (4) the shared card, (5) the neighbour's mark, (6) the dedicated card.
the server record card, concept dedicated-ip for the last beat.
005.001.011 "Consistent hard bounces, spam complaints, and spam trap hits from a given IP degrade its reputation over time. If you send via a shared IP, other senders on that IP can affect your reputation too. This is one reason high-volume senders use dedicated IPs."
the answer's third signal is not voiced (registry spam-trap, never on a public surface). "Big senders" for "high-volume senders", "a server of their own" for "dedicated IPs" (the registry gloss).
04 · What wears down the name's record
Almanac ids in this scene: 005.001.011
What wears each one down
coral marks land on the name card, one per click, complaints, no opens, no clicks. Then the name card grows a little taller than the server card, and a small label sits above it, counts most.
three marks, one card that grows taller than the other. Reveals: (1) to (3) one mark each, (4) the card grows, (5) the label.
the name record card, concept engagement-signal for the marks.
005.001.011 "If your domain consistently sends to spam traps, generates high complaint rates, or has poor engagement signals, providers associate that pattern with your domain." / "It has become the primary trust signal at Gmail, Yahoo, and other major providers because it is harder to game than IP reputation."
no complaint rate voiced, and the traps are held. "Counts most" keeps "the primary trust signal".
05 · The twist: the name follows you
Almanac ids in this scene: 005.001.011
What wears each one down
back to the hook's swap. The server card flips to a blank teal one, server B, clean. The name card beside it keeps every coral mark. An envelope from the new server still carries @send-more.example, and the name card's marks ride along with it.
one card wiped, one card unchanged. Reveals: (1) the server card flips clean, (2) the name card holds, (3) the envelope carries the marks.
the two record cards (P2, the name card holds still).
005.001.011 "Moving to a new sending IP does not reset it." / "(tied to the From domain, now the primary trust signal at Gmail and Yahoo because it cannot be reset by switching IPs)."
T3, the twist, and the hook paid off. "To every server you'll ever send from" pictures "does not reset it", not a new claim.
06 · Why the way back is slow
Almanac ids in this scene: 005.001.011
The way back
chip 3 lights. The name card. A long strip of small teal ticks starts to fill beside it, one tick at a time, too slowly to count. The coral marks fade a little only as the strip grows.
a strip that fills slowly, marks that fade only with it. Reveals: (1) the strip, (2) the ticks fill, (3) the marks fade.
the two record cards.
005.001.011 "if you clean your list and your reputation is already degraded, improvement takes time. It is not instantaneous. Providers need to see consistent good behavior over weeks or months before they adjust their trust score for your domain. There is no shortcut."
S10, says what cleaning does not do. "Weeks or months" is the answer's own, and holds every C33 figure. The myths video owns why there is no reset date (S6), not re-taught.
07 · What helps fastest
Almanac ids in this scene: 005.001.011, 021.002.013
The one you never see
an envelope goes in through a door marked accepts everything, and the door closes. Hold. No bounce comes back. On the name card, a faint no opens mark appears anyway. Then the checking desk lamp finds the address and tags it amber, catch-all.
no bounce, one quiet mark. Reveals: (1) the envelope goes in, (2) the hold, (3) the faint mark, (4) the lamp tags it.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce." 005.001.011 "has poor engagement signals" (the faint mark is the name card's own signal from scene 04).
T2, where to watch it. T7, our free tool, the answer's own pointer. The checker frame is drawn, not a screenshot, until the PM picks one.
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a list-hygiene topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
08 · Recap
What to remember
the two record cards, the coral marks, the shared card, the clean server card beside the marked name, the strip of teal ticks. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Two records, one name
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Reputation, part 1, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the free blocklist checker, named in scene 07b and the VO above. Q11: one tool name per video, so the blocklist directory is no longer the extra. The PM confirms the checker as an R14 extra, or swaps in /sos.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 13 scenes, 524 spoken words, about 3:16 of speech and about 4:15 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V073What’s the difference between complaint feedback vs bounce feedback?
waiting on YTOpen questions for YT
- Next video: this is the last script of the series.
- Registry: "no picture yet" for the report frame and the parcel and door.
- End card: RME Clean has no URL in R14.
00 · Two red lines, the wrong one first (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 when each one happens · 2 which one hurts faster · 3 what to do about each. Chips 2 and 3 grey.
Three parts to it. When each one happens. Which one hurts faster. And what to do about each, starting with the one you can't see.
01 · Brought to you by, woven in · 0:30
On screen: no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Of these two signals, bounces are the one you can catch before you send, and Review My Emails does exactly that.
02 · The parcel · 0:41
On screen: chip 1 lights. One parcel on a path to a front door. The path splits. On the left, the parcel turns at the door and comes back, stamped returned. On the right, it goes through the door, and a moment later a small letter comes out, addressed to the post office, this is spam.
When does each one happen? Picture a parcel. A bounce is the parcel coming back. Delivery failed before it ever reached a person. A complaint is the parcel that arrived. Someone opened it, or didn't, and clicked This is spam. Delivered, just not wanted.
03 · How the letter gets back to you · 1:06
On screen: the letter from scene 02 travels from the post office to Sally's email tool, and the address on it turns coral on her list. Gloss card: feedback loop · an arrangement where a mailbox provider tells a sender which of their messages were reported.
And how does that letter reach you? Through a feedback loop. The mailbox provider passes the complaint back, usually to your email marketing tool, which takes the address off your list. And the provider reads it as its own user saying no to you. That's why it hits trust so fast.
04 · Which one hurts faster · 1:29
On screen: chip 2 lights. Two timelines under the two endings. Under the letter, a short fuse burns down in a few ticks, days. Under the returned parcel, a long fuse burns slowly, over time. Three small labels drop in on the short side, one per click: spam folder · slowed · blocked.
Which one hurts faster? Complaints, in almost every case. Too many and providers start sending you to spam, slowing your sends, or blocking you, and it can happen within days. Bounces tell a provider your list isn't kept. That matters too, but it damages your reputation more slowly.
05 · Complaints: out at once, then look upstream · 1:55
On screen: chip 3 lights. The coral address from scene 03 moves onto a do-not-send list, locked. Then an arrow runs backwards from the letter, past the parcel, to the signup form it came from. Three question tags pop up along it, one per click: where from? · clear opt-in? · too often?
What do you do about each? Complaints first. Suppress that address for good, straight away. Don't wait for the next send. Then look upstream. Where did these people come from? Was their opt-in clear? Are you sending too often? The complaint is a symptom.
06 · Bounces: hard out, soft watched · 2:18
On screen: the returned parcel splits into two. One stamped coral, hard: no such address, goes straight onto the list, locked. One stamped amber, soft: try again, sits on a shelf with a small counter beside it that ticks up, send after send, until the parcel turns coral.
Then the bounces. A hard bounce means the address doesn't exist. Take it off right away. Keep sending, and your email marketing tool may even suspend you. A soft bounce is temporary. Watch it. If it keeps soft bouncing, treat it like a hard one.
07 · The twist: the complaint you never see · 2:40
On screen: the post office for one provider. The letter from scene 02 is written, and stays in a drawer. Instead, a dashboard frame lights up, one wide coloured band, spam rate, and a label, whole domain. A search box beside it reads who?, and returns nothing.
Gmail, though, doesn't send those letters at all. It never tells you who complained. You get Google Postmaster Tools instead. A free dashboard with your spam rate, shown as a band, for your whole domain. Something's wrong, it says. Not who.
08 · Pause them before they complain · 3:06
On screen: the split path again, both parcels at the depot before they leave. The complaint parcel stays as it is, a small tag consent · relevance. The bounce parcel goes under the checking desk lamp, its address turns coral, no such address, and it never leaves the depot.
Of these two, only one can be stopped before the parcel leaves. A complaint needs a person on the other end, so it's about consent and relevance. A bounce only needs a bad address. And a bad address can be found before you ever send to it.
09 · Recap · 3:49
On screen: the split path, the returned parcel, the letter, the two fuses, the locked list, the paused tiles, the lamp at the depot. All three chips lit.
One more time. A bounce is the parcel that came back. A complaint is the parcel that arrived, and wasn't wanted. Complaints hurt faster, so fix them first. Hard bounces out, soft ones watched. Check the addresses before the parcels leave. And in your tool, pause the quiet ones before they complain.
10 · Close · 4:06
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V074, no subscribe ask.
Read both signals, and fix complaints first. Nobody can stop a person clicking spam for you. That's consent and relevance. What Review My Emails takes out is the addresses that would bounce. Rather we did it for you? That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... when should I run a re-engagement campaign?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-012.007.016-complaint-vs-bounce-feedback.md
00 · Two red lines, the wrong one first (hook)
Almanac ids in this scene: 012.007.016
What's the difference between complaint feedback vs bounce feedback?
three numbered chips, the VO's words: 1 when each one happens · 2 which one hurts faster · 3 what to do about each. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the report frame. No picture yet.
012.007.016 "You open your deliverability report and see two different signals in red" / "So which one should you tackle first? In almost every case, complaints win."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 012.007.016, 015.001.001
no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress". 012.007.016 "RME Clean flags invalid, risky, and undeliverable addresses before they turn into bounce or complaint problems." Only the bounce half is voiced. Q4: one sentence, 21 words.
nothing says a clean stops complaints. The close says so.
02 · The parcel
Almanac ids in this scene: 012.007.016
When each one happens
chip 1 lights. One parcel on a path to a front door. The path splits. On the left, the parcel turns at the door and comes back, stamped returned. On the right, it goes through the door, and a moment later a small letter comes out, addressed to the post office, this is spam.
one parcel, two endings: before the door, and after it. Reveals: (1) the parcel, (2) the split, (3) the return, (4) the delivery, (5) the letter.
the parcel and the door. No picture yet.
012.007.016 "Complaint feedback is a post-delivery signal: the message reached the inbox and the recipient clicked This is spam" / "Bounce feedback means delivery failed before the message ever reached a human inbox." / "a recipient got your email, opened it (or didn't), and clicked" / "The message was delivered successfully. They just didn't want it."
T10, the returned parcel, carried to the close. "Bounce" here is the broad meaning (R3).
03 · How the letter gets back to you
Almanac ids in this scene: 012.007.009, 012.007.016
When each one happens
the letter from scene 02 travels from the post office to Sally's email tool, and the address on it turns coral on her list. Gloss card: feedback loop · an arrangement where a mailbox provider tells a sender which of their messages were reported.
one letter, one hop, one address struck. Reveals: (1) the letter travels, (2) the tool receives it, (3) the address turns coral, (4) the gloss card.
the parcel and the door, concept feedback-loop.
012.007.016 "This signal comes back to you through a Feedback Loop (FBL), where the mailbox provider reports the complaint back to your ESP. Complaints are a direct trust signal. ISPs read them as evidence that your list doesn't want to hear from you, and that hits your reputation fast." 012.007.009 "If you're sending through a major ESP, they often handle FBL processing on your behalf." / "suppress the complaining address automatically."
"usually" keeps the answer's "often" (V12). "Email marketing tool" for "ESP" (V5).
04 · Which one hurts faster
Almanac ids in this scene: 012.007.016
Which one hurts faster
chip 2 lights. Two timelines under the two endings. Under the letter, a short fuse burns down in a few ticks, days. Under the returned parcel, a long fuse burns slowly, over time. Three small labels drop in on the short side, one per click: spam folder · slowed · blocked.
a short fuse against a long one. Reveals: (1) the two fuses, (2) the short one burns, (3) to (5) one label each, (6) the long one burns on.
the parcel and the door, with the fuses.
012.007.016 "In almost every case, complaints win." / "Too many complaints and they start routing your campaigns to spam, throttling your sends, or blocking you outright. The damage can happen within days." / "Bounces tell ISPs that your list is dirty or poorly maintained." / "High bounce rates damage your IP and domain reputation over time"
no rate voiced or shown. The answer's "can trigger blocks from certain providers" for bounces is not voiced (GAP-B's shape, myth V027). "Slowing your sends" for "throttling" (registry throttling).
05 · Complaints: out at once, then look upstream
Almanac ids in this scene: 012.007.016
What to do about each
chip 3 lights. The coral address from scene 03 moves onto a do-not-send list, locked. Then an arrow runs backwards from the letter, past the parcel, to the signup form it came from. Three question tags pop up along it, one per click: where from? · clear opt-in? · too often?
one address locked, one arrow back, three questions. Reveals: (1) the lock, (2) the arrow, (3) to (5) one question each.
the parcel and the door, concept suppression-list.
012.007.016 "Suppress the address permanently and immediately. Don't wait. Then look upstream: where did these subscribers come from? Did they opt in clearly? Are you sending too frequently? The complaint is a symptom of a consent or relevance problem."
playlist 2 video 2 owns the suppression list (S6), used here as a picture only.
06 · Bounces: hard out, soft watched
Almanac ids in this scene: 012.007.016
What to do about each
the returned parcel splits into two. One stamped coral, hard: no such address, goes straight onto the list, locked. One stamped amber, soft: try again, sits on a shelf with a small counter beside it that ticks up, send after send, until the parcel turns coral.
one parcel out at once, one watched until it turns. Reveals: (1) the split, (2) the hard one locked, (3) a small account card, suspended?, flickers, (4) the soft one on the shelf, (5) the counter ticks, (6) it turns coral.
the parcel and the door, concepts hard-bounce, soft-bounce.
012.007.016 "A hard bounce means the address doesn't exist." / "Remove them from your list right away. Continuing to send to invalid addresses signals to ISPs that you don't maintain your list. Your ESP may also suspend you if bounce rates stay high." / "Monitor them. If an address soft bounces repeatedly over a few sends, treat it like a hard bounce and remove it."
R6 (YT, 2026-09-29): no fixed count. The counter shows no number to stop at. Playlist 1 video 3 (V003) owns how many retries (S6).
07 · The twist: the complaint you never see
Almanac ids in this scene: 012.007.007, 012.007.016
What to do about each
the post office for one provider. The letter from scene 02 is written, and stays in a drawer. Instead, a dashboard frame lights up, one wide coloured band, spam rate, and a label, whole domain. A search box beside it reads who?, and returns nothing.
one letter held back, one band instead of names. Reveals: (1) the letter stays in the drawer, (2) the dashboard, (3) the band, (4) the empty search.
the parcel and the door, the dashboard frame (V072's, called back).
012.007.016 "Gmail doesn't share complaint data through a traditional FBL. You'd need Google Postmaster Tools to see your complaint rate there, and it shows domain-level data, not individual addresses." 012.007.007 "Gmail never sends per-complaint ARF reports" / "spam rate (shown as banded ranges, not exact figures)" / "None of this tells you who complained."
T3, the twist. T2, where the signal shows up and what it can't show.
08 · Pause them before they complain
Almanac ids in this scene: 006.003.012, 012.007.007, 012.007.016
The one you can stop
the split path again, both parcels at the depot before they leave. The complaint parcel stays as it is, a small tag consent · relevance. The bounce parcel goes under the checking desk lamp, its address turns coral, no such address, and it never leaves the depot.
two parcels, one that only a person can stop, one the lamp stops. Reveals: (1) the depot, (2) the consent tag, (3) the lamp, (4) the coral address stays behind.
the parcel and the door, the checking desk.
012.007.016 "The complaint is a symptom of a consent or relevance problem." / "Bounce feedback means delivery failed before the message ever reached a human inbox." / "RME Clean flags invalid, risky, and undeliverable addresses before they turn into bounce or complaint problems." Only the bounce half is voiced.
Q2: the catch-all pivot is cut, a complaints video needs a pivot from its own topic. Q3: moved before the recap. Never says a clean stops complaints.
09 · Recap
What to remember
the split path, the returned parcel, the letter, the two fuses, the locked list, the paused tiles, the lamp at the depot. All three chips lit.
callbacks only.
callbacks only (S5).
10 · Close
Almanac ids in this scene: 005.010.002
Two signals, one list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V074, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10), in new words (Q1). Brand said twice, bridge and close (Q4). S8: the next video is 005.010.002, by its Almanac question word for word, which picks up the quiet subscribers paused in scene 08. Totals: 13 scenes, 582 spoken words, about 3:25 of speech and about 4:20 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V074When should I run a re-engagement campaign?
waiting on YTOpen questions for YT
- Next-video line: the Almanac question says "ESPs".
- Registry: "no picture yet" for the calendar strip and the sieve.
00 · Saving it for January (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 when someone crosses your line · 2 just before you'd let them go · 3 before a big push. Chips 2 and 3 grey.
Three moments to run it. When someone crosses your line. Just before you'd let them go. And before a big push.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The calendar holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some quiet subscribers are just busy, others are addresses that stopped working long ago, and Review My Emails tells them apart before you send.
02 · Moment one: when they cross your line · 0:39
On screen: chip 1 lights. Kai Driftwood's tile, kai@driftwood-goods.example, walks along the calendar strip. A dashed line crosses the strip, your line. As the tile steps over it, it turns amber, and the first pin goes in, with a small sieve under it.
When's the first moment? As soon as a subscriber hits your own inactivity line. That's the number of days without an open or a click that your rules call lapsed. Where's the line? That's your sunset policy's call, your written rule for quiet subscribers, and it depends on how often you send.
03 · Why not wait · 1:02
On screen: Kai's amber tile keeps walking past the line. Behind it, a small gauge fills a little with each step, risk. A pin with a question mark hovers early, before the line, plan it here.
Why not wait a bit? Because the longer an address sits quiet, the riskier it gets. As engagement drops, filters tighten, and where your mail lands suffers. So plan the win-back before someone crosses the line, not long after.
04 · Moment two: just before you'd let them go · 1:22
On screen: chip 2 lights. The second pin goes in at the far end of Kai's walk, last chance, and its sieve fills with tiles. Some tiles are caught and lift back into the list, teal. The rest fall through into a pot marked suppressed.
The second moment is the last one. Right before you'd take them off your active list. It works like a sieve. One last chance to stay. The ones who answer stay in your regular sends. The ones who don't are suppressed or removed.
05 · Moment three: before a big push · 1:41
On screen: chip 3 lights. The third pin goes in just before the teal biggest sale block, and its sieve runs once. The list that walks into the sale block is smaller, and every tile on it is teal. A volume bar beside the block climbs.
The third moment is Sally's. Before a big seasonal push, like a holiday sale, clear out the dead weight before your volume goes up. Why then? Because at Gmail and Outlook, how people engage feeds where your mail lands. Going into the rush lighter protects your domain's reputation.
06 · The twist: check them before you ask them · 2:04
On screen: the sieve at the third pin. Before it runs, the checking desk lamp passes over the tiles. A few of them turn coral, gone, and are lifted out. Then the "still with us?" envelope goes out, and nothing comes back coral. A ghost of the other version plays small in the corner: no lamp, and coral envelopes bouncing back.
Before you send the 'still with us? ' email, though, check that segment first. Some of those quiet addresses aren't quiet, they're gone. Skip the check, and the email asking them back bounces, right when you can least afford it.
07 · What to do · 2:26
On screen: one amber tile on a domain marked accepts everything sits in the third sieve. The lamp passes over it, and it stays amber. The envelope goes to it and never comes back. Then the checking desk lamp looks closer and tags it, catch-all.
Some quiet addresses never bounce at all, even when they're dead. On a domain that accepts any name, a made-up address just stays quiet, and your win-back can't tell it from a busy reader. A clean can.
08 · Recap · 3:04
On screen: the calendar strip, three pins, three sieves, the lamp over the last one. All three chips lit.
The three moments, once more. Run it when someone crosses your line. Run it as the last chance before you let them go. And run it before a big push, so you go into the rush lighter. Check the segment first, every time.
09 · Close · 3:19
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Re-engagement and suppression, part 1, no subscribe ask.
Put the three moments on your calendar, and check before you ask. Winning people back is your email's job. Clearing out the addresses that were never going to answer is ours. Clean lists for clients? Our partner programme pays fifteen percent. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how do email marketing tools typically handle suppressions?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.010.002-when-to-run-re-engagement.md
00 · Saving it for January (hook)
Almanac ids in this scene: 005.010.002
When should I run a re-engagement campaign?
three numbered chips, the VO's words: 1 when someone crosses your line · 2 just before you'd let them go · 3 before a big push. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the calendar strip. No picture yet.
005.010.002 "Time the send before major seasonal pushes (Black Friday, Q4 holidays) so dead weight is suppressed before volume ramps"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.003.005, 015.001.001
no cut away and no ad break. The calendar holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.003.005 "Your list has degraded. People changed jobs, closed accounts" 015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
nothing says a clean wins anyone back. The close says so.
02 · Moment one: when they cross your line
Almanac ids in this scene: 005.010.002
When someone crosses your line
chip 1 lights. Kai Driftwood's tile, kai@driftwood-goods.example, walks along the calendar strip. A dashed line crosses the strip, your line. As the tile steps over it, it turns amber, and the first pin goes in, with a small sieve under it.
one line, one tile crossing it, one pin. Reveals: (1) the tile, (2) the dashed line, (3) it crosses and turns amber, (4) the pin and sieve.
the calendar strip, concept re-engagement.
005.010.002 "run a re-engagement campaign as soon as a subscriber hits your defined inactivity threshold." / "Your engagement rules probably already flag these folks as lapsed or at risk."
no window voiced (C30). V045 owns how to set the window (S6), one line here. "Your own line" for "threshold", no number on screen.
03 · Why not wait
Almanac ids in this scene: 005.010.006
When someone crosses your line
Kai's amber tile keeps walking past the line. Behind it, a small gauge fills a little with each step, risk. A pin with a question mark hovers early, before the line, plan it here.
a gauge that fills with time. Reveals: (1) the tile walks on, (2) the gauge fills, (3) the early pin.
the calendar strip.
005.010.006 "When engagement drops, filters tighten and your inbox placement suffers." / "the longer an address sits inactive, the higher your risk." / "Start planning re-engagement before you hit that 90-day mark."
T1, the why. The answer's recycled-trap line and its "90-day mark" are held. "Where your mail lands" for "inbox placement", no promise either way.
04 · Moment two: just before you'd let them go
Almanac ids in this scene: 005.010.002
Just before you'd let them go
chip 2 lights. The second pin goes in at the far end of Kai's walk, last chance, and its sieve fills with tiles. Some tiles are caught and lift back into the list, teal. The rest fall through into a pot marked suppressed.
one sieve, two outcomes. Reveals: (1) the pin, (2) the sieve fills, (3) the teal ones lift back, (4) the rest fall through.
the calendar strip, the sieve, concept suppression-list for the pot.
005.010.002 "The best time is right before you'd normally remove them from your active list. You're giving them one last chance to stay." / "Think of it as a filter: the ones who respond get to stay in your regular sends. The ones who ignore your re-engagement sequence? They're safely suppressed or removed."
T10, the Almanac's own filter, drawn as a sieve.
05 · Moment three: before a big push
Almanac ids in this scene: 005.010.002
Before a big push
chip 3 lights. The third pin goes in just before the teal biggest sale block, and its sieve runs once. The list that walks into the sale block is smaller, and every tile on it is teal. A volume bar beside the block climbs.
one sieve before one block, a smaller list, a climbing volume bar. Reveals: (1) the pin, (2) the sieve runs, (3) the lighter list, (4) the bar climbs.
the calendar strip.
005.010.002 "Time the send before major seasonal pushes (Black Friday, Q4 holidays) so dead weight is suppressed before volume ramps, which protects domain reputation at Gmail and Outlook where engagement rate directly feeds inbox placement decisions." / "It's also smart to run these before major seasonal pushes (holidays, big sales events) to clear out the dead weight before you ramp up volume."
"feeds where your mail lands" keeps the answer's claim without promising inbox. The hook pays off here. V045's seasonal twist (fit the window to your buying cycle) is its own, not re-taught.
06 · The twist: check them before you ask them
Almanac ids in this scene: 005.003.005
Before a big push
the sieve at the third pin. Before it runs, the checking desk lamp passes over the tiles. A few of them turn coral, gone, and are lifted out. Then the "still with us?" envelope goes out, and nothing comes back coral. A ghost of the other version plays small in the corner: no lamp, and coral envelopes bouncing back.
a few coral tiles lifted out, then no bounces. Reveals: (1) the lamp, (2) the coral tiles, (3) lifted out, (4) the envelope goes, (5) the ghost version.
the calendar strip, the checking desk lamp, concept email-validation.
005.003.005 "Use bulk validation" / "before a re-engagement campaign to an old segment" / "Same logic applies before a re-engagement campaign. clean the list first so your 'Come back?' email doesn't bounce"
T3, the twist. "Right when you can least afford it" ties back to scene 05's push, not a new claim. The answer's "30% of the time" is not voiced.
07 · What to do
Almanac ids in this scene: 005.003.005, 005.010.002, 021.002.013
The one you never see
one amber tile on a domain marked accepts everything sits in the third sieve. The lamp passes over it, and it stays amber. The envelope goes to it and never comes back. Then the checking desk lamp looks closer and tags it, catch-all.
one tile the sieve can't sort. Reveals: (1) the tile, (2) the lamp passes, (3) no bounce, (4) the tag.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. T2, where the moments go (on your calendar). The blanks are the viewer's, no number shown (N6).
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a list topic, so the catch-all pivot fits, reworded (Q1).
08 · Recap
What to remember
the calendar strip, three pins, three sieves, the lamp over the last one. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Three pins, one calendar
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Re-engagement and suppression, part 1, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the partner programme (15%), named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word, with only "ESPs" swapped for "email marketing tools" (S8, V5). Totals: 12 scenes, 487 spoken words, about 3:03 of speech and about 3:40 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V075How do email marketing tools typically handle suppressions?
waiting on YTOpen questions for YT
- C47: what a sender pays for, three answers.
- Title swap: the upload title swaps only "ESPs" for "email marketing tools" (V5).
- Next video: V076, 005.010.003 "What makes a good re-engagement email?", named in the close (PM, 2026-09-29).
- Registry: "no picture yet" for the send report and the building.
00 · Where did 2,000 go? (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 your own list · 2 a second list, kept by the platform · 3 what that means for you. Chips 2 and 3 grey.
Three parts to it. Your own list, checked before every send. A second list, kept by the platform. And what that means for you.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Many addresses on a suppression list got there by bouncing first, and Review My Emails catches them before that first send.
02 · Layer one: your own list · 0:39
On screen: chip 1 lights. Sally's door, her doorman, his list (V007's picture). A long queue of envelopes, one per person, files past him. Four kinds of coral names are on his list, one per click: hard bounce · unsubscribe · complaint · uploaded. una.subscribe@pearl-diver.invalid reaches the door and is turned aside.
Start with your own list, your suppression list. Think of a doorman's list that works backwards. Names on it never get in. Your email marketing tool checks every single person you picked against it before anything goes. Hard bounces, unsubscribes, complaints, anything you uploaded. On the list? They're filtered out.
03 · Where you see it · 1:02
On screen: back to the report from the hook. The 2,000? gap fills with small coral names, the ones the doorman turned aside. A label under it, your suppressions. The sent: 48,000 line gets a teal underline.
Where do you see this happen? In the send count. You picked fifty thousand. Your tool quietly took out two thousand suppressions, and sent forty-eight thousand. The count you see is what went out.
04 · Layer two: the building's list · 1:22
On screen: chip 2 lights. The picture pulls back. Sally's door is one of many in one building, a doorman at each. At the street entrance, a second doorman appears, with his own list, the whole building. One neighbour's door lets out an envelope to an address that complained, and the street doorman writes that address on his list.
Then there's a second list. Many tools send mail for lots of customers from the same shared servers. If one of them damages those servers' reputation, everyone on them suffers. So many tools keep their own global list, including addresses with a lot of complaints, so nobody on those servers mails them again.
05 · The twist: skipped, but not by you · 1:48
On screen: back at Sally's door. An envelope to an address that is not on her doorman's list reaches the street entrance and is turned aside, amber, on the building's list. Sally reaches for the street doorman's list. Most of it is blurred.
Some of the people your tool skips were never on your list at all. They're on the building's. And you can't see all of that list. It isn't a glitch. It's protection from other senders' mistakes.
06 · What that means for you · 2:08
On screen: an envelope to a domain marked accepts everything walks past both doormen, neither list holds it. It goes in, and nothing comes back. Hold. Then the checking desk lamp finds the address and tags it amber, catch-all.
Both lists only hold what someone caught, though. On a domain that takes mail for any name, a made-up address usually never bounces, so it never lands on either list. A clean finds those before you send.
07 · Recap · 2:49
On screen: the report with its filled gap, the two doormen, the blurred street list, the notecard. All three chips lit.
The short version. Your tool checks every send against your list first, which is why your sent count comes in lower. Many platforms keep a second, shared list too, and you can't see all of it. Suppress fast, and ask if yours has one.
08 · Close · 3:05
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Re-engagement and suppression, part 1, no subscribe ask.
Let your tool do its job, and feed it fast. Keep your suppression list. A clean works alongside it, taking out the addresses that were never going to work. Adding people through your own forms? Our API checks each one first. Clean your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what makes a good re-engagement email?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.005.004-how-email-tools-handle-suppressions.md
00 · Where did 2,000 go? (hook)
Almanac ids in this scene: 005.005.004
How do email marketing tools typically handle suppressions?
three numbered chips, the VO's words: 1 your own list · 2 a second list, kept by the platform · 3 what that means for you. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the send report. No picture yet.
005.005.004 "You might think you're sending to 50,000 people. Your ESP silently removes 2,000 suppressions and actually sends to 48,000." / "ESPs handle suppressions at two layers."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.005.004, 015.001.001
no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.005.004 "your uploads, your bounces, your unsubscribes" 015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit" / "we'll flag what's safe to send to and what to suppress".
"often by bouncing first" is V007's close, called back, and the answer's own list of what goes on.
02 · Layer one: your own list
Almanac ids in this scene: 005.005.004
Your own list
chip 1 lights. Sally's door, her doorman, his list (V007's picture). A long queue of envelopes, one per person, files past him. Four kinds of coral names are on his list, one per click: hard bounce · unsubscribe · complaint · uploaded. una.subscribe@pearl-diver.invalid reaches the door and is turned aside.
a queue checked one by one, four kinds on the list. Reveals: (1) the doorman, (2) the queue, (3) to (6) one kind each, (7) the turned-aside envelope.
the doorman's list, concept suppression-list.
005.005.004 "When you upload a list or segment your audience, your ESP compares every recipient against your suppression file. Any address on your suppression list gets automatically filtered out before the send." / "(manual uploads, hard bounces, unsubscribes, FBL complaints from ARF reports)"
V007 owns the list and the doorman (S6), one line. "Email marketing tool" for "ESP" (V5). The answer's handoff detail stays in the Almanac (P7).
03 · Where you see it
Almanac ids in this scene: 005.005.004
Your own list
back to the report from the hook. The 2,000? gap fills with small coral names, the ones the doorman turned aside. A label under it, your suppressions. The sent: 48,000 line gets a teal underline.
the 2,000 gap fills, 48,000 underlined. Reveals: (1) the report, (2) the gap fills, (3) the label, (4) the underline.
the send report.
005.005.004 "Your ESP silently removes 2,000 suppressions and actually sends to 48,000. You only see and pay for the actual send count."
T2, where to see it. C47: only "see" is voiced. "Pay" is held, because other answers say most tools charge by contact count.
04 · Layer two: the building's list
Almanac ids in this scene: 005.005.004
A second list, kept by the platform
chip 2 lights. The picture pulls back. Sally's door is one of many in one building, a doorman at each. At the street entrance, a second doorman appears, with his own list, the whole building. One neighbour's door lets out an envelope to an address that complained, and the street doorman writes that address on his list.
many doors, one street entrance, one shared list. Reveals: (1) the pull back, (2) the many doors, (3) the street doorman, (4) the neighbour's envelope, (5) the name on his list.
the doorman's list, now two doormen (P3, the same picture growing). The building is new.
005.005.004 "Many ESPs maintain their own global suppression lists." / "Because if the whole IP pool gets blacklisted, everyone on that IP suffers." / "Some ESPs add high-complaint addresses to a shared block list so nobody on that IP accidentally mails them again."
the answer's spam-trap example is held (registry spam-trap). "Many tools" keeps "Many ESPs" (V12). "Shared servers" for "shared IP pool" (registry ip-reputation).
05 · The twist: skipped, but not by you
Almanac ids in this scene: 005.005.004
A second list, kept by the platform
back at Sally's door. An envelope to an address that is not on her doorman's list reaches the street entrance and is turned aside, amber, on the building's list. Sally reaches for the street doorman's list. Most of it is blurred.
one address skipped that her list never held, one list mostly hidden. Reveals: (1) the envelope, (2) it's turned aside at the street, (3) the amber tag, (4) the blurred list.
the two doormen (P2, Sally's door holds still).
005.005.004 "You can't see all of the ESP's global suppressions, but you're protected by them." / "The ESP is protecting you from other senders' mistakes."
T3, the twist. "It isn't a glitch" names what a viewer would think when the counts don't match, not a new claim.
06 · What that means for you
Almanac ids in this scene: 005.005.004, 021.002.013
The one you never see
an envelope to a domain marked accepts everything walks past both doormen, neither list holds it. It goes in, and nothing comes back. Hold. Then the checking desk lamp finds the address and tags it amber, catch-all.
two lists, one address on neither. Reveals: (1) past the first doorman, (2) past the second, (3) the hold, (4) the lamp tags it.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. V007 owns "keep your own master file" (S6), not re-taught.
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a suppression topic, so the catch-all pivot fits, reworded (Q1). "Usually" keeps inside C17.
07 · Recap
What to remember
the report with its filled gap, the two doormen, the blurred street list, the notecard. All three chips lit.
callbacks only.
callbacks only (S5).
08 · Close
Almanac ids in this scene: 005.010.003
Two doormen, one send
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Re-engagement and suppression, part 1, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the API, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video (V076, 005.010.003, added to this series by #1147) is named by its Almanac question word for word (S8). Totals: 11 scenes, 447 spoken words, about 2:49 of speech and about 3:30 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V076What makes a good re-engagement email?
waiting on YTOpen questions for YT
- Registry: "no picture yet" for the email card, the outcome rows and the sending lanes.
- Simile: the paper-delivery note is new to the channel.
00 · The email nobody noticed (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 say why you're writing · 2 remind them what they came for · 3 two clear choices · 4 where you send it from. Chips 2 to 4 grey.
Four parts to it. Say why you're writing. Remind them what they came for. Give them two clear choices. And watch where you send it from.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The crowded card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A 'still with us? ' email only works if it reaches someone who can answer, and Review My Emails finds the ones who can't.
02 · What the email is for, and the twist · 0:42
On screen: the card is set aside for a moment. Three small rows under Kai's name, one per click: stays and clicks in teal, unsubscribes in plain grey with a small tick, stays and ignores everything in coral, which pulses once.
What is this email for? One thing. Giving someone a reason to decide. Stay, or go. Both answers are fine. The worst outcome isn't an unsubscribe. It's the subscriber who stays on your list and ignores everything you send. That's the one damaging your reputation.
03 · Part one: say why you're writing · 1:08
On screen: Kai's inbox row. The short card arrives. Kai's row lifts, the card opens. The paper-delivery note sits on the card's corner.
Why does plain honesty work? Because it's the first email in a long while that talks to them, not at them. That kind of honesty tends to get a response when everything else didn't.
04 · Part two: remind them what they came for · 1:52
On screen: chip 2 lights. On the card, under the paragraph, one line types in: You joined for the weekly tip. Then a small second line: New since you last read: [what changed]. A struck-through we've got great content! floats off the card.
Part two. Remind them what they came for. Everyone signed up for something. A discount, a weekly tip, a community. Name that thing. If you've improved since they went quiet, say what changed. And skip 'we've got great content'. Everyone says that.
05 · Part three: two clear choices · 2:20
On screen: the finished card, whole, beside a ghost of the crowded one from the hook. The crowded one fades. A label under the short card: 1 paragraph · 1 reminder · 2 buttons.
And that's the whole email. One short paragraph, one reminder, two buttons. If they've stopped reading you, they're not reading four paragraphs. Give them a quick decision.
06 · Part four: where you send it from · 2:58
On screen: chip 4 lights. The finished card is multiplied into a long stack, quiet segment. Beside it two sending lanes: send-more.example and news.send-more.example. The stack moves to the second lane. Gloss card: subdomain · a name under your own domain, like news dot your domain, so trouble stays there. Then a lamp passes over the stack and lifts out a few coral cards before it goes.
Part four. Watch where you send it from. If the quiet segment is large, a flood of low-engagement sends can damage your sending reputation. So consider a separate IP or a subdomain, so any damage stays contained. And check the segment first, so the email that asks them back doesn't bounce.
07 · After it goes · 3:24
On screen: the coral row from scene 02. One card in it has a domain marked accepts everything. The lamp finds it and tags it amber, catch-all.
Some of that silence isn't a person deciding, either. A domain that accepts mail for any name will take a made-up address without a bounce, and it never answers. It just sits in your quiet pile. A clean finds those before the run.
08 · Recap · 3:56
On screen: the finished card, the two lanes, the closed pot. All four chips lit.
Your recipe, in one breath. Say why you're writing. Remind them what they came for. Two clear choices, and nothing else. Send it where a big quiet send can't hurt your main name. Then suppress the silence.
09 · Close · 4:12
On screen: the paper-delivery note, keep delivering, or stop?, lands on the finished card. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 005.010.009 "How can re-engagement campaigns clean a list?", no subscribe ask.
Write the note that makes them decide. The words are yours, and so are the answers. We take out the addresses that were never going to answer. Stuck on yours? Our SOS hotline is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... how can re-engagement campaigns clean a list?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.010.003-what-makes-a-good-re-engagement-email.md
00 · The email nobody noticed (hook)
Almanac ids in this scene: 005.010.003
What makes a good re-engagement email?
four numbered chips, the VO's words: 1 say why you're writing · 2 remind them what they came for · 3 two clear choices · 4 where you send it from. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the email card, crowded. No picture yet.
005.010.003 "Don't dress up a re-engagement email as a regular newsletter. Readers can tell." / "it gives a subscriber a reason to decide."
H4, H5 (S2). "Keep it short" rides with chip 3, the two choices are the whole email.
01 · Brought to you by, woven in
Almanac ids in this scene: 005.010.003, 015.001.001
no cut away and no ad break. The crowded card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.010.003 "Worth validating the segment first to catch bounces and risky addresses before they hit the campaign." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · What the email is for, and the twist
Almanac ids in this scene: 005.010.003
What it's for
the card is set aside for a moment. Three small rows under Kai's name, one per click: stays and clicks in teal, unsubscribes in plain grey with a small tick, stays and ignores everything in coral, which pulses once.
three outcomes, two fine, one harmful. Reveals: (1) teal, (2) grey with its tick, (3) coral, (4) the pulse.
the three outcome rows. A note from the paper delivery sits beside them for the first time, keep delivering, or stop?, the simile the video carries (T10).
005.010.003 "A good re-engagement email does one thing: it gives a subscriber a reason to decide. Stay, or go. Both are fine. The worst outcome is a subscriber who stays on your list but ignores everything you send. That's the one damaging your reputation."
T3, the twist. Grey, not coral, for the unsubscribe: it is a fine answer, so it gets no warning colour.
03 · Part one: say why you're writing
Almanac ids in this scene: 005.010.003
Say why you're writing
Kai's inbox row. The short card arrives. Kai's row lifts, the card opens. The paper-delivery note sits on the card's corner.
one card, one open. Reveals: (1) the card arrives, (2) it opens.
the email card in Kai's inbox.
005.010.003 "That kind of honesty tends to get a response when everything else didn't."
"in a while" is the body's own wording. The In short's "90 days" is not voiced (C30).
"tends to" keeps the Almanac's hedge. "In a long while" is framing for "in a while", no window voiced. "Talks to them, not at them" is the plain reading of "Be direct", not a new claim.
04 · Part two: remind them what they came for
Almanac ids in this scene: 005.010.003
Remind them what they came for
chip 2 lights. On the card, under the paragraph, one line types in: You joined for the weekly tip. Then a small second line: New since you last read: [what changed]. A struck-through we've got great content! floats off the card.
two lines added, one line thrown away. Reveals: (1) the reminder, (2) what changed, (3) the struck line.
the email card.
005.010.003 "People signed up for something. What was it? A discount, a weekly tip, a community, access to something specific. Remind them of that thing. If you've improved since they went quiet, mention it. Don't just say "we've got great content" (everyone says that)."
T1, the why is in the VO: everyone says it, so it says nothing.
05 · Part three: two clear choices
Almanac ids in this scene: 005.010.003
Two clear choices
the finished card, whole, beside a ghost of the crowded one from the hook. The crowded one fades. A label under the short card: 1 paragraph · 1 reminder · 2 buttons.
one, one, two, against the crowded card. Reveals: (1) the two cards side by side, (2) the crowded one fades, (3) the label.
the email card, finished.
005.010.003 "One short paragraph of context, one reminder of the value, two buttons. If they're disengaged, they're not reading four paragraphs. Give them a quick decision to make."
T4, the fresh example is the third option.
06 · Part four: where you send it from
Almanac ids in this scene: 005.010.003, 009.003.004
Where you send it from
chip 4 lights. The finished card is multiplied into a long stack, quiet segment. Beside it two sending lanes: send-more.example and news.send-more.example. The stack moves to the second lane. Gloss card: subdomain · a name under your own domain, like news dot your domain, so trouble stays there. Then a lamp passes over the stack and lifts out a few coral cards before it goes.
one large stack, two lanes, a few cards lifted out. Reveals: (1) the stack, (2) the two lanes, (3) the move, (4) the gloss, (5) the lamp.
the email card, now a stack. The lamp is V074's check, called back (S5).
005.010.003 "If you're sending re-engagement emails to a large, cold segment, consider using a separate IP or subdomain. A flood of low-engagement sends to inactive addresses can damage your sending reputation if the segment is large. Worth validating the segment first to catch bounces and risky addresses before they hit the campaign." 009.003.004 "use a subdomain rather than your root domain. If sender reputation dips, the damage stays contained."
T2, where to look: the size of the segment and the address it goes from. V074 owns the "check first" twist (S6), one line here. news.send-more.example is a name under the library's send-more.example.
07 · After it goes
Almanac ids in this scene: 005.010.003, 021.002.013
The quiet you can't read
the coral row from scene 02. One card in it has a domain marked accepts everything. The lamp finds it and tags it amber, catch-all.
one card in the silent pile, tagged. Reveals: (1) the row, (2) the card, (3) the tag.
concept catch-all.
021.002.013 "So an email sent to madeupname@somecompany.example doesn't bounce."
T5, the action. V075 owns what the tool does next (S6).
R15 (YT, 2026-09-29), backed by the catch-all answers only. "Usually" keeps inside C17.
Q3: moved before the recap. Q2: a list topic, so the catch-all pivot fits, reworded (Q1).
08 · Recap
What to remember
the finished card, the two lanes, the closed pot. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 005.010.009
The note that makes them decide
the paper-delivery note, keep delivering, or stop?, lands on the finished card. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 005.010.009 "How can re-engagement campaigns clean a list?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 14 scenes, 548 spoken words (counted 2026-09-29), about 3:28 of speech and about 4:30 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V077How can re-engagement campaigns clean a list?
waiting on YTOpen questions for YT
- C47 add: "you stop paying" against "charge by contact count".
- Next video: named by the Q sweep (2026-09-30): V089, 005.010.015.
- Registry: "no picture yet" for the quiet wall of rows.
00 · The guess (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 how the filter works · 2 why the silence counts · 3 what it clears out · 4 the last step. Chips 2 to 4 grey.
Four parts to it. How the filter works. Why the silence counts as an answer. What it clears out. And the last step, which most people leave too late.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The wall of rows holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some addresses in a quiet pile aren't there to ask at all, and Review My Emails takes them out before the run begins.
02 · Part one: how the filter works · 0:40
On screen: chip 1 lights. V074's sieve, close up. Kai's card and Pearl's card sit in it with the rest. A small calendar edge above it, several weeks. One email drops in, then another, one per click. Pearl's card lights teal on a click and lifts out to the active side. Kai's card stays amber.
The run works like a sieve. Here's what happens inside it. You send your quiet subscribers a short run of messages, over several weeks. Each one asks a single thing. Click, reply, or update your preferences. Whoever does, stays on your active list. Whoever ignores the whole run gets suppressed. Use it, or lose it.
03 · Why it's fair · 1:04
On screen: chip 2 lights. The cursor from the hook is gone. Kai's card, still in the sieve. Each email that lands beside it stays closed. A small tally under it fills, one closed envelope per click.
Why is that fair? Because they decide, not you. You're not guessing who lost interest. You're going by what they did, or didn't do. Someone who ignores message after message, for weeks, has already told you. They're not going to engage later.
04 · The twist: the whole run, not one email · 1:28
On screen: Kai's tally. One closed email alone gets a small grey not yet. The full row of closed emails gets the verdict, coral. Then Kai's name on the card fades to a plain outline, no one reading.
The signal isn't one ignored email, though. It's ignoring the entire run. And you never need to know why someone went quiet. An address that stays dark through all of it is probably not a real subscriber anymore.
05 · Part three: what it clears out · 1:52
On screen: chip 3 lights. The sieve's two sides. The teal side holds cards that lit up. The coral side holds the silent ones, some with names, some plain outlines. A small gauge beside the coral side dips while they stay, and steadies when they go.
What does the sieve clear out? Real subscribers answer a direct question. Abandoned addresses stay silent. Suppressing that silence takes out the deadweight that drags down your numbers, and damages your reputation.
06 · Where you see the split · 2:14
On screen: the sieve tips its two sides into two labelled groups: clicked, replied or bought in teal and none of it in coral. The coral group gets a small tag, suppress.
Where do you see it? At the end of the run, your quiet segment splits in two. Everyone who clicked, replied or bought during those weeks. And everyone who did none of it. That second group is your list.
07 · Part four: the last step, straight away · 2:34
On screen: the sieve before the run starts. A few cards in it have their domain crossed out. The checking lamp passes over and lifts them out, coral, before the first email drops in.
But a run takes weeks, and it only works on people who can answer. Some addresses in that quiet pile stopped existing long ago. People change jobs and close accounts. A clean finds those before the first email goes.
08 · Recap · 3:08
On screen: the sieve, the two groups, the closed pot. All four chips lit.
The gist. Ask, don't guess. Judge the whole run, not one email. Real people answer, abandoned addresses don't. And suppress the silence the day the run ends.
09 · Close · 3:24
On screen: the sieve, empty and clean. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V089, no subscribe ask.
Let them answer, then act on the silence. Only your subscribers can tell you who's still interested. We take out the addresses that can't answer at all. Rather we did it for you? That's RME Clean. Or try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how does frequency affect engagement decay?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.010.009-re-engagement-campaigns-clean-a-list.md
00 · The guess (hook)
Almanac ids in this scene: 005.010.009
How can re-engagement campaigns clean a list?
four numbered chips, the VO's words: 1 how the filter works · 2 why the silence counts · 3 what it clears out · 4 the last step. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the quiet segment as a wall of rows. No picture yet.
005.010.009 "letting you remove deadweight based on subscriber behavior rather than guesswork."
H4, H5 (S2). "Leave too late" is framing for the answer's "immediately", paid off in scene 07.
01 · Brought to you by, woven in
Almanac ids in this scene: 005.003.005, 015.001.001
no cut away and no ad break. The wall of rows holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
005.003.005 "Same logic applies before a re-engagement campaign. clean the list first so your 'Come back?' email doesn't bounce" 015.001.001 "we'll flag what's safe to send to and what to suppress".
the answer's "30% of the time" is not voiced. V074 owns this as its twist (S6), one line here.
02 · Part one: how the filter works
Almanac ids in this scene: 005.010.009
How the filter works
chip 1 lights. V074's sieve, close up. Kai's card and Pearl's card sit in it with the rest. A small calendar edge above it, several weeks. One email drops in, then another, one per click. Pearl's card lights teal on a click and lifts out to the active side. Kai's card stays amber.
one sieve, one run of emails, two sides. Reveals: (1) the sieve, (2) the weeks, (3) the emails, (4) Pearl lifts out, (5) Kai stays.
the sieve (V074), called back and carried (P3).
005.010.009 "send a short sequence ... asking dormant contacts to click, reply, or update preferences, then suppress everyone who ignores the entire sequence." / "Subscribers who don't click through multiple messages over several weeks" / "It's a simple use-it-or-lose-it system."
no run size voiced (C31). "Several weeks" is the body's own wording.
03 · Why it's fair
Almanac ids in this scene: 005.010.009
Why the silence counts
chip 2 lights. The cursor from the hook is gone. Kai's card, still in the sieve. Each email that lands beside it stays closed. A small tally under it fills, one closed envelope per click.
one card, a row of closed emails. Reveals: (1) the cursor goes, (2) to (4) one closed email each, (5) the tally.
the sieve.
005.010.009 "you're removing people at their own choice, not making the decision unilaterally." / "Subscribers who don't click through multiple messages over several weeks have already told you they're not interested. They're not going to engage later."
T1, the why is the VO. The hook's guessing is answered.
04 · The twist: the whole run, not one email
Almanac ids in this scene: 005.010.009
Why the silence counts
Kai's tally. One closed email alone gets a small grey not yet. The full row of closed emails gets the verdict, coral. Then Kai's name on the card fades to a plain outline, no one reading.
one email against the whole run. Reveals: (1) one email, not yet, (2) the full row, coral, (3) the name fades.
the sieve.
005.010.009 "People who ignore the entire sequence? They get suppressed." / "If an address goes dark through your entire re-engagement sequence, it's probably not a real subscriber anymore."
T3, the twist. V12: "probably" is kept. "You never need to know why" is the plain reading of "at their own choice", not a new claim.
05 · Part three: what it clears out
Almanac ids in this scene: 005.010.009
What it clears out
chip 3 lights. The sieve's two sides. The teal side holds cards that lit up. The coral side holds the silent ones, some with names, some plain outlines. A small gauge beside the coral side dips while they stay, and steadies when they go.
two sides, one gauge. Reveals: (1) the teal side, (2) the coral side, (3) the gauge dips, (4) it steadies.
the sieve, with concept sender-reputation (the score gauge).
005.010.009 "real subscribers respond to direct prompts while abandoned addresses and recycled spam traps stay silent" / "you're eliminating the deadweight that kills your metrics and damages your reputation."
the trap half of the line is held (registry spam-trap). "You stop paying to mail to people who won't open" is held (C47 add). "Drags down your numbers" is the plain form of "kills your metrics".
06 · Where you see the split
Almanac ids in this scene: 005.010.009
What it clears out
the sieve tips its two sides into two labelled groups: clicked, replied or bought in teal and none of it in coral. The coral group gets a small tag, suppress.
one segment, two groups. Reveals: (1) the tip, (2) the teal group, (3) the coral group, (4) the tag.
the sieve, emptied into two groups.
005.010.009 "People who click, reply, or convert stay on your active list. People who ignore the entire sequence? They get suppressed."
T2, where to look. "Bought" is the plain word for "convert". No platform screen is drawn.
07 · Part four: the last step, straight away
Almanac ids in this scene: 005.003.005, 005.010.009
Before the run
the sieve before the run starts. A few cards in it have their domain crossed out. The checking lamp passes over and lifts them out, coral, before the first email drops in.
a few cards out, before week one. Reveals: (1) the sieve, (2) the crossed cards, (3) the lamp lifts them.
the sieve, the lamp (V074).
005.003.005 "People changed jobs, closed accounts, set up forwarding." / "clean the list first so your 'Come back?' email doesn't bounce"
T5, the action. V075 owns what the tool does with the pot next (S6). "It's the one that does the cleaning" is the plain reading of "the final cleaning step".
T6 and R15 (YT, 2026-09-29), backed by 005.003.005, the answer about cleaning before a re-engagement send, not by a catch-all line this time (T4, the two videos before it used the catch-all).
Q3: moved before the recap. Q2: a list topic, the pivot is this topic's own blind spot (addresses that can't answer), no catch-all.
08 · Recap
What to remember
the sieve, the two groups, the closed pot. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 005.010.015
Let the silence answer
the sieve, empty and clean. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V089, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10), in new words (Q1). S8: the next video is V089, 005.010.015, named by the Q sweep (2026-09-30) where the batch left it open. The PM can swap it when it sequences the playlists. Totals: 13 scenes, 452 spoken words (counted 2026-09-29), about 2:43 of speech and about 3:30 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V078What is RFC 7208 (SPF)?
waiting on YTOpen questions for YT
- C48: the SPF lookup cap, "10 is the maximum" against "fewer than 10".
- Demo name: mail-tool.example in the record is a reserved .example name but not in the demo-names library.
- Registry: "no picture yet" for the seven result cards and the two-sided envelope.
00 · Anyone could be anyone (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 what an RFC is · 2 what SPF checks · 3 how to read your record · 4 what SPF never sees. Chips 2 to 4 grey.
We'll take it in four steps. What an RFC is. What SPF checks at the gate. How to read your own record. And what SPF never sees.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The empty gate holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails checks who you're sending to, and SPF is how the receiving side checks who's sending, so both ends need to be right.
02 · Part one: what an RFC is · 0:41
On screen: chip 1 lights. A single case file on a desk beside the gate, RFC 7208 · 2014. It opens, one click per line lit on the page: the record · how it's checked · what each result means. Gloss card: RFC · the published rulebook for one piece of email, which every provider builds against.
First, the name. An RFC, a Request for Comments, is how internet standards are formally written down. RFC 7208 came out in 2014 and replaced an earlier SPF spec. It says exactly how SPF works. What the record looks like, how a receiver checks it, and what each result means.
03 · Part two: what SPF checks at the gate · 1:04
On screen: the guest list folds into a single line of text inside a DNS case file, send-more.example. The SPF checker panel opens beside it, the domain typed in, and the line appears in mono: v=spf1 ip4:203.0.113.5 include:mail-tool.example ~all. The v=spf1 gets a teal underline. Gloss card: DNS · the public directory that says who may send for a domain.
Where does that list live? In your DNS, as one line of text. Paste your domain into our free SPF checker and you'll see it. It starts with v equals spf1.
04 · Part three: how to read your record · 1:48
On screen: chip 3 lights. The record line, one piece lit per click, each with a small label under it: ip4:203.0.113.5 → this one server · include:mail-tool.example → your tool's list · a and mx → your own servers · ~all → everyone else: soft fail, amber · -all → everyone else: hard fail, coral.
Now read it. Each piece is a rule the RFC defines. Some pieces name your own servers. An include hands part of the check to another domain's list, like your email marketing tool's. And the ending covers everyone else. A tilde means soft fail. A dash means hard fail.
05 · What the gate can answer · 2:18
On screen: seven small cards slide up beside the gate, one per click: pass teal, fail coral, softfail amber, neutral and none grey, temperror grey, permerror with a crack across it. A small counter beside the record, lookups: 0 of 10.
And the answer isn't only yes or no. The RFC gives a receiver seven possible answers. Pass, fail, softfail, neutral, none, and two kinds of error. Hold on to the last one, permerror. It's where the whole list stops working. The RFC also caps how many lookups a record can need, at ten.
06 · Part four, the twist: what SPF never sees · 2:42
On screen: chip 4 lights. The envelope turns over. On the back, a small return label, envelope from, that the gate checks. On the front, the big From line, sally@send-more.example, that the subscriber reads. A forger's envelope: its back label is the forger's own domain, the gate checks it against the forger's own list, teal, pass. The front still says Sally. Gloss card: envelope from · the address the servers use to route and return a message, which the reader never sees.
SPF has one blind spot. It never checks the From address your subscriber sees. It checks a behind-the-scenes address, the envelope from, used while the mail travels. So someone can pass SPF with their own domain, and still put yours in the From line.
07 · Why SPF never works alone · 3:08
On screen: the SPF checker panel again, Sally's record in it. A notecard: formatted correctly · names the servers you send from.
Today's job is a short one. Run your domain through the SPF checker. Make sure your record is formatted correctly, and that it names every server you send from. Nothing more, nothing missing.
08 · Recap · 3:44
On screen: the case file, the gate and its list, the record line, the two-sided envelope. All four chips lit.
Pulling it together. RFC 7208 is SPF's rulebook. SPF is your domain's guest list, checked at the gate. It never sees the From your subscriber reads. So run your record through the free SPF checker, and read it piece by piece.
09 · Close · 4:16
On screen: the gate, its guest list pinned and neat. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 018.010.004 "What's “SPF permerror” and how does it tank deliverability?", no subscribe ask.
Keep your guest list right, and check it again after every change. The record stays yours. Review My Emails looks after the list you send to. Stuck on your record? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what's SPF permerror, and how does it tank deliverability?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-020.002.012-what-is-rfc-7208-spf.md
00 · Anyone could be anyone (hook)
Almanac ids in this scene: 020.002.012
What is RFC 7208 (SPF)?
four numbered chips, the VO's words: 1 what an RFC is · 2 what SPF checks · 3 how to read your record · 4 what SPF never sees. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the gate, empty. Concept spoofing (a second envelope with the same name written on it).
020.002.012 "Before the internet had organized email standards, anyone could send an email claiming to be from anyone. RFC 7208 is the document that defines SPF (Sender Policy Framework). One of the key standards that changed this."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 020.002.012
no cut away and no ad break. The empty gate holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 020.002.012 "it lets a domain owner publish a list of IP addresses that are allowed to send email on behalf of that domain."
"you need both ends right" never says a clean fixes SPF (S10).
02 · Part one: what an RFC is
Almanac ids in this scene: 020.002.012
What an RFC is
chip 1 lights. A single case file on a desk beside the gate, RFC 7208 · 2014. It opens, one click per line lit on the page: the record · how it's checked · what each result means. Gloss card: RFC · the published rulebook for one piece of email, which every provider builds against.
one file, three things it defines. Reveals: (1) the file, (2) to (4) one line each, (5) the gloss.
concept rfc (a single case file on the desk, opened and read).
020.002.012 "An RFC (Request for Comments) is how internet standards are formally defined. RFC 7208, published in 2014, replaced an earlier SPF spec and defines exactly how the Sender Policy Framework works: the record syntax, how receivers should evaluate it, what results mean, and how to handle edge cases."
03 · Part two: what SPF checks at the gate
Almanac ids in this scene: 003.001.001, 003.001.004, 003.001.022, 020.002.012
What SPF checks
the guest list folds into a single line of text inside a DNS case file, send-more.example. The SPF checker panel opens beside it, the domain typed in, and the line appears in mono: v=spf1 ip4:203.0.113.5 include:mail-tool.example ~all. The v=spf1 gets a teal underline. Gloss card: DNS · the public directory that says who may send for a domain.
one domain, one line. Reveals: (1) the list folds into the file, (2) the checker, (3) the line, (4) the underline, (5) the gloss.
concept dns (a row of case files, one per domain), the SPF checker panel.
003.001.001 "publishes a TXT record at your domain listing the IP addresses and hosts authorized to send mail on its behalf." 003.001.022 "exactly one TXT record starting with v=spf1" 020.002.012 "You can check your SPF record is correctly formatted with our free SPF checker."
T2 and T7, where it lives and our free tool. The terminal command in 003.001.022 goes to the description, not the VO (P7).
04 · Part three: how to read your record
Almanac ids in this scene: 003.001.004, 020.002.012
How to read your record
chip 3 lights. The record line, one piece lit per click, each with a small label under it: ip4:203.0.113.5 → this one server · include:mail-tool.example → your tool's list · a and mx → your own servers · ~all → everyone else: soft fail, amber · -all → everyone else: hard fail, coral.
one line, five kinds of piece. Reveals: (1) ip4, (2) include, (3) a and mx, (4) tilde all, (5) dash all.
the record line inside the DNS file.
020.002.012 "mechanisms like ip4: (allow specific IPv4 addresses), include: (include another domain's allowed senders), a and mx (allow the domain's A record or MX servers), and qualifiers like ~all (softfail) and -all (hard fail)." 003.001.004 "include:esp.example.com (your ESP's sending range)"
"email marketing tool" for "ESP" (V5). Q6: the VO names one new piece, include, and says "your own servers" for ip4, a and mx, which the picture labels one by one. The mechanism names stay on screen and in the description (P7). The record shows ~all. -all is drawn beside it as the other ending.
05 · What the gate can answer
Almanac ids in this scene: 020.002.012
How to read your record
seven small cards slide up beside the gate, one per click: pass teal, fail coral, softfail amber, neutral and none grey, temperror grey, permerror with a crack across it. A small counter beside the record, lookups: 0 of 10.
seven cards, one cracked. A counter with a cap of ten. Reveals: (1) to (5) the first five, (6) the two errors, (7) the crack, (8) the counter.
the gate, no figure (T11).
020.002.012 "the seven possible results (pass, fail, softfail, neutral, none, temperror, permerror), and the 10-DNS-lookup processing limit."
points forward to video 2 without naming it (S6). C48 kept out: the cap is said, what happens at exactly ten is not.
06 · Part four, the twist: what SPF never sees
Almanac ids in this scene: 020.002.012, 021.003.001
What SPF never sees
chip 4 lights. The envelope turns over. On the back, a small return label, envelope from, that the gate checks. On the front, the big From line, sally@send-more.example, that the subscriber reads. A forger's envelope: its back label is the forger's own domain, the gate checks it against the forger's own list, teal, pass. The front still says Sally. Gloss card: envelope from · the address the servers use to route and return a message, which the reader never sees.
two addresses on one envelope, one checked. Reveals: (1) the back label, (2) the front From, (3) the forger's back label, (4) the teal pass, (5) the front still says Sally, (6) the gloss.
the gate, the envelope front and back. Concept envelope-vs-header.
020.002.012 "it only protects the envelope from address, not the header from." 021.003.001 "A spammer can pass SPF while still showing your domain in the visible From header."
T3, the twist, said by its content, never labelled (Q1). V046 owns how SPF alignment is checked (S6), not taught here.
07 · Why SPF never works alone
Almanac ids in this scene: 020.002.012
What to do
the SPF checker panel again, Sally's record in it. A notecard: formatted correctly · names the servers you send from.
one record, two checks. Reveals: (1) the panel, (2) the first line, (3) the second.
the SPF checker panel, the notecard.
020.002.012 "You can check your SPF record is correctly formatted with our free SPF checker." / "publish a list of IP addresses that are allowed to send email on behalf of that domain."
no forwarding mechanics voiced. The series' later videos are not named by title here (S8 names only the next one, in the close).
T5, the action. "Nothing more, nothing missing" is framing for "the servers you send from".
08 · Recap
What to remember
the case file, the gate and its list, the record line, the two-sided envelope. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 018.010.004
What is RFC 7208 (SPF)?
the gate, its guest list pinned and neat. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 018.010.004 "What's “SPF permerror” and how does it tank deliverability?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8), the quote marks dropped in speech. Totals: 13 scenes, 549 spoken words (recounted 2026-09-30, Q sweep), about 3:34 of speech and about 4:40 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V079What’s “SPF permerror” and how does it tank deliverability?
waiting on YTOpen questions for YT
- Demo names: mail-tool.example, crm-tool.example and help-desk.example are reserved .example names but not in the demo-names library.
- Registry: "no picture yet" for the line chart and the drawer chain.
00 · One more tool (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 what permerror is · 2 why it hurts · 3 the ways a record breaks · 4 find it and fix it. Chips 2 to 4 grey.
Four questions, in order. What permerror is. Why it hurts your mail. The ways a record breaks. And how to find the broken piece and fix it.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The gate with the cracked card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails finds broken addresses on your list, and today it's a broken record instead, the one naming who may send for you.
02 · Part one: what permerror is · 0:41
On screen: chip 1 lights. The guest list hangs on the gate. The writing on it swims and blurs. A small retry? arrow appears and is crossed out. The cracked card, permerror, is pinned to the list.
What is it, exactly? Picture your SPF record as a guest list at a gate. The receiving server checks every sender against it. Permerror means it can't read that list at all. It isn't a temporary hiccup. It's a permanent failure, and receivers won't retry it. The list is there. It's just unreadable.
03 · Part two: why it hurts · 1:04
On screen: a delivery-rate line on a small chart, level, then a sharp drop on the day the include was added.
And that's how it tanks deliverability. You'll see dramatic drops in delivery rates. Often nothing else changed, just that one line in your record.
04 · Part three: the ways a record breaks · 1:46
On screen: chip 3 lights. The guest list on the gate changes, one per click, then springs back: a list with an overflowing counter, lookups: 11 of 10, coral · a list with a smudged word · two lists pinned side by side (V032's picture) · a list whose last line points back to its own first line, an arrow curling round.
How does a list become unreadable? Four ways. Too many lookups, more than ten in the chain. Each lookup is one more place the receiving server has to go and check. A typo, or a piece written wrong. Two SPF records on one domain, which confuses receivers entirely. And a loop, where one part points back to another, round and round.
05 · The twist: your tools' lists · 2:18
On screen: Sally's record, short, three includes. Each include opens like a drawer: mail-tool.example holds two more includes, crm-tool.example holds three, help-desk.example holds two. The counter starts at 3, one per include, and climbs with each drawer, 5, 8, 10. The hook's new include is one more, and the counter tips to 11, coral.
You rarely write those lookups yourself. Each tool you add goes in as an include, a line that says, check this tool's list too. Each include counts as one lookup, and the tool's list can have includes of its own. Sally's record looked short. Add one more tool, and the chain went past ten.
06 · Part four: find the broken piece · 2:46
On screen: chip 4 lights. The SPF checker panel, send-more.example typed in. The result reads permerror, with the crack. Below it, the record line, and the hook's include lit coral, this one.
Where do you see it? Paste your domain into our free SPF checker. If it says permerror, it also shows you which piece of the record is causing it. Find the culprit first. Then fix only that.
07 · Match the fix to the cause · 3:08
On screen: the four broken lists from scene 04, each mended in turn, one per click: the counter drops back under its cap, teal · the smudge is cleaned · the second list is dropped · the curling arrow is snipped. Gloss card: flatten · cutting the lookups down by merging or removing includes.
Then match the fix to the cause. Each fix is an edit to that one line of text. Over ten lookups? Flatten the record. Consolidate includes, and remove the ones you don't need. A typo? Fix the typo. Two records? Remove all but one. A loop? Break it, by walking back through your includes.
08 · Recap · 3:38
On screen: the blurred list, the two slots, the drawer chain, the checker. All four chips lit. This is the last lesson scene, nothing new follows it (Q3).
Here's the short version. Permerror is a guest list nobody can read. It takes the SPF half away, and leaves DKIM on its own. Run the free SPF checker after every new tool you add. Find the one broken piece, and fix that.
09 · Close · 4:12
On screen: the gate, the guest list readable again, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 020.002.007 "What is RFC 6376 (DKIM)?", no subscribe ask.
Keep your guest list readable, and make the free SPF checker your first stop after every change. The record is yours to fix. Review My Emails cleans the other side, the list you send to. Fixing records for clients? Ask about our partner programme. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is RFC 6376, DKIM?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-018.010.004-spf-permerror.md
00 · One more tool (hook)
Almanac ids in this scene: 018.010.004
What's SPF permerror and how does it tank deliverability?
four numbered chips, the VO's words: 1 what permerror is · 2 why it hurts · 3 the ways a record breaks · 4 find it and fix it. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
concept spf, the gate (video 1), the cracked result card (video 1, scene 05).
018.010.004 "Your SPF record just stopped working completely, and you don't know why. That's what permerror means." / "Can't pass, can't fail. Just broken."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 020.002.012
no cut away and no ad break. The gate with the cracked card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 020.002.012 "it lets a domain owner publish a list of IP addresses that are allowed to send email on behalf of that domain."
never says a clean fixes SPF (S10).
02 · Part one: what permerror is
Almanac ids in this scene: 018.010.004, 020.002.012
What permerror is
chip 1 lights. The guest list hangs on the gate. The writing on it swims and blurs. A small retry? arrow appears and is crossed out. The cracked card, permerror, is pinned to the list.
one list, unreadable, no retry. Reveals: (1) the blur, (2) the crossed retry, (3) the pinned card.
concept spf, the gate (video 1, P3).
018.010.004 "It's not a temporary DNS hiccup. It's a permanent failure that ISPs won't retry." / "returned when the receiver cannot process the record at all"
"receivers" for "ISPs", the plain word. The guest list is re-glossed in one line for a viewer arriving from search (Q5), never "Remember the...". Backed by 020.002.012 "it lets a domain owner publish a list of IP addresses that are allowed to send email on behalf of that domain."
03 · Part two: why it hurts
Almanac ids in this scene: 018.010.004, 020.002.007
Why it hurts
a delivery-rate line on a small chart, level, then a sharp drop on the day the include was added.
one line, one drop, no figure on the axis. Reveals: (1) the level line, (2) the drop.
a small line chart. No picture yet.
018.010.004 "You'll see dramatic drops in delivery rates."
DKIM glossed in one line (Q5, P6), its one new word (Q6). The answer's DMARC line is left for video 4, which owns it, so this scene stays at one new word. DKIM gloss backed by 020.002.007 "Your mail server attaches a cryptographic signature to every email you send."
no rate on the axis. "Often nothing else changed" is the plain reading of the hook's "you don't know why", not a new claim.
04 · Part three: the ways a record breaks
Almanac ids in this scene: 018.010.004
The ways a record breaks
chip 3 lights. The guest list on the gate changes, one per click, then springs back: a list with an overflowing counter, lookups: 11 of 10, coral · a list with a smudged word · two lists pinned side by side (V032's picture) · a list whose last line points back to its own first line, an arrow curling round.
four broken lists, one counter past its cap. Reveals: (1) to (4) one each.
concept spf, with spf-lookup-limit (the counter).
018.010.004 "a syntax error, a duplicate SPF TXT record on the domain, or exceeding the 10-DNS-lookup ceiling" / "Syntax errors come from typos or malformed SPF qualifiers. Duplicate SPF records confuse receivers entirely. Circular references (where one SPF include points back to another, creating a loop) also cause permerror."
lookup glossed in one line, the scene's one new word (Q5, Q6). The four ways are one list changing per click, the picture carries it (Q7). No callback to V032, a searcher has not seen it (Q5). C48: only "more than ten" is voiced.
05 · The twist: your tools' lists
Almanac ids in this scene: 003.001.004, 018.010.004, 020.002.012
The ways a record breaks
Sally's record, short, three includes. Each include opens like a drawer: mail-tool.example holds two more includes, crm-tool.example holds three, help-desk.example holds two. The counter starts at 3, one per include, and climbs with each drawer, 5, 8, 10. The hook's new include is one more, and the counter tips to 11, coral.
a short line, a long chain. The count climbs to ten, then one more. Reveals: (1) the short record, (2) to (4) one drawer each with the count, (5) the new include, (6) eleven.
concept spf-lookup-limit, the counter (video 1, scene 05, carried).
018.010.004 "Excessive DNS lookups happen when you're using too many nested includes in your SPF record. Each include directive counts as a lookup, and 10 is the maximum." / "more than 10 lookups in your SPF chain" 003.001.004 "include:esp.example.com (your ESP's sending range)"
T3, the twist, said by its content, never labelled (Q1). Include glossed in one line, the scene's one new word (Q6), backed by 020.002.012 "include hands part of the check to another domain's list" (V078's gloss). N5: three includes, plus two, three and two inside them, makes ten. One more makes eleven. The drawer counts are demo numbers that add up.
06 · Part four: find the broken piece
Almanac ids in this scene: 018.010.004
Find it and fix it
chip 4 lights. The SPF checker panel, send-more.example typed in. The result reads permerror, with the crack. Below it, the record line, and the hook's include lit coral, this one.
one domain, one result, one piece lit. Reveals: (1) the panel, (2) the result, (3) the lit piece.
the SPF checker panel (video 1).
018.010.004 "use Review My Emails SPF Checker. Paste your domain and see if you get a permerror result. If you do, the tool will show you exactly which mechanism is causing the problem." / "start by identifying which mechanism is the culprit"
T2 and T7, where to see it and our free tool.
07 · Match the fix to the cause
Almanac ids in this scene: 018.010.004
Find it and fix it
the four broken lists from scene 04, each mended in turn, one per click: the counter drops back under its cap, teal · the smudge is cleaned · the second list is dropped · the curling arrow is snipped. Gloss card: flatten · cutting the lookups down by merging or removing includes.
four lists, four fixes, the counter back under ten. Reveals: (1) to (4) one each, (5) the gloss.
concept spf, the four lists.
018.010.004 "If you're over the 10-lookup limit, you'll need to flatten your SPF record by consolidating includes or removing unnecessary mechanisms. If it's a syntax error, fix the typo. If you've somehow created duplicate SPF records, remove all but one. If there's a circular reference, break the loop by reviewing your include chain."
T5, the action. The DNS edits themselves go to the description (P7).
08 · Recap
What to remember
the blurred list, the two slots, the drawer chain, the checker. All four chips lit. This is the last lesson scene, nothing new follows it (Q3).
callbacks only.
callbacks only (S5).
"After every new tool you add" is the plain reading of the twist (scene 05), not a new claim.
09 · Close
Almanac ids in this scene: 020.002.007
What's SPF permerror?
the gate, the guest list readable again, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 020.002.007 "What is RFC 6376 (DKIM)?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the partner programme (15%), named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). The 15% is on the end card, not spoken. Totals: 12 scenes, 539 spoken words (recounted 2026-09-30, Q sweep), about 3:15 of speech and about 4:15 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V080What is RFC 6376 (DKIM)?
waiting on YTOpen questions for YT
- C49: "hard requirement for DMARC" against "SPF or DKIM".
- Demo name: mail-tool.example (from video 1), the PM adds it to the library or names a swap.
- Scene 06 names Gmail: the Almanac's own how-to names it as where to send the test.
- Registry: "no picture yet" for the settings row and the ledger.
00 · The green tick (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 what the seal proves · 2 where the key lives · 3 why receivers care · 4 whose name is on yours. Chips 2 to 4 grey.
Four things to know about that seal. What it proves. Where the key to it lives. Why receivers care. And whose name is on yours.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The sealed envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails checks who's at the other end of your mail, and DKIM is how you prove who's at yours.
02 · Part one: what the seal proves · 0:39
On screen: the envelope turns front side up. The big From line, sally@send-more.example. A thin dotted line runs from the From to the seal on the back, with a ? on it, grey, DMARC, coming up.
What it doesn't prove is that the signing domain matches the From your subscriber sees. A seal can be perfect, and still not be yours. That check belongs to DMARC, the rule that compares the two, and the last video in this series.
03 · Part two: where the key lives · 1:20
On screen: chip 2 lights. Beside the gate, a small locked stamp at Sally's sending desk, private key. In the DNS row of case files (video 1), one file opens at a mono address: s1._domainkey.send-more.example, holding public key. The key slides out of the file and onto the seal, and the two match, teal. Gloss card: selector · the name that points at which public key was used to sign.
How does a receiver check a seal it's never seen? Your server signs with a private key that only it holds. You publish the matching public key in your DNS, at a special name under your domain, built from a selector. The receiver fetches that key and checks the math. If it adds up, DKIM passes.
04 · Part three: why receivers care · 1:48
On screen: chip 3 lights. A small ledger opens at the gate, send-more.example, and each sealed envelope that passes adds a teal line to it. An unsealed envelope arrives with no name to write down. Its ledger line stays blank, grey.
Why does that matter for where your mail lands? Mailbox providers use DKIM as a reputation signal. A valid signature tells them your domain has a real identity they can track over time. Without it, your mail looks anonymous. And anonymous senders don't get the benefit of the doubt. DMARC uses it too, alongside SPF.
05 · Part four, the twist: whose name is on it · 2:14
On screen: chip 4 lights. The hook's seal, turned to the light. The lettering reads mail-tool.example, amber. The green tick from the hook stays green. Then a second seal beside it, send-more.example, teal, with a small stronger tag.
Now back to that green tick. Most email marketing tools set up DKIM for you. But they often sign with their own domain, not yours. The seal is intact. It just has their name pressed into it. That's fine to start. Signing with your own domain is the stronger setup.
06 · Where you see whose name it is · 2:38
On screen: a test email in an inbox. The three-dot menu opens, Show original. A page of raw header text, and one line lights: dkim=pass header.i=@send-more.example, with dkim=pass in teal and the domain underlined. Then the free header analyzer panel with the same line laid out in rows.
Where do you see it? Send a test from your tool to a Gmail account you control. Open it, choose Show original, and find the Authentication-Results line. You want dkim equals pass, with your own domain after it. Rather not read raw text? Paste the header into our free Email Header Analyzer.
07 · What to do with what you find · 3:06
On screen: the header line, three versions one per click: dkim=pass header.i=@mail-tool.example amber, a small arrow to add a record to your DNS · dkim=fail coral · dkim=none coral. A notecard: pass with your domain teal.
If it says pass with your tool's domain, ask your tool how to sign with yours. It's usually a record or two you add to your DNS during setup. And if it says fail, or none, the seal isn't verifying at all. That one needs fixing first.
08 · Recap · 3:30
On screen: the seal checked at the gate, the DNS file, the ledger, the two seals, the header line. All four chips lit.
In short. DKIM is a seal on every email, checked with a key in your DNS. It proves who signed it, and that nothing changed. Receivers track it over time. And a green tick doesn't tell you whose name is on it. So send a test, and read the seal.
09 · Close · 4:04
On screen: the seal with send-more.example, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 020.002.008 "What is RFC 7489 (DMARC)?", no subscribe ask.
Put your own name on your seal, and let a test send prove it's there. The setup stays yours. Review My Emails checks the list that sealed mail goes to. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is RFC 7489, DMARC?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-020.002.007-what-is-rfc-6376-dkim.md
00 · The green tick (hook)
Almanac ids in this scene: 020.002.007
What is RFC 6376 (DKIM)?
four numbered chips, the VO's words: 1 what the seal proves · 2 where the key lives · 3 why receivers care · 4 whose name is on yours. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
concept dkim (a seal pressed into the envelope). The settings row is drawn, no platform named.
020.002.007 "Most ESPs set up DKIM for you automatically, but they often sign with their own domain rather than yours."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 020.002.007
no cut away and no ad break. The sealed envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 020.002.007 "A valid signature proves the message originated from the signing domain".
never says a clean fixes DKIM (S10).
02 · Part one: what the seal proves
Almanac ids in this scene: 003.002.001, 020.002.007, 020.002.008
What the seal proves
the envelope turns front side up. The big From line, sally@send-more.example. A thin dotted line runs from the From to the seal on the back, with a ? on it, grey, DMARC, coming up.
one From, one seal, one open question. Reveals: (1) the front, (2) the dotted line, (3) the label.
the two-sided envelope (video 1, scene 06), carried.
003.002.001 "A few things DKIM doesn't prove: that the signing domain matches what your recipients see in the "From" address. That alignment check is DMARC's job."
DMARC is pointed forward with a one-line gloss for a searcher (Q5), backed by 020.002.008 "The domain authenticated by SPF or DKIM has to match the domain in the visible From address.". V046 owns the d= tag.
03 · Part two: where the key lives
Almanac ids in this scene: 003.002.001, 020.002.007
Where the key lives
chip 2 lights. Beside the gate, a small locked stamp at Sally's sending desk, private key. In the DNS row of case files (video 1), one file opens at a mono address: s1._domainkey.send-more.example, holding public key. The key slides out of the file and onto the seal, and the two match, teal. Gloss card: selector · the name that points at which public key was used to sign.
one private key, one public key, one match. Reveals: (1) the stamp, (2) the DNS file and its address, (3) the fetch, (4) the match, (5) the gloss.
concepts dkim, dns, dkim-selector.
020.002.007 "the receiving server verifies it against a public key published as a TXT record at selector._domainkey.yourdomain.com." 003.002.001 "Your mail server signs the message with a private key. You publish the matching public key in your DNS. When your message arrives at Gmail, Outlook, or any other inbox, their server retrieves your public key from DNS and uses it to verify the signature. If the math checks out, DKIM passes."
T1, the how. s1 is a demo selector name. The DNS record's contents go to the description (P7).
04 · Part three: why receivers care
Almanac ids in this scene: 020.002.007
Why receivers care
chip 3 lights. A small ledger opens at the gate, send-more.example, and each sealed envelope that passes adds a teal line to it. An unsealed envelope arrives with no name to write down. Its ledger line stays blank, grey.
one ledger, a row of lines, one blank. Reveals: (1) the ledger, (2) lines fill, (3) the unsealed envelope, (4) the blank line.
concept domain-reputation (the ledger by name), the gate.
020.002.007 "Mailbox providers use DKIM as a reputation signal. A valid DKIM signature tells them your domain has a real identity they can track over time. Without it, your emails look anonymous, and anonymous senders don't get the benefit of the doubt." / "DMARC uses DKIM (and SPF)"
C49 kept out: "hard requirement" is not voiced. No inbox promise, the VO says what providers use, not where mail lands.
05 · Part four, the twist: whose name is on it
Almanac ids in this scene: 020.002.007
Whose name is on yours
chip 4 lights. The hook's seal, turned to the light. The lettering reads mail-tool.example, amber. The green tick from the hook stays green. Then a second seal beside it, send-more.example, teal, with a small stronger tag.
one intact seal, the wrong name, then the right one. Reveals: (1) the seal turned, (2) the name, amber, (3) the tick still green, (4) the second seal, (5) the tag.
concept dkim, the seal.
020.002.007 "Most ESPs set up DKIM for you automatically, but they often sign with their own domain rather than yours. That's fine to start, but aligning your DKIM signature with your sending domain is the stronger setup and the one deliverability experts recommend."
T3, the twist, paid off from the hook. "Email marketing tools" for "ESPs" (V5). "Often" kept (V12).
06 · Where you see whose name it is
Almanac ids in this scene: 003.002.016
Whose name is on yours
a test email in an inbox. The three-dot menu opens, Show original. A page of raw header text, and one line lights: dkim=pass header.i=@send-more.example, with dkim=pass in teal and the domain underlined. Then the free header analyzer panel with the same line laid out in rows.
one test, one line, two parts read. Reveals: (1) the test, (2) Show original, (3) the line, (4) the pass, (5) the domain, (6) the analyzer.
the header sheet (V046, reused, S5), the header analyzer panel. Concept auth-results.
003.002.016 "Send any email from your ESP to a Gmail or Outlook account you control. In Gmail, open the message, click the three-dot menu in the top right, and choose "Show original." Look for the Authentication-Results line near the top. A correct setup looks like this: dkim=pass header.i=@yourdomain.example" / "Paste the full header into our email header analyzer for a clean breakdown without reading raw text."
T2 and T7, where and how to read it, and our free tool.
07 · What to do with what you find
Almanac ids in this scene: 003.002.001, 003.002.016
What to do
the header line, three versions one per click: dkim=pass header.i=@mail-tool.example amber, a small arrow to add a record to your DNS · dkim=fail coral · dkim=none coral. A notecard: pass with your domain teal.
three results, one goal. Reveals: (1) the amber pass, (2) the arrow, (3) fail, (4) none, (5) the notecard.
the header line, the notecard.
003.002.001 "If you're using an ESP, they've almost certainly configured DKIM for you, usually by having you add a CNAME or TXT record to your DNS during setup." 003.002.016 "If you see dkim=fail or dkim=none, the signature isn't verifying."
T5, the action. "Ask your tool" is framing for the answer's "aligning your DKIM signature with your sending domain". The record types go to the description (P7).
08 · Recap
What to remember
the seal checked at the gate, the DNS file, the ledger, the two seals, the header line. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 020.002.008
What is RFC 6376 (DKIM)?
the seal with send-more.example, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 020.002.008 "What is RFC 7489 (DMARC)?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 12 scenes, 535 spoken words (recounted 2026-09-30, Q sweep), about 3:26 of speech and about 4:20 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V081What is RFC 7489 (DMARC)?
waiting on YTOpen questions for YT
- C50: DMARCbis "still being finalised" against "published in May 2026", and 020.002.008 silent on it.
- Next video: named in the Q sweep (2026-09-30), 015.003.019, Authentication part 2 episode 1.
- Registry: "no picture yet" for the three policy boxes, the tag chips and the summary sheet.
00 · Both pass, still forged (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 the rule it adds · 2 what to do with failures · 3 the reports · 4 the order to switch it on. Chips 2 to 4 grey.
Here's the plan, in four pieces. The rule DMARC adds. What to do with mail that fails. The reports it sends you. And the order to switch it on in.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The gate and the blank card hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails looks after the list you send to, and DMARC looks after your name when someone else tries to send as you.
02 · Part one: the rule it adds · 0:41
On screen: the forger's envelope from the hook, turned over. Its back label, his own domain (grey, unnamed). Its front, Sally's. The two labels slide towards each other and don't line up, coral. Then a small tab on the case file, DMARCbis, with same record · same settings · same reports.
That's what stops the forger from the start of this video. They pass SPF with a domain they control. But they show your domain in the From. The two don't match, so DMARC fails them. And there's an updated version now, DMARCbis. A revision, not a replacement.
03 · Part two: what to do with failures · 1:30
On screen: the DNS row of case files (video 1). One opens at _dmarc.send-more.example. Inside, three tag chips, one per click, never joined into one line: v=DMARC1 → it's DMARC · p=quarantine → the setting · rua=mailto:sally@send-more.example → where reports go.
Where does that card live? One record in your DNS, under your domain, at a name that starts with dmarc. It says three things. It's DMARC. Here's the setting. And here's where to send the reports.
04 · Part three: the reports · 2:16
On screen: chip 3 lights. From the gate, small report cards travel back to Sally's desk. One is a summary sheet with rows, passing teal and failing coral, one row per sender. The other is a single card, one failure, in detail. Gloss card: aggregate report · the regular summary a receiving server sends back about mail claiming to be you.
The third thing the RFC defines is reporting. When a server gets mail claiming to be from your domain, it can send you a report. Aggregate reports sum up what's passing and failing, across everyone sending as you. Forensic reports give detail on single failures.
05 · The twist: not all strangers · 2:40
On screen: the summary sheet. Its failing rows get labels, one per click: your invoicing tool (amber, a small wrench) · your help desk (amber, a wrench) · unknown sender (coral). The coral row repeats, again and again, down the sheet.
Those reports can surprise you. The senders they turn up aren't all strangers. Some are your own tools, set up wrong. Others are someone pretending to be you. And you'd be surprised how often that's happening quietly, in the background.
06 · Part four: the order to switch it on · 3:02
On screen: the DMARC parser panel, send-more.example typed in, the three tag chips laid out. Then the DMARC generator panel, a blank form turning into the three chips.
Not sure what your record says, or whether you even have one? Check it with our free DMARC parser. Starting from scratch? Our free DMARC generator builds your first record.
07 · Recap · 3:46
On screen: the whole gate: the guest list, the sealed envelope, the filled-in card, a report travelling back. All four chips lit.
Put together. SPF is the guest list. DKIM is the seal. DMARC is the card beside the gate. It checks that the name that passed matches the From, says what to do when it doesn't, and reports back. Start at none, and read before you reject.
08 · Close · 4:22
On screen: the whole gate, the card filled in, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 015.003.019 "What are authentication-related bounces?" (Authentication, part 2, episode 1), no subscribe ask.
Pin up the card, start at none, and read your record in the free DMARC parser before you move it. Your DMARC stays yours. Review My Emails keeps the list behind it clean. Stuck between none and reject? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what are authentication-related bounces?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-020.002.008-what-is-rfc-7489-dmarc.md
00 · Both pass, still forged (hook)
Almanac ids in this scene: 020.002.008
What is RFC 7489 (DMARC)?
four numbered chips, the VO's words: 1 the rule it adds · 2 what to do with failures · 3 the reports · 4 the order to switch it on. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the gate (video 1), concept dmarc (the instruction card beside it).
020.002.008 "SPF checks the sending server. DKIM checks the message signature. Both are useful, but neither one helps ensure the email actually comes from the domain you see in the From field. That's the gap RFC 7489 was written to close."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 020.002.008
no cut away and no ad break. The gate and the blank card hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 020.002.008 "That alignment check is what stops sophisticated spoofing."
never says a clean fixes DMARC (S10).
02 · Part one: the rule it adds
Almanac ids in this scene: 003.003.034, 020.002.008
The rule it adds
the forger's envelope from the hook, turned over. Its back label, his own domain (grey, unnamed). Its front, Sally's. The two labels slide towards each other and don't line up, coral. Then a small tab on the case file, DMARCbis, with same record · same settings · same reports.
two labels that don't line up. One tab. Reveals: (1) the back label, (2) the front, (3) they don't match, (4) coral, (5) the tab.
concept alignment, the two-sided envelope (video 1).
020.002.008 "Without it, an attacker could send from a domain they control (passing SPF), while displaying your domain in the From field." 003.003.034 "DMARCbis is the updated version of the original DMARC specification, not a new protocol or a replacement." / "Everything else (the DMARC record, the p=none/quarantine/reject policies, SPF, DKIM, alignment, and rua reporting) stays the same."
C50 kept out: no date, no status (published or being finalised) voiced. The tab lists only what stays the same.
03 · Part two: what to do with failures
Almanac ids in this scene: 003.003.001, 020.002.008
What to do with failures
the DNS row of case files (video 1). One opens at _dmarc.send-more.example. Inside, three tag chips, one per click, never joined into one line: v=DMARC1 → it's DMARC · p=quarantine → the setting · rua=mailto:sally@send-more.example → where reports go.
one record, three tags. Reveals: (1) the file, (2) to (4) one tag each.
concept dns, the three tag chips.
003.003.001 "you publish a TXT record in your DNS at _dmarc.yourdomain.com." 020.002.008 "That one line tells receiving servers your policy and where to send aggregate reports."
the record is drawn as three chips, never as one line with its separators (zero semicolons). The reports address is the library's sally@send-more.example.
04 · Part three: the reports
Almanac ids in this scene: 020.002.008
The reports
chip 3 lights. From the gate, small report cards travel back to Sally's desk. One is a summary sheet with rows, passing teal and failing coral, one row per sender. The other is a single card, one failure, in detail. Gloss card: aggregate report · the regular summary a receiving server sends back about mail claiming to be you.
many senders summed in one sheet, one card for one failure. Reveals: (1) the cards travel, (2) the summary sheet, (3) its rows, (4) the single card, (5) the gloss.
concept dmarc-aggregate, the report travelling back (registry dmarc).
020.002.008 "When a server receives a message claiming to be from your domain, it can send you a report. Aggregate reports (rua) summarize what's passing and failing across all senders using your domain. Forensic reports (ruf) give detail on individual failures."
05 · The twist: not all strangers
Almanac ids in this scene: 020.002.008
The reports
the summary sheet. Its failing rows get labels, one per click: your invoicing tool (amber, a small wrench) · your help desk (amber, a wrench) · unknown sender (coral). The coral row repeats, again and again, down the sheet.
failing rows, two of them yours, the rest not. Reveals: (1) to (3) one label each, (4) the coral row repeats.
the summary sheet.
020.002.008 "These reports are how you find out about misconfigured third-party senders or someone trying to impersonate your domain (and you'd be surprised how often that's happening quietly in the background)."
T3, the twist. The two tools are drawn by role, never named.
06 · Part four: the order to switch it on
Almanac ids in this scene: 003.003.018, 020.002.008
The order to switch it on
the DMARC parser panel, send-more.example typed in, the three tag chips laid out. Then the DMARC generator panel, a blank form turning into the three chips.
one record read, one record built. Reveals: (1) the parser, (2) the chips, (3) the generator.
the two tool panels.
020.002.008 "if you want to see what your DMARC record currently says (or whether you even have one), you can check it with our free DMARC Parser. And if you're starting from scratch, the DMARC Generator will build your first record"
T2 and T7. The answer's "in about 60 seconds" is not voiced.
07 · Recap
What to remember
the whole gate: the guest list, the sealed envelope, the filled-in card, a report travelling back. All four chips lit.
callbacks only, the full gate for the first time.
callbacks only (S5).
08 · Close
Almanac ids in this scene: 015.003.019
What is RFC 7489 (DMARC)?
the whole gate, the card filled in, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 015.003.019 "What are authentication-related bounces?" (Authentication, part 2, episode 1), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says the DMARC stays yours (S10). The next video is named by its Almanac question word for word (S8, Q sweep 2026-09-30: no dead end at the end of a series). Totals: 13 scenes, 545 spoken words (recounted 2026-09-30, Q sweep), about 3:25 of speech and about 4:40 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V083What is a DMARC or SPF-fail rejection?
waiting on YTOpen questions for YT
- C53: "most receivers" against "many servers" inside 003.001.025.
00 · Rejected per policy (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 whose rule it is · 2 the SPF kind · 3 the DMARC kind · 4 why your own mail trips it. Chips 2 to 4 grey.
Four stops on the way. Whose rule it is. The SPF kind of rejection. The DMARC kind. And why your own mail trips it.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The gate and the turning card hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails looks after who you send to, but this rejection is about who's sending, and the rule you wrote for it.
02 · Part one, the twist: whose rule it is · 0:41
On screen: chip 1 lights. The card finishes turning. On its back, in handwriting, written by send-more.example. A line runs from the card to Sally's DNS case files. The card glows at the gate.
This isn't the receiving server making a judgement call. The domain owner wrote the rules, by publishing records in DNS. The server just enforces them. So if you own the domain, and your own mail is being rejected, your records are wrong, or they're missing something.
03 · How the server reads your rules · 1:05
On screen: the three pieces at the gate light in turn, each with its question as a one-line label: the guest list is this server allowed?, the seal is the seal valid?, the card do they line up with the From?.
What does it read? Three records. SPF, is this server allowed to send for you. DKIM, does the message carry your valid seal. Then DMARC ties both together, and asks one more thing. Do those results line up with the From your reader sees?
04 · Part two: the SPF kind · 1:28
On screen: chip 2 lights. The guest list, its last line lit: ~all amber, soft fail, the envelope waved on with a small amber flag. Then -all coral, fail, and the envelope is pushed back out.
The SPF kind first. The server that sent it isn't on your list. And the result comes back as fail, not softfail. Your SPF record ends with a rule for everyone else. A tilde there means soft fail. A dash means hard fail. With a fail, and a receiving server set to reject on it, back it comes.
05 · Part three: the DMARC kind · 1:56
On screen: chip 3 lights. Two quick envelopes at the card. The first: both ticks coral. The second: both ticks teal, but their labels don't line up with the From, coral. The card's reject box lights, and both are shut out.
The DMARC kind. Either SPF and DKIM both fail. Or they pass, but neither lines up with your From. If your DMARC setting is reject, the server drops the message entirely. The card said so, and the card is yours.
06 · Part four: why your own mail trips it · 2:20
On screen: the DNS row of case files. send-more.example is open, its record teal. The envelope's return label says mail.send-more.example. That case file opens instead. It's empty. A grey card, none, then it turns coral.
And one that catches people out. You send from a subdomain, like mail dot your domain. Your main domain has SPF. The subdomain doesn't inherit it. It's its own entry in DNS. So the server looks there, finds nothing, and SPF comes back none. Many servers treat that as a failure.
07 · What to do · 3:10
On screen: a report card travels back to Sally. It opens as a wall of raw data, then the DMARC parser panel lays it out in rows, one per sender. One row lights coral, your help desk.
Still seeing DMARC failures? Your reports say which sender. They arrive as raw data, so read them in our free DMARC parser. It shows you exactly which sending source is misbehaving.
08 · Recap · 3:50
On screen: the card, its author send-more.example, the three pieces at the gate. All four chips lit.
Here's what it comes to. A DMARC or SPF-fail rejection is the server following your own rule. A fail on SPF, or nothing lining up under reject. When it's your own mail, something new is missing from your records. Find it, and cover it.
09 · Close · 4:22
On screen: the gate, the card written in Sally's hand, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 015.014.005 "How can SPF/DKIM misconfigurations cause indirect bounces?", no subscribe ask.
When your own mail is rejected, read your own rule first, and let the free DMARC parser show which sender broke it. The records are yours to fix. Review My Emails looks after the addresses you send to. Setting up records for clients? Ask about our partner programme. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... how can SPF, DKIM misconfigurations cause indirect bounces?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.003.020-dmarc-spf-fail-rejection.md
00 · Rejected per policy (hook)
Almanac ids in this scene: 015.003.020
What is a DMARC or SPF-fail rejection?
four numbered chips, the VO's words: 1 whose rule it is · 2 the SPF kind · 3 the DMARC kind · 4 why your own mail trips it. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the gate and the card (V081).
015.003.020 "instead of landing in the inbox it came straight back with something like "Message rejected per DMARC policy"" / "it means the receiving server followed exactly the instructions your domain (or the sending domain) published."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 015.003.020
no cut away and no ad break. The gate and the turning card hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 015.003.020 "The domain owner wrote the rules by publishing those DNS records."
never says a clean fixes authentication (S10).
02 · Part one, the twist: whose rule it is
Almanac ids in this scene: 015.003.020
Whose rule it is
chip 1 lights. The card finishes turning. On its back, in handwriting, written by send-more.example. A line runs from the card to Sally's DNS case files. The card glows at the gate.
one rule, one author. Reveals: (1) the card turns, (2) the author, (3) the line to her DNS, (4) the card glows.
concept dmarc (the card), concept dns (the case files).
015.003.020 "It's worth saying clearly: this isn't the receiving server making an editorial decision. The domain owner wrote the rules by publishing those DNS records. The receiving server is just enforcing them. If you're the domain owner and your own emails are getting rejected, the records are either misconfigured or incomplete."
T3, the twist.
03 · How the server reads your rules
Almanac ids in this scene: 015.003.020
Whose rule it is
the three pieces at the gate light in turn, each with its question as a one-line label: the guest list is this server allowed?, the seal is the seal valid?, the card do they line up with the From?.
three questions, asked in order. Reveals: (1) to (3) one each.
the gate, all three part 1 pieces (S5).
015.003.020 "the receiving server checks your SPF record to see whether the IP address that sent the message is actually allowed to send for your domain. It also checks DKIM to see whether the message carries a valid signature from your domain. Then DMARC ties both of those results together and asks one more question: do those results actually align with the From address the recipient sees?"
called back in pictures, not taught again (S6).
04 · Part two: the SPF kind
Almanac ids in this scene: 015.003.020, 020.002.012
The SPF kind
chip 2 lights. The guest list, its last line lit: ~all amber, soft fail, the envelope waved on with a small amber flag. Then -all coral, fail, and the envelope is pushed back out.
two endings, two outcomes. Reveals: (1) the server not on the list, (2) ~all, (3) waved on, (4) -all, (5) pushed back.
concept spf (V078's record line, reused, S5).
015.003.020 "SPF-fail rejection. The sending IP isn't listed in your SPF record, the result comes back as "fail" (not "softfail"), and the receiving server is configured to reject on that result." 020.002.012 "qualifiers like ~all (softfail) and -all (hard fail)."
"waved on" is only "not rejected for this": the video makes no inbox claim for a softfail.
05 · Part three: the DMARC kind
Almanac ids in this scene: 015.003.020
The DMARC kind
chip 3 lights. Two quick envelopes at the card. The first: both ticks coral. The second: both ticks teal, but their labels don't line up with the From, coral. The card's reject box lights, and both are shut out.
two routes to one rejection. Reveals: (1) both fail, (2) pass but don't line up, (3) reject, (4) shut out.
concepts dmarc, alignment (V081, reused, S5).
015.003.020 "DMARC-fail rejection. Both SPF and DKIM fail, or they pass but don't align with the From domain. The domain's DMARC policy is set to p=reject, so the receiving server drops the message entirely."
06 · Part four: why your own mail trips it
Almanac ids in this scene: 003.001.025, 015.003.020
Why your own mail trips it
the DNS row of case files. send-more.example is open, its record teal. The envelope's return label says mail.send-more.example. That case file opens instead. It's empty. A grey card, none, then it turns coral.
two case files, one full, one empty. Reveals: (1) the main file, (2) the label, (3) the empty file, (4) none, (5) coral.
concept dns (the case files).
015.003.020 "You're sending from a subdomain that doesn't inherit your parent domain's SPF or DKIM setup." 003.001.025 "Subdomains don't inherit anything from the parent domain." / "When a receiving server checks SPF for a message sent from captain@mail.deepcurrent.example, it looks up the SPF record at mail.deepcurrent.example, not at deepcurrent.example. If there's nothing at mail.deepcurrent.example, SPF returns "none," which is treated as a failure by many servers."
"help desk" is the plain word for the answer's "support platform". No tool named.
T4, the fresh example. C53 kept out: "many", as the body says.
07 · What to do
Almanac ids in this scene: 003.001.025, 015.003.020
What to do
a report card travels back to Sally. It opens as a wall of raw data, then the DMARC parser panel lays it out in rows, one per sender. One row lights coral, your help desk.
one report, one row that fails. Reveals: (1) the report, (2) the raw data, (3) the rows, (4) the coral row.
concept dmarc-aggregate, the parser panel.
015.003.020 "If DMARC is still showing failures, the DMARC Parser can help you read the XML reports and find exactly which sending source is misbehaving."
T2, where you see it. "Raw data" is the plain word for "XML" (P7).
08 · Recap
What to remember
the card, its author send-more.example, the three pieces at the gate. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 015.014.005
What is a DMARC or SPF-fail rejection?
the gate, the card written in Sally's hand, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 015.014.005 "How can SPF/DKIM misconfigurations cause indirect bounces?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the partner programme (15%), named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word, the slash read as a pause (S8). The 15% is on the end card, not spoken. Totals: 13 scenes, 577 spoken words (recounted 2026-09-30, Q sweep), about 3:43 of speech and about 4:46 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V084How can SPF/DKIM misconfigurations cause indirect bounces?
waiting on YTOpen questions for YT
- C51 and C52: both in one line of 015.014.005.
- Registry: the SMTP transcript page and the pile of returned envelopes have no registry picture yet.
00 · Still bouncing (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 why they're called indirect · 2 how to tell from the bounce · 3 the three things to check · 4 how to stop the bleeding. Chips 2 to 4 grey.
Four parts, starting with the name. Why they're called indirect. How to tell from the bounce. The three things to check. And how to stop the bleeding.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The pile holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
At Review My Emails a bounce usually means the address, but every address on this pile is real, so look behind the sender.
02 · Part one: why they're called indirect · 0:41
On screen: chip 1 lights. One envelope from the pile, replayed at the gate. The three pieces check it, coral. The card beside the gate, its reject box lit. The envelope is pushed back onto the pile. Over it, three lines, one per click: address: real teal, content: fine teal, setup: failed coral.
Why indirect? The receiving server runs its checks, SPF, DKIM and DMARC. Your checks fail. Your DMARC setting says reject. So it doesn't let the message through with a flag. It sends it back. The address exists. The content would have been fine. Your configuration killed the delivery.
03 · Part two: how to tell from the bounce · 1:08
On screen: chip 2 lights. One returned envelope's note, full size, in mono: 550 5.7.x. Three phrases light one per click: Authentication failed, DMARC policy violation, SPF. Beside it, two signposts: reputation grey, authentication teal, and the arrow swings to authentication.
How do you tell it's this, and not your reputation? Read the words. These come back as 550, 5. 7 something, with words like authentication failed, or DMARC policy violation, or SPF, DKIM or DMARC by name. See those, and authentication is your first stop. Not reputation.
04 · Part three: check one, SPF · 1:34
On screen: chip 3 lights. The guest list from V078. Three tags try the gate, one per click: email marketing tool on the list, teal · CRM not on it, coral · receipts tool not on it, coral.
Three things to check, in order. One, SPF. Is every server and service you send from on your record? Not just your email marketing tool. Your CRM. Any tool that sends receipts or password resets from your domain. Miss one, and its mail fails.
05 · Check two, DKIM · 1:58
On screen: the seal from V080 and the key in its case file. They don't match, coral. Then envelopes run through the gate, one after another, every seal cracking coral.
Two, DKIM. Is your public key published in DNS, and is it the right one? If the key in DNS doesn't match the key your mail server signs with, it doesn't fail now and then. It fails every time. Every message, every seal.
06 · Check three, and the twist · 2:22
On screen: chip 4 lights. The card beside the gate, reject lit, the pile still growing. Click: the card slides back to none, grey, and the pile stops growing. Envelopes pass. Then SPF and DKIM go teal, and the card climbs again, quarantine, then reject, teal.
Three, your DMARC setting, and this one can hurt the most. If it's set to reject, and you've got failures, you're bouncing real mail right now. So the first fix is to loosen your own rule. Drop to none for now, to stop the bleeding. Fix the records. Then work back up.
07 · Where the reason is written · 2:52
On screen: the SPF checker panel, send-more.example typed in, the record laid out. Then a small card, SOS · free.
Start with SPF, it's the quickest. Our free SPF checker reads your record in seconds. And if something looks off and you're not sure what to fix, our SOS hotline is free. No pitch, just help.
08 · Recap · 3:34
On screen: the pile, the three checks at the gate, the card going down and back up. All four chips lit.
Boiled down. An indirect bounce is a real address refused because of your setup. The words in the bounce point to authentication. Check SPF, then DKIM, then your DMARC setting. If you're bleeding, drop to none, fix, and climb back.
09 · Close · 4:10
On screen: the gate, envelopes passing, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 018.010.003 "How do DNS or SPF lookup errors affect trust?", no subscribe ask.
When real addresses bounce, look behind you first, starting with the free SPF checker. Your records are yours to fix. Review My Emails sorts out the addresses that were never real. Bouncing right now? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... how do DNS or SPF lookup errors affect trust?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.014.005-spf-dkim-misconfigurations-indirect-bounces.md
00 · Still bouncing (hook)
Almanac ids in this scene: 015.014.005
How can SPF/DKIM misconfigurations cause indirect bounces?
four numbered chips, the VO's words: 1 why they're called indirect · 2 how to tell from the bounce · 3 the three things to check · 4 how to stop the bleeding. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the gate (V078), the pile of returned envelopes, concept dns.
015.014.005 "Your emails are bouncing, the recipient address is valid, your content looks fine, and yet the rejections keep coming. That's the signature of an authentication misconfiguration. The problem isn't the destination. It's your own setup."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 015.014.005
no cut away and no ad break. The pile holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 015.014.005 "The address exists."
never says a clean fixes authentication (S10).
02 · Part one: why they're called indirect
Almanac ids in this scene: 015.014.005
Why they're called indirect
chip 1 lights. One envelope from the pile, replayed at the gate. The three pieces check it, coral. The card beside the gate, its reject box lit. The envelope is pushed back onto the pile. Over it, three lines, one per click: address: real teal, content: fine teal, setup: failed coral.
three checks, one setting, three lines with one cause. Reveals: (1) the checks, (2) reject, (3) back on the pile, (4) to (6) one line each.
the gate, concept dmarc-policies (V081's boxes).
015.014.005 "When a receiving mail server gets your message, it runs three checks: SPF, DKIM, and DMARC." / "the server doesn't just let the message through and flag it. It bounces it back. The address exists. Your content would have been fine. Your configuration killed the delivery." / "That's why these are called indirect bounces. The fix isn't on the recipient's end at all. It's yours."
C51 and C52 kept out. The VO says "your checks fail" (never "SPF or DKIM fails" alone) and names only reject as the setting that sends it back.
03 · Part two: how to tell from the bounce
Almanac ids in this scene: 015.014.005
How to tell from the bounce
chip 2 lights. One returned envelope's note, full size, in mono: 550 5.7.x. Three phrases light one per click: Authentication failed, DMARC policy violation, SPF. Beside it, two signposts: reputation grey, authentication teal, and the arrow swings to authentication.
one code, three phrases, two signposts. Reveals: (1) the code, (2) to (4) one phrase each, (5) the arrow.
the note (video 1, reused, S5).
015.014.005 "The bounce codes you'll see in both cases tend to be 550 5.7.x variants, often with language like "Authentication failed", "DMARC policy violation", or explicit mentions of SPF, DKIM, or DMARC in the rejection message. If you're reading bounce logs and seeing those strings, authentication is your first stop, not reputation."
video 1 owns the code families (S6). This scene only adds the signpost.
04 · Part three: check one, SPF
Almanac ids in this scene: 015.014.005
The three things to check
chip 3 lights. The guest list from V078. Three tags try the gate, one per click: email marketing tool on the list, teal · CRM not on it, coral · receipts tool not on it, coral.
three senders, one covered. Reveals: (1) to (3) one each.
concept spf.
015.014.005 "Check your SPF record and confirm every IP or sending service you use is covered. Don't forget ESPs, CRMs, and any transactional tools that send from your domain."
"email marketing tool" for "ESP" (V5). "Receipts or password resets" is the plain word for "transactional tools". Video 2 owns why a new tool gets missed (S6).
05 · Check two, DKIM
Almanac ids in this scene: 015.014.005
The three things to check
the seal from V080 and the key in its case file. They don't match, coral. Then envelopes run through the gate, one after another, every seal cracking coral.
one mismatch, every message failing. Reveals: (1) the key, (2) the seal, (3) no match, (4) the run of cracked seals.
concept dkim.
015.014.005 "Verify your DKIM public key is published correctly in DNS. A mismatch between what's in DNS and what your mail server is signing with will fail every time." / "DKIM failures ... happen when the public key in your DNS doesn't match the private key used to sign the message, or when the key isn't published at all."
T1, why it matters (every message, not some).
06 · Check three, and the twist
Almanac ids in this scene: 015.014.005, 020.002.008
How to stop the bleeding
chip 4 lights. The card beside the gate, reject lit, the pile still growing. Click: the card slides back to none, grey, and the pile stops growing. Envelopes pass. Then SPF and DKIM go teal, and the card climbs again, quarantine, then reject, teal.
one setting down, the pile stops, two fixes, the setting back up. Reveals: (1) reject and the pile, (2) down to none, (3) the pile stops, (4) the fixes, (5) back up.
concept dmarc-policies.
015.014.005 "Check what your DMARC policy is actually set to. If it's reject and you've got auth failures, you're bouncing real mail. Drop to none temporarily to stop the bleeding, fix the config, then work back up." 020.002.008 "you move to quarantine, then reject."
T3, the twist. V081 owns the order up (S6), called back in the last reveal only.
07 · Where the reason is written
Almanac ids in this scene: 015.014.005
Where the reason is written
the SPF checker panel, send-more.example typed in, the record laid out. Then a small card, SOS · free.
one record read, one call. Reveals: (1) the checker, (2) the card.
the SPF checker panel.
015.014.005 "you can check your SPF record in seconds with our free SPF checker" / "If something looks off and you're not sure what to fix, the SOS hotline is free. No pitch, just help."
T7. The answer's "DKIM record lookup" link points at the header analyzer (V080's note), so no DKIM lookup is voiced.
08 · Recap
What to remember
the pile, the three checks at the gate, the card going down and back up. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 018.010.003
How can SPF/DKIM misconfigurations cause indirect bounces?
the gate, envelopes passing, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 018.010.003 "How do DNS or SPF lookup errors affect trust?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 12 scenes, 497 spoken words (recounted 2026-09-30, Q sweep), about 3:14 of speech and about 4:32 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V085How do DNS or SPF lookup errors affect trust?
waiting on YTOpen questions for YT
- C54: permerror "cascades into DMARC failure" against "lean on DKIM alone".
- Registry: the tally board and the dns-propagation rows have no picture yet.
00 · Everything set up, still sinking (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 the check that couldn't finish · 2 the one that's broken for good · 3 how failures turn into distrust · 4 how to tell which you've got. Chips 2 to 4 grey.
Let's break that into four. The check that couldn't finish. The one that's broken for good. How failures turn into distrust. And how to tell which you've got.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The gate and the flickering line hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails spends its days telling list problems from everything else, and this one looks like a list or reputation problem, but it's neither.
02 · Part one: the check that couldn't finish · 0:41
On screen: chip 1 lights. The gate's line to the DNS case files. A small clock beside it runs out, and a grey card comes back: temperror. The envelope splits into two outcomes, one per click: a small tray, held, try again, and a scale, their own call, amber. Gloss card: temperror · the SPF check couldn't finish, so there's no answer either way.
When your email arrives, the receiving server looks up your SPF record in DNS. If that look-up times out, or can't be resolved, it logs a temperror. A temporary error. It doesn't mean you failed. It doesn't mean you passed. Some servers hold the message and try again. Others treat it as a soft failure and make their own call.
03 · Part two: the one that's broken for good · 1:08
On screen: chip 2 lights. The counter from V078 beside the record, lookups, ticks past its cap, coral. The cracked permerror card from V079. On the card beside the gate, the SPF slot goes coral. Gloss card: permerror · an SPF record the receiving server can't read at all.
The other error is permerror, a record that can't be read at all. Say your record needs more than ten look-ups, often after you add a new tool. The result is a permanent error. Every SPF check fails until you fix it. And DMARC sees the SPF half as a hard failure too.
04 · Part three: how failures turn into distrust · 1:32
On screen: chip 3 lights. A tally board beside the gate, failed checks from send-more.example. One grey mark, then it fills, mark after mark, grey and coral. The board's title changes, one word at a time, to can't prove who it is.
How does this wear down trust? Receiving servers build a picture of you over time. One temperror won't sink you. But if your DNS is flaky, or your SPF keeps hitting permerror, they keep logging failures from your domain. That pattern doesn't look like a glitch. It looks like a domain that can't prove who it is.
05 · The twist: a DNS problem in disguise · 2:00
On screen: two panels, volume and content, both teal. The line chart drops. A label over it, reputation?, peels off like a mask, and underneath, DNS.
Your volume can be clean. Your content can be clean. But your deliverability drops, and it reads like a reputation problem. It isn't. It's a DNS problem in disguise. And that difference matters, because it decides what you go and fix.
06 · Part four: how to tell. Count, then look · 2:22
On screen: two short rows of envelopes. Row one: every seal-slot coral, labelled every time → your record. Row two: coral, teal, teal, coral, labelled now and then → DNS or a resolver. Then the Email Header Analyzer panel, the trail laid out in rows.
Then ask one question. Does it fail every time, or now and then? Every time means a configuration error, your record. Now and then often points to DNS changes still spreading, or a look-up server timing out upstream. Our free Email Header Analyzer reads the whole header trail in one go.
07 · Recap · 3:14
On screen: the grey card, the cracked card, the tally board, the two rows. All four chips lit.
Two errors, one lesson. A temperror means the check couldn't finish. A permerror means it's broken until you fix it. Keep failing, and receivers stop trusting a domain that can't prove who it is. Count your look-ups, read your headers, and ask every time, or now and then.
09 · Close · 3:50
On screen: the gate, the look-up line steady, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 017.007.003 "What is a recommended TTL for SPF/DKIM/DMARC records?", no subscribe ask.
Before you blame your reputation, check your DNS. The records are yours to fix. Review My Emails takes care of the list, the addresses that were never going to work. Wondering about a blocklist instead? Start at our free blocklist directory. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is a recommended TTL for SPF, DKIM, DMARC records?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-018.010.003-dns-spf-lookup-errors-trust.md
00 · Everything set up, still sinking (hook)
Almanac ids in this scene: 018.010.003
How do DNS or SPF lookup errors affect trust?
four numbered chips, the VO's words: 1 the check that couldn't finish · 2 the one that's broken for good · 3 how failures turn into distrust · 4 how to tell which you've got. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the gate (V078), concept dns.
018.010.003 "You've done the work. You've set up SPF, configured DKIM, maybe even added a DMARC policy. But if your DNS records have errors or your SPF is hitting its lookup limit, none of that preparation matters." / "your deliverability tanks and it reads like a reputation problem."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 018.010.003
no cut away and no ad break. The gate and the flickering line hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 018.010.003 "It isn't. It's a DNS problem in disguise."
never says a clean fixes authentication (S10).
02 · Part one: the check that couldn't finish
Almanac ids in this scene: 018.010.003
The check that couldn't finish
chip 1 lights. The gate's line to the DNS case files. A small clock beside it runs out, and a grey card comes back: temperror. The envelope splits into two outcomes, one per click: a small tray, held, try again, and a scale, their own call, amber. Gloss card: temperror · the SPF check couldn't finish, so there's no answer either way.
one look-up, no answer, two ways a server handles it. Reveals: (1) the look-up, (2) the clock runs out, (3) the card, (4) held, (5) their own call, (6) the gloss.
concept dns, the guest list (V078).
018.010.003 "If that query times out, returns an unexpected result, or fails to resolve, the server logs a temperror. That's a temporary error. It means the check couldn't complete, not that you're definitely failing, but not that you're passing either. Some receivers will defer the message and try again. Others will treat it as a soft failure and apply their own judgment about whether to deliver it."
V078 named temperror among the seven results. This is the first video to explain it (S6).
03 · Part two: the one that's broken for good
Almanac ids in this scene: 018.010.003, 018.010.004
The one that's broken for good
chip 2 lights. The counter from V078 beside the record, lookups, ticks past its cap, coral. The cracked permerror card from V079. On the card beside the gate, the SPF slot goes coral. Gloss card: permerror · an SPF record the receiving server can't read at all.
a counter past its cap, one cracked card, one slot lost. Reveals: (1) the counter, (2) past the cap, (3) the cracked card, (4) the SPF slot, (5) the gloss.
concept spf-lookup-limit (V078's counter), V079's cracked card, reused (S5).
018.010.003 "SPF allows a maximum of 10 DNS lookups per check." / "Many senders accidentally exceed this limit, especially after adding a new ... marketing tool. When you go over 10, the result is a permerror. That's a permanent error. Every SPF check fails until you fix it." / "a permerror means DMARC sees SPF as a hard failure too."
V079 owns permerror in full (S6), so this scene re-glosses it in one line for a searcher (Q5), backed by 018.010.004 "returned when the receiver cannot process the record at all". C48 kept to "more than ten". C54 kept out: only the SPF half is said to fail, not DMARC as a whole.
04 · Part three: how failures turn into distrust
Almanac ids in this scene: 018.010.003
How failures turn into distrust
chip 3 lights. A tally board beside the gate, failed checks from send-more.example. One grey mark, then it fills, mark after mark, grey and coral. The board's title changes, one word at a time, to can't prove who it is.
one mark, then a full board, one reading. Reveals: (1) one mark, (2) the board fills, (3) the new title.
the tally board (new).
018.010.003 "Receiving servers and spam filters build a picture of you over time. A single temperror won't sink you. But if your DNS is flaky or your SPF is consistently hitting permerror, the receiving server keeps logging authentication failures from your domain. That pattern looks suspicious. It doesn't look like a technical glitch. It looks like a domain that can't prove who it is."
T1, what the receiver is looking at. N1: the count of marks is the picture, no number on it.
05 · The twist: a DNS problem in disguise
Almanac ids in this scene: 018.010.003
How failures turn into distrust
two panels, volume and content, both teal. The line chart drops. A label over it, reputation?, peels off like a mask, and underneath, DNS.
two clean panels, one drop, one label swapped. Reveals: (1) the panels, (2) the drop, (3) the mask, (4) underneath.
the line chart (V079, reused), concept dns.
018.010.003 "Your sending volume and content might be completely clean, but your deliverability tanks and it reads like a reputation problem. It isn't. It's a DNS problem in disguise. (And yes, that distinction matters a lot when you're troubleshooting.)"
T3, the twist.
06 · Part four: how to tell. Count, then look
Almanac ids in this scene: 018.010.003
How to tell which you've got
two short rows of envelopes. Row one: every seal-slot coral, labelled every time → your record. Row two: coral, teal, teal, coral, labelled now and then → DNS or a resolver. Then the Email Header Analyzer panel, the trail laid out in rows.
two rows, one pattern each. Reveals: (1) row one, (2) its label, (3) row two, (4) its label, (5) the analyzer.
concept dns-propagation (row two), the header analyzer panel.
018.010.003 "Check whether failures are consistent or intermittent. Consistent means a configuration error. Intermittent often points to DNS propagation issues or an upstream resolver timing out." / "Our free Email Header Analyzer reads all of that in one go."
T5, the action. "DNS changes still spreading" is the registry's gloss for dns-propagation, "a look-up server" the plain word for "resolver". "Often", as the answer says (V12).
07 · Recap
What to remember
the grey card, the cracked card, the tally board, the two rows. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 017.007.003
How do DNS or SPF lookup errors affect trust?
the gate, the look-up line steady, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 017.007.003 "What is a recommended TTL for SPF/DKIM/DMARC records?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/directory, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word, the slashes read as pauses (S8). Totals: 11 scenes, 522 spoken words (recounted 2026-09-30, Q sweep), about 3:20 of speech and about 4:14 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V086What is a recommended TTL for SPF/DKIM/DMARC records?
waiting on YTOpen questions for YT
- Registry: TTL has no registry entry.
- Tool idea (T7), for the PM, not voiced: no free tool shows a record's TTL.
00 · The new key nobody sees yet (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 what TTL is · 2 the everyday setting · 3 the trade-off · 4 how to change a record without a gap. Chips 2 to 4 grey.
Four pieces to this one. What TTL is. The everyday setting. The trade-off. And how to change a record without a gap.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The file and its copies hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails cares about what's true right now on your list, and TTL is about what's true right now in DNS.
02 · Part one: what TTL is · 0:41
On screen: chip 1 lights. The case file, then copies fanning out to desks. Each copy gets a small amber timer, keep until. On the file itself, beside the record, a number: TTL 3600 → 1 hour, then TTL 86400 → 1 day. Gloss card: TTL · how long, in seconds, other servers keep a copy of your record before they check for a new one.
Your record lives in one place. But servers around the world keep a copy, so they don't have to ask every time. TTL, time to live, tells them how long to keep that copy before checking again. It's a number of seconds, set on each record. 3600 is an hour. 86400 is a day.
03 · Part two: the everyday setting · 1:08
On screen: chip 2 lights. Three records in the case file, SPF, DKIM, DMARC, each with TTL 3600, teal. The copies' timers all read 1 hour.
What should yours be? For most senders, 3600. One hour. Your SPF record rarely changes once it's settled. Same with DKIM. So an hour is a solid middle ground, and it's what most providers recommend for routine use.
04 · Part three: the trade-off · 1:30
On screen: chip 3 lights. A balance. On one side, long timers, change is slow amber. On the other, short timers and a stream of arrows back to Sally's file, more checks on your servers amber. The balance settles on 3600 for everyday, then tips to low with a changing now tag.
Why not just set it high, or low? Because each costs something. High means copies last longer, so a change takes longer to reach everyone. Low means changes spread fast, but more checks land on your own DNS servers. For records that rarely change, high is fine. For records you're changing, go low for a while.
05 · When it matters · 1:56
On screen: chip 4 lights. Three change cards, one per click: new DKIM key, DMARC: none → quarantine, SPF: new include. Each lands on the case file while the copies around it still show the old version, coral.
When does it matter? When you change something. Swapping your DKIM key, like Sally. Moving your DMARC setting up from none. Editing what's included in your SPF record. That's when slow copies become a real problem.
06 · The twist: lower it the day before · 2:18
On screen: replay: the TTL drops to 300 and the change lands in the same click. The copies' timers still read 1 day, coral, and don't move. Rewind. The TTL drops to 300 alone. A clock runs 24 hours. One by one, the copies' timers shrink to 5 min, amber. Only then does the change land, and the copies refresh fast, teal.
Timing is the trap. Lowering it on the day doesn't help. Every copy out there is still holding the old timer. An hour. Maybe a day. So you lower it first, and let it sit for 24 hours, until every copy has picked up the short timer. Then you change the record.
07 · The steps · 2:44
On screen: the SPF checker panel, send-more.example typed in, the new record shown, teal, beside a small tag, live DNS.
And after the change, don't just trust that it worked. Testing straight away can mislead you. Our free SPF checker reads live DNS and shows exactly what the world is seeing right now.
08 · Recap · 3:26
On screen: the case file, the copies, the timers, the four-step card. All four chips lit.
Short version. TTL is how long other servers keep a copy of your record. An hour is the everyday setting. Before a change, drop it to five or ten minutes and wait a day. Then change the record, check it, and put the hour back.
09 · Close · 4:00
On screen: the case file and its copies, all timers matching, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 020.002.009 "What is RFC 8617 (ARC)?", no subscribe ask.
Set an hour, lower it the day before any change, and check the result in the free SPF checker. Your DNS stays yours. Review My Emails keeps the list you send to just as current. Changing records for clients? Ask about our partner programme. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is RFC 8617, ARC?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-017.007.003-ttl-for-spf-dkim-dmarc-records.md
00 · The new key nobody sees yet (hook)
Almanac ids in this scene: 017.001.006, 017.007.003
What is a recommended TTL for SPF/DKIM/DMARC records?
four numbered chips, the VO's words: 1 what TTL is · 2 the everyday setting · 3 the trade-off · 4 how to change a record without a gap. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
concept dns (the case file), concept dns-propagation (the copies, first time drawn).
017.007.003 "If you're rotating DKIM keys, consider lowering TTL to 300-600 seconds before you make the switch. Lower TTL means ISPs pick up your new key faster, reducing the window where messages might fail authentication." 017.001.006 "During propagation, different senders may see different versions of your record."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 017.001.006
no cut away and no ad break. The file and its copies hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 017.001.006 "Recursive DNS servers around the world cache your old record to save time."
never says a clean fixes authentication (S10).
02 · Part one: what TTL is
Almanac ids in this scene: 017.001.006
What TTL is
chip 1 lights. The case file, then copies fanning out to desks. Each copy gets a small amber timer, keep until. On the file itself, beside the record, a number: TTL 3600 → 1 hour, then TTL 86400 → 1 day. Gloss card: TTL · how long, in seconds, other servers keep a copy of your record before they check for a new one.
one file, many copies, one timer each. Reveals: (1) the copies, (2) the timers, (3) 3600, (4) 86400, (5) the gloss.
concept dns, concept dns-propagation.
017.001.006 "Recursive DNS servers around the world cache your old record to save time." / "TTL is a number you set on each DNS record that tells caching servers how long (in seconds) to hold onto it before checking for updates. A TTL of 3600 means servers cache your record for one hour. A TTL of 86400 means they hold it for a full day."
T2, where TTL sits (a number on each record). N4: said for the ear, digits for the eye, the same.
03 · Part two: the everyday setting
Almanac ids in this scene: 017.007.003
The everyday setting
chip 2 lights. Three records in the case file, SPF, DKIM, DMARC, each with TTL 3600, teal. The copies' timers all read 1 hour.
three records, one setting. Reveals: (1) to (3) one record each, (4) the timers.
the case file with three records.
017.007.003 "Your SPF record rarely changes once you've locked it down. Same with DKIM. For most senders, setting TTL to 3600 seconds is a solid middle ground." / "Most providers recommend 3600 for routine use."
3600 is a setting, not a rate or a pass mark.
04 · Part three: the trade-off
Almanac ids in this scene: 017.007.003
The trade-off
chip 3 lights. A balance. On one side, long timers, change is slow amber. On the other, short timers and a stream of arrows back to Sally's file, more checks on your servers amber. The balance settles on 3600 for everyday, then tips to low with a changing now tag.
two sides, one cost each. Reveals: (1) the high side, (2) its cost, (3) the low side, (4) its cost, (5) everyday, (6) changing now.
a balance (new).
017.007.003 "High TTL means faster delivery once a resolver caches your record, but changes take longer to roll out globally. Low TTL spreads updates faster but puts more load on your authoritative nameservers. For authentication records that rarely change, high is fine. For records you're actively modifying, go low temporarily, then bump it back up once you're done."
"your own DNS servers" is the plain word for "authoritative nameservers" (P6).
05 · When it matters
Almanac ids in this scene: 017.007.003
How to change a record without a gap
chip 4 lights. Three change cards, one per click: new DKIM key, DMARC: none → quarantine, SPF: new include. Each lands on the case file while the copies around it still show the old version, coral.
three changes, each with stale copies. Reveals: (1) to (3) one change each, (4) the stale copies.
the case file and copies.
017.007.003 "Before a planned change (DKIM key rotation, DMARC policy move from p=none to p=quarantine or p=reject, SPF include: edits), lower TTL to 300 to 600 seconds" / "Same logic applies if you're moving your DMARC policy from 'none' to 'quarantine' or 'reject'. That's when slow propagation becomes a real problem."
V081 owns why you move up from none (S6), named here only as a change.
06 · The twist: lower it the day before
Almanac ids in this scene: 017.001.006, 017.007.003
How to change a record without a gap
replay: the TTL drops to 300 and the change lands in the same click. The copies' timers still read 1 day, coral, and don't move. Rewind. The TTL drops to 300 alone. A clock runs 24 hours. One by one, the copies' timers shrink to 5 min, amber. Only then does the change land, and the copies refresh fast, teal.
the same change twice, one with a gap, one without. Reveals: (1) same-day drop, (2) stale timers, (3) rewind, (4) the day, (5) the timers shrink, (6) the change, (7) teal.
concept dns-propagation.
017.007.003 "drop to 300-600 before, let it sit for 24 hours so everything caches the new low value, then flip your record" 017.001.006 "lower your TTL before you make the change. If you drop it to 300 seconds (five minutes) a day or two in advance, old caches clear quickly and your update spreads in near real-time."
T3, the twist. "Every copy is still holding the old timer" is the plain reading of "so everything caches the new low value".
07 · The steps
Almanac ids in this scene: 017.001.006, 017.007.003
How to change a record without a gap
the SPF checker panel, send-more.example typed in, the new record shown, teal, beside a small tag, live DNS.
one live look. Reveals: (1) the panel, (2) the record, (3) the tag.
the SPF checker panel.
017.001.006 "That's why testing immediately after a change can give you misleading results." / "verify it with a DNS lookup tool rather than just trusting that it worked. Our free SPF checker will query live DNS and show you exactly what the world is seeing right now."
T2 and T7. The checker is shown for the SPF record only, as the answer backs it.
08 · Recap
What to remember
the case file, the copies, the timers, the four-step card. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 020.002.009
What is a recommended TTL for SPF/DKIM/DMARC records?
the case file and its copies, all timers matching, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 020.002.009 "What is RFC 8617 (ARC)?", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the partner programme (15%), named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word, as part 1 read "RFC 7489, DMARC" (S8). The 15% is on the end card, not spoken. Totals: 12 scenes, 509 spoken words (recounted 2026-09-30, Q sweep), about 3:22 of speech and about 4:22 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V087What is RFC 8617 (ARC)?
waiting on YTOpen questions for YT
- C55: does your own email tool sign ARC.
- Next video: named in the Q sweep (2026-09-30), 012.004.001 (V088).
- Registry: arc has a gloss and no picture.
00 · Nobody spoofed anything (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 why forwarding breaks the checks · 2 what ARC does · 3 who sets it up · 4 what it can't do. Chips 2 to 4 grey.
Four things, in the order they happen. Why forwarding breaks the checks. What ARC does. Who sets it up. And what it can't do.
01 · Brought to you by, woven in · 0:31
On screen: no cut away and no ad break. The envelope at the second stop holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails sorts out which failures are yours, and some aren't, because your mail can fail after it has left you.
02 · Part one: why forwarding breaks the checks · 0:41
On screen: chip 1 lights. The second stop re-sends the envelope from a new post box: the SPF tick smudges, coral. It stamps a footer on: the seal cracks, coral. At the final gate, two shadows side by side, spoofer? and mailing list?, and a grey ? over the gate.
Why does it fail? SPF checks the server that sent the mail, and a forward goes out from a new server, so SPF breaks. DKIM is a seal on the message, and a footer added on the way breaks that too. So the last server sees a failure, and it can't tell a spoofer from a mailing list just doing its job.
03 · Part two: what ARC does · 1:08
On screen: the logbook's line opens into three header lines, one per click, each with a plain label under it: ARC-Authentication-Results → what the checks found · ARC-Message-Signature → signs the message · ARC-Seal → seals the chain.
Each entry is three lines added to the header. One records what the checks found. One signs the message. And one seals the chain, so nobody can slip a line in later.
04 · Where you'll meet it · 1:54
On screen: three stops on the envelope's road, one per click: work → personal forward (to wren@mailbox.example), mailing list · subject tag, footer, security gateway · scan, re-route. Each adds a line to the logbook, teal.
Where will you run into it? Someone forwards their work email to a personal inbox. A mailing list adds a tag to the subject, or a footer. Or a security gateway scans your message and re-routes it before delivery. Each one is a stop that can break the checks.
05 · Part three: who sets it up · 2:16
On screen: chip 3 lights. Sally's desk, a settings panel with no ARC switch on it, grey. Then the three stops light up, each holding a pen for the logbook, teal.
Who sets it up? Not you. As a sender, you don't configure ARC. The stops in the middle do. Mailing lists, forwarders, security gateways. If you run one of those, it's your job. If you just send, it isn't.
06 · Part four, the twist: what it can't do · 2:40
On screen: the three part 1 pieces at the first gate, teal. The logbook's first line writes itself, pass, teal, and the envelope travels on.
Your job stays the same, then. A valid SPF record, solid DKIM, a working DMARC policy. Pass those before your mail reaches a forwarder, and the logbook's first line says pass. The forwarder's ARC handles the rest.
07 · Where to see it · 3:28
On screen: a DMARC report card (V081) with one failing row, forwarded. Then a header pasted into the Email Header Analyzer panel, the three ARC lines from scene 03b laid out in rows, the first result pass, teal.
Seeing DMARC failures in your reports, and forwarding's in the picture? ARC is where to look. Paste the header of one of those messages into our free Email Header Analyzer. It shows whether ARC seals are there, and what they report.
08 · Recap · 3:48
On screen: the envelope's whole road, the logbook with its signed lines, the first line teal. All four chips lit. The whole gate from part 1 behind it, for the last time in this series.
In one breath. Forwarding breaks the checks through no fault of yours. ARC is a sealed logbook each stop signs, so the last server can see you passed at the start. You don't set it up. You make sure that first line says pass.
09 · Close · 4:22
On screen: the envelope's road, the logbook signed at every stop, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 012.004.001 "What is content reputation?" (V088, Sending and engagement, part 1, episode 1), no subscribe ask.
Get the basics right before your mail leaves, and let the logbook do the rest. Your authentication stays yours. Review My Emails takes care of the list it goes to. Failures you can't explain? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. And next... what is content reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-020.002.009-what-is-rfc-8617-arc.md
00 · Nobody spoofed anything (hook)
Almanac ids in this scene: 020.002.009
What is RFC 8617 (ARC)?
four numbered chips, the VO's words: 1 why forwarding breaks the checks · 2 what ARC does · 3 who sets it up · 4 what it can't do. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
the gate and envelope (V078 to V081).
020.002.009 "You've set up SPF, DKIM, and DMARC correctly. Everything looks clean. Then someone forwards one of your emails through a mailing list, and suddenly DMARC fails. No spoofing happened. No one did anything wrong. The forwarding just broke the authentication chain. That's the exact problem ARC was built to fix."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 020.002.009
no cut away and no ad break. The envelope at the second stop holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress" 020.002.009 "understanding it helps you make sense of why DMARC reports sometimes show failures that aren't actually your fault."
never says a clean fixes authentication (S10).
02 · Part one: why forwarding breaks the checks
Almanac ids in this scene: 020.002.009
Why forwarding breaks the checks
chip 1 lights. The second stop re-sends the envelope from a new post box: the SPF tick smudges, coral. It stamps a footer on: the seal cracks, coral. At the final gate, two shadows side by side, spoofer? and mailing list?, and a grey ? over the gate.
two checks lost, two possible senders, no way to tell. Reveals: (1) new server, SPF, (2) the footer, the seal, (3) the two shadows.
the envelope and seal (V046, V080, reused, S5).
020.002.009 "The server IP changes (breaking SPF). The message body might get a footer added (breaking DKIM). When the receiving mailbox then runs DMARC, it sees a failed authentication and has no way to know whether that failure came from a spoofer or just a legitimate mailing list doing its job."
V046 owns this (S6), called back in one line. C35: only the footer case breaks the seal, as V046 said.
03 · Part two: what ARC does
Almanac ids in this scene: 003.005.001, 020.002.009
What ARC does
the logbook's line opens into three header lines, one per click, each with a plain label under it: ARC-Authentication-Results → what the checks found · ARC-Message-Signature → signs the message · ARC-Seal → seals the chain.
one entry, three lines. Reveals: (1) to (3) one line each.
concept email-header.
020.002.009 "Each hop adds three headers (ARC-Authentication-Results, ARC-Message-Signature, and ARC-Seal) cryptographically sealing what it saw on arrival" 003.005.001 "that entry is locked with a digital signature so it can't be forged."
T10, the Almanac's own simile.
the three names are on screen for scene 07, not spoken (P7). "Seals the chain, so nobody can slip a line in later" is the plain reading of "so it can't be forged".
04 · Where you'll meet it
Almanac ids in this scene: 020.002.009
Where you'll meet it
three stops on the envelope's road, one per click: work → personal forward (to wren@mailbox.example), mailing list · subject tag, footer, security gateway · scan, re-route. Each adds a line to the logbook, teal.
three kinds of stop, one line each. Reveals: (1) to (3) one stop each.
concept arc.
020.002.009 "Email forwarding (someone forwards work email to a personal inbox)" / "Mailing list software that adds subject tags or footers" / "Security gateways that scan and re-route messages before delivery"
T4, the gateway is the example people don't think of.
05 · Part three: who sets it up
Almanac ids in this scene: 003.005.009, 020.002.009
Who sets it up
chip 3 lights. Sally's desk, a settings panel with no ARC switch on it, grey. Then the three stops light up, each holding a pen for the logbook, teal.
one sender with nothing to switch on, three stops that write. Reveals: (1) Sally's panel, (2) to (4) one stop each.
concept arc.
020.002.009 "As a sender, you don't configure ARC yourself. It's handled by the intermediaries." 003.005.009 "ARC is implemented by intermediaries like mailing list services, email forwarders, and security gateways" / "If you run a mailing list, manage an email forwarding service, or operate a security gateway, you do need to implement ARC."
C55 kept out: your own email tool is not said to sign or not sign.
06 · Part four, the twist: what it can't do
Almanac ids in this scene: 003.005.008, 003.005.009
What it can't do
the three part 1 pieces at the first gate, teal. The logbook's first line writes itself, pass, teal, and the envelope travels on.
three basics, one first line. Reveals: (1) to (3) one piece each, (4) the first line.
the gate, concept arc.
003.005.009 "As a sender, your job is still the basics: valid SPF, solid DKIM, and a working DMARC policy. If your emails pass those checks before they hit a forwarder, the forwarder's ARC implementation will handle the rest."
T5, the action.
07 · Where to see it
Almanac ids in this scene: 020.002.009
Where to see it
a DMARC report card (V081) with one failing row, forwarded. Then a header pasted into the Email Header Analyzer panel, the three ARC lines from scene 03b laid out in rows, the first result pass, teal.
one failing row, three lines read. Reveals: (1) the report row, (2) the paste, (3) the lines, (4) the pass.
concept dmarc-aggregate, the header analyzer panel.
020.002.009 "If you're seeing unexpected DMARC failures in your reports and forwarding is in the picture, ARC is where to look. You can analyze the email headers directly with our free Email Header Analyzer to see if ARC seals are present and what they're reporting."
T2 and T7, where and how, and our tool.
08 · Recap
What to remember
the envelope's whole road, the logbook with its signed lines, the first line teal. All four chips lit. The whole gate from part 1 behind it, for the last time in this series.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 012.004.001
What is RFC 8617 (ARC)?
the envelope's road, the logbook signed at every stop, teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, 012.004.001 "What is content reputation?" (V088, Sending and engagement, part 1, episode 1), no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says the authentication stays yours (S10). The next video is named by its Almanac question word for word (S8, Q sweep 2026-09-30: no dead end at the end of a series, the next V number in VIDEO-INDEX.md). Totals: 13 scenes, 556 spoken words (recounted 2026-09-30, Q sweep), about 3:35 of speech and about 4:44 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V088What is content reputation?
waiting on YTOpen questions for YT
- C56: vary your templates (012.004.001) vs no need to redesign (012.004.002, 012.004.004).
- Registry: the print on the envelope (content-fingerprinting) and the three-gauge row (content-reputation) are new pictures to register.
00 · Everything passes, and it still lands in spam (hook) · 0:00
On screen: four numbered chips, the VO's words: 1 what they judge · 2 what spoils it · 3 what a new domain won't wash off · 4 how to tell, and what to do. Chips 2 to 4 grey.
Four parts. What they judge. What spoils it. What a new domain won't wash off. And how to tell it's the content, and what to do.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
What you send is half the story, and Review My Emails checks the other half, whether the people it lands with can still get it.
02 · Part one: what they judge · 0:40
On screen: chip 1 lights. The envelope opens flat. Five small labels light on it, one per click: words · code · images · links · layout. Beside it, three gauges in a row: domain · IP · content. Only the third one moves.
What are they judging? The stuff inside your email. The words, the code underneath, the images, the links, the layout. Gmail and Outlook give all of that its own trust score. It sits apart from your domain's reputation, and apart from your IP's. The email earns a record of its own.
03 · How they know it's the same email · 1:02
On screen: the layout of the envelope presses down into a fingerprint on its front. A second envelope slides in with a new subject line and a new picture, and its print lines up with the first one, a small bell icon rings. Then a row of small reactions appears under the print: opened · clicked · deleted unread · spam.
But how do they know it's the same email next time? They take its fingerprint. The layout and the text get turned into a signature. And it doesn't need to be an exact match. You can change the subject line and swap the main image, and still ring the same bell. Then they watch what people do with it.
04 · Part two: what spoils it · 1:30
On screen: chip 2 lights. The print, with the spam reaction ticking up until the print turns coral, flagged. Then four small smudges land on it, one per click: subject that tricks · all picture, no text · links that don't match · hidden unsubscribe.
When enough people mark that print as spam, it gets flagged on future messages. Even from other senders. What spoils it most? A subject line the email doesn't live up to. People feel tricked, and hit spam. An email that's nearly all picture and hardly any text. Links that don't go where the words say. And an unsubscribe link nobody can find, so they reach for the spam button instead.
05 · Part three: the twist, a new domain won't wash it off · 2:02
On screen: chip 3 lights. The coral print lifts off the envelope and lands on a fresh one tagged new domain. A small row of past spam prints slides in beside it, and the match lights up. The new domain tag fades, the print stays.
Here's the part that catches people off guard. Sally could move to a brand-new domain. But if she brings the same content with her, the print comes too. Filters compare it with known spam, and if it's close enough, it's flagged, whoever sent it. That's why spammers keep swapping domains. And why it doesn't work for long.
06 · Part four: how to tell it's the content · 2:28
On screen: chip 4 lights. Gloss card, one line: Google Postmaster Tools · Google's free dashboard that shows how Gmail views your sending domain. A plain dashboard frame, its domain reputation row reading fine, next to a spam tray that fills. Then two envelopes side by side, template A and template B, landing in two different trays.
How do you tell it's the content? Open Google Postmaster Tools. If it shows no domain reputation problem, but delivery still feels off, that gap often points to content. Two more signs. Spam placement climbs even though your sign-in checks pass. Or two different templates in a test land in wildly different places.
07 · What to do about it · 2:58
On screen: the print, with a small list of cards behind it. A few cards are crossed out, coral. The checking lamp passes over and lifts them away, and the rates beside the print read true.
One catch. Those signs only point to content on a clean list. Dead addresses and people who never read drag your rates down too, and wear on your reputation. Ruling those out first is what a clean does.
08 · Recap · 3:48
On screen: the print, the four smudges, the new envelope, the dashboard frame. All four chips lit.
Here's the gist. Your email has a record of its own. People's reactions build it. A new domain won't wash it off. Rule out the list, then read the signs, and send to your most engaged subscribers first.
09 · Close · 4:04
On screen: the teal print on a clean envelope. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
Treat your content as its own record. Cleaning fixes addresses, never content. If your placement shifted and you can't see why, our SOS hotline is free. Try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how does frequency affect engagement decay?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-012.004.001-what-is-content-reputation.md
00 · Everything passes, and it still lands in spam (hook)
Almanac ids in this scene: 012.004.001
What is content reputation?
four numbered chips, the VO's words: 1 what they judge · 2 what spoils it · 3 what a new domain won't wash off · 4 how to tell, and what to do. Chips 2 to 4 grey.
a count of four chips. Reveals: the chips.
one envelope. No print yet.
012.004.001 "Spam folder placement increases even though your authentication is set up correctly and your domain reputation looks fine." / "Think of it as the record your messages build on their own, independent of who sent them."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The envelope holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress". The VO's who it lands with is paid off in scene 07 ("send to engaged subscribers first") and scene 07b.
02 · Part one: what they judge
Almanac ids in this scene: 012.004.001
What they judge
chip 1 lights. The envelope opens flat. Five small labels light on it, one per click: words · code · images · links · layout. Beside it, three gauges in a row: domain · IP · content. Only the third one moves.
five parts, three gauges, one of them the email's own. Reveals: (1) to (5) the labels, (6) the three gauges, (7) the third one moves.
concept content-reputation (no picture yet), with the sender-reputation gauge drawn three times.
012.004.001 "the trust score that mailbox providers attach to the actual stuff inside your emails: the text, HTML structure, images, links, and formatting patterns. It's separate from your domain reputation and your IP reputation."
"Gmail and Outlook" are the answer's own examples, named as mailbox providers, not as a claim about their systems beyond the answer.
03 · How they know it's the same email
Almanac ids in this scene: 012.004.001, 012.004.002
What they judge
the layout of the envelope presses down into a fingerprint on its front. A second envelope slides in with a new subject line and a new picture, and its print lines up with the first one, a small bell icon rings. Then a row of small reactions appears under the print: opened · clicked · deleted unread · spam.
two envelopes, one print. Reveals: (1) the print forms, (2) the second envelope, (3) the prints line up, (4) the reactions.
concept content-fingerprinting (no picture yet). This print is the video's one picture from here.
012.004.002 "They generate a signature from the structural elements of your message and compare it against what they've seen before." / "providers don't need an exact match." / "You can change the subject line and swap the hero image and still ring the same bell." 012.004.001 "tracking how recipients respond to each format."
the "80 percent" figure is not voiced (P7, how-to detail, and no number to read as a target). "Hash" is not voiced: "fingerprint" is the one word (P5).
04 · Part two: what spoils it
Almanac ids in this scene: 012.004.001
What spoils it
chip 2 lights. The print, with the spam reaction ticking up until the print turns coral, flagged. Then four small smudges land on it, one per click: subject that tricks · all picture, no text · links that don't match · hidden unsubscribe.
one print, four smudges. Reveals: (1) the spam count rises, (2) coral, (3) to (6) the smudges.
the print.
012.004.001 "When enough recipients mark a particular content pattern as spam, that fingerprint gets flagged across future messages, even from different senders." / "Misleading or high-pressure subject lines that don't match the body. Readers open, feel tricked, and hit spam." / "Image-heavy emails with very little text." / "Link destinations that don't match their anchor text" / "Recipients who can't find the unsubscribe button hit the spam button instead."
70 words, the cap (S2). The trigger-phrase bullet is held (C25, V951 owns it). The link line is the destination only, as V033 (C24 kept out).
05 · Part three: the twist, a new domain won't wash it off
Almanac ids in this scene: 012.004.001
What a new domain won't wash off
chip 3 lights. The coral print lifts off the envelope and lands on a fresh one tagged new domain. A small row of past spam prints slides in beside it, and the match lights up. The new domain tag fades, the print stays.
one print, two envelopes. Reveals: (1) the new envelope, (2) the print moves, (3) the spam row, (4) the match, (5) the tag fades.
the print, carried to a new envelope (P2, the print holds still, the envelope changes).
012.004.001 "Even switching to a brand-new domain won't fully protect you if you bring the same content patterns with you." / "Hash-based filters compare fingerprints of your message body against known spam samples. If the match is close enough, the message gets flagged regardless of sender identity. That's why spammers rotate domains constantly, and why it doesn't actually work for long."
T3, the twist. V12: "won't fully protect you" is kept as "the print comes too", not "you're always flagged". "Close enough" is the answer's own wording.
06 · Part four: how to tell it's the content
Almanac ids in this scene: 004.007.001, 012.004.001
How to tell, and what to do
chip 4 lights. Gloss card, one line: Google Postmaster Tools · Google's free dashboard that shows how Gmail views your sending domain. A plain dashboard frame, its domain reputation row reading fine, next to a spam tray that fills. Then two envelopes side by side, template A and template B, landing in two different trays.
one fine row against one filling tray, then two templates, two trays. Reveals: (1) the gloss, (2) the fine row, (3) the tray fills, (4) the two templates, (5) the two trays.
concept google-postmaster (no picture yet, a plain frame, no real screen drawn), and the print on both test envelopes.
012.004.001 "Gmail Postmaster Tools shows no domain reputation issues, but delivery still feels off. That gap often points to content." / "Spam folder placement increases even though your authentication is set up correctly and your domain reputation looks fine." / "A/B tests with meaningfully different templates produce wildly different inbox placement rates. The content is the variable." Gloss: 004.007.001 "Google Postmaster Tools is a free dashboard from Google that shows you how Gmail views your sending domain."
T2, where to look. V12: "often points to" is kept.
07 · What to do about it
Almanac ids in this scene: 005.001.012, 012.004.001, 012.004.002
Before you blame the content
the print, with a small list of cards behind it. A few cards are crossed out, coral. The checking lamp passes over and lifts them away, and the rates beside the print read true.
a few cards out, then the rates settle. Reveals: (1) the list behind, (2) the crossed cards, (3) the lamp lifts them.
the print, and the lamp (concept list-cleaning).
012.004.001 "Your open rates drop sharply despite a clean list and consistent sending volume." 005.001.012 "unengaged and invalid addresses inflate the denominator" / "sending to dead or complaining addresses degrades domain reputation at Gmail and Outlook"
T5, the action. T7, our tool, which the answer names. C56: "Vary your templates" is not voiced as a rule. The VO says only what all three answers agree on.
Q3: moved before the recap. Q2: the pivot comes from this topic (rule the list out before blaming content), no catch-all. Q12: the old line named "opens dropping" as the first warning sign, which scene 06 never says, so it now points at "those signs".
T6 and R15 (YT, 2026-09-29). Backed by the answer's own condition, not by a catch-all line this time (T4).
08 · Recap
What to remember
the print, the four smudges, the new envelope, the dashboard frame. All four chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 012.004.001
The email's own record
the teal print on a clean envelope. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: /sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
012.004.001 "the SOS hotline is free."
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 13 scenes (00 to 09, with 00b and 07b). Word count in Step 4. Over two minutes, so no Short cut note (R12).
V089How does frequency affect engagement decay?
waiting on YTOpen questions for YT
- C30 add: a fourth set of windows (005.010.015).
- Tool idea (T7): the Frequency Cap Calculator exists on preview only.
- Registry: the door and its letters, the calendar strip.
00 · More emails, fewer readers (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what silence means · 2 how more turns warm readers cold · 3 before you send more. Chips 2 and 3 grey.
Three parts. What silence means, and why it depends on your schedule. How sending more can turn warm readers cold. And what to do before you send more.
01 · Brought to you by, woven in · 0:27
On screen: no cut away and no ad break. A row of doors, one or two with no light behind them. A small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Sending more means more mail to every address on your list, the empty ones too, and Review My Emails finds the empty ones.
02 · Part one: count the emails, not the days · 0:38
On screen: chip 1 lights. One door, with a strip of the last thirty days under it. Daily: thirty small letters land, one per tick, the door stays dark. Then the strip resets to monthly: one letter in the same thirty days. A small counter under each: 30 letters and 1 letter.
Why does silence depend on your schedule? Count the emails, not the days. Thirty days of silence, for a daily sender, is thirty ignored emails. That's a clear signal. For a monthly sender, it's one email. Calling someone inactive after one chance would be absurd.
03 · Move the line when you change the schedule · 1:04
On screen: the door and its strip. A small line marked inactive after slides along the strip when the schedule changes. One card under the door gets a grey not yet tag instead of a flag.
What happens when you change how often you send? Move your inactive line with it. The count underneath has changed. Someone who looked fine on the old schedule hasn't had enough chances on the new one yet. Give them time before you flag them.
04 · Part two, the twist: sending more can cause the decay · 1:25
On screen: chip 2 lights. The door, lit teal, one letter a month, the door opens each time. Then the letters come daily. The door opens less, then not at all, its light going teal to amber to coral.
Now the other side, and it's the one people miss. Sending more can cause the decay. Picture someone mildly interested. They'd happily read a monthly email. Daily, they get overwhelmed, and start ignoring everything, not just the extra ones. Over time, the volume turned a warm reader cold.
05 · Why one cooling reader matters to all of them · 1:51
On screen: zoom out from the one door to a whole street of doors. The amber and coral doors spread. A small inbox tray at the end of the street shrinks, even for the teal doors.
Why does that matter beyond one reader? Mailbox providers like Gmail measure engagement across everything you send. When a big part of your list stops engaging, it changes how your mail is treated for everyone. Your active readers too. So a big, half-quiet list, mailed more often, often hurts more than it helps.
06 · Part three: before you send more · 2:18
On screen: one door on the street with a throwaway tag. One letter, it flickers open once, then the light goes out and the door turns into a plain outline. The checking lamp passes over the street and lifts it out, coral.
One more thing. Some of that silence was never a reader cooling off. A throwaway inbox can open once, then go dark. Nobody checks it. No schedule brings that back. A clean spots those addresses before they skew your count.
07 · Recap · 3:02
On screen: the door and strip, the sliding line, the dimming door, the sieve. All three chips lit.
The short version. Count the emails, not the days. Move the line when the schedule changes. More sends can turn warm readers cold. And before you turn it up, run a re-engagement pass and suppress the silence.
09 · Close · 3:17
On screen: the teal street, letters landing, doors opening. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
Set your line by the emails, not the calendar, and clear the quiet ones before you send more. No list check makes anyone read more. It takes out the addresses nobody reads. Rather we did it for you? That's RME Clean. Or try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what's the difference between static and dynamic segmentation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.010.015-frequency-and-engagement-decay.md
00 · More emails, fewer readers (hook)
Almanac ids in this scene: 005.010.015
How does frequency affect engagement decay?
three numbered chips, the VO's words: 1 what silence means · 2 how more turns warm readers cold · 3 before you send more. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the calendar strip. The door arrives in scene 02.
005.010.015 "Someone who's mildly interested might happily read a monthly email but get overwhelmed by a daily one and start ignoring everything." / "Over time, you've turned a warm subscriber cold through volume."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.007.023, 015.001.001
no cut away and no ad break. A row of doors, one or two with no light behind them. A small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress". 005.007.023 "the inbox is never checked". Paid off in scene 06b.
02 · Part one: count the emails, not the days
Almanac ids in this scene: 005.010.015
What silence means
chip 1 lights. One door, with a strip of the last thirty days under it. Daily: thirty small letters land, one per tick, the door stays dark. Then the strip resets to monthly: one letter in the same thirty days. A small counter under each: 30 letters and 1 letter.
the same thirty days, thirty letters against one. Reveals: (1) the door and strip, (2) thirty letters, (3) the counter, (4) the reset, (5) one letter, (6) its counter.
the door on the calendar strip, this video's one picture.
005.010.015 "Send more often and your activity window for measuring inactivity gets shorter." / "If you're mailing daily, someone who hasn't opened in 30 days has ignored 30 consecutive emails. That's a pretty clear signal." / "If you're mailing monthly, someone who hasn't opened in 30 days has only had one chance. Calling them inactive at that point would be absurd."
V045's line is called back in one sentence (S6). The thirty is the answer's own example and a count of emails, not a window to copy (C30 add). N5: 30 days, one a day, 30 emails.
03 · Move the line when you change the schedule
Almanac ids in this scene: 005.010.015
What silence means
the door and its strip. A small line marked inactive after slides along the strip when the schedule changes. One card under the door gets a grey not yet tag instead of a flag.
one line that moves with the schedule. Reveals: (1) the schedule changes, (2) the line slides, (3) the not yet tag.
the door.
005.010.015 "If you've recently changed your sending frequency, update your inactivity thresholds accordingly." / "might not have had enough chances to click under a weekly one. Give them time before you flag them."
the answer's own case is monthly to weekly. The VO keeps it general ("the old schedule, the new one"), no direction claimed beyond the answer's.
04 · Part two, the twist: sending more can cause the decay
Almanac ids in this scene: 005.010.015
How more turns warm readers cold
chip 2 lights. The door, lit teal, one letter a month, the door opens each time. Then the letters come daily. The door opens less, then not at all, its light going teal to amber to coral.
the same door, more letters, less light. Reveals: (1) monthly, open, (2) daily letters, (3) amber, (4) coral.
the door.
005.010.015 "High sending frequency can also accelerate the decay of borderline subscribers. Someone who's mildly interested might happily read a monthly email but get overwhelmed by a daily one and start ignoring everything. Over time, you've turned a warm subscriber cold through volume."
T3, the twist. V12: "can" and "might" are kept as "can" and a "picture someone" example, never a rule for every reader.
05 · Why one cooling reader matters to all of them
Almanac ids in this scene: 005.010.015
How more turns warm readers cold
zoom out from the one door to a whole street of doors. The amber and coral doors spread. A small inbox tray at the end of the street shrinks, even for the teal doors.
one door to a street, the tray shrinking for all of them. Reveals: (1) zoom out, (2) the spread, (3) the tray shrinks.
the door, zoomed out to a street (N3), and the inbox-placement tray.
005.010.015 "Inbox providers like Gmail measure engagement signals across your full sending volume. When a large portion of your list isn't engaging, it affects how your mail is treated for everyone, including your active readers. This is why sending to a huge, partially-disengaged list at high frequency often hurts more than it helps."
T1, the why. "Gmail" is the answer's own example.
06 · Part three: before you send more
Almanac ids in this scene: 005.007.005, 005.007.023, 005.010.009, 005.010.015
Silence with no one behind it
one door on the street with a throwaway tag. One letter, it flickers open once, then the light goes out and the door turns into a plain outline. The checking lamp passes over the street and lifts it out, coral.
one door, one flicker, then out. Reveals: (1) the tag, (2) the flicker, (3) dark, (4) the lamp lifts it.
the door, the lamp (concept list-cleaning).
Q3: moved before the recap. Q2: the pivot comes from this topic (silence that was never a reader), no catch-all.
005.007.005 "they create a single fake open before going dark, which inflates initial engagement then accelerates decay" 005.007.023 "the inbox is never checked"
T5, the action. T2, where: the quiet segment goes through the sieve before the schedule changes.
T6 and R15 (YT, 2026-09-29). A throwaway inbox this time, not a catch-all (T4). V021 owns what a disposable provider is, one line here (S6).
07 · Recap
What to remember
the door and strip, the sliding line, the dimming door, the sieve. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Count the emails, not the days
the teal street, letters landing, doors opening. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 12 scenes (00 to 09, with 00b and 06b, no 08). Word count in the PR body. Over two minutes, so no Short cut note (R12).
V090What’s the difference between static and dynamic segmentation?
waiting on YTOpen questions for YT
- C57: platform naming for dynamic segments (014.008.003, 006.003.010).
- Registry: the frame as photo and window, the two pipes.
00 · The list that never noticed (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the photo, and why it goes stale · 2 the window, and where it matters · 3 which one wins, for which job. Chips 2 and 3 grey.
Three parts. The photo, and why it goes stale. The window, and where it matters. And which one wins, for which job.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The frame holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Whichever kind you build, a segment is only as good as the addresses inside it, and Review My Emails checks those.
02 · Part one: the photo · 0:38
On screen: chip 1 lights. The frame takes a flash, and a thin white photo border snaps around it, January buyers. The calendar turns to February. Half the cards get a small bought again tag, a few go amber, not opened since. The photo doesn't change.
A static segment is a photo. You build the list, and who's on it is fixed right then. It only changes if you go in and update it yourself. Export everyone who bought in January, and by next month it's frozen in time. Half of them have bought again. Some haven't opened an email since.
03 · Why a frozen list hurts · 1:02
On screen: Sally's spring frame again, engaged, eight small month marks along its edge. Most cards amber. An envelope flies to each amber card, and a small reputation gauge beside the frame drifts down.
Why does that matter? Because people keep changing, and the photo doesn't. An 'engaged' list built eight months ago holds people who stopped opening seven months ago. You're still mailing them as if they're active. And that wears down your sender reputation.
04 · Part two: the window · 1:26
On screen: chip 2 lights. The photo border dissolves, and the frame becomes a window with a small rule card on its sill: clicked in the last 30 days. An amber card slides out of the window, a card that clicks slides back in, lit teal.
A dynamic segment is a window, not a photo. It runs on a rule. Say, 'clicked in the last 30 days'. Someone who goes quiet falls out by themselves. Someone who starts clicking again drops back in. The segment always shows your list as it is today.
05 · Where the difference bites · 1:48
On screen: two small flows side by side, welcome and re-engagement, each with a pipe to a frame. New cards arrive at the edge of the screen. The pipe to the photo lets none of them in. The pipe to the window takes each one in as it arrives.
Where does the difference bite hardest? Inside your automations. If your welcome flow or your re-engagement run pulls from a static list, it never picks up anyone who qualifies after you built it. A dynamic segment keeps the flow up to date, without you babysitting it every week.
06 · Part three, the twist: the photo still wins one job · 2:12
On screen: chip 3 lights. The photo, stamped with a date, sent: 12 Oct, sits next to the window. Weeks pass. The window's cards have moved. The photo's cards are exactly where they were, and a small record tick lands on it.
Does the window always win? No. The photo still wins one job, proof. If you need to show exactly who got a campaign on a given date, a static list is a clean, unchanged record. A dynamic one can shift between the day you send and the day you check.
07 · The rule of thumb · 2:36
On screen: a sign-up sheet photo, event import, slides toward the frame. A few cards on it are crossed out, coral. The checking lamp passes over the sheet and lifts them out before it lands.
One more thing. A one-time import is a photo in its purest form. And your email marketing tool will happily send to every address in it, the bad ones too, then log the bounces and dent your reputation. Clean it before it goes in.
08 · Recap · 3:22
On screen: the frozen photo, the window, the two pipes, the dated record. All three chips lit.
Photo or window, in short. A static list is a photo, frozen when you built it. A dynamic one is a window, run on a rule. Flows want the window. Proof wants the photo. And any photo you import gets cleaned first.
09 · Close · 3:36
On screen: the window, cards moving, all teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
Use the window for anything that should stay current, and the photo for proof. Sorting segments is your call. Making sure there's someone behind each card is ours. Rather we did it for you? That's RME Clean. Or try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is lifecycle segmentation in email?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-014.008.003-static-vs-dynamic-segmentation.md
00 · The list that never noticed (hook)
Almanac ids in this scene: 006.001.012
What's the difference between static and dynamic segmentation?
three numbered chips, the VO's words: 1 the photo, and why it goes stale · 2 the window, and where it matters · 3 which one wins, for which job. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the frame, this video's one picture.
006.001.012 "An 'engaged subscribers' list built eight months ago now contains people who stopped opening seven months ago, but you're still mailing them as if they're active"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The frame holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress". Paid off in scene 07b.
02 · Part one: the photo
Almanac ids in this scene: 014.008.003
The photo
chip 1 lights. The frame takes a flash, and a thin white photo border snaps around it, January buyers. The calendar turns to February. Half the cards get a small bought again tag, a few go amber, not opened since. The photo doesn't change.
one frozen frame, half tagged, a few amber. Reveals: (1) the flash, (2) the border, (3) February, (4) the tags, (5) the amber.
the frame, as a photo.
014.008.003 "Static segments fix membership at creation time: you build the list, and it doesn't change unless you manually re-export or update it." / "Imagine you export a list of everyone who bought from you in January and drop it into a campaign. Next month, that list is frozen in time. Half those people have bought again. Some have never opened an email since."
03 · Why a frozen list hurts
Almanac ids in this scene: 006.001.012
The photo
Sally's spring frame again, engaged, eight small month marks along its edge. Most cards amber. An envelope flies to each amber card, and a small reputation gauge beside the frame drifts down.
eight months on the frame, seven of them quiet for most cards, the gauge falling. Reveals: (1) the month marks, (2) the amber, (3) the envelopes, (4) the gauge.
the frame, with concept sender-reputation (the score gauge).
006.001.012 "a segment defined once becomes stale the moment subscriber behavior changes, and behavior changes constantly." / "An 'engaged subscribers' list built eight months ago now contains people who stopped opening seven months ago, but you're still mailing them as if they're active, which degrades sender reputation."
T1, the why. N5: eight months built, quiet for seven, so they went quiet one month in.
04 · Part two: the window
Almanac ids in this scene: 006.003.010, 014.008.003
The window
chip 2 lights. The photo border dissolves, and the frame becomes a window with a small rule card on its sill: clicked in the last 30 days. An amber card slides out of the window, a card that clicks slides back in, lit teal.
one window, one rule, cards moving in and out. Reveals: (1) the border goes, (2) the rule card, (3) one out, (4) one in.
the frame, as a window (P2, the frame holds, only its border changes).
014.008.003 "Dynamic segments work off rules. A contact qualifies when they meet the criteria, and they exit when they no longer do." / "Someone who was active in March but went quiet in April will automatically fall out of that segment." / "The segment always reflects the current state of your list." 006.003.010 "You define the rule once ("clicked any email in the last 30 days") and your email platform keeps it fresh."
the rule is a click rule, per V062 and C46. "30 days" is the example rule's wording, not a window to copy.
05 · Where the difference bites
Almanac ids in this scene: 014.008.003
The window
two small flows side by side, welcome and re-engagement, each with a pipe to a frame. New cards arrive at the edge of the screen. The pipe to the photo lets none of them in. The pipe to the window takes each one in as it arrives.
two pipes, new cards reaching only one. Reveals: (1) the two flows, (2) the new cards, (3) the photo pipe stays empty, (4) the window pipe fills.
the frame, photo and window side by side.
014.008.003 "If your welcome flow or re-engagement campaign draws from a static list, it won't pick up new people who qualify after you built it. Dynamic segments fix that. They keep your automations self-updating so you're not manually babysitting membership rules every week."
T2, where: in the flow, the list it pulls from.
06 · Part three, the twist: the photo still wins one job
Almanac ids in this scene: 014.008.003
Which one wins
chip 3 lights. The photo, stamped with a date, sent: 12 Oct, sits next to the window. Weeks pass. The window's cards have moved. The photo's cards are exactly where they were, and a small record tick lands on it.
one date, one frame that moved and one that didn't. Reveals: (1) the date stamp, (2) weeks pass, (3) the window has changed, (4) the photo hasn't, (5) the tick.
the frame, photo and window.
014.008.003 "Where static still wins is accountability and compliance. If you need to prove exactly who received a specific campaign on a specific date, a static list gives you a clean, unchanged record. Dynamic segments can shift between the time you send and the time you audit."
T3, the twist. The date on screen is a made-up example, not a claim.
07 · The rule of thumb
Almanac ids in this scene: 005.006.006, 006.001.012, 014.008.003
Before it goes in
a sign-up sheet photo, event import, slides toward the frame. A few cards on it are crossed out, coral. The checking lamp passes over the sheet and lifts them out before it lands.
one sheet, a few cards out, before import. Reveals: (1) the sheet, (2) the crossed cards, (3) the lamp lifts them, (4) it lands clean.
the frame, the lamp (concept list-cleaning).
005.006.006 "If you import a list with 8% known-bad addresses, your ESP will happily send to all of them, log the bounces, and ding your reputation." / "Most senders should clean before importing"
T5, the action. T2, where. V12: "almost always" is voiced as a rule of thumb, "pick by the job", not "always". No platform or product name (C57). No rebuild cadence voiced, "on a schedule" only.
Q3: moved before the recap. Q2: the pivot comes from this topic (an import is a photo nobody checked), no catch-all.
T6 and R15 (YT, 2026-09-29). Backed by the import line, not a catch-all line this time (T4).
08 · Recap
What to remember
the frozen photo, the window, the two pipes, the dated record. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
A photo or a window
the window, cards moving, all teal. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 12 scenes (00 to 09, with 00b and 07b). Word count in the PR body. Over two minutes, so no Short cut note (R12).
V091What is lifecycle segmentation in email?
waiting on YTOpen questions for YT
- Next-video line: the next question carries "(e.g., company size, industry, job title - B2B)".
- Registry: the map with five stops.
00 · Right email, wrong moment (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the stops, and each one's job · 2 where it's won or lost · 3 keeping the map honest. Chips 2 and 3 grey.
Three parts. The stops, and each one's job. The stop where it's won or lost. And keeping the map honest, so the right email reaches the right person.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The two cards hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every stop on that map is only worth an email if someone's still at the address, and Review My Emails checks that.
02 · Part one: the stops · 0:39
On screen: chip 1 lights. A path draws itself left to right with five stops, one per click: new · first-time buyer · active · at-risk · lapsed. A small sixth stop pops up above active, VIP, dotted.
Lifecycle segmentation groups people by where they are with you, and sends what fits that stage. The core stops. A new subscriber. A first-time buyer. An active customer. An at-risk customer, fading but not gone yet. And a lapsed one. Some programs add a top tier, for their best customers.
03 · Why each stop needs its own email · 1:03
On screen: a small job card lands on each of the first three stops, one per click: a reason to stay · a second step · keep it up, don't over-mail.
Why split them up? Because each stop has a different job. A new subscriber needs a reason to stay, before any pitch. A first-time buyer needs a nudge to a second step, that's where real retention starts. And active customers need the relationship kept up. Keep them informed, reward them, and don't over-mail them.
04 · Part two, the twist: the stop where it's won or lost · 1:28
On screen: chip 2 lights. A card on active slides to at-risk and turns amber, a small clock over it. A short run of emails reaches it there, and it slides back to active, teal. A second card slips on to lapsed, coral. One win-back email, no answer, and the card drops into the suppress pot, its lid closing.
Here's the stop people miss. Not lapsed. At-risk. They're fading, but they haven't gone dark. It's your most time-sensitive group. A targeted re-engagement run here costs far less than a win-back later. And lapsed? Try a win-back. If that fails, suppress them, to protect your sender reputation.
05 · Part three: how you wire it · 1:56
On screen: chip 3 lights. A plain settings panel, no product drawn, with two date fields: last engaged · last order. A small arrow on the path between new and first-time buyer, tagged first purchase. Then a paper card beside the panel, triggers, written first.
How do you run it? In your email marketing tool, set each stop's rule from two dates. When they last engaged, and when they last ordered. Then let automations move people along when they cross a line. A first purchase moves a new subscriber to customer. Write those triggers down before you touch the tool. Most messes start with fuzzy triggers.
06 · Who wins when someone fits two stops · 2:22
On screen: the active stop, crowded. Half its cards turn into plain outlines, and envelopes keep flying to them. The checking lamp passes over the stop and lifts the outlines away, coral. The triggers fire only on the cards that stay.
One thing no rule can fix. Automation only works on clean data. If your active stop is half invalid addresses, your triggers keep messaging ghosts, and your sender reputation pays for it. So check the addresses before the rules run.
07 · Recap · 3:07
On screen: the map with its job cards, the amber card saved, the paper card, the test copy. All three chips lit.
The map, in short. Sort people by where they are with you. Give each stop its own job. Save them at at-risk, before they lapse. Write your rules down, including who wins, and test them on a copy first.
09 · Close · 3:22
On screen: the map, clean, cards moving stop to stop. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its full question, "What is firmographic segmentation in email? (e.g., company size, industry, job title - B2B)", no subscribe ask.
Map the stops, and watch at-risk closest. Moving people along is your automation's job. Making sure its triggers fire on real people is ours. Check addresses as they arrive, through our API, or try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... what is firmographic segmentation in email? For example, company size, industry and job title.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-006.007.001-what-is-lifecycle-segmentation.md
00 · Right email, wrong moment (hook)
Almanac ids in this scene: 006.007.001
What is lifecycle segmentation in email?
three numbered chips, the VO's words: 1 the stops, and each one's job · 2 where it's won or lost · 3 keeping the map honest. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
two cards. The map arrives in scene 02.
006.007.001 "You wouldn't pitch a loyalty reward to someone who signed up yesterday, and you wouldn't send a basic welcome email to a customer who's bought from you a dozen times. Lifecycle segmentation is how you avoid both of those mistakes."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001
no cut away and no ad break. The two cards hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress". Paid off in scene 06b.
02 · Part one: the stops
Almanac ids in this scene: 006.007.001
The stops, and each one's job
chip 1 lights. A path draws itself left to right with five stops, one per click: new · first-time buyer · active · at-risk · lapsed. A small sixth stop pops up above active, VIP, dotted.
five stops on one path, one optional stop above. Reveals: (1) to (5) the stops, (6) the dotted VIP stop.
the map, this video's one picture. Concept segmentation.
006.007.001 "Grouping subscribers by where they are in their relationship with your brand and sending content that matches that stage." / "The core stages are: new subscriber (just joined, hasn't converted), first-time buyer or trial user, active customer (buying or engaging regularly), at-risk customer (engagement or purchase frequency declining), and lapsed customer" / "Some programs also include a champion or VIP tier at the top for high-value customers"
03 · Why each stop needs its own email
Almanac ids in this scene: 006.007.001, 006.007.002
The stops, and each one's job
a small job card lands on each of the first three stops, one per click: a reason to stay · a second step · keep it up, don't over-mail.
three stops, three jobs. Reveals: (1) to (3) the job cards.
the map.
006.007.001 "Each stage has a different email job. New subscribers need onboarding that builds trust and answers "why should I stay on this list."" 006.007.002 "Email goal: build trust and establish relevance before pitching anything." / "Your job now is reducing buyer's remorse and encouraging a second action, that's when real retention begins." / "keep them informed, reward loyalty, and don't over-mail them."
T1, the why. "Don't over-mail them" calls back video 2 of this series without re-teaching it.
04 · Part two, the twist: the stop where it's won or lost
Almanac ids in this scene: 006.007.001, 006.007.002
Where it's won or lost
chip 2 lights. A card on active slides to at-risk and turns amber, a small clock over it. A short run of emails reaches it there, and it slides back to active, teal. A second card slips on to lapsed, coral. One win-back email, no answer, and the card drops into the suppress pot, its lid closing.
one card saved at at-risk, one lost at lapsed. Reveals: (1) the slide to at-risk, (2) the clock, (3) the run, (4) back to active, (5) the second card to lapsed, (6) the win-back, (7) the pot.
the map, and concept suppression-list (the pot, its lid closing).
006.007.002 "At-risk customer: engagement or purchase frequency is declining, but they haven't gone fully dark. This is your most time-sensitive segment. A targeted re-engagement sequence here costs far less than a win-back campaign later." 006.007.001 "Lapsed customers need a win-back campaign, and if that fails, a suppression decision to protect your sender reputation."
T3, the twist. V074 to V077 own the run and V045 the suppression call (S6): no timing, no run size (C31).
05 · Part three: how you wire it
Almanac ids in this scene: 006.007.001, 006.007.004
Keeping the map honest
chip 3 lights. A plain settings panel, no product drawn, with two date fields: last engaged · last order. A small arrow on the path between new and first-time buyer, tagged first purchase. Then a paper card beside the panel, triggers, written first.
two dates, one trigger arrow, one card. Reveals: (1) the panel, (2) the dates, (3) the arrow, (4) the card moves along it, (5) the paper card.
the map, with a plain panel.
006.007.001 "define the behavioral criteria for each stage in your ESP, typically based on engagement dates and purchase history, and set up automations that move subscribers between stages when they meet or fall below thresholds." 006.007.004 "First purchase moves prospect to customer." / "Write these rules on paper before you touch the tool. Most messes start with fuzzy triggers."
T2, where. T5, the action. No day counts voiced (C30, C46).
62 words. The answer's "prospect" is voiced as "new subscriber", the video's own stop name (P5).
06 · Who wins when someone fits two stops
Almanac ids in this scene: 006.007.004
Before the rules run
the active stop, crowded. Half its cards turn into plain outlines, and envelopes keep flying to them. The checking lamp passes over the stop and lifts the outlines away, coral. The triggers fire only on the cards that stay.
one stop, half of it outlines, then lifted out. Reveals: (1) the outlines, (2) the envelopes, (3) the lamp, (4) the clean stop.
the map, the lamp (concept list-cleaning).
006.007.004 "Automation only works on clean data. If your active segment is half invalid addresses, you'll keep messaging ghosts and killing your sender reputation. Validate before the rules run" / "so triggers fire on real people."
T4, a fresh example. T5, the action. T1, the why. "Records" is the plain word for "rows".
T6 and R15 (YT, 2026-09-29). Backed by the answer's own closing line, not a catch-all line (T4).
Q3: moved before the recap. Q2: the pivot comes from this topic (triggers firing on dead data), no catch-all.
07 · Recap
What to remember
the map with its job cards, the amber card saved, the paper card, the test copy. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Keep the map honest
the map, clean, cards moving stop to stop. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its full question, "What is firmographic segmentation in email? (e.g., company size, industry, job title - B2B)", no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: the API, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video's question is voiced word for word up to its question mark. Its bracketed examples are on screen only, since "e.g." does not read aloud (S8, noted for the PM). Totals: 12 scenes (00 to 09, with 00b and 06b). Word count in the PR body. Over two minutes, so no Short cut note (R12).
V092What is firmographic segmentation in email? (e.g., company size, industry, job title - B2B)
waiting on YTOpen questions for YT
- Title: the Almanac question carries "(e.g., company size, industry, job title - B2B)".
- Registry: the contact card with a company badge, the tracks.
00 · One pitch, two companies (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what you sort by, and why · 2 using it without overdoing it · 3 how fast it goes stale. Chips 2 and 3 grey.
Three parts. What you sort by, and why. How to use it without overdoing it. And the catch, how fast it goes stale.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The two cards hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
With business lists, the person behind a work address can move on, and Review My Emails checks which addresses still land.
02 · Part one: what you sort by · 0:40
On screen: chip 1 lights. A badge clips on to the contact card, and four lines fill on it, one per click: size · industry · title · department. Gloss card, one line: enrichment · a service that matches an email address to a job title, company size and industry, without asking the subscriber.
Firmographic segmentation is for business lists. It groups contacts by company traits, not personal ones. Four main ones. Company size, by staff or revenue. Industry. Job title. And department. Most of that data comes from enrichment tools.
03 · Why the company changes the pitch · 1:04
On screen: the badge's size line lights. Two small lists slide out from it, small: quick setup · cost · no IT team and big: security review · fits our tools · formal buying. Then the title line lights, and the one card becomes two, engineering manager and finance chief, same company line on both.
Why does the company matter so much? Because they buy differently. Small businesses care about quick setup, cost, and not needing their own IT people. Big companies care about security reviews, fitting their existing tools, and formal buying steps. And the title goes one layer deeper. An engineering manager needs different content than the finance chief, even at the same company.
04 · Part two: using it without overdoing it · 1:32
On screen: chip 2 lights. The cards fan into a small set of tracks, 6 to 8, and a crossed-out pile beside them, 60. Then one email close up: its greeting line stays the same, its opening paragraph swaps. Last, a small line on the badge, matched, not told, with a don't imply tag.
How do you use it? Start with separate tracks by company size and role. Different language, proof and calls to action in each. Keep it to six to eight working segments, not sixty. Change the angle of the message, not just the name in the greeting. And never use matched data to hint at a relationship they never gave you.
05 · Part three, the twist: the finer the aim, the worse stale data hurts · 2:00
On screen: chip 3 lights. The badge's lines go amber one by one: title: changed jobs · company: acquired · size: grew. A small clock on the badge, 12 to 18 months. Then the tracks from scene 04 split finer, and the amber spreads faster through the finer ones.
Here's the catch. Firmographic data goes stale fast. People change jobs. Companies get bought. Startups grow out of the small-business tier. Treat anything older than twelve to eighteen months as suspect. And the finer your targeting, the more damage stale data does.
06 · What to do about stale badges · 2:26
On screen: the card with its badge, IT director, still teal on the badge. The address line under it turns coral and the envelope bounces back. The checking lamp passes over and lifts the card out before the send.
And one thing an audit of titles won't show you. When someone leaves a company, their work address goes dead. The badge still says 'IT director'. The mailbox is gone. A clean finds those before you send.
07 · Recap · 3:04
On screen: the badge, the tracks, the email, the amber clock. All three chips lit.
In short. Sort business contacts by company size, industry, title and department. Change the angle, not the greeting. Keep your segments few. And before a big campaign, audit the old badges, and the addresses behind them.
09 · Close · 3:19
On screen: the cards in their tracks, teal badges. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
Sort by the company, write for the role, and keep your badges fresh. Job titles are yours to keep current. Whether each address still works is what a clean tells you. Rather we did it for you? That's RME Clean. Or try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how can inbox metrics predict reputation decay?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-006.004.003-what-is-firmographic-segmentation.md
00 · One pitch, two companies (hook)
Almanac ids in this scene: 006.004.003
What is firmographic segmentation in email?
three numbered chips, the VO's words: 1 what you sort by, and why · 2 using it without overdoing it · 3 how fast it goes stale. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the contact card, this video's one picture. The badge arrives in scene 02.
006.004.003 "The pitch that lands with a five-person startup is usually wrong for the IT director at a 5,000-person enterprise. Even if both are interested in your product."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 004.011.006, 015.001.001
no cut away and no ad break. The two cards hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress". 004.011.006 "corporate email addresses go dead when employees leave companies." Paid off in scene 06b.
02 · Part one: what you sort by
Almanac ids in this scene: 006.004.003, 006.004.004
What you sort by, and why
chip 1 lights. A badge clips on to the contact card, and four lines fill on it, one per click: size · industry · title · department. Gloss card, one line: enrichment · a service that matches an email address to a job title, company size and industry, without asking the subscriber.
one badge, four lines. Reveals: (1) the badge, (2) to (5) the lines, (6) the gloss.
the card and its badge.
006.004.003 "Firmographic segmentation is a B2B targeting method that groups email contacts by company-level attributes rather than individual behavior. The core dimensions are company size (employee count or revenue), industry vertical, job title, and department, typically pulled from enrichment tools" Gloss: 006.004.004 "B2B enrichment services (Clearbit, ZoomInfo, Apollo) that match an email to job title, company size, industry, and tech stack without asking the subscriber."
no enrichment vendor named. "Business lists" is the plain word for B2B.
03 · Why the company changes the pitch
Almanac ids in this scene: 006.004.003
What you sort by, and why
the badge's size line lights. Two small lists slide out from it, small: quick setup · cost · no IT team and big: security review · fits our tools · formal buying. Then the title line lights, and the one card becomes two, engineering manager and finance chief, same company line on both.
two sizes, three needs each, then one company, two roles. Reveals: (1) the size line, (2) small needs, (3) big needs, (4) the title line, (5) the two cards.
the card and its badge.
006.004.003 "SMBs care about quick setup, cost efficiency, and not needing dedicated IT support. Enterprises prioritize security reviews, integrations with existing tools, and formal procurement processes. Job title goes one layer deeper: an engineering manager needs different content than a CFO, even if they work at identical companies."
T1, the why. "Finance chief" is the plain word for CFO.
61 words.
04 · Part two: using it without overdoing it
Almanac ids in this scene: 006.004.003, 006.004.006
Using it without overdoing it
chip 2 lights. The cards fan into a small set of tracks, 6 to 8, and a crossed-out pile beside them, 60. Then one email close up: its greeting line stays the same, its opening paragraph swaps. Last, a small line on the badge, matched, not told, with a don't imply tag.
six to eight tracks against sixty, then one email with one part changed. Reveals: (1) the tracks, (2) the crossed pile, (3) the email, (4) the paragraph swaps, (5) the tag.
the cards, fanned into tracks.
006.004.003 "The clearest quick win is creating separate nurture tracks by company size and role. The language, proof points, and CTAs can be meaningfully different for each." 006.004.006 "Six to eight working segments beats sixty. Personalize the angle of the message, not the salutation. And never use enriched third-party data to imply a relationship the recipient never gave you."
T5, the action. T2, where it shows: the opening, not the greeting. "Six to eight" is a count of segments, not a rate.
61 words.
05 · Part three, the twist: the finer the aim, the worse stale data hurts
Almanac ids in this scene: 006.004.003
How fast it goes stale
chip 3 lights. The badge's lines go amber one by one: title: changed jobs · company: acquired · size: grew. A small clock on the badge, 12 to 18 months. Then the tracks from scene 04 split finer, and the amber spreads faster through the finer ones.
one badge ageing, then fine tracks taking more damage than broad ones. Reveals: (1) to (3) the amber lines, (4) the clock, (5) the finer split, (6) the spread.
the card and its badge, going out of date.
006.004.003 "Firmographic data gets stale fast. People change jobs, companies get acquired, startups graduate out of the SMB tier. Treat firmographic data older than 12 to 18 months as suspect." / "The more granular your targeting, the more damage stale data does."
T3, the twist. The age is the answer's own, for badge data, not a decay rate (C13 kept out).
06 · What to do about stale badges
Almanac ids in this scene: 004.011.006, 005.011.001, 006.004.003
When the person leaves
the card with its badge, IT director, still teal on the badge. The address line under it turns coral and the envelope bounces back. The checking lamp passes over and lifts the card out before the send.
one card, a live badge on a dead address. Reveals: (1) the badge, (2) the address turns coral, (3) the bounce, (4) the lamp lifts it.
the card, the lamp (concept list-cleaning).
Q3: moved before the recap. Q2: the pivot comes from this topic (the title outlives the job), no catch-all.
004.011.006 "corporate email addresses go dead when employees leave companies." 005.011.001 "People change jobs and stop using their work email."
T5, the action. V019 owns the preference center (S6), named only.
T6 and R15 (YT, 2026-09-29). Backed by the B2B bounce line, not a catch-all line (T4).
07 · Recap
What to remember
the badge, the tracks, the email, the amber clock. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
The title outlives the job
the cards in their tracks, teal badges. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: Sending and engagement, part 1, the next video by its question, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
says what a clean does not do (S10). The next video is named by its Almanac question word for word (S8). Totals: 12 scenes (00 to 09, with 00b and 06b). Word count in the PR body. Over two minutes, so no Short cut note (R12).
V093How can inbox metrics predict reputation decay?
waiting on YTOpen questions for YT
- Next video: named by the Q sweep (2026-09-30): V072, 005.001.011.
- Registry: the dashboard with four needles, the seed list picture.
00 · The notice that never comes (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the four early signs · 2 a trend, or noise · 3 when to act. Chips 2 and 3 grey.
Three parts. The four early signs, and where to find them. How to tell a trend from noise. And when to act.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The dashboard holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some of those needles move because of who's on your list, and Review My Emails checks those addresses before the needles move.
02 · Part one: why early signs matter · 0:39
On screen: chip 1 lights. The dashboard, four small needles in a row under the big dial, each with a blank label that fills in its own scene.
Why watch the small needles at all? Because your metrics aren't just a scorecard. They're an early warning system. Decay rarely announces itself. Four signs tend to shift before placement falls. Here's the first.
03 · Sign one, and the twist: a drop at one provider · 0:58
On screen: needle one fills in, opens by provider. The report splits into three small bars, one per provider. All three dip, tagged could be content. Then reset: only the Gmail bar dips, the others hold, tagged reputation. A small + clicks, complaints tag clips on to the needle.
Split your open rates by mailbox provider. A drop across your whole list could be your content. But a drop at Gmail alone, while Outlook holds steady? That points to reputation at that provider, not your content. The specificity is the tell. Just don't read opens alone. Check clicks and complaints beside them.
04 · Signs two and three: complaints, and Postmaster Tools · 1:24
On screen: needle two fills in, complaints, and nudges up a notch, amber. Needle three fills in, Postmaster: domain reputation, with its four bands, High · Medium · Low · Bad, and the needle slides from High to Medium. The big dial still reads fine.
Sign two. Your complaint rate ticking up. Even a small rise is worth taking seriously. Providers weigh complaints heavily, and they see complaint data you don't. Sign three. In Google Postmaster Tools, your domain reputation slides from High to Medium. That can happen before your placement visibly shifts.
05 · Sign four: a slow seed drift, and new bounce messages · 1:50
On screen: needle four fills in, seed tests. Gloss card, one line: seed list · real test addresses at several mailbox providers, added to a send so you can see where each copy lands. Three small dots on a six-week line, 95% · 88% · 81%, joined by a sloping line. A faint 60% mark further down, crossed out. Last, a new bounce message card slides in, its policy line highlighted.
Sign four. Your seed list results drifting. Not a sudden failure. A slide. Inbox placement at ninety-five percent, then eighty-eight, then eighty-one, over six weeks. That's a pattern. Don't wait for sixty. And watch for blocks or deferrals you haven't seen before. The message text usually names the provider's policy.
06 · Part two: a trend, or noise · 2:18
On screen: chip 2 lights. The needles over a row of sends. One send dips alone and recovers, noise. Then three small question cards drop beside the dashboard: new list source? · volume up fast? · unusual complaints?. Last, a line that keeps sliding across many sends, trend.
How do you tell a trend from noise? One bad send isn't decay. Decay is a trend across several sends. When something looks off, ask what changed. A new segment or list source? Volume raised quickly? A campaign with unusual complaints? If it just keeps dipping, with no trigger you can find, that's the pattern to act on.
07 · Part three: when to act · 2:44
On screen: a new batch of cards slides into the list, tagged new source. A few are crossed out, coral. The checking lamp passes over the batch and lifts them out before the send, and the needles stay teal.
One question on that list is worth asking before anything moves. Did it start with a new list source? New addresses that don't belong there can pull every needle at once. A clean checks them before they reach a send.
08 · Recap · 3:29
On screen: the dashboard, all four needles labelled, the falling line, the paused segment. All three chips lit.
Four needles, then. Opens by provider, complaints, Postmaster reputation, and seed drift. Look for a trend, not one bad send. And act before the big dial moves, starting with the segments most at risk.
09 · Close · 3:44
On screen: the dashboard, four needles teal, the big dial steady. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V072, no subscribe ask.
Read the small needles, and act on the trend. No clean can rescue a reputation that's already sliding. What it does is keep bad addresses out of your sends. Can't tell noise from trouble? Our SOS hotline is free. Try your first 1,000 free at reviewmyemails dot com slash get started. And in the next video... how do hygiene issues affect sender reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-016.011.006-inbox-metrics-predict-reputation-decay.md
00 · The notice that never comes (hook)
Almanac ids in this scene: 016.011.006
How can inbox metrics predict reputation decay?
three numbered chips, the VO's words: 1 the four early signs · 2 a trend, or noise · 3 when to act. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the dashboard, this video's one picture.
016.011.006 "Mailbox providers don't send you a notice. They just quietly start sending more of your email to spam. By the time you notice a placement problem, the reputational damage is already weeks old."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 016.011.006
no cut away and no ad break. The dashboard holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1 and R13 (YT, 2026-09-29).
015.001.001 "we'll flag what's safe to send to and what to suppress". 016.011.006 "Did this happen after a list segment change or a new acquisition source?" Paid off in scene 07b.
02 · Part one: why early signs matter
Almanac ids in this scene: 016.011.006
The four early signs
chip 1 lights. The dashboard, four small needles in a row under the big dial, each with a blank label that fills in its own scene.
four needles, one dial. Reveals: (1) the dial, (2) the four needles.
the dashboard.
016.011.006 "Your metrics aren't just scorecards. They're an early warning system." / "reputation decay: it rarely announces itself." / "four leading indicators that shift before placement collapses"
35 words.
03 · Sign one, and the twist: a drop at one provider
Almanac ids in this scene: 016.011.006
The four early signs
needle one fills in, opens by provider. The report splits into three small bars, one per provider. All three dip, tagged could be content. Then reset: only the Gmail bar dips, the others hold, tagged reputation. A small + clicks, complaints tag clips on to the needle.
three bars, all dipping, then one. Reveals: (1) the needle, (2) the split, (3) all dip, (4) the reset, (5) one dips, (6) the tag.
the dashboard, needle one.
016.011.006 "A drop across your whole list could be a content problem. A drop specifically at Gmail or Outlook while other providers hold steady is a provider-level reputation signal. That specificity is the tell." / "Open rate alone won't give you enough signal, especially with Apple MPP inflating numbers. Layer it with click rate, complaint rate"
T3, the twist, and a call back to video 1 (content) without re-teaching it. T2, where: split the report by provider. V12: "could be" is kept.
04 · Signs two and three: complaints, and Postmaster Tools
Almanac ids in this scene: 016.011.006
The four early signs
needle two fills in, complaints, and nudges up a notch, amber. Needle three fills in, Postmaster: domain reputation, with its four bands, High · Medium · Low · Bad, and the needle slides from High to Medium. The big dial still reads fine.
one notch up, one band down, the big dial still. Reveals: (1) needle two, (2) the notch, (3) needle three, (4) the bands, (5) the slide, (6) the big dial holding.
the dashboard, needles two and three. Postmaster Tools is called back from video 1 (S6), no gloss.
016.011.006 "Even a small uptick in spam reports is worth taking seriously. Inbox providers weight complaints heavily, and they see complaint data you don't." / "Gmail's Postmaster Tools shows domain reputation as High, Medium, Low, or Bad. Movement from High to Medium can happen before your placement numbers visibly shift."
no complaint threshold voiced (N6).
05 · Sign four: a slow seed drift, and new bounce messages
Almanac ids in this scene: 016.011.006, 022.008.003
The four early signs
needle four fills in, seed tests. Gloss card, one line: seed list · real test addresses at several mailbox providers, added to a send so you can see where each copy lands. Three small dots on a six-week line, 95% · 88% · 81%, joined by a sloping line. A faint 60% mark further down, crossed out. Last, a new bounce message card slides in, its policy line highlighted.
three dots, each seven points lower, a slope. Reveals: (1) the needle, (2) the gloss, (3) to (5) the dots, (6) the slope, (7) the crossed mark, (8) the bounce card.
the dashboard, needle four, and concept seed-list.
016.011.006 "watch for gradual drift, not just sudden failures. An inbox placement rate that slides from 95% to 88% to 81% over six weeks is a pattern. Don't wait until it hits 60% to ask questions." / "Blocks and deferrals you haven't seen before" / "The message text usually names the provider's policy, which tells you where the friction is." Gloss: 022.008.003 "a set of real test email addresses at multiple mailbox providers" / "that you add to a send so you can manually check where each copy landed"
N5, 95 to 88 to 81 drops seven each time. These are the answer's example of a slope, not a pass mark (N6). V12: "usually" is kept. 50 words.
06 · Part two: a trend, or noise
Almanac ids in this scene: 016.011.006
A trend, or noise
chip 2 lights. The needles over a row of sends. One send dips alone and recovers, noise. Then three small question cards drop beside the dashboard: new list source? · volume up fast? · unusual complaints?. Last, a line that keeps sliding across many sends, trend.
one dip that recovers against a line that keeps falling. Reveals: (1) the one dip, (2) to (4) the question cards, (5) the falling line.
the dashboard.
016.011.006 "One bad send doesn't mean decay. Reputation decay looks like a trend across multiple sends, not a one-time dip." / "Did this happen after a list segment change or a new acquisition source? Did it happen after you increased send volume quickly? Did the timing line up with a campaign that got unusual complaints?" / "If the dip just... keeps dipping with no obvious trigger, that's the pattern worth acting on."
T1, the how. 59 words.
07 · Part three: when to act
Almanac ids in this scene: 006.003.012, 015.001.001, 016.011.006
Before the needles move
a new batch of cards slides into the list, tagged new source. A few are crossed out, coral. The checking lamp passes over the batch and lifts them out before the send, and the needles stay teal.
one new batch, a few out, needles held. Reveals: (1) the batch, (2) the crossed cards, (3) the lamp, (4) the needles hold.
the dashboard, the lamp (concept list-cleaning).
016.011.006 "Did this happen after a list segment change or a new acquisition source?" / "look at what's changed in your list sources" 015.001.001 "we'll flag what's safe to send to and what to suppress"
T5, the action. The answer's "10% drop" is not voiced. C33 kept out, no recovery time.
Q3: moved before the recap. Q2: the pivot comes from this topic (a new list source moves every needle), no catch-all.
T6 and R15 (YT, 2026-09-29). Backed by the answer's own list-source question, not a catch-all line (T4).
08 · Recap
What to remember
the dashboard, all four needles labelled, the falling line, the paused segment. All three chips lit.
callbacks only.
callbacks only (S5).
09 · Close
Almanac ids in this scene: 005.001.011, 016.011.006
The needle moves first
the dashboard, four needles teal, the big dial steady. The dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V072, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra that fits this video: /sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning (M-25, M-23, M-24).
016.011.006 "our free SOS hotline is there for exactly this kind of question."
says what a clean does not do (S10), in new words (Q1). S8: the next video is V072, 005.001.011, named by the Q sweep (2026-09-30) where the batch left it open. The PM can swap it when it sequences the playlists. Totals: 12 scenes (00 to 09, with 00b and 07b). Word count in the PR body. Over two minutes, so no Short cut note (R12).
V100What are the legal responsibilities for list hygiene?
waiting on YTOpen questions for YT
- R7 sentence reused: this is YT's own sentence from R7, also voiced in 008.001.004.
- Registry: the road and the rental contract, no picture yet.
00 · The law doesn't care, so why bother (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what the law asks · 2 the rule that isn't a law · 3 three habits that cover both. Chips 2 and 3 grey.
Three parts to it. What the law asks of every list. The rule that isn't a law. And three habits that cover both.
01 · Brought to you by, woven in · 0:25
On screen: no cut away and no ad break. The list card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Keeping a list clean is a habit, not a legal box, and Review My Emails checks every address on it before you send.
02 · What the law asks · 0:33
On screen: chip 1 lights. One road across the screen. Two road signs rise in turn, EU: opt-in required and US: opt-out allowed, working unsubscribe. A small brake pedal icon sits under both. Gloss card: opt-in · a person actively asking to receive your mail, rather than being added without being asked.
What does the law ask of your list? It depends where your subscribers live, the way driving does. In the EU opt-in is required, and in the US opt-out is allowed with a working unsubscribe link. Different roads. Every one of them needs working brakes.
03 · The brakes are your unsubscribe · 0:53
On screen: the brake icon from scene 02 grows into a small flow: unsubscribe link → removed → stays removed. A sheet slides in beside it, titled how our unsubscribe works, three lines filling in one per click.
The brakes are your unsubscribe. Someone asks to stop, you stop, and you keep stopping. That's the part every region agrees on. And write down how your unsubscribe works, step by step, so if anyone ever asks, you can prove it.
04 · The rule that isn't a law · 1:13
On screen: chip 2 lights. The road holds. A glovebox opens, and a folded contract comes out, terms of service. One line on it highlights, no known fake addresses. A small reputation dial beside the road dips.
Here's the part people miss. The US opt-out law barely looks at how clean your list is. Your email marketing tool does. Sending to addresses you know are fake breaks its terms of service. It's the rental contract in the glovebox. And your sender reputation pays either way.
05 · Three habits, and where they live · 1:37
On screen: chip 3 lights. Three icons in a row, one per click, each with its home written under it: hard bounces → suppression list · how they said yes → custom field · stop requests → honoured. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
Three habits cover the law and the contract. Take hard bounces off, onto your suppression list, the list of addresses you never send to again. Tag how each person said yes, in a custom field on every contact in your email marketing tool. And honour every request to stop.
06 · Not a one-time check · 2:05
On screen: the road scrolls on. Small service markers pass at a steady rhythm, clean. A second road below with heavier traffic has the markers closer together.
And none of it is a one-time check. List hygiene is ongoing. Set how often you clean by how much you send. A bigger sender, cleaning more often. The road keeps going, and so does the upkeep.
07 · The fake addresses you don't know about · 2:24
On screen: the list card from the hook. Most lines plain. Two lines look just like the rest, until a desk lamp sweeps over them and they turn coral, no such mailbox and typo domain.
The contract says addresses you know are fake. The trouble is the ones you don't. A mailbox that no longer exists, or a typo in the domain, looks like any other line on your list. Until you send to it.
08 · Recap · 2:44
On screen: the road with its two signs, the brake flow, the contract, the three habit icons. All three chips lit.
One more time. The rules of the road change by region, and every road needs brakes. Your unsubscribe is the brakes, so write it down. Your email tool's terms want real addresses. And tag how each person said yes.
09 · Close · 3:02
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Follow both rulebooks, the road's and the contract's. Cleaning can't give you consent, that part is yours. What Review My Emails takes out is the addresses that can't take mail. That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what's the difference between legally required suppression and operational suppression?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.012.001-legal-responsibilities-list-hygiene.md
00 · The law doesn't care, so why bother (hook)
Almanac ids in this scene: 005.012.001
What are the legal responsibilities for list hygiene?
three numbered chips, the VO's words: 1 what the law asks · 2 the rule that isn't a law · 3 three habits that cover both. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the list card. No picture yet.
005.012.001 "It doesn't care much about list quality." / "But sending to addresses you know are fake violates ESP terms of service and tanks your sender reputation."
H4, H5 (S2: 21 words).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.012.001, 015.001.001
no cut away and no ad break. The list card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13 (YT, 2026-09-29). Q4: one sentence, 23 words.
005.012.001 "It's not a one-time audit. It's an ongoing process." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · What the law asks
Almanac ids in this scene: 005.012.001, 005.012.010
What the law asks
chip 1 lights. One road across the screen. Two road signs rise in turn, EU: opt-in required and US: opt-out allowed, working unsubscribe. A small brake pedal icon sits under both. Gloss card: opt-in · a person actively asking to receive your mail, rather than being added without being asked.
one road, two signs, one brake shared by both. Reveals: (1) the road, (2) the EU sign, (3) the US sign, (4) the brake under both, (5) the gloss card.
the road. No picture yet. Concept opt-in (registry gloss, word for word).
R7 (YT, 2026-09-29): her sentence, regions, no law named, no timing.
005.012.001 "the legal rules around how you maintain that list vary wildly by region." / "CAN-SPAM in the US is an opt-out law." / "GDPR in Europe is stricter. You need explicit consent to send". 005.012.010 "GDPR, CASL, and CAN-SPAM all say you can't keep emailing someone who's opted out."
the law names are in the backing only, never in VO or on screen (R7, registry gdpr, can-spam held).
03 · The brakes are your unsubscribe
Almanac ids in this scene: 005.012.001, 005.012.010, 005.012.011
What the law asks
the brake icon from scene 02 grows into a small flow: unsubscribe link → removed → stays removed. A sheet slides in beside it, titled how our unsubscribe works, three lines filling in one per click.
one flow of three steps, one written sheet. Reveals: (1) the flow, (2) to (4) one line each on the sheet.
the road, the brakes.
005.012.001 "honor withdrawal requests" / "Document your unsubscribe process so you can prove compliance if asked." 005.012.010 "you can't keep emailing someone who's opted out."
no timing (R10, C14). Q8: where (a written sheet) and how (step by step). Hygiene logs, where the sheet lives, are episode 4 (005.012.011), not taught here.
04 · The rule that isn't a law
Almanac ids in this scene: 005.012.001
The rule that isn't a law
chip 2 lights. The road holds. A glovebox opens, and a folded contract comes out, terms of service. One line on it highlights, no known fake addresses. A small reputation dial beside the road dips.
one contract, one highlighted line, one dial that dips. Reveals: (1) the glovebox, (2) the contract, (3) the line, (4) the dial.
the road, the rental contract.
005.012.001 "It doesn't care much about list quality. It cares that you honor unsubscribe requests" / "But sending to addresses you know are fake violates ESP terms of service and tanks your sender reputation." / "And they matter for your reputation, not just your inbox."
T3, the twist. T10, the rental contract carries the "not a law" rule. "Email marketing tool" for "ESP" (V5).
05 · Three habits, and where they live
Almanac ids in this scene: 005.012.001, 006.017.004
Three habits that cover both
chip 3 lights. Three icons in a row, one per click, each with its home written under it: hard bounces → suppression list · how they said yes → custom field · stop requests → honoured. Gloss card: suppression list · the addresses you keep on record precisely so you never send to them again.
three habits, three homes. Reveals: (1) to (3) one habit each, (4) the gloss card.
the road, three icons. Concept suppression-list (called back from V007 with its picture, Q5).
005.012.001 "you need to regularly clean your list (remove hard bounces), segment by consent type, and honor withdrawal requests." 006.017.004 "tagging every subscriber record with the consent source and exact opt-in language at collection (stored as a custom field in your ESP)".
Q7, three items drawn as three icons with their homes. Q8, each habit says where.
06 · Not a one-time check
Almanac ids in this scene: 005.012.001
Three habits that cover both
the road scrolls on. Small service markers pass at a steady rhythm, clean. A second road below with heavier traffic has the markers closer together.
two roads, markers spaced by traffic. Reveals: (1) the markers pass, (2) the busier road, (3) its closer markers.
the road.
005.012.001 "It's not a one-time audit. It's an ongoing process." / "make sure your list cleaning frequency matches your sending volume."
no cadence number (V9). The answer gives none.
07 · The fake addresses you don't know about
Almanac ids in this scene: 005.003.002
The ones you can't see
the list card from the hook. Most lines plain. Two lines look just like the rest, until a desk lamp sweeps over them and they turn coral, no such mailbox and typo domain.
two coral lines among many plain ones. Reveals: (1) the card, (2) the lamp, (3) the first line turns, (4) the second.
the checking desk.
005.003.002 "Validation catches nonexistent mailboxes, spamtraps (honeypot addresses that flag poor list hygiene), and typo domains before send". Only the nonexistent-mailbox and typo-domain halves are voiced.
Q2, a list-topic pivot, not the catch-all line. Held word from 005.003.002 not voiced (registry spam-trap, internal). Q3: before the recap.
08 · Recap
What to remember
the road with its two signs, the brake flow, the contract, the three habit icons. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
09 · Close
Almanac ids in this scene: 008.009.001
Two rulebooks, one list
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
S10, says what a clean does not do (consent). Q4, brand twice (01 and 09). S8, the next video is 008.009.001 by its Almanac question, the "(e.g., unsubscribes)" and "(e.g., bounces)" asides kept in the title and not spoken, as V019 does with its own "(e.g., ...)". Totals: 11 scenes, 441 spoken words, about 2:40 of speech and about 3:20 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V101What's the difference between legally required suppression (e.g., unsubscribes) and operational suppression (e.g., bounces)?
waiting on YTOpen questions for YT
- C59: for #almanac-to-check: the hard-bounce retry line reads three ways across 008.009.001, 008.009.003 and 008.009.002.
- Registry: operational-suppression proposed, the drawer, padlock and latch have no picture yet.
00 · A win-back to everyone (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the ones the law locks · 2 the ones you lock yourself · 3 the label every address needs. Chips 2 and 3 grey.
Three parts. The ones the law locks. The ones you lock yourself. And the label every address needs, so you know which is which.
01 · Brought to you by, woven in · 0:27
On screen: no cut away and no ad break. The drawer holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Some addresses end up in that drawer only because they bounced, and Review My Emails finds those before you ever send.
02 · The ones the law locks · 0:35
On screen: chip 1 lights. Three tags lift out of the drawer, one per click, and hang on a coral padlock: unsubscribed · asked for erasure · complained. The complaint tag arrives as the small letter to the post office from V073. Gloss cards, one at a time: suppression list · the addresses you keep on record precisely so you never send to them again. feedback loop · an arrangement where a mailbox provider tells a sender which of their messages were reported.
Your suppression list holds the addresses you never send to again. Some are there by law. Unsubscribes. People who asked you to erase their data, where only a small marker stays. And spam complaints, passed back to you through a feedback loop. Every one of them said no.
03 · The key is theirs · 0:58
On screen: a small key appears on the far side of the padlock, out of Sally's reach, labelled subscriber. A calendar flips six months, and the padlock stays shut. Then a signup form fills in by itself, and only then does the key turn.
And the key to that padlock isn't yours. The law requires you to keep these out, and the only way back is a fresh, documented opt-in from the person themselves. You can't decide to give it another try six months later. They sign themselves back up, or they stay out.
04 · The ones you lock yourself · 1:18
On screen: chip 2 lights. Three more tags lift out and hang on an amber latch, not a padlock: hard bounce · test address · flagged by you. The latch has no key, just a lever on Sally's side. Gloss card: operational suppression · addresses you keep out for practical reasons, not because anyone asked you to stop.
Everything else is operational suppression. Addresses you keep out for practical reasons, not legal ones. Hard bounces, addresses that don't exist. Your own test addresses. Contacts you've flagged yourself, like a competitor. Nobody said no. You decided.
05 · A quiet subscriber isn't a no · 1:40
On screen: a fourth tag slides onto the latch, paused: quiet. The we miss you envelope from the hook lowers, and this time it goes only to the latch. It bounces off the padlock, which stays shut.
Now the part that flips Sally's plan. Someone who just went quiet never said no. If you paused them for not engaging, that was your call, and a re-engagement email can bring them back. Send that same email to an unsubscribe, and you've crossed the line.
06 · Your latch, lifted rarely · 2:03
On screen: the lever on the latch. The hard bounce tag stays put, a small returned envelope beside it. The flagged by you tag lifts off, and its label changes to now a customer.
Holding the lever doesn't mean pulling it often. A hard bounce is still a dead address, and sending again only makes more bounces. Lift the latch when something has changed, like a competitor you flagged who's now a customer.
07 · The label every address needs · 2:23
On screen: chip 3 lights. The drawer again, every tag now carrying a small reason stamp, coral on the padlock side, amber on the latch side. A second, unmarked drawer slides in, labelled inherited. Every tag marked unsubscribe or opt-out in it moves to the padlock.
One unlabelled list can't tell a lock from a latch. In your email marketing tool, give every suppressed address a reason, with a custom field or a list label. Unsubscribe, complaint, hard bounce, manual. Inherited a list with no reasons? Treat anything marked unsubscribe or opt-out as a no.
08 · The lock that can go on early · 2:50
On screen: a new tag arrives at the drawer before any envelope leaves. It passes under the checking desk lamp, its address turns coral, no such mailbox, and it hangs on the latch with no returned envelope beside it.
The law's padlock only ever goes on after a person says no. The bounce latch doesn't have to wait for a bounce. An address that doesn't exist can be found, and kept out, before your first send to it.
09 · Recap · 3:08
On screen: the padlock with its three tags and the key on the far side, the latch with its tags, the envelope reaching only the latch, the stamped drawer. All three chips lit.
One more time. Unsubscribes, erasures and complaints sit behind a padlock, and only the subscriber holds the key. Bounces, tests and your own flags sit behind your latch. Quiet subscribers can be won back. And label every address with its reason.
10 · Close · 3:26
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Label the reason, and send win-backs only through the latch. Consent is yours to keep. What Review My Emails takes out is the addresses that don't exist. Not sure how your drawer is sorted? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what does data minimization mean for email lists?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.009.001-legal-vs-operational-suppression.md
00 · A win-back to everyone (hook)
Almanac ids in this scene: 006.017.009
What's the difference between legally required suppression and operational suppression?
three numbered chips, the VO's words: 1 the ones the law locks · 2 the ones you lock yourself · 3 the label every address needs. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the suppression drawer. No picture yet.
006.017.009 "you can't decide that a better offer justifies a re-engagement attempt." / "The re-engagement question only applies to the behavioral group, never to the consent group."
H4, H5 (S2: 24 words).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.003.002, 015.001.001
no cut away and no ad break. The drawer holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 21 words.
005.003.002 "Validation catches nonexistent mailboxes" / "before send". 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · The ones the law locks
Almanac ids in this scene: 008.009.001
The ones the law locks
chip 1 lights. Three tags lift out of the drawer, one per click, and hang on a coral padlock: unsubscribed · asked for erasure · complained. The complaint tag arrives as the small letter to the post office from V073. Gloss cards, one at a time: suppression list · the addresses you keep on record precisely so you never send to them again. feedback loop · an arrangement where a mailbox provider tells a sender which of their messages were reported.
three tags on one padlock. Reveals: (1) to (3) one tag each, (4) and (5) the gloss cards.
the suppression drawer, concepts suppression-list, feedback-loop (V073's letter, Q5).
008.009.001 "Unsubscribed contacts" / "Contacts who've exercised GDPR erasure rights (where you retain a suppression marker but not the full record)" / "Addresses that complained through a feedback loop" / "these suppressions exist because of consent withdrawal or legal rights."
Q5, both words re-glossed with their pictures. "Erase their data" for the answer's named right (R7, registry gdpr held).
03 · The key is theirs
Almanac ids in this scene: 008.009.001, 008.009.003
The ones the law locks
a small key appears on the far side of the padlock, out of Sally's reach, labelled subscriber. A calendar flips six months, and the padlock stays shut. Then a signup form fills in by itself, and only then does the key turn.
one padlock, one key on the wrong side, one way it opens. Reveals: (1) the key, (2) the calendar flips, (3) still shut, (4) the form, (5) the key turns.
the suppression drawer, the padlock.
R7, the one legal sentence, no law named, no penalty.
008.009.001 "If a legal suppression like an unsubscribe is reversed, it requires a new verified opt-in from the subscriber." 008.009.003 "Unsubscribes require a fresh, documented opt-in from the recipient themselves" / "You can't decide to "give it another try" six months later" / "If they want to come back, they need to sign themselves back up."
T10, the key the subscriber holds.
04 · The ones you lock yourself
Almanac ids in this scene: 008.009.001
The ones you lock yourself
chip 2 lights. Three more tags lift out and hang on an amber latch, not a padlock: hard bounce · test address · flagged by you. The latch has no key, just a lever on Sally's side. Gloss card: operational suppression · addresses you keep out for practical reasons, not because anyone asked you to stop.
three tags on one latch. Reveals: (1) the latch, (2) to (4) one tag each, (5) the gloss card.
the suppression drawer, the latch.
008.009.001 "Operational suppression covers addresses you don't send to for deliverability and practical reasons, not legal ones" / "Hard bounces. addresses that no longer exist or permanently reject mail" / "Internal addresses, test accounts" / "Contacts you've manually flagged for business reasons (competitors, litigants, etc.)" / "operational suppressions can be managed as business decisions."
the answer's held-word item and its role-address item are not voiced (registry spam-trap internal). Q7: three items drawn as three tags.
05 · A quiet subscriber isn't a no
Almanac ids in this scene: 006.017.009
The ones you lock yourself
a fourth tag slides onto the latch, paused: quiet. The we miss you envelope from the hook lowers, and this time it goes only to the latch. It bounces off the padlock, which stays shut.
one envelope, two locks, one it may open. Reveals: (1) the quiet tag, (2) the envelope, (3) it reaches the latch, (4) it stops at the padlock.
the suppression drawer, concept re-engagement.
006.017.009 "They didn't ask to stop receiving emails. They just stopped engaging. That distinction matters because behavioral suppression is reversible. A well-designed re-engagement campaign can bring them back into active sends if they respond to it." / "The re-engagement question only applies to the behavioral group, never to the consent group."
T3, the twist. The answer's "90 to 180 days" is not voiced (C30). "Re-engagement email" is the registry's word, taught in V927, used here in plain words (Q6, not counted new).
06 · Your latch, lifted rarely
Almanac ids in this scene: 008.009.003
The ones you lock yourself
the lever on the latch. The hard bounce tag stays put, a small returned envelope beside it. The flagged by you tag lifts off, and its label changes to now a customer.
one lever, one tag lifted, one left. Reveals: (1) the lever, (2) the hard-bounce tag stays, (3) the flagged tag lifts, (4) its new label.
the suppression drawer, concept hard-bounce.
008.009.003 "Hard bounces carry no consent barrier but no operational upside either." / "you're just generating bounce events and hurting your sender score." / "Manual or operational suppressions (legal disputes, competitors, known bad actors): these are your own business decision, and you can reverse them if the situation changes."
C59, no side taken on retrying a reactivated hard bounce. "Now a customer" is the picture's example of "the situation changes", not an Almanac case.
07 · The label every address needs
Almanac ids in this scene: 006.017.009, 008.009.001
The label every address needs
chip 3 lights. The drawer again, every tag now carrying a small reason stamp, coral on the padlock side, amber on the latch side. A second, unmarked drawer slides in, labelled inherited. Every tag marked unsubscribe or opt-out in it moves to the padlock.
one drawer sorted by stamp, one inherited drawer sorted the safe way. Reveals: (1) the stamps, (2) the colours split, (3) the inherited drawer, (4) its opt-outs move to the padlock.
the suppression drawer.
008.009.001 "should tag each address with its suppression type so you can apply the right rules. Mixing them all into one unlabeled list makes it impossible to manage retention policies or respond to data subject requests correctly." 006.017.009 "Most ESPs let you tag or separate these with custom fields or list labels" / "a safe default is to treat anything labeled "unsubscribe" or "opt-out" as consent-based".
Q8, where (your email marketing tool) and how (a custom field or a list label). T5, the action.
08 · The lock that can go on early
Almanac ids in this scene: 005.003.002, 008.009.001
The lock that can go on early
a new tag arrives at the drawer before any envelope leaves. It passes under the checking desk lamp, its address turns coral, no such mailbox, and it hangs on the latch with no returned envelope beside it.
one tag latched with zero bounces. Reveals: (1) the tag, (2) the lamp, (3) it turns, (4) it hangs, no envelope.
the checking desk.
005.003.002 "Validation catches nonexistent mailboxes" / "before send". 008.009.001 "these suppressions exist because of consent withdrawal or legal rights."
Q2, a suppression-topic pivot, not the catch-all line. Q3, before the recap.
09 · Recap
What to remember
the padlock with its three tags and the key on the far side, the latch with its tags, the envelope reaching only the latch, the stamped drawer. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
10 · Close
Almanac ids in this scene: 005.012.003, 005.012.007
Two locks, one drawer
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
005.012.007 "Our SOS hotline is free, and we don't pitch you anything."
S10, says what a clean does not do (consent). Q4, brand twice. S8, the next video is 005.012.003 by its Almanac question. Totals: 12 scenes, 498 spoken words, about 3:00 of speech and about 3:40 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V102What does “data minimization” mean for email lists?
waiting on YTOpen questions for YT
- C30 and C38 adds: for #almanac-to-check (dormant window, purge vs suppress).
- Registry: the suitcase as data-minimization's picture, proposed.
00 · Fifteen fields, two used (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what to ask for · 2 what to stop keeping · 3 the check on your own form. Chips 2 and 3 grey.
Three parts. What to ask for when someone signs up. What to stop keeping. And the check you can run on your own form today.
01 · Brought to you by, woven in · 0:26
On screen: no cut away and no ad break. The form holds, the email field glows, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
The one field every list needs is the email address, and Review My Emails checks that each one on your list can still take mail.
02 · What it means · 0:34
On screen: chip 1 lights. The form folds into a suitcase, stuffed so full the lid won't shut. Three small tags hang from the handle, one per click: less risk · less storage · respect. Gloss card: data minimization · collecting only what you actually need, so there is less to hold and less to lose.
Data minimization means collecting only what you'll use. Not the stuff you might need someday. Not the stuff that's interesting to have. It's a core principle in most privacy laws, because it cuts risk, cuts storage costs, and respects the people who signed up.
03 · The one-question test · 0:55
On screen: items lift out of the suitcase one per click and hover over a small question, would anything break?. email drops back in. first name drops back in with a small note, used in greetings. birthday, phone, job title stay out, grey.
Your form is a suitcase. Pack for the trip you're on. The test for each field: if you took it out, would your email program break? The email address, always. A first name, only if you greet people by it. Everything else needs a send that uses it.
04 · Ask later, not now · 1:19
On screen: three small packing cubes go into the suitcase, one per group. Later, a fourth cube arrives on its own, with a small envelope beside it, quick question, and slots in.
What about fields you might want later? Ask for what you segment on right now. Launched with three audience groups? Collect what tells those three apart. Add a fourth group next year, and ask for that detail then, from the people already on your list.
05 · Keeping is collecting too · 1:40
On screen: chip 2 lights. Beside the suitcase, a stack of old profile cards grows, dusty. A small crack runs across a safe, breach. The stack spills out. Next to it, a single card with just address and preference barely moves.
And it isn't only the form. It's how long you hold on. Data on people who haven't engaged in years isn't minimization. It's accumulation. And if a breach ever happens, years of detailed profiles hurt far more than an address and a preference.
06 · The one thing you keep on purpose · 2:03
On screen: the small card from scene 05 shrinks further, to one line, do not send, and slides into the suppression drawer from V101. The stack beside it is gone.
Minimizing doesn't mean wiping everything, though. Someone who unsubscribed still needs a small note on your suppression list, the addresses you never send to again. Just the address, nothing else. That note and minimization work together. Keep the least that stops harm.
07 · The check on your own form · 2:25
On screen: chip 3 lights. A two-column checklist: field and used by. Rows fill in one per click. email → every send. first name → greetings. company size → blank, and the row turns amber, candidate to remove.
Try this on your own form. Open your signup form, then the profile fields in your email marketing tool. For each field, ask what you do with it right now. If you can't point to a segment or a send that uses it, it's a candidate to remove.
08 · The field that can die quietly · 2:50
On screen: the suitcase, now light and shut. On its tag, the address. The checking desk lamp sweeps over a row of tags, and one of them turns coral, no such mailbox.
Pack light, and you're left with the field that matters most. The address. It can stop working without telling you. A mailbox that no longer exists still sits on your list, looking like any other.
09 · Recap · 3:09
On screen: the full suitcase, the three items left out, the fourth cube, the spilled stack, the one-line note in the drawer, the checklist. All three chips lit.
One more time. Pack for the trip you're on. Ask for what a send uses, and ask for the rest later. Don't hold what you don't use. Keep the do-not-send note. And check every field on your form for what uses it.
10 · Close · 3:26
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Collect less, keep less, and make what's left count. Which fields to ask for is your call. What Review My Emails checks is that the address still works. That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... how should hygiene logs be stored for auditability?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.012.003-data-minimization-email-lists.md
00 · Fifteen fields, two used (hook)
Almanac ids in this scene: 005.012.003, 006.017.007
What does data minimization mean for email lists?
three numbered chips, the VO's words: 1 what to ask for · 2 what to stop keeping · 3 the check on your own form. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the signup form. No picture yet.
005.012.003 "Do you really need 15 fields, or just email and name?" 006.017.007 "Every data point you hold creates compliance surface area: it has to be protected, disclosed in your privacy policy, and defensible if a subscriber asks what you're doing with it."
H4, H5 (S2: 24 words).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 020.012.003
no cut away and no ad break. The form holds, the email field glows, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence.
020.012.003 "Email address. Always necessary. No field, no email." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · What it means
Almanac ids in this scene: 005.012.003, 020.012.003
What to ask for
chip 1 lights. The form folds into a suitcase, stuffed so full the lid won't shut. Three small tags hang from the handle, one per click: less risk · less storage · respect. Gloss card: data minimization · collecting only what you actually need, so there is less to hold and less to lose.
one suitcase that won't close, three tags. Reveals: (1) the fold into a suitcase, (2) the lid won't shut, (3) to (5) one tag each, (6) the gloss card.
the suitcase. No picture yet. Concept data-minimization (registry gloss, word for word).
R7, the one legal sentence, no law named.
005.012.003 "Data minimization means collecting only the information you'll actually use. Not the stuff you might need someday. It's a core principle in GDPR and most privacy laws because it reduces risk, cuts storage costs, and respects subscriber boundaries." 020.012.003 "Not data that's interesting to have."
03 · The one-question test
Almanac ids in this scene: 020.012.003
What to ask for
items lift out of the suitcase one per click and hover over a small question, would anything break?. email drops back in. first name drops back in with a small note, used in greetings. birthday, phone, job title stay out, grey.
two items back in, three left out. Reveals: (1) the question, (2) email back, (3) first name back, (4) the three stay out.
the suitcase.
020.012.003 "if you removed this data field, would your email program break or meaningfully fail the subscriber?" / "Email address. Always necessary." / "First name. Necessary if you personalize subject lines or greetings."
T10, the suitcase, carried to the close.
04 · Ask later, not now
Almanac ids in this scene: 005.012.003
What to ask for
three small packing cubes go into the suitcase, one per group. Later, a fourth cube arrives on its own, with a small envelope beside it, quick question, and slots in.
three cubes now, a fourth added later. Reveals: (1) to (3) one cube each, (4) the envelope, (5) the fourth cube.
the suitcase.
005.012.003 "ask for what you'll segment on right now. Did you launch with three audience groups? Collect data to identify those three. If you add a fourth later, you can ask returning subscribers for that detail."
"next year" is the picture's timing, the answer says "later". Q7: three groups, drawn as cubes.
05 · Keeping is collecting too
Almanac ids in this scene: 020.012.003
What to stop keeping
chip 2 lights. Beside the suitcase, a stack of old profile cards grows, dusty. A small crack runs across a safe, breach. The stack spills out. Next to it, a single card with just address and preference barely moves.
a tall stack against one small card. Reveals: (1) the stack grows, (2) the crack, (3) the stack spills, (4) the small card.
the suitcase, the profile stack.
020.012.003 "Data minimization covers both what you collect upfront and how long you keep it. Holding onto data for subscribers who haven't engaged in two years isn't minimization. It's accumulation." / "A data breach hurts more when you're storing five years of behavioral profiles than when you're storing an email address and a preference flag."
"in years" carries the answer's "two years", no window voiced (C30 add). "Keep only what you use", never "delete" or "suppress" as a rule (C38 add).
06 · The one thing you keep on purpose
Almanac ids in this scene: 005.012.010
What to stop keeping
the small card from scene 05 shrinks further, to one line, do not send, and slides into the suppression drawer from V101. The stack beside it is gone.
one line kept, a stack gone. Reveals: (1) the card shrinks, (2) to one line, (3) into the drawer, (4) the stack clears.
the suitcase, concept suppression-list (re-glossed, Q5).
005.012.010 "So this is where data minimization and suppression actually reinforce each other. Keep the minimum needed to prevent harm, nothing more." / "You don't need their name, preferences, or purchase history. Just enough to recognize the address if it shows up again."
T3, the twist. "Just the address" follows 005.012.010's "Just enough to recognize the address". V007 owns what else the record may hold.
07 · The check on your own form
Almanac ids in this scene: 020.012.003
The check on your own form
chip 3 lights. A two-column checklist: field and used by. Rows fill in one per click. email → every send. first name → greetings. company size → blank, and the row turns amber, candidate to remove.
three rows, two filled, one blank. Reveals: (1) the columns, (2) to (4) one row each.
the checklist.
020.012.003 "Go to your signup form and your subscriber profile fields. For each field, ask yourself: what do I do with this data in my email program right now? If you can't point to a specific workflow or segment, that field is a candidate to remove."
Q8, where (the form and the profile fields in your tool) and how (one field at a time, name what uses it). T5, the action.
08 · The field that can die quietly
Almanac ids in this scene: 005.003.002, 020.012.003
The field that matters most
the suitcase, now light and shut. On its tag, the address. The checking desk lamp sweeps over a row of tags, and one of them turns coral, no such mailbox.
one light suitcase, one coral tag. Reveals: (1) the shut suitcase, (2) the lamp, (3) the coral tag.
the checking desk.
020.012.003 "Email address. Always necessary." 005.003.002 "Validation catches nonexistent mailboxes" / "before send".
Q2, a list-topic pivot. Q3, before the recap.
09 · Recap
What to remember
the full suitcase, the three items left out, the fourth cube, the spilled stack, the one-line note in the drawer, the checklist. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
10 · Close
Almanac ids in this scene: 005.012.011
Pack light
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
S10, says what a clean does not do (choose your fields). Q4, brand twice. S8, the next video is 005.012.011 by its Almanac question. Totals: 12 scenes, 489 spoken words, about 2:57 of speech and about 3:44 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V103How should hygiene logs be stored for auditability?
waiting on YTOpen questions for YT
- C60: for #almanac-to-check: five different retention answers across four pages.
- Registry: hygiene-log proposed, the ship's log picture.
00 · "You've spammed me for years" (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what goes in the log · 2 where the log lives · 3 how to keep anyone from quietly rewriting it. Chips 2 and 3 grey.
Three parts to it. What goes in the log. Where the log lives. And how to keep anyone from quietly rewriting it.
01 · Brought to you by, woven in · 0:27
On screen: no cut away and no ad break. The timeline holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Every bounce in a log is one that already happened, and Review My Emails finds the bad addresses before they bounce.
02 · The ship's log · 0:35
On screen: chip 1 lights. A ship's logbook opens. Three column heads ink in, one per click: time · reason · at the wheel. A small wave passes under the page and nothing is written. Gloss card: hygiene log · a dated record of every change to a contact's status, and why it changed.
A hygiene log is your list's ship's log. Every course change gets written down, with the time, the reason, and who was at the wheel. You don't explain every wave. And if anyone official ever asks how you handle subscriber data, this is what you hand them.
03 · What every line holds · 0:58
On screen: lines write themselves into the log, one per click, each a short event word in the reason column: hard bounce (coral) · complaint · unsubscribe · consent update · manual removal · deletion request. Then one line zooms in, its four cells lit: address · event · 2026-09-30 14:02 · system.
What gets a line? Every change to a contact's status. A hard bounce, a spam complaint, an unsubscribe, a consent update, a manual removal, a deletion request. And every line holds the same things. The address, what happened, the date and time, and whether a person or the system did it.
04 · The history that isn't yours · 1:22
On screen: chip 2 lights. The logbook sits on an amber shelf labelled your email tool. A small sign on the shelf, limited window. Then the shelf slides away, account closed, and the book goes with it.
Your email marketing tool already keeps some of this. The catch? That history isn't yours. Some tools only keep a limited window. And if you move platforms, or close the account, it can disappear with it.
05 · Write your own copy · 1:43
On screen: a second logbook on a teal shelf, yours. Each new event writes into both books at once. Then a file drops onto the teal shelf, list-clean-2026-09-30.csv, beside the list, which stays as it was.
Write your own copy, then. When a bounce or a complaint comes in, log it somewhere you own. A spreadsheet works for a small sender. A database table works better as you grow. And when you clean your list, keep the results as a dated file. Don't just overwrite the list.
06 · Pages that can't be rewritten · 2:07
On screen: chip 3 lights. The teal logbook. A new line writes at the bottom. An eraser hovers over an old line and can't touch it. A small key ring with two keys, write access. A second copy of the book appears on a separate shelf, with a stack of faint earlier versions behind it.
How do you keep it honest? Nothing fancy. Logs that can't be quietly edited later. New rows get added, old rows never change. Only a few people can write to it. And a backup copy lives somewhere separate, in cloud storage that keeps old versions.
07 · Keep one even if nobody asks · 2:30
On screen: the message card from the hook returns. The teal logbook opens to one address's pages: signed up · consent given · the lines since. The message card fades.
No particular rule over you? Keep the log anyway. It protects you. When that subscriber says you've spammed them for years, you can show when they signed up, what they agreed to, and every change since.
08 · The line you never have to write · 2:50
On screen: the coral hard bounce lines in the log pulse once each, and a small reputation dial beside the book dips a notch with each. Then a new address passes under the checking desk lamp before any send, turns coral, and no line is written.
A log tells you what already happened. Every hard bounce in it is one your sender reputation has already paid for. The cheapest line is the one you never write, a bounce from an address you checked first.
09 · Recap · 3:08
On screen: the logbook with its three columns, the six lines, the borrowed shelf sliding away, the teal shelf, the eraser that can't touch it, the backup. All three chips lit.
One more time. Your list's ship's log. Every status change, with the address, what happened, when, and who did it. Your email tool's history isn't yours, so keep your own copy. And make it a book that only grows, with a backup somewhere else.
10 · Close · 3:25
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Log every change, somewhere you own. Nobody can keep that log for you. What Review My Emails can do is take out the addresses that would fill it with bounces. Want a hand checking what your setup captures? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what is consent expiry?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.012.011-hygiene-logs-auditability.md
00 · "You've spammed me for years" (hook)
Almanac ids in this scene: 005.012.011
How should hygiene logs be stored for auditability?
three numbered chips, the VO's words: 1 what goes in the log · 2 where the log lives · 3 how to keep anyone from quietly rewriting it. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the activity timeline. No picture yet.
005.012.011 "If a subscriber emails to say you've been spamming them for years, you want to show exactly when they signed up, what consent they gave, and every action taken on their record since." / "hoping your ESP's activity history goes back far enough. It usually doesn't."
H4, H5 (S2: 22 words).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.003.002, 015.001.001
no cut away and no ad break. The timeline holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence.
005.003.002 "Validation catches nonexistent mailboxes" / "before send". 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · The ship's log
Almanac ids in this scene: 005.012.011
What goes in the log
chip 1 lights. A ship's logbook opens. Three column heads ink in, one per click: time · reason · at the wheel. A small wave passes under the page and nothing is written. Gloss card: hygiene log · a dated record of every change to a contact's status, and why it changed.
one book, three columns, one wave left out. Reveals: (1) the book, (2) to (4) one column each, (5) the wave, (6) the gloss card.
the ship's log. No picture yet.
R7, the one legal sentence, no law named ("anyone official" for the answer's "regulator").
005.012.011 "Think of it like a ship's log. Every course correction gets recorded, with the time, the reason, and who was at the wheel. You don't need to explain every wave" / "If a regulator ever asks how you handle subscriber data, your hygiene log is what you hand them."
T10, the answer's own simile, carried to the close.
03 · What every line holds
Almanac ids in this scene: 005.012.011
What goes in the log
lines write themselves into the log, one per click, each a short event word in the reason column: hard bounce (coral) · complaint · unsubscribe · consent update · manual removal · deletion request. Then one line zooms in, its four cells lit: address · event · 2026-09-30 14:02 · system.
six lines, then one line with four cells. Reveals: (1) to (6) one line each, (7) the zoom, (8) the four cells.
the ship's log.
005.012.011 "Every meaningful change to a contact's status deserves a record. That includes hard bounces, spam complaints, manual removals, unsubscribes, consent updates, suppression events, and any action taken in response to a DSAR or erasure request. Each entry should capture the event type, a timestamp, the source (was it automated or did a human do it?)" / "The key fields to capture are the email address (or a hashed version if you've already suppressed the full address for privacy reasons), the event type, the date and time, the source system, and any operator notes."
Q7, six events drawn as six lines in one log, not a spoken list on a card. "Deletion request" for the answer's "DSAR or erasure request" (V051 owns it).
04 · The history that isn't yours
Almanac ids in this scene: 005.012.011
Where it lives
chip 2 lights. The logbook sits on an amber shelf labelled your email tool. A small sign on the shelf, limited window. Then the shelf slides away, account closed, and the book goes with it.
one book on a borrowed shelf, gone with it. Reveals: (1) the shelf, (2) the sign, (3) the shelf slides away, (4) the book goes too.
the ship's log, the borrowed shelf.
005.012.011 "its history window is limited" / "The problem is that ESP-side logs aren't really yours. If you migrate platforms or close an account, that history can disappear."
T3, the twist. V12: "some tools" keeps the answer's one-platform example from becoming a rule about all of them.
05 · Write your own copy
Almanac ids in this scene: 005.012.011
Where it lives
a second logbook on a teal shelf, yours. Each new event writes into both books at once. Then a file drops onto the teal shelf, list-clean-2026-09-30.csv, beside the list, which stays as it was.
two books written at once, one dated file kept. Reveals: (1) the teal shelf, (2) an event writes twice, (3) the dated file, (4) the list untouched.
the ship's log, your own shelf.
005.012.011 "The safer approach is to write your own copies. When a bounce fires or a complaint comes in, log it somewhere you own." / "works for small senders. A database table or a dedicated logging service works better at scale." / "keep those results as a dated file. Don't just overwrite your list. Store the output with a filename that includes the date, so you can show what was removed and when."
Q8, where (a spreadsheet or a database table you own) and how (every event, both places, a dated file per clean). The answer's brand names are not voiced.
06 · Pages that can't be rewritten
Almanac ids in this scene: 005.012.011
How to keep anyone from rewriting it
chip 3 lights. The teal logbook. A new line writes at the bottom. An eraser hovers over an old line and can't touch it. A small key ring with two keys, write access. A second copy of the book appears on a separate shelf, with a stack of faint earlier versions behind it.
one book that only grows, two keys, one copy elsewhere. Reveals: (1) the new line, (2) the eraser fails, (3) the keys, (4) the backup, (5) its versions.
the ship's log.
005.012.011 "You don't need a blockchain or a certified audit system. You need logs that can't be quietly edited after the fact. That usually means append-only storage (you can add rows, you can't change them), access controls so not everyone can overwrite records, and a backup copy stored somewhere separate from your main system. Cloud storage with versioning enabled" / "handles this reasonably well without a lot of setup."
"Append-only" said in plain words (Q6). Storage product names not voiced.
07 · Keep one even if nobody asks
Almanac ids in this scene: 005.012.011
How to keep anyone from rewriting it
the message card from the hook returns. The teal logbook opens to one address's pages: signed up · consent given · the lines since. The message card fades.
one address, its full history in order. Reveals: (1) the card returns, (2) the book opens, (3) to (5) one entry each, (6) the card fades.
the ship's log.
005.012.011 "If you don't operate under a specific regulation, you still want logs. They protect you. If a subscriber emails to say you've been spamming them for years, you want to show exactly when they signed up, what consent they gave, and every action taken on their record since."
pays off the hook. No retention period (C60).
08 · The line you never have to write
Almanac ids in this scene: 005.003.002, 015.001.001
The line you never have to write
the coral hard bounce lines in the log pulse once each, and a small reputation dial beside the book dips a notch with each. Then a new address passes under the checking desk lamp before any send, turns coral, and no line is written.
coral lines, one dip each, then one line never written. Reveals: (1) the coral lines pulse, (2) the dial dips, (3) the lamp, (4) the empty row.
the checking desk.
015.001.001 "Keep sending to bounced addresses and your sender reputation will take a hit". 005.003.002 "Validation catches nonexistent mailboxes" / "before send".
Q2, a list-topic pivot. Q3, before the recap. "Already paid for" keeps 015.001.001's "take a hit", no size claimed.
09 · Recap
What to remember
the logbook with its three columns, the six lines, the borrowed shelf sliding away, the teal shelf, the eraser that can't touch it, the backup. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
10 · Close
Almanac ids in this scene: 005.012.006, 005.012.011
Keep the log
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
005.012.011 "Want help checking what your current setup actually captures? Our SOS hotline is free, and we can walk through your specific tools with you."
S10, says what a clean does not do (keep your log). Q4, brand twice. S8, the next video is 005.012.006 by its Almanac question. Totals: 12 scenes, 498 spoken words, about 3:00 of speech and about 3:43 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V104What is consent expiry?
waiting on YTOpen questions for YT
- Series end: the close names 016.013.001, the first of "Deliverability monitoring, part 1" (V105, this batch).
- Registry: consent-expiry and re-permission proposed.
00 · A sale to a two-year-old yes (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 why a yes can run out · 2 the two clocks to watch · 3 the email that asks again. Chips 2 and 3 grey.
Three parts. Why a yes can run out. The two clocks to watch. And the email that asks for the yes again.
01 · Brought to you by, woven in · 0:25
On screen: no cut away and no ad break. The stack holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Before you ask anyone for a fresh yes, Review My Emails checks which of those old addresses can still receive the question.
02 · Why a yes can run out · 0:33
On screen: chip 1 lights. One card lifts from the stack and turns into a membership card, member since. Three small region tags sit under it, one per click: a clock · must stay current · no clock. Gloss card: consent expiry · the idea that someone's permission to be emailed can go stale over time.
Consent expiry means permission to email someone doesn't last forever. It's like a gym membership. Some places put a clock on certain kinds of consent, some expect it to stay current, and some have no clock at all. It depends where your subscriber lives, and how they signed up.
03 · The first clock: time · 0:57
On screen: chip 2 lights. The card grows a small date dial in its corner. It starts at said yes, then resets once when a small opened tick lands, and runs on from there.
There are two clocks to watch. The first is time, the legal one. Where there's a clock, it starts from the moment they said yes, or from the last time they engaged with you. The date on the card.
04 · The second clock: activity · 1:16
On screen: a second dial on the card, an activity meter, draining slowly. The date dial beside it still reads fine. A small reputation gauge under the card dips as the meter empties. The no clock tag from scene 02 lights, and the activity meter keeps draining anyway.
The second clock is the one that catches people out. Someone who hasn't opened, clicked or bought anything in a long while may still be fine to email on paper. Sending to them is still likely hurting your sender reputation. And where there's no legal clock at all, this one still ticks.
05 · Watch both, on the contact · 1:42
On screen: a contact record opens. Two fields sit side by side, consent date and last engaged. A slider sets your limit. Cards past it turn amber, each with a small flag, ask again.
Watch both. In your email marketing tool, keep the date each person said yes on their contact record, right next to their last engagement. Set a time limit that fits your list. Then flag everyone who's passed it, before the window closes.
06 · The email that asks again · 2:06
On screen: chip 3 lights. A plain envelope goes to the amber cards. Inside, one line and one teal button, yes, keep me on the list, and below it a small, equally clear link, no thanks. Gloss card: re-permission · an email asking someone already on your list to actively confirm they still want your mail.
Then ask them, with a re-permission email. It does one thing. It asks them to confirm they still want to hear from you. Be honest. Give one clear yes, keep me on the list. And make it just as easy to say no, or to not answer at all.
07 · Silence is an answer · 2:30
On screen: the amber cards split. Cards with a yes turn teal, their date dial resetting to said yes today. Cards with no reply turn coral and slide off the sending stack.
What about the ones who never reply? No yes means no more email. Their card comes off your sends. The ones who click yes get a fresh date on their card, and the clock starts again.
08 · Clean before you ask · 2:48
On screen: before the envelope leaves, the amber cards pass under the checking desk lamp. A few of them turn coral, no longer active, and drop out. The envelope goes only to the rest.
One step before that email goes out. Some of those old addresses don't work anymore. Asking a dead address to confirm is budget spent on nobody. Clean the old batch first, then ask the ones who can answer.
09 · Recap · 3:08
On screen: the membership card with its region tags, the two dials, the contact record, the lamp, the re-permission envelope, the split stack. All three chips lit.
One more time. A yes is like a membership, and it can lapse. Watch the date and the activity. Keep the consent date on the contact, set a limit, and flag who's passed it. Clean first. Then ask for a clear yes.
10 · Close · 3:26
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
Treat a yes as something that lapses, and ask before it does. Nobody can re-confirm your subscribers for you. What Review My Emails does is take out the dead addresses first. That's RME Clean. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what is an email deliverability audit?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.012.006-what-is-consent-expiry.md
00 · A sale to a two-year-old yes (hook)
Almanac ids in this scene: 005.012.006
What is consent expiry?
three numbered chips, the VO's words: 1 why a yes can run out · 2 the two clocks to watch · 3 the email that asks again. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the membership card. No picture yet.
005.012.006 "You collected someone's email address two years ago. They signed up, maybe opened a few emails, then went quiet. Are you still allowed to email them?"
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 005.012.006, 015.001.001
no cut away and no ad break. The stack holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence.
005.012.006 "it's worth cleaning before that re-permission send. No point spending budget re-permissioning addresses that are no longer active." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · Why a yes can run out
Almanac ids in this scene: 005.012.006
Why a yes can run out
chip 1 lights. One card lifts from the stack and turns into a membership card, member since. Three small region tags sit under it, one per click: a clock · must stay current · no clock. Gloss card: consent expiry · the idea that someone's permission to be emailed can go stale over time.
one card, three kinds of rule. Reveals: (1) the card, (2) to (4) one tag each, (5) the gloss card.
the membership card. No picture yet.
R7, the one legal sentence, no law named, no period.
005.012.006 "Consent expiry is the idea that permission to email someone doesn't last forever." / "That depends on where they live, how they signed up, and whether their consent has expired." / "implied consent expires on a schedule" / "doesn't set a specific time limit, but it does require that consent remains" / "doesn't include a consent expiry concept at all."
T10, the gym membership, carried to the close.
03 · The first clock: time
Almanac ids in this scene: 005.012.006
The two clocks to watch
chip 2 lights. The card grows a small date dial in its corner. It starts at said yes, then resets once when a small opened tick lands, and runs on from there.
one dial, one reset. Reveals: (1) the dial, (2) it runs, (3) the tick, (4) it resets.
the membership card, the date dial.
005.012.006 "the clock starts ticking from the moment they gave consent or the last time they engaged with you." / "Time-based expiry is the legal version."
no period voiced (C30).
04 · The second clock: activity
Almanac ids in this scene: 005.012.006
The two clocks to watch
a second dial on the card, an activity meter, draining slowly. The date dial beside it still reads fine. A small reputation gauge under the card dips as the meter empties. The no clock tag from scene 02 lights, and the activity meter keeps draining anyway.
two dials, one fine and one empty, one gauge that dips. Reveals: (1) the meter, (2) it drains, (3) the date dial holds, (4) the gauge dips, (5) the no clock tag, (6) still draining.
the membership card, concept sender-reputation (the gauge).
005.012.006 "Engagement-based expiry is more of a deliverability and best-practice lens. If someone hasn't opened, clicked, or bought anything in the past 12 months, their consent may technically still be valid, but sending to them is likely hurting your sender reputation." / "ignoring engagement decay is still a deliverability risk even if it isn't a legal one in the US."
T3, the twist. "In a long while" carries the answer's "12 months" (C30). "Likely" kept (V12).
05 · Watch both, on the contact
Almanac ids in this scene: 005.012.006, 020.005.011
The two clocks to watch
a contact record opens. Two fields sit side by side, consent date and last engaged. A slider sets your limit. Cards past it turn amber, each with a small flag, ask again.
two fields, one limit, the cards past it flagged. Reveals: (1) the record, (2) the two fields, (3) the slider, (4) the amber cards, (5) the flags.
the membership card, the contact record.
020.005.011 "Store consent source, consent date, and consent language alongside every contact record". 005.012.006 "The practical answer is to treat both as real. Set a time limit (12 or 24 months is common), and flag subscribers who've passed it for a re-permission campaign before that window closes."
Q8, where (the contact record in your email marketing tool) and how (two fields, a limit, a flag). The slider shows no number (C30, N6). T5, the action.
06 · The email that asks again
Almanac ids in this scene: 005.012.006
The email that asks again
chip 3 lights. A plain envelope goes to the amber cards. Inside, one line and one teal button, yes, keep me on the list, and below it a small, equally clear link, no thanks. Gloss card: re-permission · an email asking someone already on your list to actively confirm they still want your mail.
one email, one yes, one no. Reveals: (1) the envelope, (2) the line, (3) the button, (4) the no link, (5) the gloss card.
the membership card, the envelope.
005.012.006 "a re-permission email does one thing: it asks the subscriber to actively confirm they still want to hear from you. It should be honest, have a clear "yes, keep me on the list" action, and make it easy to say no (or just not respond)."
no count of emails (C31). Registry: re-engagement is the quieter "still want to hear from us?" run (V927). This is its sharper form, asking for a yes, proposed as its own concept.
07 · Silence is an answer
Almanac ids in this scene: 005.012.006
The email that asks again
the amber cards split. Cards with a yes turn teal, their date dial resetting to said yes today. Cards with no reply turn coral and slide off the sending stack.
one stack split in two. Reveals: (1) the split, (2) the teal cards reset, (3) the coral cards slide off.
the membership card.
005.012.006 "Anyone who doesn't re-confirm gets suppressed" / "the clock starts ticking from the moment they gave consent".
C38, "suppressed, not deleted" is not voiced, only that they stop getting email, which every answer agrees on. "A fresh date" is the consent date from scene 05 updating, the answer's own clock.
08 · Clean before you ask
Almanac ids in this scene: 005.012.006
Clean before you ask
before the envelope leaves, the amber cards pass under the checking desk lamp. A few of them turn coral, no longer active, and drop out. The envelope goes only to the rest.
a few cards out before the send. Reveals: (1) the lamp, (2) the coral cards, (3) they drop, (4) the envelope leaves.
the checking desk.
005.012.006 "if your list has a significant chunk of contacts who signed up more than two years ago with no recent engagement, it's worth cleaning before that re-permission send. No point spending budget re-permissioning addresses that are no longer active."
Q2, the answer's own pivot, a list topic. Q3, before the recap.
09 · Recap
What to remember
the membership card with its region tags, the two dials, the contact record, the lamp, the re-permission envelope, the split stack. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
10 · Close
Almanac ids in this scene: 005.012.006, 016.013.001
A yes that's still a yes
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: RME Clean, named in the VO above and in the answer.
the dot grid into three pots, no counts.
concept list-cleaning.
005.012.006 "You can run a validation pass with RME Clean to strip the dead weight first."
S10, says what a clean does not do (re-confirm consent). Q4, brand twice. S8, the next video is 016.013.001 by its Almanac question, the first of "Deliverability monitoring, part 1". Totals: 12 scenes, 487 spoken words, about 2:56 of speech and about 3:45 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V105What is an email deliverability audit?
waiting on YTOpen questions for YT
- C61: for #almanac-to-check: five areas vs six.
- Tool name: in 016.013.001 ("analyzer") vs the channel's "DMARC parser".
- Series: episode 2 is V106, 004.006.001 "What is inbox placement rate?" (batch 10, PR #1190), named in the close (coordinator, 2026-09-30).
- Registry: deliverability-audit proposed.
00 · Rewriting subject lines, guessing (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the five areas · 2 what a good one hands you · 3 when to run one. Chips 2 and 3 grey.
Three parts. The five areas an audit checks. What a good one hands you at the end. And when to run one without waiting.
01 · Brought to you by, woven in · 0:26
On screen: no cut away and no ad break. The open-rate line holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
One of those five areas is your list itself, and Review My Emails checks every address on it before you send.
02 · What an audit is · 0:34
On screen: chip 1 lights. A check-up monitor switches on, five empty traces waiting. A clipboard beside it, three small ticks: technical check · data pull · pattern. Gloss card: deliverability audit · a structured review of everything that affects whether your email reaches the inbox.
A deliverability audit is a structured review of everything that affects whether your emails reach the inbox. It's a health check for your sending. Part technical check, part data pull, part spotting the pattern.
03 · Five signs · 0:53
On screen: the five traces label themselves, one per click: authentication · reputation · list quality · content and setup · engagement. All five flat for now.
This answer splits it into five areas. Authentication. Reputation. List quality. Content and setup. And engagement. Five signs on one monitor, and each one looks for something different.
04 · Authentication, and where to look · 1:12
On screen: the first trace lights and beats. Three small tiles sit under it with their registry pictures: SPF (the guest list), DKIM (the seal), DMARC (the rule). A record pastes into a box labelled DMARC parser, and it reads back in plain lines: policy, alignment.
Start with authentication, the three records that prove your mail is from you. Are they valid, is every message signed, and do they line up? It's the quick check that catches the most common show-stoppers. Our free DMARC parser reads your DMARC record, and the reports you're already getting.
05 · Reputation, from the providers themselves · 1:38
On screen: the second trace lights. A thirty-day strip slides in under it, three small lines on it: domain · sending IP · spam rate trend. A small tag hangs off the strip, not set up? step zero.
Then reputation. Pull the last thirty days from the free sender dashboards the big mailbox providers offer. Look at your domain's reputation, your sending server's reputation, and which way your spam rate is heading. Never set those dashboards up? That's step zero.
06 · List quality, broken down by source · 2:02
On screen: the third trace lights. Three small signup doors feed the list, form, event, import. A bar under each door, bounces and complaints. The import bar runs amber, and the whole trace dips with it.
Then the list. Where do new subscribers come from? When was the list last checked? And what are your bounces and complaints, broken down by where each subscriber came from? A single bad source can drag the whole list down.
07 · Setup, and who's still reading · 2:25
On screen: the fourth trace lights, three small checks under it: own sending domain · clean links · one- click unsubscribe. Then the fifth trace, a row of subscriber tiles sorted by recency, the oldest end fading grey.
Then content and setup. Do you send from a dedicated sending domain, or mix receipts and marketing? Are your links on clean domains? Is unsubscribing one click? And last, engagement. Split clicks and replies by how recently people engaged, and the quiet groups dragging you down show up.
08 · What a good audit hands you · 2:52
On screen: chip 2 lights. A long checklist scrolls up off the clipboard and falls away. What's left on the clipboard is three lines, each pointing at one amber trace on the monitor.
A good audit is shorter than you'd think. It doesn't hand you a forty-item checklist of trivia. It hands you the two or three things that are hurting you. Short is the point. That's how Sally stops guessing.
09 · When to run one · 3:12
On screen: chip 3 lights. A year strip with one big mark and four small ones. Then five trigger icons drop onto it, one per click, each jumping the next check forward to today: opens drop · bounces spike · new email tool · DNS change · new sending domain.
When should you run one? There's a baseline, a full audit once a year and a lighter check each quarter. But don't wait for the date when something changes. Opens drop suddenly, bounces spike, you move email tools, change your DNS, or add a sending domain. Each of those can break what was working.
10 · The question most lists can't answer · 3:38
On screen: the third trace from scene 06, the list. The clipboard line reads last checked: ?. The checking desk lamp sweeps a row of addresses, and one turns coral, no such mailbox.
The list area asks a question most senders can't answer. When was it last checked? Addresses stop working quietly. A mailbox that no longer exists looks like any other line, until a send finds it.
11 · Recap · 3:57
On screen: the monitor with all five traces, the parser read-back, the thirty-day strip, the source doors, the three-line clipboard, the trigger icons. All three chips lit.
One more time. An audit is a health check with five signs. Start with the three records in the DMARC parser. Pull thirty days from the providers' dashboards. Split your list by source. Expect two or three findings, not forty. And audit right away when something changes.
12 · Close · 4:16
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V106, no subscribe ask.
Check all five before you change a thing. Cleaning covers one sign, the list, not the other four. That's the part Review My Emails checks, every address. Want the full walkthrough with a human? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what is inbox placement rate?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-016.013.001-what-is-a-deliverability-audit.md
00 · Rewriting subject lines, guessing (hook)
Almanac ids in this scene: 016.013.001, 016.013.003
What is an email deliverability audit?
three numbered chips, the VO's words: 1 the five areas · 2 what a good one hands you · 3 when to run one. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the open-rate line. No picture yet.
016.013.003 "Start auditing immediately when: your open rates drop suddenly and significantly". 016.013.001 "Done right, it surfaces the two or three things that are actually hurting you".
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 016.013.001
no cut away and no ad break. The open-rate line holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence.
016.013.001 "List quality. Where do new subscribers come from? When was the list last validated?" 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · What an audit is
Almanac ids in this scene: 016.013.001, 016.013.002
The five areas
chip 1 lights. A check-up monitor switches on, five empty traces waiting. A clipboard beside it, three small ticks: technical check · data pull · pattern. Gloss card: deliverability audit · a structured review of everything that affects whether your email reaches the inbox.
one monitor, five empty traces, three ticks. Reveals: (1) the monitor, (2) the traces, (3) to (5) one tick each, (6) the gloss card.
the check-up monitor. No picture yet.
016.013.001 "A deliverability audit is a structured review of everything that affects whether your emails reach the inbox. It's equal parts technical check, data pull, and pattern-spotting." 016.013.002 "Think of it as a complete health check for your sending infrastructure."
T10, the health check, the Almanac's own simile, carried to the close.
03 · Five signs
Almanac ids in this scene: 016.013.001
The five areas
the five traces label themselves, one per click: authentication · reputation · list quality · content and setup · engagement. All five flat for now.
five traces, labelled. Reveals: (1) to (5) one label each.
the check-up monitor.
016.013.001 "a structured review of the five domains that determine inbox placement: authentication" / "reputation" / "list quality" / "content and infrastructure" / "and engagement patterns".
C61, "this answer splits it into five", never "an audit has five". Q7, five items drawn as five traces.
04 · Authentication, and where to look
Almanac ids in this scene: 016.013.001, 023.001.007, 023.002.006
The five areas
the first trace lights and beats. Three small tiles sit under it with their registry pictures: SPF (the guest list), DKIM (the seal), DMARC (the rule). A record pastes into a box labelled DMARC parser, and it reads back in plain lines: policy, alignment.
three tiles, one parser. Reveals: (1) the trace lights, (2) to (4) one tile each, (5) the paste, (6) the plain read-back.
the check-up monitor, concepts spf and its siblings (from V078 to V081, Q5).
016.013.001 "Is SPF valid, is DKIM signing every message, does DMARC align, and what's the policy? This is the 20-minute check that catches the most common show-stoppers." / "Our free DMARC analyzer covers area one in about three minutes." 023.002.006 "You can check your current DMARC record and see how it reads with our free DMARC Parser". 023.001.007 "the DMARC Parser to read any reports you're already getting."
Q6, the three names are on-screen labels only. Q8, where (our free DMARC parser) and how (paste the record or a report). Q11, the tool is "DMARC parser", the channel's one name, though 016.013.001 says "analyzer". The minute counts are not voiced.
05 · Reputation, from the providers themselves
Almanac ids in this scene: 016.013.001
The five areas
the second trace lights. A thirty-day strip slides in under it, three small lines on it: domain · sending IP · spam rate trend. A small tag hangs off the strip, not set up? step zero.
one thirty-day strip, three lines. Reveals: (1) the trace, (2) the strip, (3) to (5) one line each, (6) the tag.
the check-up monitor, concept sender-reputation.
016.013.001 "Pull Google Postmaster Tools and Microsoft SNDS for the last 30 days. Look at domain reputation, IP reputation, and spam rate trend. If you haven't set these up, that's step zero."
held brand names not voiced or shown (registry internal). No spam rate figure. "Your sending server" in VO for "IP" (never "address", which the channel uses for email addresses), the label on screen says sending IP.
06 · List quality, broken down by source
Almanac ids in this scene: 016.013.001
The five areas
the third trace lights. Three small signup doors feed the list, form, event, import. A bar under each door, bounces and complaints. The import bar runs amber, and the whole trace dips with it.
three sources, one amber bar, one trace that dips. Reveals: (1) the trace, (2) the three doors, (3) the bars, (4) the amber one, (5) the dip.
the check-up monitor.
016.013.001 "Where do new subscribers come from? When was the list last validated? What's your bounce rate and complaint rate by acquisition source? A single bad source can drag the whole list down."
no rate shown. Q8, where (bounces and complaints split by source) and how (one bar per source).
07 · Setup, and who's still reading
Almanac ids in this scene: 016.013.001
The five areas
the fourth trace lights, three small checks under it: own sending domain · clean links · one- click unsubscribe. Then the fifth trace, a row of subscriber tiles sorted by recency, the oldest end fading grey.
three checks, one row sorted by recency. Reveals: (1) the fourth trace, (2) to (4) one check each, (5) the fifth trace, (6) the tiles sort, (7) the grey end.
the check-up monitor, the subscriber tiles (V073's, called back).
016.013.001 "Are you using a dedicated sending domain, or mixing transactional and marketing? Are your links on clean domains? Is your unsubscribe link above the fold and one-click?" / "Open rate, click rate, and reply rate by segment and recency." / "engagement patterns segmented by recency to identify inactive cohorts dragging placement down."
"the quiet groups" carries the answer's "older than 12 months" (C30). "Receipts" for "transactional" in plain words. Opens not voiced as a measure (Q12, the channel treats opens as unreliable).
08 · What a good audit hands you
Almanac ids in this scene: 016.013.001
What a good one hands you
chip 2 lights. A long checklist scrolls up off the clipboard and falls away. What's left on the clipboard is three lines, each pointing at one amber trace on the monitor.
forty lines gone, three kept. Reveals: (1) the long list, (2) it falls away, (3) the three lines, (4) each points at its trace.
the check-up monitor, the clipboard.
016.013.001 "Done right, it surfaces the two or three things that are actually hurting you, not a 40-item checklist of trivia."
T3, the twist. Pays off the hook.
09 · When to run one
Almanac ids in this scene: 016.013.003
When to run one
chip 3 lights. A year strip with one big mark and four small ones. Then five trigger icons drop onto it, one per click, each jumping the next check forward to today: opens drop · bounces spike · new email tool · DNS change · new sending domain.
one year, one big mark and four small, five triggers that pull the check forward. Reveals: (1) the strip, (2) the marks, (3) to (7) one trigger each.
the check-up monitor, the calendar strip.
016.013.003 "Full audit once a year." / "Light quarterly review." / "Start auditing immediately when: your open rates drop suddenly and significantly, your bounce rates spike, you migrate to a new ESP, you make major DNS changes, you add a new sending domain" / "Each of these events can break things that were working fine before."
Q7, five triggers drawn as five icons. The quarterly check's rates are not voiced (N6). "Email tools" for "ESP" (V5). The answer's sixth trigger (a new audience) is left out for the count on screen.
10 · The question most lists can't answer
Almanac ids in this scene: 005.003.002, 016.013.001
The one you can fix before a send
the third trace from scene 06, the list. The clipboard line reads last checked: ?. The checking desk lamp sweeps a row of addresses, and one turns coral, no such mailbox.
one question mark, one coral address. Reveals: (1) the trace, (2) the question mark, (3) the lamp, (4) the coral address.
the checking desk.
016.013.001 "When was the list last validated?" 005.003.002 "Validation catches nonexistent mailboxes" / "before send".
Q2, the pivot grows from the audit's own list area. Q3, before the recap.
11 · Recap
What to remember
the monitor with all five traces, the parser read-back, the thirty-day strip, the source doors, the three-line clipboard, the trigger icons. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
12 · Close
Almanac ids in this scene: 004.006.001, 016.013.001
Stop guessing
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V106, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
016.013.001 "For the full walkthrough with a human, the SOS hotline is how most people start."
S10, says what a clean does not fix (the other four signs: authentication, reputation, setup, engagement). Q4, brand twice. S8, the next video is 004.006.001 (V106, "Deliverability monitoring, part 1" episode 2, PR #1190) by its Almanac question word for word. Totals: 14 scenes, 552 spoken words, about 3:20 of speech and about 4:36 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V106What is inbox placement rate?
waiting on YTOpen questions for YT
- C62: for #almanac-to-check: Promotions counted outside the inbox (004.006.001) vs "did reach them" (016.006.004).
- Series order: this is episode 2, after V105.
- Registry: panel-data proposed.
00 · Ninety-eight percent, and she stops looking (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what it measures · 2 how you get it · 3 how to read it. Chips 2 and 3 grey.
Three steps get us there. What the number measures. How you get it, when your email tool won't give it to you. And how to read it.
01 · Brought to you by, woven in · 0:36
On screen: no cut away and no ad break. The report card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Review My Emails works one step before this number, on the addresses, so every send starts with mail that has somewhere real to go.
02 · Two moments: the gate, then the trays · 0:50
On screen: chip 1 lights. A gate, and behind it three trays: inbox · spam · tab. A stream of envelopes reaches the gate. Two turn coral and bounce off. The rest pass, then each drops into a tray. Gloss card: delivery rate · the share of messages a receiving server accepted, which says nothing about where they landed.
Every email meets two moments. First, the gate. The receiving server accepts it or turns it away. Count what got accepted and that's your delivery rate, the number your email tool shows you. Then, past the gate, the provider drops it into a tray. Inbox, spam, or a tab.
03 · The number for the second moment · 1:12
On screen: the trays fill. The spam tray turns amber and fills to four of ten marks. The report card from scene 00 slides back in, still reading delivered 98%, unchanged. A second card appears beside it, inbox placement, with a gauge that has no number yet, and a small tag, measured with a test. Gloss card: inbox placement rate · the share of accepted messages that reached an inbox rather than another folder.
Inbox placement rate measures the second moment. Of the emails that got through the gate, how many landed in the inbox instead of spam? Ninety-eight percent delivered sounds great, until forty percent of those went straight to spam. Your delivery rate doesn't care. Placement does. And you measure it with a test.
04 · What decides the tray · 1:34
On screen: a lever under the trays, one end at inbox, the other at spam. Four weights drop onto it, one per click: reputation · authentication · content · engagement. The last weight is split, half teal, half amber, and the lever tips with it.
What decides the tray? The provider weighs a mix. Your sender reputation. Your authentication records. What's inside the message. And how your subscribers treat your mail. Readers who want it pull you toward the inbox. A stale list, with low opens and high spam complaints, tends to pull the other way.
05 · Why it moves first · 1:56
On screen: the spam tray's level creeps up by one mark. Beside it, two other gauges, volume and opens, still sit flat. Three small cause tags fall in, one per click: cold contacts · spam reports · authentication gap.
Why watch this number at all? It catches a reputation shift before your sending volume drops, or your opens collapse. If it starts slipping, something changed. Maybe a batch of cold contacts. Maybe a campaign that drew unusual spam reports. Maybe a gap in your authentication. It surfaces the problem early.
06 · The number your tool can't show · 2:18
On screen: chip 2 lights. A camera icon labelled your email tool sits on the sender's side of the gate. Its view reaches the gate and stops. Everything past it, the trays, dims.
The catch? Most email marketing tools don't report it at all. Mailbox providers don't tell senders which folder your mail landed in. Your tool sees the gate. After that, it's in the dark.
07 · Way one: a seed list · 2:36
On screen: a handful of small envelopes, each tagged with a provider icon (no brand names, three plain icons), slip into the stream at the gate. Past it, each lands in a tray, and a small table fills in: one row per icon, inbox · spam · missing.
How do you get the number, then? Two ways. The first is a seed list: test addresses at the big providers that you add to your send. A testing tool checks each one and reports inbox, spam or missing, provider by provider, usually within minutes. The next video takes the seed list apart.
08 · Way two: panel data · 2:58
On screen: a row of inbox icons, each with a small tick, opted in. Your envelope lands in each, and each reports its tray. Beside it, the seed table from scene 07. Two labels drop under them: seeds: steady coverage · panels: real readers. The panel row for one small provider has only two icons in it, thin.
The second is panel data. Real subscribers agree to let a monitoring service see where mail lands in their inbox. Seeds give you steady coverage across providers. Panels show how real, engaged readers see you, but they can run thin at smaller providers. Senders who take placement seriously use both.
09 · Read it by provider · 3:20
On screen: chip 3 lights. The seed table becomes three small lines over time. One drops off a ledge while two hold flat, one provider. Then all three sag slowly together, everywhere. Then a single dip that recovers, one send, beside three dips in a row, act.
Now, how do you read it? By provider, not as one number. A sharp drop at one provider, while the rest stay flat, usually means that provider's filters caught something. A slow slide everywhere points at your reputation as a whole. And one bad send can mean nothing. Two or three in a row is when you act.
10 · One reason you can check today · 3:44
On screen: the one-provider drop from scene 09. A book opens at the gate, the registry's blocklist picture. A box labelled blocklist checker takes a sending domain, send-more.example, and returns a short list of lookups, each ticked or flagged.
One usual suspect behind that sharp drop is a blocklist. And that one you can check before any test. Paste your sending domain into our free blocklist checker. It shows whether you're listed anywhere right now.
11 · Recap · 4:00
On screen: the gate, the trays, the lever, the dimmed camera view, the seed table, the three lines, the book. All three chips lit.
The short version. Delivery rate counts the gate. Inbox placement rate counts the trays. Your email tool won't show it, so measure it with seeds, panels, or both. Read it provider by provider, and act on a pattern, not one send. And check the blocklists today.
12 · Close · 4:18
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 3, no subscribe ask.
Look past the gate before you trust the report. Cleaning checks the addresses before they reach the gate. It doesn't choose the tray. Want to see who on your list has gone quiet? That's RME Insights, from Review My Emails. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what is a seed list?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-004.006.001-what-is-inbox-placement-rate.md
00 · Ninety-eight percent, and she stops looking (hook)
Almanac ids in this scene: 004.006.001, 016.011.007
What is inbox placement rate?
three numbered chips, the VO's words: 1 what it measures · 2 how you get it · 3 how to read it. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the report card. No picture yet.
004.006.001 "Your email got delivered. But did it actually land where anyone would see it? That's the question inbox placement rate answers." 016.011.007 "\"delivered\" just means the receiving server accepted the message."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 016.001.002
no cut away and no ad break. The report card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 24 words.
016.001.002 "When a server rejects a message outright or returns a hard bounce, that pulls your delivery rate down." 015.001.001 "we'll flag what's safe to send to and what to suppress".
says nothing about placement improving. The close says what a clean does not set.
02 · Two moments: the gate, then the trays
Almanac ids in this scene: 016.001.002, 016.011.007
What it measures
chip 1 lights. A gate, and behind it three trays: inbox · spam · tab. A stream of envelopes reaches the gate. Two turn coral and bounce off. The rest pass, then each drops into a tray. Gloss card: delivery rate · the share of messages a receiving server accepted, which says nothing about where they landed.
one gate, a hundred envelopes, two turned away, three trays. Reveals: (1) the gate, (2) the trays, (3) the envelopes arrive, (4) two turn coral, (5) the rest drop into trays, (6) the gloss card.
the gate and the trays, concept inbox-placement (M-37, M-18). The registry's own picture.
016.001.002 "Delivery rate measures how many messages the receiving server accepted during the SMTP transaction" / "The mailbox provider accepts your message and then decides where to put it. Inbox, spam folder, Promotions tab, Updates tab." 016.011.007 "ESPs measure what happens on their side of the transaction. Delivery rate (server accepted it), opens, clicks, bounces, and unsubscribes."
Q5, delivery rate re-glossed with the registry's line for a viewer arriving from search. "Your email tool" for "ESP" (V5). T10, the gate and the trays, carried to the close.
03 · The number for the second moment
Almanac ids in this scene: 004.006.001
What it measures
the trays fill. The spam tray turns amber and fills to four of ten marks. The report card from scene 00 slides back in, still reading delivered 98%, unchanged. A second card appears beside it, inbox placement, with a gauge that has no number yet, and a small tag, measured with a test. Gloss card: inbox placement rate · the share of accepted messages that reached an inbox rather than another folder.
ten marks on the spam tray, four filled, while the delivered card stays at 98. Reveals: (1) the trays fill, (2) the spam tray reaches four marks, (3) the old card, unchanged, (4) the new card, (5) the tag, (6) the gloss card.
the gate and the trays, concept inbox-placement-rate.
004.006.001 "It's different from your delivery rate, which only tells you whether the server accepted the message. IPR tells you what happened after that." / "a 98% delivery rate sounds great until you find out 40% of those delivered emails went straight to spam. Your delivery rate doesn't care. Your inbox placement rate does." / "IPR is measured via seed-list testing"
C62, the rate is voiced against the spam folder only, tabs are not called a miss. The figures are the answer's own example, voiced once, never a pass mark (N6). Q10, the answer and its action by about 1:34.
04 · What decides the tray
Almanac ids in this scene: 004.006.001
What it measures
a lever under the trays, one end at inbox, the other at spam. Four weights drop onto it, one per click: reputation · authentication · content · engagement. The last weight is split, half teal, half amber, and the lever tips with it.
one lever, four weights, one that tips it. Reveals: (1) the lever, (2) to (5) one weight each, (6) the tip.
the gate and the trays, concept sender-reputation.
004.006.001 "Mailbox providers like Gmail, Outlook, and Yahoo Mail make folder decisions based on a mix of signals. Your sender reputation, authentication records, content signals, and subscriber engagement all feed into that decision. A clean list with genuinely interested readers tends to land in the inbox. A stale list with low opens and high spam complaints tends not to."
Q7, four items drawn as four weights. "Tends to" kept (V12). No provider named. Opens are only the answer's description of a stale list, never the measure (Q12).
05 · Why it moves first
Almanac ids in this scene: 004.006.001
What it measures
the spam tray's level creeps up by one mark. Beside it, two other gauges, volume and opens, still sit flat. Three small cause tags fall in, one per click: cold contacts · spam reports · authentication gap.
one tray up by one mark while two gauges hold flat. Reveals: (1) the mark, (2) the flat gauges, (3) to (5) one tag each.
the gate and the trays.
004.006.001 "IPR is also the metric that catches reputation shifts before your sending volume drops or your open rates collapse. If your inbox placement rate starts slipping, something changed. Maybe you added a lot of cold contacts. Maybe a recent campaign triggered an unusual number of spam reports. Maybe your authentication has a gap. IPR surfaces the problem early."
06 · The number your tool can't show
Almanac ids in this scene: 004.006.001, 016.011.007
How you get it
chip 2 lights. A camera icon labelled your email tool sits on the sender's side of the gate. Its view reaches the gate and stops. Everything past it, the trays, dims.
one view that ends at the gate. Reveals: (1) the camera, (2) its view, (3) the trays dim.
the gate and the trays.
004.006.001 "IPR isn't natively reported by most ESPs." / "because mailbox providers don't expose folder placement directly to senders". 016.011.007 "the moment your email leaves the ESP's infrastructure, the visibility mostly stops." / "Your ESP doesn't know where the message landed once it was accepted."
T3, the twist. "Most" kept (V12).
07 · Way one: a seed list
Almanac ids in this scene: 004.006.002
How you get it
a handful of small envelopes, each tagged with a provider icon (no brand names, three plain icons), slip into the stream at the gate. Past it, each lands in a tray, and a small table fills in: one row per icon, inbox · spam · missing.
a handful of seeds, one row each. Reveals: (1) the seeds join, (2) they pass the gate, (3) each lands, (4) the table fills, row by row.
the gate and the trays, concept seed-list.
004.006.002 "A seed list is a curated set of real test addresses spread across major mailbox providers" / "you add those addresses to your send (or send to them separately), and the testing tool logs exactly where each message lands: inbox, spam folder, or somewhere else entirely." / "The tool checks each seed address and reports back, usually within minutes".
Q8, where (added to your send) and how (a testing tool, per provider). No vendor named. S6, a one-line gloss here, episode 3 (the next video) owns the seed list.
08 · Way two: panel data
Almanac ids in this scene: 004.006.002
How you get it
a row of inbox icons, each with a small tick, opted in. Your envelope lands in each, and each reports its tray. Beside it, the seed table from scene 07. Two labels drop under them: seeds: steady coverage · panels: real readers. The panel row for one small provider has only two icons in it, thin.
two sources side by side, one thin row. Reveals: (1) the inbox icons, (2) the envelope lands, (3) the trays report, (4) and (5) one label each, (6) the thin row.
the gate and the trays.
004.006.002 "Real subscribers (usually opted-in through browser extensions or app permissions) allow their inbox behavior to be anonymously monitored." / "it reflects how actual mailbox filters are treating your messages for your audience." / "You might get strong data for Gmail but thin data for smaller providers. Seed tests give you more consistent coverage across providers, even obscure ones." / "Most senders who take inbox placement seriously use both."
T11, the panel is inbox icons, never people drawn. No provider named.
09 · Read it by provider
Almanac ids in this scene: 004.006.009
How to read it
chip 3 lights. The seed table becomes three small lines over time. One drops off a ledge while two hold flat, one provider. Then all three sag slowly together, everywhere. Then a single dip that recovers, one send, beside three dips in a row, act.
three lines, three patterns. Reveals: (1) the lines, (2) the one-provider drop, (3) the slow sag, (4) the single dip, (5) three in a row.
the trend lines.
004.006.009 "You'll see the placement percentage drop sharply for that provider while others stay flat." / "Sharp drop at one provider only usually means a blocklist hit or a filtering rule that provider added recently." / "Gradual decline across all providers suggests a broader sender reputation problem" / "A single bad send can look alarming but mean nothing. A pattern across two or three consecutive sends is when you need to act."
Q8, how to read it. "Usually" and "can" kept (V12). V093 owns reading drift as decay, this scene only says how to read the rate.
10 · One reason you can check today
Almanac ids in this scene: 004.006.001, 004.006.009, 012.002.012
One check you can run now
the one-provider drop from scene 09. A book opens at the gate, the registry's blocklist picture. A box labelled blocklist checker takes a sending domain, send-more.example, and returns a short list of lookups, each ticked or flagged.
one drop, one book, one lookup. Reveals: (1) the drop, (2) the book, (3) the paste, (4) the results.
concept blocklist (the book held open at the gate).
004.006.009 "Sharp drop at one provider only usually means a blocklist hit". 004.006.001 "our free Blocklist Checker is a good starting point for spotting reputation issues that might be pushing you out of the inbox." 012.002.012 "run a quick domain reputation check with our free blocklist checker to see if you're listed anywhere right now."
Q2, the pivot grows from this topic (a tray that tips), not the catch-all line. Q3, before the recap. Q11, "blocklist checker", one name. Demo domain from 01-library/demo-names.md (send-more.example, Sally Send's).
11 · Recap
What to remember
the gate, the trays, the lever, the dimmed camera view, the seed table, the three lines, the book. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
12 · Close
Almanac ids in this scene: 022.008.003
Past the gate
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 3, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: RME Insights, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
S10, says what a clean does not do (it doesn't choose the tray). Q4, brand twice (bridge and close). S8, the next video is 022.008.003 by its Almanac question, word for word. Totals: 14 scenes, 620 spoken words, about 3:44 of speech and about 4:40 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V107What is a Seed List?
waiting on YTOpen questions for YT
- C63: for #almanac-to-check: seeds per provider, 5 to 10 vs 3 to 5 vs 20+ vs 25.
- Registry: seed-weighting-bias proposed, and the house plan as the picture for seed-list.
00 · A week on the wrong provider (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what goes on it · 2 build or use a service · 3 read the average. Chips 2 and 3 grey.
Three things to know. What goes on a seed list. Whether to build your own or use a service's. And how to read the average without it misleading you.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A seed list is test addresses you own, and Review My Emails checks the other kind, the real addresses on your list.
02 · What it is: detectors in every room · 0:37
On screen: chip 1 lights. A house plan, three rooms, each a plain provider icon. A small detector clicks onto each ceiling, labelled seed. An envelope arrives in each room, and each detector shows one word: inbox, spam, missing. Gloss card: seed list · a set of addresses you own, sent to on purpose, to watch where a campaign lands.
A seed list is a set of real addresses, spread across several mailbox providers, that you control. You add them to your send, then check each inbox. Inbox. Spam. Or missing entirely. Each one is a smoke detector, one in every room.
03 · Which rooms get a detector · 0:58
On screen: the house grows a fourth room, smaller, a regional icon, and a detector clicks onto it. Dots for subscribers fill each room, most in the first room.
Which providers go on it? The ones your subscribers use. At minimum, the biggest mailbox providers. Then more, if your audience leans somewhere else, like a regional provider. Put the detectors where your people live.
04 · How many detectors · 1:16
On screen: one room zooms in. A single detector, then a row of them appears on the ceiling, three shades: new · established · different history. Beside the plan, a five-detector house is stamped misleads.
How many? More than a handful. One seed at a provider tells you almost nothing, and a five-address list can mislead you more than it helps. More seeds cover more kinds of accounts. New ones. Established ones. Ones with different histories. That's a broader picture.
05 · Building your own · 1:39
On screen: chip 2 lights. One detector, three switches on its side, flipped one per click: account · script access · kept alive. A clock over the third switch ticks, and a small pulse shows on the detector each time it's used.
Can you build your own? Yes. Open accounts you control at those providers. Turn on access, so a script can check where each email lands. Then keep every account alive, with logins, opens, a click, the odd reply. Providers shut down dormant accounts.
06 · Homemade lists wear out · 2:02
On screen: one detector on the ceiling gets a small tag stuck to it by the room, tester. Its reading greys out. Beside the house, a second set of detectors swaps in and out on a slow rotation, rotated.
Homemade lists wear out, though. Once a provider recognises an address as a tester, it can treat it differently. Then you're testing how it handles a known test address, not a subscriber. Services rotate and refresh their seeds for exactly that reason, and handle the upkeep.
07 · The average that lies · 2:24
On screen: chip 3 lights. The four rooms from scene 03, each detector's reading as a bar. The bars pour into one average with equal spoons, one per room. The small room's amber bar pulls the average down. Then the dots in each room light up, most in the first room, few in the small one. Gloss card: seed weighting bias · when the mix of providers in your seeds doesn't match your real list, so the average misleads.
Now the average. Most seed reports blend every provider into one number, as if each mattered equally. Your list doesn't split that way. That gap is called seed weighting bias. A bad result in a small room drags the number down, while barely touching your business.
08 · Weight it in five minutes · 2:48
On screen: a subscriber export slides out of an email tool window. Its rows sort into the rooms by provider. Each room shows its share as a slice. Then the spoons resize to match the slices, and the average moves. A small label: off by 10+ points.
The fix takes about five minutes. Export your active subscribers from your email marketing tool. Group them by the provider behind each domain. Then weight each provider's seed result by its share of your list, and add them up. An unweighted average can be off by ten points or more.
09 · What a detector is for · 3:14
On screen: every detector in the house goes amber at once, spam everywhere, and an alarm icon flashes. Then it clears. Beside it, a weather icon stays greyed out, not this.
Then read it for what it is. A smoke detector, not a weather forecast. It catches the obvious fire, a campaign going to spam across the board, or a setup that's broken. Use seeds to catch problems before they hit your whole list, and pair them with other signals.
10 · Recap · 3:36
On screen: the house plan with its detectors, the row of three kinds, the three switches, the rotating set, the resized spoons, the alarm. All three chips lit.
Put together, then. A seed list is test addresses you own, at the providers your subscribers use. More than a handful. Homemade lists need upkeep, and wear out. Weight the average by where your subscribers live. And treat it as a smoke detector.
11 · Close · 3:54
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 4, no subscribe ask.
Put your detectors where your people live, and weight what they tell you. A seed list tests where test mail lands. Whether your real addresses exist is a different check, and that's the one Review My Emails runs. Unsure what setup fits? Our SOS line is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... do inbox placement tools manipulate reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-022.008.003-what-is-a-seed-list.md
00 · A week on the wrong provider (hook)
Almanac ids in this scene: 016.003.013
What is a Seed List?
three numbered chips, the VO's words: 1 what goes on it · 2 build or use a service · 3 read the average. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the seed report. No picture yet.
016.003.013 "Your seed report says you hit 92% inbox at Gmail and 60% at Yahoo. The aggregate number on the dashboard says 78%." / "panicking about a Yahoo problem that does not move revenue."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 022.008.003
no cut away and no ad break. The report holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 22 words.
022.008.003 "Seeds are controlled test accounts, not the full range of individual inbox reputations". 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · What it is: detectors in every room
Almanac ids in this scene: 004.006.004, 022.008.003
What goes on it
chip 1 lights. A house plan, three rooms, each a plain provider icon. A small detector clicks onto each ceiling, labelled seed. An envelope arrives in each room, and each detector shows one word: inbox, spam, missing. Gloss card: seed list · a set of addresses you own, sent to on purpose, to watch where a campaign lands.
three rooms, three detectors, three readings. Reveals: (1) the plan, (2) the detectors, (3) the envelopes, (4) to (6) one reading each, (7) the gloss card.
the house plan, concept seed-list. No picture yet for the house.
022.008.003 "A seed list is a collection of real email addresses spread across multiple mailbox providers (MBPs). You add those addresses to your send, fire off the campaign, and then check each inbox to see where your message ended up. Inbox. Spam. Missing entirely." 004.006.004 "Think of them as a smoke detector, not a weather forecast."
T10, the Almanac's own simile, carried to the close. No address is shown, only the label seed (V7). Episode 2 glossed the word in one line and pointed here (S6).
03 · Which rooms get a detector
Almanac ids in this scene: 022.008.003
What goes on it
the house grows a fourth room, smaller, a regional icon, and a detector clicks onto it. Dots for subscribers fill each room, most in the first room.
four rooms, dots filling them unevenly. Reveals: (1) the fourth room, (2) its detector, (3) the dots fill.
the house plan.
022.008.003 "A good seed list covers the MBPs your actual subscribers use." / "Depending on your audience, you might also want coverage at iCloud Mail, Zoho Mail, or regional providers relevant to your market."
Q8, where (the providers your subscribers use). No provider named in VO. The uneven dots set up scene 07.
04 · How many detectors
Almanac ids in this scene: 016.003.006, 022.008.003
What goes on it
one room zooms in. A single detector, then a row of them appears on the ceiling, three shades: new · established · different history. Beside the plan, a five-detector house is stamped misleads.
one detector becomes a row of three kinds. Reveals: (1) the single detector, (2) the row, (3) to (5) one kind each, (6) the small house and its stamp.
the house plan.
016.003.006 "One Gmail seed address tells you almost nothing." 022.008.003 "You don't need hundreds to get directional signal, but a five-address list is going to mislead you more than help you." / "More seeds give you a broader picture across inbox types and account states (new accounts, established accounts, accounts with different engagement histories)."
C63, no count per provider voiced or shown. Q7, the kinds drawn as three detectors.
05 · Building your own
Almanac ids in this scene: 016.003.006
Build or use a service
chip 2 lights. One detector, three switches on its side, flipped one per click: account · script access · kept alive. A clock over the third switch ticks, and a small pulse shows on the detector each time it's used.
three switches, one that needs flipping again and again. Reveals: (1) to (3) one switch each, (4) the clock, (5) the pulse.
the house plan, one detector close up.
016.003.006 "Yes, you can build a DIY seedlist, though it takes ongoing maintenance." / "For each provider, create separate addresses that you control." / "Without this step, you can't automate the placement check" / "Inbox providers deactivate dormant accounts" / "interact with some real emails (open, click, reply occasionally), and make the accounts look like real people use them."
Q8, where and how in three steps. The setup settings are not voiced (P7, description only). Q7, three steps drawn as three switches.
06 · Homemade lists wear out
Almanac ids in this scene: 004.006.004, 016.003.006, 022.008.003
Build or use a service
one detector on the ceiling gets a small tag stuck to it by the room, tester. Its reading greys out. Beside the house, a second set of detectors swaps in and out on a slow rotation, rotated.
one detector tagged and greyed, a set that rotates. Reveals: (1) the tag, (2) the grey reading, (3) the rotating set.
the house plan.
022.008.003 "DIY lists are free but degrade fast. Mailbox providers can detect and filter seeds differently once they recognize the address as a tester." / "rotate and refresh their seed accounts regularly to avoid that detection problem." 004.006.004 "You're sometimes testing how a provider handles a known monitoring address, not how it handles a real subscriber." 016.003.006 "Commercial tools already have aged, warmed accounts distributed across many providers, and they handle all the maintenance."
no service named. "Can" kept (V12). The occasional spot check stays fair game (next scene's opener keeps it neutral, G2).
07 · The average that lies
Almanac ids in this scene: 016.003.013
Read the average
chip 3 lights. The four rooms from scene 03, each detector's reading as a bar. The bars pour into one average with equal spoons, one per room. The small room's amber bar pulls the average down. Then the dots in each room light up, most in the first room, few in the small one. Gloss card: seed weighting bias · when the mix of providers in your seeds doesn't match your real list, so the average misleads.
four bars, four equal spoons, one average pulled by the smallest room. Reveals: (1) the bars, (2) the equal pour, (3) the pull, (4) the dots light, (5) the gloss card.
the house plan, the average.
016.003.013 "Seed weighting bias is when the mix of mailbox providers in your seed list does not match your real subscriber list, so the aggregate inbox rate on your dashboard is misleading." / "A straight average treats every provider as equal weight. Reality does not." / "Yahoo is dragging the average down while barely mattering to your business."
T3, the twist. Pays off the hook. No provider named.
08 · Weight it in five minutes
Almanac ids in this scene: 016.003.013
Read the average
a subscriber export slides out of an email tool window. Its rows sort into the rooms by provider. Each room shows its share as a slice. Then the spoons resize to match the slices, and the average moves. A small label: off by 10+ points.
four slices set the spoon sizes, and the average moves. Reveals: (1) the export, (2) the rows sort, (3) the slices, (4) the spoons resize, (5) the average moves, (6) the label.
the house plan, the average.
016.003.013 "Pull your active subscriber list from your ESP." / "Group by the MX of the recipient domain." / "Calculate the share of each. Use that share as your weight." / "Take the inbox rate at each provider, multiply by that provider's share of your actual list, then sum." / "It takes five minutes" / "An unweighted seed average can be off by ten points or more."
Q8, where (your email marketing tool's export) and how (group, weight, add). "The provider behind each domain" carries MX without a new word (Q6). N5, the sum is shown as moving spoons, not spoken as figures. "Email marketing tool" for "ESP" (V5).
09 · What a detector is for
Almanac ids in this scene: 004.006.004, 022.008.003
Read the average
every detector in the house goes amber at once, spam everywhere, and an alarm icon flashes. Then it clears. Beside it, a weather icon stays greyed out, not this.
every room alarms together, then clears. Reveals: (1) all amber, (2) the alarm, (3) it clears, (4) the greyed weather icon.
the house plan.
004.006.004 "Think of them as a smoke detector, not a weather forecast. They'll tell you the house is on fire. They won't tell you the humidity." / "They're useful for catching obvious problems, like if a campaign is going to spam across the board, or if a specific domain configuration is broken." 022.008.003 "use seeds to catch placement problems before they hit your whole list. Don't rely on them as the only measure of deliverability health."
M5, V099 owns why seeds miss per-person results. This scene only says what they're good for.
10 · Recap
What to remember
the house plan with its detectors, the row of three kinds, the three switches, the rotating set, the resized spoons, the alarm. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
11 · Close
Almanac ids in this scene: 012.015.003, 022.008.003
Detectors where people live
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 4, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
022.008.003 "If you're not sure where to start, our SOS hotline is free and we're happy to walk through what testing setup makes sense for your volume and audience."
S10, a clean checks addresses, it does not test placement. Q4, brand twice. S8, the next video is 012.015.003 by its Almanac question, word for word. Totals: 13 scenes, 557 spoken words, about 3:21 of speech and about 4:16 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V108Do inbox placement tools manipulate reputation?
waiting on YTOpen questions for YT
- C65: for #almanac-to-check: "at all" (012.015.003) vs the cold-domain edge case (016.003.016).
- Registry: placement-tool (the thermometer) and warmup-tool proposed.
00 · Afraid of the test (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 how it works · 2 why it can't move it · 3 which domain to test from. Chips 2 and 3 grey.
Three questions settle it. How a placement tool works. Why it can't move your reputation. And which domain to test from, so the reading means something.
01 · Brought to you by, woven in · 0:27
On screen: no cut away and no ad break. The button holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Reputation is built from your real subscribers, and Review My Emails checks those real addresses on your list before you send.
02 · How it works: a copy to the seeds · 0:34
On screen: chip 1 lights. One envelope copies itself into a small fan of copies, each flying to a plain provider icon. Each icon shows one word: inbox, spam, missing. The words gather into one small snapshot card, right now. Gloss card: seed list · a set of addresses you own, sent to on purpose, to watch where a campaign lands.
How does a placement tool work? It sends a copy of your email to its own test accounts, a seed list, spread across the big providers. Each one checks where the copy landed. Inbox, spam, or missing. That's a snapshot of how those providers see you right now.
03 · A thermometer · 0:56
On screen: the snapshot card turns into a thermometer. Its line rises to amber, running hot. A second thermometer reading beside it doesn't move the first one at all. Then a small tag under it: the fix: how you send.
Nothing about that process changes your standing. The tool is a thermometer. It tells you the temperature. Taking your temperature never gave anyone a fever. And fixing the fever takes changes to how you send.
04 · Why a test can't move it · 1:14
On screen: chip 2 lights. A large jar fills from four streams, one per click: engagement · complaints · bounces · steady sending. Then a single drop, 150 test sends, falls into the jar. The level doesn't change. A counter beside it: 100,000 subscribers.
Why can't it move your reputation? Providers build it from your real subscribers. Engagement from real people. Complaints. Bounces. How steadily you send. Next to that, a test is a drop. A hundred and fifty test addresses, against a hundred thousand subscribers. That's not enough to move any metric that matters.
05 · The tool that does try · 1:39
On screen: the jar from scene 04. A small pump labelled warmup tool pushes fake bubbles into it. A magnifier drifts over the bubbles and marks each one automated. The bubbles fade. Gloss card: warmup tool · a service whose accounts open and click your mail automatically, to make engagement look real.
The tools that do try to move it are a different category. A warmup tool opens your emails automatically from fake accounts, to pump up your engagement. Providers have got good at spotting that pattern. Our myth video, do email warmup tools build real reputation, goes deeper.
06 · Test from your real domain · 2:00
On screen: chip 3 lights. Two thermometers side by side. One labelled fresh domain reads cool. The other, send-more.example, Sally's own, reads amber. An equals sign between them is struck out.
Which domain do you test from? The one you send from every day. A fresh domain shows how providers treat a stranger, useful for checking your setup on its own. But a clean result there doesn't mean your real domain lands the same way. Your real domain carries your history. That's what your subscribers see.
07 · What the reading is for · 2:25
On screen: a row of small thermometers, one per plain provider icon. One runs amber. A spotlight lands on it, gap. A closed padlock sits beside the tool's icon, can't fix.
Then use the reading for what it is. A tool like this surfaces the gaps, like one provider where you run hotter than the rest. It can't close them for you. Closing them takes changes to what you send, and who you send to.
08 · The signal you can head off · 2:45
On screen: the jar from scene 04, its bounces stream highlighted. Upstream of it, a row of addresses passes under the checking desk lamp. One turns coral, no such mailbox, and is lifted out before it reaches the stream.
Of those real signals, one can be dealt with before a single email goes out. Bounces. An address that no longer exists bounces whether you test or not. And a dead address can be found before you send to it.
09 · Recap · 3:04
On screen: the snapshot card, the thermometer, the jar and its drop, the faded bubbles, the two readings, the coral address. All three chips lit.
Back to Sally's worry, then. A placement tool is a thermometer. It reads you, it doesn't change you. A test is a drop next to your real sends. Warmup tools are a different thing. Test from the domain you send from every day. And check your addresses before the send.
10 · Close · 3:21
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 5, no subscribe ask.
Run the test, and read it from your real domain. A clean only takes out addresses that would bounce. It can't cool a reputation. That's RME Clean, from Review My Emails. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... how to monitor your domain reputation?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-012.015.003-do-placement-tools-manipulate-reputation.md
00 · Afraid of the test (hook)
Almanac ids in this scene: 012.015.003
Do inbox placement tools manipulate reputation?
three numbered chips, the VO's words: 1 how it works · 2 why it can't move it · 3 which domain to test from. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the test button. No picture yet.
012.015.003 "You've probably wondered whether running your campaigns through an inbox placement tool could somehow backfire. Like, what if all those test accounts skew your reputation? The short answer is no. Legitimate inbox placement tools measure your deliverability."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 012.015.003, 015.001.001
no cut away and no ad break. The button holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 21 words.
012.015.003 "Your reputation is built on what happens with your real subscribers." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · How it works: a copy to the seeds
Almanac ids in this scene: 012.015.003
How it works
chip 1 lights. One envelope copies itself into a small fan of copies, each flying to a plain provider icon. Each icon shows one word: inbox, spam, missing. The words gather into one small snapshot card, right now. Gloss card: seed list · a set of addresses you own, sent to on purpose, to watch where a campaign lands.
one email, a fan of copies, one snapshot. Reveals: (1) the copies, (2) they land, (3) the three words, (4) the snapshot card, (5) the gloss card.
the snapshot card. Concept seed-list.
012.015.003 "The tool sends a copy of your email to a network of test accounts (called seeds) spread across providers like Gmail, Outlook, and Yahoo Mail. Those accounts check where the message landed: inbox, spam, or missing entirely. That result is a snapshot of your current reputation as those providers see it."
Q5, the seed list re-glossed with the registry's line. No provider named in VO.
03 · A thermometer
Almanac ids in this scene: 012.015.003
How it works
the snapshot card turns into a thermometer. Its line rises to amber, running hot. A second thermometer reading beside it doesn't move the first one at all. Then a small tag under it: the fix: how you send.
one reading, read twice, unchanged. Reveals: (1) the thermometer, (2) the amber line, (3) the second reading, no change, (4) the tag.
the thermometer. No picture yet.
012.015.003 "Nothing about the process changes your standing with them." / "The tool is a thermometer. It tells you the temperature. Fixing the fever takes actual changes to your sending behaviour."
T10, the Almanac's own simile, carried to the close. "Never gave anyone a fever" is the simile's own logic, not a new email claim.
04 · Why a test can't move it
Almanac ids in this scene: 012.015.003, 016.003.016
Why it can't move it
chip 2 lights. A large jar fills from four streams, one per click: engagement · complaints · bounces · steady sending. Then a single drop, 150 test sends, falls into the jar. The level doesn't change. A counter beside it: 100,000 subscribers.
a full jar, one drop, a level that holds. Reveals: (1) the jar, (2) to (5) one stream each, (6) the drop, (7) the level holds, (8) the counter.
the jar of real signals. No picture yet.
012.015.003 "Engagement signals from actual humans, complaint rates, bounce rates, and sending consistency are what mailbox providers track. A handful of seed accounts can't move those numbers." 016.003.016 "if your regular campaigns go to 100,000 subscribers, a test send to 150 seed addresses represents 0.15% of your total. That's not enough to move any metric in a direction that matters."
Q7, four signals drawn as four streams. N5, the two counts are shown and spoken, the percentage is left off so the ear isn't asked to divide. C65: never "never" or "at all".
05 · The tool that does try
Almanac ids in this scene: 012.015.003
Why it can't move it
the jar from scene 04. A small pump labelled warmup tool pushes fake bubbles into it. A magnifier drifts over the bubbles and marks each one automated. The bubbles fade. Gloss card: warmup tool · a service whose accounts open and click your mail automatically, to make engagement look real.
fake bubbles pumped in, then marked and faded. Reveals: (1) the pump, (2) the bubbles, (3) the magnifier, (4) they fade, (5) the gloss card.
the jar of real signals.
012.015.003 "There's a different category of tool called a warm-up bot. These services auto-open your emails and \"move them to inbox\" using fake accounts, with the explicit goal of inflating your engagement metrics." / "Mailbox providers have gotten quite good at recognizing automated interaction patterns".
R8, a neutral description, never a recommendation, no names, no prices. S6, V030 owns it, called back here by its Almanac question. Q9, V030's word "warmup tool" (P5), not the answer's "warm-up bot".
the answer's "worse spot than before" is not voiced as a penalty claim, only "spotting that pattern". The gloss is new wording, proposed to the registry beside email-warmup.
06 · Test from your real domain
Almanac ids in this scene: 016.003.017
Which domain to test from
chip 3 lights. Two thermometers side by side. One labelled fresh domain reads cool. The other, send-more.example, Sally's own, reads amber. An equals sign between them is struck out.
two readings that disagree. Reveals: (1) the fresh one, (2) the real one, (3) the struck equals sign.
the thermometer.
016.003.017 "Cold-domain testing sends from a brand-new domain with zero reputation history" / "so they treat it as an unknown sender" / "A clean result on a fresh domain doesn't mean your production domain will land the same way." / "Production testing gives you real-world placement data, the kind that reflects what your subscribers are actually experiencing right now." / "use cold-domain testing to benchmark infrastructure"
T3, the twist. T2 and Q8, where (the domain you send from every day). Demo domain from the library (send-more.example, Sally Send's).
07 · What the reading is for
Almanac ids in this scene: 012.015.003
Which domain to test from
a row of small thermometers, one per plain provider icon. One runs amber. A spotlight lands on it, gap. A closed padlock sits beside the tool's icon, can't fix.
a row of readings, one hot. Reveals: (1) the row, (2) the hot one, (3) the spotlight, (4) the padlock.
the thermometer.
012.015.003 "A placement tool surfaces those gaps. It can't close them for you." / "Fixing the fever takes actual changes to your sending behaviour."
the answer's provider pair is not named. "What you send, and who you send to" is carried by "sending behaviour" and by scene 04's real signals.
08 · The signal you can head off
Almanac ids in this scene: 005.003.002, 012.015.003
One you can head off
the jar from scene 04, its bounces stream highlighted. Upstream of it, a row of addresses passes under the checking desk lamp. One turns coral, no such mailbox, and is lifted out before it reaches the stream.
one stream, one coral address lifted out. Reveals: (1) the stream lights, (2) the lamp, (3) the coral address, (4) it's lifted out.
the checking desk.
012.015.003 "complaint rates, bounce rates, and sending consistency are what mailbox providers track." 005.003.002 "Validation catches nonexistent mailboxes, spamtraps (honeypot addresses that flag poor list hygiene), and typo domains before send".
Q2, the pivot grows from this topic's real signals. Q3, before the recap. Only the bounce half is claimed, never complaints or engagement.
09 · Recap
What to remember
the snapshot card, the thermometer, the jar and its drop, the faded bubbles, the two readings, the coral address. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
10 · Close
Almanac ids in this scene: 012.002.012
Read, then change
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 5, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
S10, says what a clean does not do (it can't cool a reputation). Q1, "A clean only takes out" is not the stock "A clean won't". Q4, brand twice. S8, the next video is 012.002.012 by its Almanac question, word for word. Totals: 12 scenes, 503 spoken words, about 3:02 of speech and about 3:40 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V109How to monitor your domain reputation?
waiting on YTOpen questions for YT
- Registry: sender-dashboard proposed as the public word for the held provider tools.
- Style call: no provider is named here, even as a provider, so the three reports read as kinds of report.
00 · One dashboard, once a month (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 why no single score · 2 which reports to read · 3 what makes you stop. Chips 2 and 3 grey.
It comes down to three things. Why there's no single score. Which reports to read, and what each one shows. And what should make you stop and look.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The cards hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Reputation reports grade how you send, and Review My Emails checks the part that starts on your list, the addresses.
02 · Why there's no single score · 0:36
On screen: chip 1 lights. A folder opens. Three report cards fan out, each in a different format: one with a letter-style band, one with a traffic light, one with a trend line. Gloss card: domain reputation · the part of your reputation that belongs to your domain name.
Why no single score? Your domain reputation isn't kept in one place. Every major mailbox provider works it out on its own, and each one tells you something slightly different. Picture report cards from different graders, each on their own scale. Monitoring means a small routine across a few of them.
03 · The biggest provider's card · 1:00
On screen: chip 2 lights. The first card lifts out of the folder. A four-step scale along its top, High · Medium · Low · Bad, a marker on High. Three small rows fill in under it: spam rate · authentication passes · delivery errors. A calendar strip beside it gets a tick every week. Gloss card: sender dashboard · a free page where a mailbox provider shows senders how it sees their mail.
Start with the biggest provider's free sender dashboard. It grades your domain in four bands. High, Medium, Low, or Bad. Beside the grade, your spam rate, how often your authentication passes, and delivery errors. It only covers that provider's own mail, so it's not the whole picture. Check it weekly.
04 · Reading that card · 1:25
On screen: the marker slides from High to Medium, and a small amber tag drops, look now. Then it slides on to Low, and the tag turns coral, emergency. The other cards in the folder stay face down, not covered.
How do you read it? One step down, from High to Medium, is worth investigating straight away. Low or Bad, treat it as an emergency. And a good grade there tells you about that one provider, not the others.
05 · A second grader, a traffic light · 1:42
On screen: the second card from the hook lifts out. A row of small server icons, each with its own traffic light, most green, one amber. A complaint line runs under them. The card slides in beside the first, alongside.
A second provider grades a different thing. It gives each of your sending servers a traffic light, green, yellow or red, and shows complaint rates from its own users. It's about your servers, not your domain, so it sits beside the first card, not in place of it. Yellow or red there probably means you're already suffering at that provider.
06 · A third card, and the view from outside · 2:06
On screen: a third card, a simple trend line, joins the other two. Then the folder zooms out, and outside it a book opens at the gate, the registry's blocklist picture. A box labelled blocklist checker takes send-more.example and returns a short list of lookups, each ticked or flagged.
A third provider shows delivery trends. Less detailed, but worth a look alongside. Then step outside the providers. Blocklist and filtering services show how your domain looks to the wider filtering world. They can't see inside a provider, but they can catch a new listing the dashboards haven't shown yet. Paste your domain into our free blocklist checker to see if you're listed anywhere right now.
07 · What should make you stop · 2:34
On screen: chip 3 lights. A weekly card with five small lamps in a row, each lighting amber in turn: grade down · spam rate up · green to yellow · authentication failing · new listing.
What should make you stop and look? Any one of these, week over week. The grade drops a step. Your spam rate climbs. A light turns from green to yellow. Your authentication passes less often, which means something's misconfigured or broken. Or a new blocklist listing.
08 · Then look at that week · 2:57
On screen: the lit lamp points back along a week strip. Three small tags fall onto that week, one per click: new campaign · old segment · volume jump.
Then pause, and look at what you sent in that stretch. A new campaign? A segment you hadn't mailed in a while? A sudden jump in volume? Any one lamp is reason enough to check what changed.
09 · One cause you can check first · 3:17
On screen: the old segment tag from scene 08 lifts out. Its rows pass under the checking desk lamp before the send. A few turn coral, no such mailbox, and stay behind. The cards in the folder stay still.
One of those causes can be checked before any card moves. The segment you haven't mailed in a while. Import an old list and blast everyone at once, and a flood of bounces and complaints almost always follows. Check it before your next send to it.
10 · Recap · 3:37
On screen: the folder, the four-step scale, the server lights, the trend card, the book, the five lamps, the week strip, the lamp at the desk. All three chips lit.
Your weekly routine, in a breath. There's no single score, just report cards from different graders. Read the biggest provider's dashboard weekly, and the others beside it. Check the blocklists from outside. Stop at any lamp, and look at that week. And check an old segment before you send to it.
11 · Close · 3:55
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 6, no subscribe ask.
Read every card, every week. No clean can raise a grade. What it checks is the addresses you send to, and that's the part Review My Emails does. Watching reputation for clients? Ask about our partner programme. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... how often should you review inbox placement trends?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-012.002.012-how-to-monitor-domain-reputation.md
00 · One dashboard, once a month (hook)
Almanac ids in this scene: 012.002.012
How to monitor your domain reputation?
three numbered chips, the VO's words: 1 why no single score · 2 which reports to read · 3 what makes you stop. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the folder of report cards. No picture yet.
012.002.012 "Your domain reputation isn't one number sitting in one place." / "not just checking one dashboard once a month." / "A yellow or red flag on SNDS means your Outlook deliverability is likely already suffering."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 012.002.012, 015.001.001
no cut away and no ad break. The cards hold, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 20 words.
012.002.012 "investigate your sending practices for that period" / "a list segment you hadn't mailed in a while". 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · Why there's no single score
Almanac ids in this scene: 012.002.012
Why no single score
chip 1 lights. A folder opens. Three report cards fan out, each in a different format: one with a letter-style band, one with a traffic light, one with a trend line. Gloss card: domain reputation · the part of your reputation that belongs to your domain name.
one folder, three cards, three scales. Reveals: (1) the folder, (2) to (4) one card each, (5) the gloss card.
the folder of report cards. Concept domain-reputation.
012.002.012 "Every major mailbox provider calculates it independently, and each one tells you something slightly different. That's why monitoring reputation means building a small routine across a few sources" / "Monitoring domain reputation means checking several provider-specific dashboards on a recurring schedule, because no single score exists."
T3, the first half of the twist. T10, the report cards, carried to the close. Q5, domain reputation re-glossed with the registry's line.
03 · The biggest provider's card
Almanac ids in this scene: 012.002.012
Which reports to read
chip 2 lights. The first card lifts out of the folder. A four-step scale along its top, High · Medium · Low · Bad, a marker on High. Three small rows fill in under it: spam rate · authentication passes · delivery errors. A calendar strip beside it gets a tick every week. Gloss card: sender dashboard · a free page where a mailbox provider shows senders how it sees their mail.
one scale of four steps, three rows, a tick each week. Reveals: (1) the card, (2) the scale, (3) to (5) one row each, (6) the weekly ticks, (7) the gloss card.
the folder of report cards, the first card.
012.002.012 "Postmaster Tools gives you a domain reputation score (High, Medium, Low, or Bad) along with spam rate, authentication pass rates, and delivery errors. It only shows data for Gmail traffic, so it's not the whole picture" / "Check it weekly."
held tool, never named or shown by its brand (registry google-postmaster). The provider is "the biggest provider". No spam rate figure. Q8, where (the provider's free sender dashboard) and how often (weekly).
04 · Reading that card
Almanac ids in this scene: 012.002.012
Which reports to read
the marker slides from High to Medium, and a small amber tag drops, look now. Then it slides on to Low, and the tag turns coral, emergency. The other cards in the folder stay face down, not covered.
one marker moving down the scale, two tags. Reveals: (1) the step to Medium, (2) the amber tag, (3) the step to Low, (4) the coral tag, (5) the face-down cards.
the folder of report cards, the first card.
012.002.012 "If your domain reputation drops from High to Medium, that's worth investigating immediately. If it hits Low or Bad, treat it as an emergency." / "It only shows data for Gmail traffic".
05 · A second grader, a traffic light
Almanac ids in this scene: 012.002.012
Which reports to read
the second card from the hook lifts out. A row of small server icons, each with its own traffic light, most green, one amber. A complaint line runs under them. The card slides in beside the first, alongside.
one light per server, one amber. Reveals: (1) the card, (2) the server lights, (3) the amber one, (4) the complaint line, (5) it slides beside the first card.
the folder of report cards, the second card. Concept ip-reputation.
012.002.012 "gives you traffic light indicators (green, yellow, red) for your sending IPs and shows complaint rates for Outlook and Hotmail recipients. It's IP-focused rather than domain-focused, so it complements Gmail Postmaster rather than replacing it. A yellow or red flag on SNDS means your Outlook deliverability is likely already suffering."
held tool and provider, never named (registry microsoft-snds). "Sending servers" for IPs in VO, the label on screen says sending IP. "Probably" carries the answer's "likely" (V12).
06 · A third card, and the view from outside
Almanac ids in this scene: 012.002.012
Which reports to read
a third card, a simple trend line, joins the other two. Then the folder zooms out, and outside it a book opens at the gate, the registry's blocklist picture. A box labelled blocklist checker takes send-more.example and returns a short list of lookups, each ticked or flagged.
three cards inside, one book outside. Reveals: (1) the third card, (2) the zoom out, (3) the book, (4) the paste, (5) the results.
the folder of report cards, concept blocklist.
012.002.012 "Yahoo Postmaster shows delivery trends and reputation signals" / "It's less granular than Gmail's tool" / "Worth a look alongside the others." / "show how your domain and IPs look to the blocklist and filtering ecosystem. They don't reflect what Gmail or Outlook actually see internally, but they're useful for catching problems that the postmaster tools might not surface yet, like a new blocklist listing." / "run a quick domain reputation check with our free blocklist checker to see if you're listed anywhere right now."
held services never named. T2 and Q8, where (our free blocklist checker) and how (paste your domain). Q11, "blocklist checker", one name. Demo domain from the library.
07 · What should make you stop
Almanac ids in this scene: 012.002.012
What makes you stop
chip 3 lights. A weekly card with five small lamps in a row, each lighting amber in turn: grade down · spam rate up · green to yellow · authentication failing · new listing.
one weekly card, five lamps. Reveals: (1) the card, (2) to (6) one lamp each.
the folder of report cards, the weekly card.
012.002.012 "A few signals worth tracking week over week:" / "Gmail domain reputation drops from High to Medium or lower" / "SNDS shifts from green to yellow on any of your sending IPs" / "(that means something is misconfigured or broken)" / "A new blocklist listing on Spamhaus or Barracuda".
N6, no spam-rate or pass-rate figure is voiced or shown. Q7, five items drawn as five lamps.
08 · Then look at that week
Almanac ids in this scene: 012.002.012
What makes you stop
the lit lamp points back along a week strip. Three small tags fall onto that week, one per click: new campaign · old segment · volume jump.
one week, three possible causes. Reveals: (1) the week strip, (2) to (4) one tag each.
the folder of report cards, the week strip.
012.002.012 "Any one of these is a reason to pause, investigate your sending practices for that period, and check whether something changed: a new campaign, a list segment you hadn't mailed in a while, or a sudden spike in volume."
T5 and Q8, the action says where (what you sent that week) and how (three questions).
09 · One cause you can check first
Almanac ids in this scene: 005.014.010, 016.008.013
One you can check first
the old segment tag from scene 08 lifts out. Its rows pass under the checking desk lamp before the send. A few turn coral, no such mailbox, and stay behind. The cards in the folder stay still.
one old segment, a few coral rows held back, cards that don't move. Reveals: (1) the segment, (2) the lamp, (3) the coral rows, (4) the still cards.
the checking desk.
016.008.013 "Importing an old list you haven't mailed in months and blasting everyone at once almost always triggers a flood of bounces and complaints." 005.014.010 "revalidate before your next send" / "You're sending to a segment you haven't mailed in over 6 months".
Q2, the pivot grows from this topic's own list of causes. Q3, before the recap. "A while" carries the answer's "in a while", the six months is not voiced.
10 · Recap
What to remember
the folder, the four-step scale, the server lights, the trend card, the book, the five lamps, the week strip, the lamp at the desk. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
11 · Close
Almanac ids in this scene: 016.011.008
Read every card
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 6, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: the partner programme, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
S10, says what a clean does not do (it doesn't raise a grade). Q4, brand twice. S8, the next video is 016.011.008 by its Almanac question, word for word. The partner programme's percentage is left to the end card (R14). Totals: 13 scenes, 587 spoken words, about 3:32 of speech and about 4:18 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V110How often should you review inbox placement trends?
waiting on YTOpen questions for YT
- C66: and C67 for #almanac-to-check.
- Registry: monitoring-cadence proposed.
00 · Half the list, weeks too late (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 the weekly baseline · 2 around a big send · 3 daily, or the same day. Chips 2 and 3 grey. A dial appears beside the calendar, set to its lowest notch.
The dial has three settings. The weekly baseline. The checks around a big send. And when to turn it up to daily, or drop everything the same day.
01 · Brought to you by, woven in · 0:29
On screen: no cut away and no ad break. The calendar holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
A send to a list you haven't mailed in a while is one moment in this rhythm, and Review My Emails checks those addresses first.
02 · The weekly baseline · 0:37
On screen: chip 1 lights. The dial clicks to weekly. One tick lands on each week of the calendar. Beside each tick, three small cards stack: placement · engagement · sender dashboards.
Once a week, pull the core numbers. Your inbox placement rate, the share of accepted mail that reached an inbox, from whatever measures it for you. Your engagement trends, from your email marketing tool. Then the providers' free sender dashboards, for your domain reputation and your spam rate.
03 · Why the dashboards come first · 1:00
On screen: two small timelines under the weekly ticks. The dashboard line dips first, amber, in week two. The email tool's line dips later, in week four. An arrow marks the gap between them, earlier.
Why the dashboards? Their data is often the earliest sign that something is shifting, well before your email tool's reports show a problem. And if a number is sliding, don't wait for it to get worse.
04 · Around a big send · 1:17
On screen: chip 2 lights. The dial clicks to around a send. Three small flags plant on one day of the calendar, one per click: bigger segment · re-engagement · not contacted in a while. A seed test tick lands just before the day, and a second tick lands one to two days after it.
Around a big send, add two checks. Before it, when you're mailing a much bigger segment than usual, running a re-engagement campaign, or writing to a list you haven't contacted in a while, run a quick placement check with your seeds. After it, look again within a day or two, for complaint spikes or bounce jumps.
05 · When something's off, go daily · 1:43
On screen: chip 3 lights. The dial clicks to daily. Ticks land on every day of one week, and the first two are ringed amber, first 48 hours. The slope from the hook flattens after them.
When something's off, turn the dial up to daily. A placement problem, bounces climbing, or complaints moving the wrong way. Watch every day until it settles. The first two days after you notice matter most. That's when you can still correct course, before the damage compounds.
06 · Some things can't wait for tomorrow · 2:05
On screen: the dial swings to its last notch, today. Three coral pins drop onto today's square, one per click: opens fall hard · complaint or bounce spike · blocklist listing. A clock on the square starts.
And some things can't wait for tomorrow. Opens falling hard, with no content reason. A spike in complaints or hard bounces on a send. Your domain turning up on a blocklist. Pull the data that same day and start diagnosing. The longer you wait, the harder the recovery.
07 · No single source is enough · 2:28
On screen: the email tool's card shows a big green delivered. Behind it, the trays from episode 2, half amber. Then three cards line up in a row, email tool · sender dashboards · seed test, and a bracket joins them.
One trap under all of this. Your email tool can report healthy delivery while half your mail sits in spam. So a real rhythm combines three views. Your email tool, the providers' dashboards, and a seed test now and then. No single one is enough.
08 · The moment that's yours to prepare · 2:50
On screen: the not contacted in a while flag from scene 04. Its rows pass under the checking desk lamp the day before the send. A few turn coral, no such mailbox, and stay behind. The send day's flag stays teal.
Most of this rhythm is watching. One moment is preparing. Before you write to a list you haven't contacted in a while, check whether those addresses still exist. An old list, sent to all at once, almost always brings a flood of bounces and complaints.
09 · Recap · 3:10
On screen: the calendar with all its ticks, the dial at each notch in turn, the three flags, the coral pins, the three cards joined. All three chips lit.
The whole rhythm, dial by dial. Weekly, pull placement, engagement and the providers' dashboards. Around a big send, a seed test before and a look a day or two after. Daily when something's off. The same day for a spike or a listing. And never one source alone.
10 · Close · 3:28
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 7, no subscribe ask.
Set the dial to weekly, and turn it up when the calendar tells you to. Reading the trend is your job. Checking the addresses is ours. Already broken? The SOS line from Review My Emails is free. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... what are leading indicators of recovery? For example, reduced bounces, fewer complaints.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-016.011.008-how-often-review-inbox-placement-trends.md
00 · Half the list, weeks too late (hook)
Almanac ids in this scene: 016.011.008
How often should you review inbox placement trends?
three numbered chips, the VO's words: 1 the weekly baseline · 2 around a big send · 3 daily, or the same day. Chips 2 and 3 grey. A dial appears beside the calendar, set to its lowest notch.
a count of three chips, one dial. Reveals: the chips, the dial.
the calendar and the dial. No picture yet.
016.011.008 "Most senders find out something went wrong weeks after it started. Open rates slipped quietly, inbox placement drifted, and nobody noticed until a major campaign landed in spam for half the list."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 016.011.008
no cut away and no ad break. The calendar holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 25 words.
016.011.008 "mailing a list that hasn't been contacted in a while, run a quick placement check before you hit send." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · The weekly baseline
Almanac ids in this scene: 016.011.008
The weekly baseline
chip 1 lights. The dial clicks to weekly. One tick lands on each week of the calendar. Beside each tick, three small cards stack: placement · engagement · sender dashboards.
four ticks a month, three cards each. Reveals: (1) the dial clicks, (2) the ticks, (3) to (5) one card each.
the calendar and the dial. Concept inbox-placement-rate.
016.011.008 "Once a week, pull your core deliverability metrics: inbox placement rate, spam placement rate, and engagement trends from your ESP. If you have access to postmaster tools from Gmail or Outlook, check your domain reputation and spam rate there too."
C67, placement is pulled "from whatever measures it for you" (episode 2: seeds or panels), never "from your email tool". Q5, the rate re-glossed in one line. Held tools not named.
03 · Why the dashboards come first
Almanac ids in this scene: 016.011.008
The weekly baseline
two small timelines under the weekly ticks. The dashboard line dips first, amber, in week two. The email tool's line dips later, in week four. An arrow marks the gap between them, earlier.
two dips, two weeks apart. Reveals: (1) the dashboard dip, (2) the tool's dip, (3) the gap.
the calendar and the dial.
016.011.008 "Postmaster data is often the earliest signal that something is shifting, well before your ESP dashboard shows a problem." / "Don't wait for it to get worse."
"Often" kept (V12). The answer's open-rate percentage is not voiced (N6).
04 · Around a big send
Almanac ids in this scene: 016.011.008
Around a big send
chip 2 lights. The dial clicks to around a send. Three small flags plant on one day of the calendar, one per click: bigger segment · re-engagement · not contacted in a while. A seed test tick lands just before the day, and a second tick lands one to two days after it.
one send day, three flags, a tick before and a tick after. Reveals: (1) the dial, (2) to (4) one flag each, (5) the tick before, (6) the tick after.
the calendar and the dial. Concept re-engagement.
016.011.008 "Any time you're sending to a significantly larger segment than usual, running a reactivation campaign, or mailing a list that hasn't been contacted in a while, run a quick placement check before you hit send. Seed testing is useful here." / "After the send, check again within 24-48 hours to catch any sudden complaint spikes or bounce increases."
Q5, re-engagement campaign is the registry's word for the answer's "reactivation campaign" (P5), its gloss on screen only: a short run of emails asking quiet subscribers to say whether they still want to hear from you. "A day or two" for "24-48 hours", for the ear. Q7, three moments drawn as three flags. Q8, where (your seeds) and when (before, then a day or two after).
05 · When something's off, go daily
Almanac ids in this scene: 016.011.008
Daily, or the same day
chip 3 lights. The dial clicks to daily. Ticks land on every day of one week, and the first two are ringed amber, first 48 hours. The slope from the hook flattens after them.
a tick every day, two ringed. Reveals: (1) the dial, (2) the daily ticks, (3) the two rings, (4) the slope flattens.
the calendar and the dial.
016.011.008 "complaints moving in the wrong direction, switch to daily monitoring until it stabilizes. The first 48 hours after you notice a problem are the most important. That's when you can still course-correct before the damage compounds into a longer reputation recovery."
the answer's "above 2%" bounce line is carried by "bounces climbing" (N6, C16 family).
06 · Some things can't wait for tomorrow
Almanac ids in this scene: 016.011.008
Daily, or the same day
the dial swings to its last notch, today. Three coral pins drop onto today's square, one per click: opens fall hard · complaint or bounce spike · blocklist listing. A clock on the square starts.
one day, three pins, a clock. Reveals: (1) the dial, (2) to (4) one pin each, (5) the clock.
the calendar and the dial. Concept blocklist.
016.011.008 "Open rate drops more than 15-20% from your recent average with no obvious content reason" / "Your domain shows up on a blocklist" / "These aren't \"check it next week\" moments. Pull the data the same day and start diagnosing. The longer you wait, the harder the recovery."
N6 and C66, no trigger figure voiced or shown for opens, complaints or bounces. Q7, three triggers drawn as three pins. Opens here are the answer's own trigger, voiced as a fall, never as a measure of placement (Q12).
07 · No single source is enough
Almanac ids in this scene: 016.011.007, 016.011.008
Daily, or the same day
the email tool's card shows a big green delivered. Behind it, the trays from episode 2, half amber. Then three cards line up in a row, email tool · sender dashboards · seed test, and a bracket joins them.
one green card hiding half in amber, then three cards joined. Reveals: (1) the green card, (2) the amber trays behind, (3) to (5) one card each, (6) the bracket.
the gate and the trays (episode 2, called back), the calendar.
016.011.008 "Your ESP might report healthy delivery rates while half your emails are landing in spam. Building a real monitoring cadence means combining ESP data, postmaster tool data, and occasional seed testing together, not relying on any single source." 016.011.007 "Your ESP doesn't know where the message landed once it was accepted."
T3, the twist. The "So" sits mid-scene, not as an opener.
08 · The moment that's yours to prepare
Almanac ids in this scene: 005.003.002, 016.008.013, 016.011.008
The moment you can prepare
the not contacted in a while flag from scene 04. Its rows pass under the checking desk lamp the day before the send. A few turn coral, no such mailbox, and stay behind. The send day's flag stays teal.
one old list, a few coral rows held back. Reveals: (1) the flag, (2) the lamp, (3) the coral rows, (4) the teal flag.
the checking desk.
016.011.008 "mailing a list that hasn't been contacted in a while". 016.008.013 "Importing an old list you haven't mailed in months and blasting everyone at once almost always triggers a flood of bounces and complaints." 005.003.002 "Validation catches nonexistent mailboxes" / "before send".
Q2, the pivot grows from this topic's own big-send moment. Q3, before the recap. Only the bounce side is claimed as preventable by a check.
09 · Recap
What to remember
the calendar with all its ticks, the dial at each notch in turn, the three flags, the coral pins, the three cards joined. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
10 · Close
Almanac ids in this scene: 016.011.008, 018.013.002
Turn the dial
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, episode 7, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: reviewmyemails.com/sos, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
016.011.008 "if something's already broken, the SOS hotline is free and we actually pick up."
S10, says what a clean does not do (it doesn't read a trend). Q1, not the stock "A clean won't" line. Q4, brand twice. S8, the next video is 018.013.002 by its Almanac question, word for word, with "e.g." read as "for example". Totals: 13 scenes, 529 spoken words, about 3:11 of speech and about 3:50 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V111What are leading indicators of recovery? (e.g., reduced bounces, fewer complaints)
waiting on YTOpen questions for YT
- Series end: this closes on V093 (016.011.006), as V105 does today.
- Registry: leading-indicator and lagging-indicator proposed.
00 · The score that won't move (hook) · 0:00
On screen: three numbered chips, the VO's words: 1 what a leading sign is · 2 the four to watch · 3 read them honestly. Chips 2 and 3 grey.
Three things, one at a time. What a leading sign is. The four to watch for. And how to read them without fooling yourself.
01 · Brought to you by, woven in · 0:28
On screen: no cut away and no ad break. The score card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
Bounces are usually the first sign to shift, and Review My Emails checks the addresses behind them before you send.
02 · The bleeding stops before the wound heals · 0:36
On screen: chip 1 lights. A dressing on a plain shape. Under it, a small coral spot stops spreading, bleeding stopped, tagged leading. Beside it, a greyed tag waits, healed, marked lagging, with the flat score card from the hook hanging off it. Gloss card: leading indicator · an early signal that recovery is working, before the scores move.
A leading indicator is an early signal that things are moving the right way, days or weeks before your reputation scores budge. Leading signs tell you the bleeding has stopped. The lagging ones, your scores, tell you the wound has healed. You'll see the first kind first.
03 · Sign one: fewer rejections, clearer words · 0:58
On screen: chip 2 lights. A board with four small charts, the first one lit. Weekly bars of coral rejections, high, then shorter, then shorter. Beside it, one bounce message rewrites itself: message refused becomes a specific reason line, then fades out.
Sign one, and usually the first to shift. Your policy bounces, the provider refusing your mail, start falling week over week. You're not looking for zero yet. You're looking for the trend to turn. And read the wording. A vague refusal that turns into a specific reason, before it disappears, often means the filters are loosening.
04 · Sign two: fewer complaints, and the good kind of goodbye · 1:24
On screen: the second chart lights. Two lines on it. The complaint line, coral, falls. The unsubscribe line, teal, holds flat and then lifts slightly. A small door icon opens by the teal line, proper exit.
Sign two. Your complaints fall, week over week. It's one of the clearest signs your list is getting healthier. And watch what unsubscribes do. As spam reports drop, unsubscribes often hold flat, or even rise a little. That's good news. Someone leaving through the proper door beats someone hitting the spam button.
05 · Sign three: fewer deferrals, a faster queue · 1:50
On screen: the third chart lights. A queue of amber envelopes, each stamped not now, stretches out. Then it shortens, and a small clock beside it drops from 4 hours to under 30 minutes. Gloss card: deferral · a receiving server saying "not right now" instead of "never".
Sign three. Fewer deferrals, the provider saying not right now, instead of never. In a dip they pile up, mail sits in your sending queue, and delivery crawls. As things recover, the queue clears faster. Mail that took four hours to deliver lands in under thirty minutes.
06 · Sign four: nothing new going wrong · 2:15
On screen: the fourth chart lights. A line of small red flags appearing week after week, then a week with none, then another. The line goes flat, plateau, and a teal tick lands on it, progress. A box labelled blocklist checker returns a short list, all ticked.
Sign four is the quietest. Stability. While reputation is sliding, new blocklist entries and new rejections keep turning up. Recovery looks like that stopping. No new blocks. No new providers flagging you. A boring plateau is progress. Our free blocklist checker shows whether you're still listed anywhere.
07 · Read the trend, not the day · 2:40
On screen: chip 3 lights. The first chart from scene 03, stretched across four weeks. It dips, blips up in week three, and carries on down. A bracket spans the four weeks, the trend. A single-day zoom beside it is struck out, not this.
How do you read them honestly? They don't move in a straight line. Bounces can drop in week two, then tick up in week three as you widen your sends again. That's normal. Watch the overall trend across two to four weeks, not day by day. The pattern matters more than the speed.
08 · Each week a little better · 3:04
On screen: four weekly squares, each a shade more teal than the last, a small tick on each, on track. The greyed healed tag from scene 02 starts to fill with colour.
The test is simple. If each week is a small improvement on the last, you're on track. Keep sending the way you've been sending, and let the lagging scores catch up.
09 · Where recovery slips · 3:20
On screen: the four-week chart. A wider send arrow joins in week three. A coral spike threatens on the chart, restart. Then the paused rows pass under the checking desk lamp first. A few turn coral, no such mailbox, and stay behind. The spike never comes.
Where does recovery slip? When you widen your sends again. A spike in complaints or hard bounces mid-recovery restarts the trust-building. Bring your most engaged people back first. And run the paused addresses through a check before they rejoin.
10 · Recap · 3:40
On screen: the dressing, the board with all four charts lit, the four-week bracket, the lamp at the desk. All three chips lit.
Is it working, then? Leading signs mean the bleeding has stopped, before the scores say it's healed. Fewer rejections, with clearer wording. Fewer complaints, even if unsubscribes rise. A faster queue. Nothing new going wrong. Read the trend over weeks, and check the paused addresses before they come back.
11 · Close · 3:58
On screen: the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V093, no subscribe ask.
Watch the early signs, and don't undo the work before the scores catch up. Keeping dead addresses out of your sends is what a clean does. The healing takes its own time. That's RME Clean, from Review My Emails. Clean your first 1,000 free at reviewmyemails dot com slash get started. Next... how can inbox metrics predict reputation decay?
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-018.013.002-leading-indicators-of-recovery.md
00 · The score that won't move (hook)
Almanac ids in this scene: 018.013.002
What are leading indicators of recovery?
three numbered chips, the VO's words: 1 what a leading sign is · 2 the four to watch · 3 read them honestly. Chips 2 and 3 grey.
a count of three chips. Reveals: the chips.
the score card. No picture yet.
018.013.002 "You've cleaned your list, fixed your authentication, and pulled back on send volume. Now what? How do you know any of it is actually working?" / "often days or weeks before your reputation scores officially budge."
H4, H5 (S2).
01 · Brought to you by, woven in
Almanac ids in this scene: 015.001.001, 018.013.002
no cut away and no ad break. The score card holds, and a small Review My Emails logo sits in the corner while the line plays. No sting, no jingle.
R1, R13. Q4: one sentence, 20 words.
018.013.002 "This is usually the first thing to shift." 015.001.001 "we'll flag what's safe to send to and what to suppress".
02 · The bleeding stops before the wound heals
Almanac ids in this scene: 018.013.002, 018.013.003
What a leading sign is
chip 1 lights. A dressing on a plain shape. Under it, a small coral spot stops spreading, bleeding stopped, tagged leading. Beside it, a greyed tag waits, healed, marked lagging, with the flat score card from the hook hanging off it. Gloss card: leading indicator · an early signal that recovery is working, before the scores move.
one spot that stops growing, one tag still grey. Reveals: (1) the dressing, (2) the spot stops, (3) the leading tag, (4) the grey lagging tag, (5) the score card, (6) the gloss card.
the dressing. No picture yet.
018.013.002 "These are the early signals that show things are moving in the right direction, often days or weeks before your reputation scores officially budge." / "Think of it this way: leading indicators tell you the bleeding has stopped. Lagging indicators tell you the wound has healed." / "you'll see leading signals first." 018.013.003 "They confirm recovery only after it has already happened".
T10, the Almanac's own simile, carried to the close. T11, a plain shape, no body drawn.
03 · Sign one: fewer rejections, clearer words
Almanac ids in this scene: 018.013.002
The four to watch
chip 2 lights. A board with four small charts, the first one lit. Weekly bars of coral rejections, high, then shorter, then shorter. Beside it, one bounce message rewrites itself: message refused becomes a specific reason line, then fades out.
weekly bars that shrink, one message that sharpens then goes. Reveals: (1) the board, (2) the bars, (3) they shrink, (4) the vague message, (5) it sharpens, (6) it fades.
the board of four charts. Concept block-bounce.
018.013.002 "This is usually the first thing to shift. If you were seeing a wave of policy bounces (5xx errors telling you the mailbox provider is rejecting your mail), watch for that number to fall. You're not looking for zero yet. You're looking for the trend to reverse." / "Vague, generic rejections like \"message refused\" sometimes soften into more specific ones before disappearing entirely. That shift in language often means the filters are loosening up."
Q8, where (your bounce messages, week over week) and how (the count, and the wording). "Often" kept (V12). "Policy bounces" re-glossed inline from Bounces part 3 (Q5), no code number voiced.
04 · Sign two: fewer complaints, and the good kind of goodbye
Almanac ids in this scene: 018.013.002
The four to watch
the second chart lights. Two lines on it. The complaint line, coral, falls. The unsubscribe line, teal, holds flat and then lifts slightly. A small door icon opens by the teal line, proper exit.
two lines crossing paths, one down, one flat or up. Reveals: (1) the chart, (2) the complaint line falls, (3) the unsubscribe line holds, (4) it lifts, (5) the door.
the board of four charts. Concept complaint-rate.
018.013.002 "A falling complaint rate is one of the clearest signs your list quality is improving." / "as spam reports go down, unsubscribes often stay flat or even rise slightly. That's actually good news. People opting out through the proper channel is far better than hitting the spam button."
T3, the twist. "Often" kept (V12). V073 owns the feedback loop, not named here.
05 · Sign three: fewer deferrals, a faster queue
Almanac ids in this scene: 018.013.002
The four to watch
the third chart lights. A queue of amber envelopes, each stamped not now, stretches out. Then it shortens, and a small clock beside it drops from 4 hours to under 30 minutes. Gloss card: deferral · a receiving server saying "not right now" instead of "never".
one queue that shortens, one clock that drops. Reveals: (1) the long queue, (2) the stamps, (3) it shortens, (4) the clock drops, (5) the gloss card.
the board of four charts. Concept deferred-message, throttling.
018.013.002 "Deferrals are temporary rejections (4xx errors) where the receiving server says \"not right now\" rather than \"never.\" During a reputation dip, these pile up. Emails sit in queues. Delivery slows to a crawl. As things recover, deferrals drop and your queues clear faster. If emails that used to take four hours to deliver are suddenly landing in under thirty minutes, that's a meaningful signal."
Q8, where (how long mail sits in your sending queue). The four hours and thirty minutes are the answer's own example, shown once (N6). No code number voiced.
06 · Sign four: nothing new going wrong
Almanac ids in this scene: 018.013.002
The four to watch
the fourth chart lights. A line of small red flags appearing week after week, then a week with none, then another. The line goes flat, plateau, and a teal tick lands on it, progress. A box labelled blocklist checker returns a short list, all ticked.
flags that stop appearing, a flat line. Reveals: (1) the flags, (2) the empty weeks, (3) the flat line, (4) the tick, (5) the checker.
the board of four charts. Concept blocklist.
018.013.002 "When reputation is tanking, new blocklist entries or new domain-level rejections keep appearing. Recovery looks like things stopping to get worse. No new blocks. No new ISPs flagging you." / "That plateau, boring as it sounds, is actually progress." / "our free blocklist checker can tell you whether your domain or IP is still flagged anywhere."
Q11, "blocklist checker", one name. T7, the answer's own tool pointer.
07 · Read the trend, not the day
Almanac ids in this scene: 018.013.002
Read them honestly
chip 3 lights. The first chart from scene 03, stretched across four weeks. It dips, blips up in week three, and carries on down. A bracket spans the four weeks, the trend. A single-day zoom beside it is struck out, not this.
four weeks, one blip, one bracket. Reveals: (1) the four weeks, (2) the dip, (3) the blip, (4) the bracket, (5) the struck-out day.
the board of four charts.
018.013.002 "You might see bounces drop in week two, then tick up slightly in week three as you expand your sends again. That's normal. Watch the overall trend across two to four weeks, not day-by-day noise." / "The pattern matters more than the speed."
C33, no recovery time voiced. "Two to four weeks" is the answer's window for reading a trend, voiced as that only.
08 · Each week a little better
Almanac ids in this scene: 018.013.002, 018.013.003
Read them honestly
four weekly squares, each a shade more teal than the last, a small tick on each, on track. The greyed healed tag from scene 02 starts to fill with colour.
four weeks, each a step better. Reveals: (1) to (4) one square each, (5) the tag fills.
the dressing, the weekly squares.
018.013.002 "If each week is a small improvement on the last, you're on track." 018.013.003 "They confirm recovery only after it has already happened, often weeks later."
"Keep sending the way you've been sending" carries the answer's framing of recovery as the work already done in the hook. No timeline voiced (C33).
09 · Where recovery slips
Almanac ids in this scene: 005.003.002, 016.009.010
Where recovery slips
the four-week chart. A wider send arrow joins in week three. A coral spike threatens on the chart, restart. Then the paused rows pass under the checking desk lamp first. A few turn coral, no such mailbox, and stay behind. The spike never comes.
one wider send, one spike that doesn't happen. Reveals: (1) the wider send, (2) the threatened spike, (3) the lamp, (4) the coral rows held back, (5) the flat chart.
the checking desk.
016.009.010 "Any spike in complaints or hard bounces mid-recovery restarts the trust-building process." / "Send to your most engaged subscribers first." 005.003.002 "Validation catches nonexistent mailboxes" / "before send".
Q2, the pivot grows from this topic (the week-three wobble). Q3, before the recap. Only the bounce side is claimed as preventable by a check. 016.009.010's timelines are not voiced (C33).
10 · Recap
What to remember
the dressing, the board with all four charts lit, the four-week bracket, the lamp at the desk. All three chips lit.
callbacks only.
callbacks only (S5). Q3: ends on the action.
11 · Close
Almanac ids in this scene: 016.011.006
Let it heal
the dot grid pours into the three verdict pots. CTA in teal: Clean your first 1,000 free, reviewmyemails.com/get-started in mono. End screen: the next video, V093, no subscribe ask.
the logo, trust beats tactics, reviewmyemails.com/get-started, and one extra: RME Clean, named in the VO above.
the dot grid into three pots, no counts.
concept list-cleaning.
S10, says what a clean does not do (it doesn't speed the healing). Q4, brand twice. S8, the next video is 016.011.006 (V093, on main) by its Almanac question, word for word. Totals: 13 scenes, 564 spoken words, about 3:24 of speech and about 4:18 with scene breaks and reveals. Every scene is 20 to 70 words (S2). Over two minutes, so no Short cut note (R12).
V901What happens when you press Send
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the earlier Almanac scripts in this series.
- The launch wording on the end card. RME-16 (the launch-messaging framework) is still open per 00-inbox/decisions/2026-09-21-story-1-launch-messaging.md, and 00-inbox/decisions/2026-09-22-app-live-before-webinar.md notes /get-started...
- Keep both invented addresses, or one throughout. The script uses a working address for steps 1 through 6 and a second, dead one for the rewind in shot 7, so the failure case reads as clearly separate from the success case.
- Keep or cut the envelope beat (shot 3). It is the most surprising line in the answer and it is the one beat that ties directly to the header-cheat-sheet lead magnet (see the content review), but it is also the most technical beat in the...
01 · The hook · 0:00
On screen: paper. A compose window, mono, small: To: hello@lighthouse-letterpress.example. A cursor lands on a button labelled Send and clicks it. Large Lora headline settles under it: "One click. Five steps you never see."
You hit Send. It isn't instant. Five things happen first.
02 · Step one, authenticate · 0:05
On screen: mono tag STEP 1 top left. A small padlock icon. Label: your email app then an arrow to submission server. Sub-line: checks your login first.
Step one, your email app hands the message to a submission server, and it checks your login before anything moves.
03 · Step two, the envelope · 0:11
On screen: the compose window's message slides into a second, larger envelope shape labelled SMTP envelope, mono. Two small tags appear, one sealed inside the envelope reading Return-Path, one still visible on the letter reading From.
Step two, it gets sealed in an envelope you never see, separate from the From line you do, which is why Return-Path and From don't always match.
04 · Step three, DNS · 0:19
On screen: mono tag STEP 3. A small DNS query line types out: MX record for lighthouse-letterpress.example?, then resolves to a server icon with a green check.
Step three, your server asks DNS which server accepts mail for that domain, using its MX record.
05 · Step four, the handoff · 0:26
On screen: two server icons connect with a line. Three small badges light up along it in order: SPF, DKIM, reputation.
Step four, your server connects to theirs, and that handoff is where SPF, DKIM and your sending reputation all get checked before anything is accepted.
06 · Step five, retrieval · 0:33
On screen: mono tag STEP 5. An inbox icon and a spam-folder icon sit side by side. Small line beneath both: accepted is not the same as delivered.
Step five, it waits there until they open their mail, and being accepted still isn't the same as landing in the inbox.
07 · The rewind · 0:40
On screen: the whole sequence rewinds visually back to the step 3 frame, but the address swaps to orders@doesnotresolve.test in suppress red #ED5746. The DNS query line types out and returns nothing. A red X lands. Steps 4 and 5 grey out, unreachable, off to the side.
All five steps assume the address you typed is real. Send that click to a dead address instead, and it never gets past step three, so four and five never get a turn.
08 · End card · 0:47
On screen: the five step tags collapse into one line, mono: 5 steps. 1 dead address ends it at step 3. Under it, small logo lockup, never a cartoon octopus, then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
So before you hit Send again, clean the list, so a dead address doesn't waste the other four steps.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-001.001.007-press-send.md
01 · The hook
paper. A compose window, mono, small: To: hello@lighthouse-letterpress.example. A cursor lands on a button labelled Send and clicks it. Large Lora headline settles under it: "One click. Five steps you never see."
no music yet, room tone and a single soft click sound on the button press.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). The click itself is the most universal gesture there is, everyone has done it an hour ago.
the address is invented. Never a real one, never a client's.
02 · Step one, authenticate
Almanac ids in this scene: 001.001.007
mono tag STEP 1 top left. A small padlock icon. Label: your email app then an arrow to submission server. Sub-line: checks your login first.
the pulse of a light bed starts, one beat per step from here on.
Almanac 001.001.007: "Your email client hands the message to a submission server (usually running on port 587). This server checks your login credentials. If you're not authenticated, the message doesn't go anywhere."
"submission server" is explained in the sub-line and the VO's own clause ("checks your login"), not left as bare jargon, per the pre-screen instruction against deep SMTP terms on a marketing surface.
starting on a login check, not a send, tells the viewer this was never as simple as the button made it look.
03 · Step two, the envelope
Almanac ids in this scene: 001.001.007
the compose window's message slides into a second, larger envelope shape labelled SMTP envelope, mono. Two small tags appear, one sealed inside the envelope reading Return-Path, one still visible on the letter reading From.
a soft paper-fold sound as the envelope closes.
Almanac 001.001.007: "The submission server wraps your message in an SMTP envelope. Think of this like putting a letter in a postal envelope. The SMTP envelope contains routing info... separate from the message headers your recipient will see. This is why reply-to addresses and return-path addresses can be different from the visible 'From' line."
the most surprising, most shareable fact in the answer, and it is the one beat that earns its own lead magnet (see the content review beside this script).
04 · Step three, DNS
Almanac ids in this scene: 001.001.007
mono tag STEP 3. A small DNS query line types out: MX record for lighthouse-letterpress.example?, then resolves to a server icon with a green check.
a short data-tick sound on the resolve.
Almanac 001.001.007: "Your server needs to know where to deliver the message. It queries DNS for the recipient domain's MX record, which points to the receiving mail server."
this is the checkpoint the closing shot rewinds to, so it has to read clean and successful here first, before the video shows what it looks like when it fails.
05 · Step four, the handoff
Almanac ids in this scene: 001.001.007
two server icons connect with a line. Three small badges light up along it in order: SPF, DKIM, reputation.
three matching ticks, one per badge.
Almanac 001.001.007: "Your sending server opens an SMTP connection to the recipient's mail server and transmits the message. The receiving server might accept it right away, or it might queue it for spam filtering first. This is where SPF, DKIM, and sender reputation checks happen."
"queue it for spam filtering" in the source stays a generic mention, no spam trap language, no complaint-rate figure, none appear in the source answer either. "Before anything is accepted" is as far as the claim goes, no inbox-placement promise.
this is where the checks people already know (SPF, DKIM) turn out to be one hop in five, not the whole story.
06 · Step five, retrieval
Almanac ids in this scene: 001.001.007
mono tag STEP 5. An inbox icon and a spam-folder icon sit side by side. Small line beneath both: accepted is not the same as delivered.
the bed thins to a single held note.
Almanac 001.001.007: "The email sits on the receiving server until the recipient's email client pulls it down (via IMAP or POP3) or they log in to webmail... just because the recipient's server accepted your email doesn't mean it landed in the inbox."
stated as a fact about the gap between acceptance and placement, never as a guarantee either way. No inbox-placement promise.
closes the honest structure of the answer, five steps, with the one caveat the Almanac itself adds at the end.
07 · The rewind
Almanac ids in this scene: 001.001.007
the whole sequence rewinds visually back to the step 3 frame, but the address swaps to orders@doesnotresolve.test in suppress red #ED5746. The DNS query line types out and returns nothing. A red X lands. Steps 4 and 5 grey out, unreachable, off to the side.
the bed drops out entirely, one low tone under the X.
Almanac 001.001.007: "If there's no MX record (or if DNS fails), the email bounces immediately."
the address is invented and uses the .test reserved domain (RFC 2606), so it cannot resolve to anyone's real address. No claim that a bounce here is a spam-trap hit or a complaint, it is a domain that never had a mail server behind it, which is the source's own example.
this is the RME hook the angle note asks for, landed on the answer's own fact rather than invented, and it carries the longest sentence in the script on purpose, paced to the moment the whole machine stops cold.
08 · End card
the five step tags collapse into one line, mono: 5 steps. 1 dead address ends it at step 3. Under it, small logo lockup, never a cartoon octopus, then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
music returns, warmer, under "clean the list."
the claim stays scoped to catching a dead or non-existent address before it wastes a send. Nothing here implies list cleaning fixes SPF, DKIM, MX or blocklist problems, those are steps 4 and the domain's own DNS, a different layer entirely.
ends on a decision, not a number (voice guide section 6). The number (five steps) was already spent doing its job in shot 7.
V902What email deliverability actually means
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first two Almanac scripts.
- The launch wording on the end card. Same open item the spam-placement script flagged: RME-16 is defining which posts read as waitlist, coming-soon, or live.
- The CTA destination. Specced as reviewmyemails.com/get-started, matching both earlier scripts in this series rather than the platform.reviewmyemails.com subdomain CLAUDE.md rule 5 names, because that subdomain has no DNS record anywhere...
- Whether the free Blocklist Checker is the right single tool to spotlight in the anchor video. It is the Almanac's own recommended first move, but this script only checks one of the four signals it just taught (authentication and...
01 · The hook · 0:00
On screen: paper. Top, mono, invented address: newsletter@seaglass-ceramics.example. Middle, Lora, ink, large: "SENT." with a small teal checkmark beside it. Below, dashed and hollow: "Delivered?"
Your email marketing tool says sent. That is a different question from delivered.
02 · The gap · 0:06
On screen: the checkmark dims. Three paths branch off the address, mono: the inbox solid and teal, spam dashed, gone dashed and fading to nothing.
An email can leave your server, clear the queue, and still land in spam, in Promotions, or nowhere at all. Deliverability is the whole trip, not the send.
03 · The four signals · 0:14
On screen: four rows build one at a time under the address, each a mono label with a short gloss in Lora: - authentication: did this come from who it claims - reputation: a history of sending wanted mail - filtering: does the content or structure look spammy - engagement: do people open you, or ignore and delete
Mailbox providers check four things before they decide where you land. Authentication. Does your setup prove who you are. Reputation. Do you have a history of sending wanted mail. Filtering. Does your content or structure look spammy. Engagement. Do people actually open you, or ignore and delete.
04 · The quiet failure · 0:30
On screen: the engagement row dims to a hollow outline. No bounce icon anywhere, it is crossed out. The envelope from shot 1 fades slowly into a spam-folder icon.
If one of those four is off, you will not get a bounce. You will get quietly routed to spam instead, and it often stays invisible until it is serious, until the open rate that used to hold steady starts sliding, or a campaign that always performed well suddenly does not.
05 · The decision · 0:38
On screen: one card, mono, teal accent: check now over free blocklist checker.
Start there. Check your own blocklist status free, before you guess at anything else.
06 · End card · 0:44
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.001.001-what-is-deliverability.md
01 · The hook
paper. Top, mono, invented address: newsletter@seaglass-ceramics.example. Middle, Lora, ink, large: "SENT." with a small teal checkmark beside it. Below, dashed and hollow: "Delivered?"
no music yet. Room tone only.
"Email deliverability is whether your emails actually land in the inbox. Not just whether they were sent, not whether the server accepted them."
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A checkmark that turns out to mean less than people think is the itch nobody scrolls past.
the address is invented. Never a real one, never a client's.
02 · The gap
the checkmark dims. Three paths branch off the address, mono: the inbox solid and teal, spam dashed, gone dashed and fading to nothing.
a low pulse starts under the three branching paths.
"The distinction matters because sending and delivering are different things. An email can leave your server, clear your ESP's queue, and still end up in spam, in the Promotions tab, or simply disappear. Deliverability is the full journey: from your sending infrastructure through mailbox provider filtering to inbox placement."
the Almanac's own wording says "ESP's queue." Spoken as "the queue" instead, matching the house rule to say email marketing tool, never ESP, on anything a customer hears.
this is where the reframe lands, sent and delivered split into visibly different outcomes before the video explains why.
03 · The four signals
four rows build one at a time under the address, each a mono label with a short gloss in Lora: - authentication: did this come from who it claims - reputation: a history of sending wanted mail - filtering: does the content or structure look spammy - engagement: do people open you, or ignore and delete
music settles into a steady bed as the four rows land.
"Four things mailbox providers check when deciding where your email goes: Authentication: did this actually come from who it claims? Reputation: does this sender have a history of sending wanted email? Filtering: does the content or structure look spammy? Engagement: do recipients interact with email from this sender, or ignore and delete it?"
naming all four plainly is the actual content of the video. It is the frame the rest of the series will keep pointing back to, so it has to be exact and unhurried.
04 · The quiet failure
the engagement row dims to a hollow outline. No bounce icon anywhere, it is crossed out. The envelope from shot 1 fades slowly into a spam-folder icon.
the bed thins to one held note as the envelope fades into the spam icon.
"If any of those are off, you won't necessarily get a bounce. You'll get quietly routed to spam." and "Deliverability problems are often invisible until they're serious. If your open rates have been declining and you haven't changed your content, or a campaign that usually performs well suddenly didn't, inbox placement is worth investigating."
this is the actual stakes of the definition. No error message means no one goes looking, so the video has to say that plainly before it hands over anything to check.
05 · The decision
one card, mono, teal accent: check now over free blocklist checker.
a single soft note as the card lands.
"The free Blocklist Checker is a quick starting point."
this checks the sender's own domain and IP standing, it is not a claim that any recipient should be suppressed for being on a blocklist. DNSBL measures sending reputation, not a reason to drop an address. No inbox-placement promise, this is a starting point, not a fix.
ends on a decision, not a number (voice guide section 6). It is the Almanac's own recommended first move, in the Almanac's own words.
06 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording. The destination is /get-started, matching the first two scripts in this series. See "Needs YT's yes" on the launch wording.
V903The four factors that decide deliverability
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics.
- Launch-state wording on the end card, pending RME-16.
- Keep the crack-and-tilt visual in shot 4, or a simpler flip.
01 · The hook · 0:00
On screen: paper. One line, Lora, big: "You fixed your SPF. You are still in spam." Below, mono, small: and you cannot work out why.
You set up authentication, and you are still landing in spam. Here is the part nobody told you.
02 · The reframe · 0:05
On screen: the word "SPAM" at the top. Four empty pillars build under it, mono labels: authentication, reputation, engagement, list quality.
Deliverability is not one thing. It is four things holding each other up. Authentication. Reputation. Engagement. And the quality of your list.
03 · What each pillar is · 0:13
On screen: each pillar fills as the VO names it, with a one-line gloss in mono beside it. - authentication: proves the mail really came from you - reputation: your sending history, at the domain and the IP - engagement: do people open you, or ignore and delete - list quality: are you only sending to people who signed up and still want it
Authentication proves the mail really came from you. Reputation is your sending history. Engagement is whether people open you or ignore you. And list quality is whether you are only sending to people who asked for it.
04 · The turn · 0:32
On screen: three pillars glow, one, engagement, cracks. The whole structure tilts and the top flips back to "SPAM" in #ED5746.
Here is the catch. Perfect authentication does not save you if the other three are weak. One cracked pillar tilts the whole thing, and you are back in spam.
05 · The decision · 0:40
On screen: the four pillars clear to two, side by side: authentication over "check it free" and list quality over "clean it". A thin teal rule between them.
Two of the four are yours to fix today. Check your authentication with our free tools, and clean your list so the dead weight stops dragging your reputation down.
06 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.001.002-main-deliverability-factors.md
01 · The hook
paper. One line, Lora, big: "You fixed your SPF. You are still in spam." Below, mono, small: and you cannot work out why.
room tone, no music yet.
it names the exact trap, believing deliverability is one fixable thing, so the correction lands.
02 · The reframe
Almanac ids in this scene: 002.001.002
the word "SPAM" at the top. Four empty pillars build under it, mono labels: authentication, reputation, engagement, list quality.
Almanac 002.001.002: "email deliverability isn't one thing. It's four pillars working together, and if one breaks, the whole structure wobbles."
03 · What each pillar is
Almanac ids in this scene: 002.001.002
each pillar fills as the VO names it, with a one-line gloss in mono beside it. - authentication: proves the mail really came from you - reputation: your sending history, at the domain and the IP - engagement: do people open you, or ignore and delete - list quality: are you only sending to people who signed up and still want it
Almanac 002.001.002, its four named pillars: "Authentication proves you're really you... Reputation is your sending history score... Engagement tells mailbox providers whether their users actually want your mail... List hygiene means you're only sending to people who signed up."
the Almanac's list-quality line also names spam traps and a complaint-rate cap. Both are cut, this is a marketing surface. List quality is spoken as permission and still-wanting-it only.
04 · The turn
Almanac ids in this scene: 002.001.002
three pillars glow, one, engagement, cracks. The whole structure tilts and the top flips back to "SPAM" in #ED5746.
Almanac 002.001.002: "these four pillars don't work in isolation. You can have perfect authentication and terrible engagement, and you'll still land in spam."
05 · The decision
Almanac ids in this scene: 002.001.002
the four pillars clear to two, side by side: authentication over "check it free" and list quality over "clean it". A thin teal rule between them.
Almanac 002.001.002: "check authentication first (it's the easiest to fix), then look at your list hygiene... authentication and hygiene are under your control right now."
the two checks stay two separate sentences for two separate pillars. Cleaning a list is never implied to fix authentication. No inbox-placement guarantee.
06 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). The in-video promo is the generic call only, the specific magnet or tool link lives in the editable description, never the video.
V904The same email, her inbox, his spam
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the split-screen device throughout, or only for the hook and reveal.
01 · The hook · 0:00
On screen: paper split in two. Left, an inbox with your email at the top. Right, a spam folder with the same email. One line, Lora: "Same email. Her inbox. His spam."
This is the exact same email, from you, on the same day. It landed in her inbox and his spam. Here is how that happens.
02 · The layers · 0:06
On screen: the email passes through a stack of gates, each a mono label lighting as the VO names it: authentication, reputation, engagement, content.
Providers decide in layers. First, does your authentication check out. Then, what is your sending reputation. Then, and this is the big one, how do people actually treat your mail. Content is near the end, not the start.
03 · The reveal · 0:20
On screen: back to the split screen. Under "her", a green trail of opens and clicks. Under "his", a grey trail of deletes.
Here is the part that surprises people. Engagement is measured for each person, not for the whole send. She opens you, so you keep landing in her inbox. He deletes you unread, so the filter starts hiding you from him. Same sender, same email, two different homes.
04 · The turn · 0:36
On screen: a big grey block of "never open" addresses drags the whole inbox meter down.
And it gets worse. Every email you send to someone who never opens is you training the filter that your mail is not wanted. Their silence quietly drags down where you land for everyone else.
05 · The decision · 0:42
On screen: the grey block is lifted off, and the inbox meter rises. Text: "stop sending to the silent".
So stop paying to reach people who will never open you. Clean the silent weight off your list, and your good subscribers stop paying for it.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.001.003-how-mailbox-providers-decide.md
01 · The hook
paper split in two. Left, an inbox with your email at the top. Right, a spam folder with the same email. One line, Lora: "Same email. Her inbox. His spam."
room tone.
the split frame is the whole idea, and it works muted.
02 · The layers
Almanac ids in this scene: 002.001.003
the email passes through a stack of gates, each a mono label lighting as the VO names it: authentication, reputation, engagement, content.
Almanac 002.001.003: "The filtering decisions happen in layers... Layer 1 Authentication... Layer 2 Sender Reputation... Layer 3 Engagement Behavior... this is the biggest lever... Content filtering... is now just one input among many."
the Almanac's user-feedback layer names complaint-rate figures. Cut, marketing surface.
03 · The reveal
Almanac ids in this scene: 002.001.003
back to the split screen. Under "her", a green trail of opens and clicks. Under "his", a grey trail of deletes.
Almanac 002.001.003: "Engagement is measured differently for each recipient... future emails to subscriber A still land in the inbox while emails to subscriber B might get filtered to spam. Same sender, same campaign, different placement."
the whole point, so it carries the longest sentence.
04 · The turn
Almanac ids in this scene: 002.001.003
a big grey block of "never open" addresses drags the whole inbox meter down.
Almanac 002.001.003: "sending to unengaged subscribers hurts you. You're training the filters that your emails aren't wanted... their silence tells the algorithm to deprioritize your future messages."
05 · The decision
Almanac ids in this scene: 002.001.003
the grey block is lifted off, and the inbox meter rises. Text: "stop sending to the silent".
Almanac 002.001.003: "that's why sending to unengaged subscribers hurts you."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V905Why some emails go to spam
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first Almanac script.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- The CTA destination. Specced as reviewmyemails.com/get-started.
- Keep or cut the content-myth beat (shot 5). It is the most shareable line in the answer and it is faithfully grounded, but it adds about seven seconds and it is the one beat a careless watcher could hear as "content never matters." It...
01 · The hook · 0:00
On screen: paper. One address alone, mono, large: dispatch@driftwood-goods.example. Above it a single word in Lora, ink, big: "SPAM." Below, dashed and hollow, the question: "It did everything right."
This email passed every check you know how to run. It still went to spam.
02 · The myth · 0:05
On screen: three guesses type out and cross through, one at a time, mono: a spammy word, the link, no SPF record. Each gets a thin strike.
So you start hunting for the one thing that did it. A word. A link. A record you forgot. You will not find it, because there is no one thing.
03 · The five signals · 0:12
On screen: the address moves up. Five gauges build under it, one per line as the VO names it, each a mono label with a small dial. All five settle reading well. - sender reputation with your domain and IP history - engagement with do people open or ignore - authentication with SPF, DKIM, DMARC - list quality with who is actually on the list - sending pattern with steady or spiky
Mailbox providers score you across five signals. Your sending reputation. Whether people open you or ignore you. Whether your authentication checks out. What your list is made of. And whether your sending stays steady or spikes.
04 · The turn · 0:26
On screen: four dials hold and glow green. One, engagement, drops into red. The placement word at the top flips back to "SPAM" in #ED5746.
Here is the part that traps people. Perfect authentication does not save you. If the people you send to quietly stopped opening months ago, their mailbox provider noticed that silence long before you did, and it has been routing you to spam ever since.
05 · The one everyone blames · 0:33
On screen: a sixth row tries to push in at the top, labelled the words you wrote, and gets pushed to the bottom of the stack, dimmed.
And the thing you were about to rewrite? The words? That one matters least. Fix the signals above it first.
06 · The decision · 0:40
On screen: the five gauges clear to two, side by side, each a mono card. authentication over "check it free" and list quality over "clean it". A thin teal rule between them.
So stop rewriting the email. Find the signal that is dragging you down. Two you can check today. Your authentication, with our free SPF and DMARC checkers. And your list, cleaned so the dead weight stops pulling your reputation down.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.001.004-why-emails-go-to-spam.md
01 · The hook
paper. One address alone, mono, large: dispatch@driftwood-goods.example. Above it a single word in Lora, ink, big: "SPAM." Below, dashed and hollow, the question: "It did everything right."
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A right answer that still failed is the itch nobody scrolls past.
the address is invented. Never a real one, never a client's.
02 · The myth
Almanac ids in this scene: 002.001.004
three guesses type out and cross through, one at a time, mono: a spammy word, the link, no SPF record. Each gets a thin strike.
low pulse comes in under the first strike.
Almanac 002.001.004: "The most common mistake is thinking spam filtering is about one thing. It's not."
name the wrong search out loud so the correction lands as relief, not a lecture.
03 · The five signals
Almanac ids in this scene: 002.001.004
the address moves up. Five gauges build under it, one per line as the VO names it, each a mono label with a small dial. All five settle reading well. - sender reputation with your domain and IP history - engagement with do people open or ignore - authentication with SPF, DKIM, DMARC - list quality with who is actually on the list - sending pattern with steady or spiky
music settles into a steady bed as the dials rise.
Almanac 002.001.004, its five named categories: "Sender reputation... Engagement history... Authentication setup... List quality... Sending patterns." List quality in the Almanac lists purchased contacts and addresses that have not engaged in years.
the Almanac's list-quality line also names spam traps. It is cut, because spam-trap claims are banned on marketing surfaces and this is one. Engagement is spoken as open-or-ignore only. No complaint-rate number is shown or said, because a threshold on a marketing surface is off limits.
naming all five honestly is what sets up the turn. If the viewer believes the five are real, the reveal that four can be fine and still fail actually bites.
04 · The turn
Almanac ids in this scene: 002.001.004
four dials hold and glow green. One, engagement, drops into red. The placement word at the top flips back to "SPAM" in #ED5746.
the bed thins to one held note as the red dial lands.
Almanac 002.001.004: "You can have perfect authentication and still land in spam if your engagement is terrible... Spam filtering is a weighted combination of all these signals, and different mailbox providers weigh them differently."
this is the whole point in one beat, so it carries the longest sentence in the script on purpose, paced to the slow way the damage actually happens.
05 · The one everyone blames
Almanac ids in this scene: 002.001.004
a sixth row tries to push in at the top, labelled the words you wrote, and gets pushed to the bottom of the stack, dimmed.
a single soft knock as the row drops.
Almanac 002.001.004: "This one's overstated (engagement and reputation matter more)... Content alone rarely causes spam placement for a sender with good reputation and engagement."
it is the most shareable line in the answer and it releases the viewer from the busywork they were about to do, which is the firemen-not-salesmen move.
06 · The decision
Almanac ids in this scene: 002.001.004
the five gauges clear to two, side by side, each a mono card. authentication over "check it free" and list quality over "clean it". A thin teal rule between them.
music returns, warmer, under "clean it".
Almanac 002.001.004: "Check your authentication setup first (it's the easiest to fix). Then look at your engagement metrics and list quality. You can check your SPF and DMARC with our free tools."
the two checks stay two separate sentences for two separate signals. Cleaning the list is never implied to fix authentication, and neither one is a promise of inbox placement. No inbox-placement guarantee, ever.
ends on a decision, not a number (voice guide section 6). It hands the viewer the two moves the Almanac itself hands them, in the Almanac's own order.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is /get-started, which is the confirmed target and the one that resolves. See "Needs YT's yes" on the launch wording.
V906Delivered is not inboxed
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two prior scripts in this series.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, coming-soon, or live.
- The CTA destination. Specced as reviewmyemails.com/get-started.
- Keep or cut the four-cause shot (shot 4). It is the most literal, Almanac-sourced part of the script but it adds about twelve seconds on its own.
- No lead magnet in this script maps to the answer's own advice. The answer's closing move is "run an inbox placement test" and "segment out unengaged subscribers." Neither has a lead magnet in the current five-priority list (see the...
01 · The hook · 0:00
On screen: paper. Large mono stat, top: 10,000 sent. Below it, Lora, ink, bold: "99% delivered." A green check sits beside it. Half a second later a diagonal strike cuts through the whole line and, underneath, in #ED5746 mono: 60% inboxed.
Ten thousand emails. Ninety-nine percent delivered. Only sixty percent ever reached an inbox.
02 · The false relief · 0:05
On screen: an invented sender dashboard, mono: newsletter@tidewell-supply.example under a green badge reading 99% DELIVERED. A cursor hovers, about to click away.
You saw that ninety-nine and called it a win. Your inbox provider never agreed.
03 · Two separate verdicts · 0:12
On screen: one mail icon splits into two boxes that build in sequence. Box 1, mono label: ACCEPT OR REJECT, sub-lines fading in under it: IP blocklisted?, SPF and DKIM valid?, sending rate too fast?, then a check and 250 OK. Box 2 slides in after, mono label: INBOX, SPAM, OR PROMOTIONS, sub-lines: content, reputation, engagement history.
Every email gets two separate verdicts. First, will the server even take it. That is delivery, decided in seconds. Second, where does it put it. That is placement, decided afterward, on a completely different set of signals.
04 · Four ways the gap opens · 0:24
On screen: box 2 from the last shot expands into four mono rows, building one at a time: content triggers, engagement history, domain reputation lag, Gmail tab filtering. Each gets one short sub-line as it lands.
Four things push accepted mail into spam anyway. A subject line that trips a filter. Subscribers who quietly stopped opening months ago. A domain reputation still recovering from old problems. Or Gmail deciding you belong in promotions, where most people never look.
05 · The gap named · 0:36
On screen: two mono numbers land side by side: 98% delivery and 65% inbox placement. A bracket opens between them and expands into a red stat: 1 IN 3 GONE.
Ninety-eight percent delivery next to sixty-five percent inbox placement is not a rounding error. That is a third of your list disappearing, and your dashboard will never flag it.
06 · The decision · 0:42
On screen: two mono cards side by side. Card A, MEASURE IT, under it "run an inbox placement test." Card B, WORK THE SIGNAL, under it "clean the list dragging your engagement down." A thin teal rule between them.
So stop admiring the delivery number. Run an inbox placement test so you can see where your mail actually lands, then work the signal dragging you into spam, starting with the unengaged subscribers your list is still carrying.
07 · End card · 0:50
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.002.004-delivered-not-inboxed.md
01 · The hook
Almanac ids in this scene: 002.002.004
paper. Large mono stat, top: 10,000 sent. Below it, Lora, ink, bold: "99% delivered." A green check sits beside it. Half a second later a diagonal strike cuts through the whole line and, underneath, in #ED5746 mono: 60% inboxed.
no music yet, room tone, a single low thud on the strike.
Almanac 002.002.004: "You send 10,000 emails. Your ESP reports a 99% delivery rate... only 60% actually made it to the primary inbox."
the numbers are the Almanac's own worked example, not invented for shock value. Nothing here claims this gap happens on every send.
it has to work muted and as the thumbnail, because the image earns the click (BIBLE section 8). Two numbers a real dashboard could show, side by side, is the whole hook.
02 · The false relief
Almanac ids in this scene: 002.002.004
an invented sender dashboard, mono: newsletter@tidewell-supply.example under a green badge reading 99% DELIVERED. A cursor hovers, about to click away.
the low bed starts under "your inbox provider."
Almanac 002.002.004: "Your ESP reports a 99% delivery rate. Sounds great, right?... What happened?"
the address and domain are invented. Never a real one, never a client's.
name the false relief before puncturing it, so the correction lands as rescue, not a scold.
03 · Two separate verdicts
Almanac ids in this scene: 002.002.004
one mail icon splits into two boxes that build in sequence. Box 1, mono label: ACCEPT OR REJECT, sub-lines fading in under it: IP blocklisted?, SPF and DKIM valid?, sending rate too fast?, then a check and 250 OK. Box 2 slides in after, mono label: INBOX, SPAM, OR PROMOTIONS, sub-lines: content, reputation, engagement history.
the bed settles into a steady pulse as box 2 arrives.
Almanac 002.002.004: "Accept or reject (delivery decision). This happens at SMTP time... Is your IP blocklisted? Does your domain have valid SPF and DKIM? Is your sending rate too aggressive?... Inbox, spam, or promotions (filtering decision). This happens AFTER acceptance... it operates completely separately from the delivery layer."
the "IP blocklisted" line describes a check on the sender's own sending reputation at SMTP time, exactly as the Almanac frames it. It is never shown or implied as a reason to suppress a recipient, that reading is banned regardless of context.
this is the spine. If the two-verdict structure does not land here, nothing after it makes sense.
04 · Four ways the gap opens
Almanac ids in this scene: 002.002.004
box 2 from the last shot expands into four mono rows, building one at a time: content triggers, engagement history, domain reputation lag, Gmail tab filtering. Each gets one short sub-line as it lands.
bed holds steady, one soft accent per row landing.
Almanac 002.002.004, its four named causes: "Content triggers... Engagement history... Domain reputation lag... Tab filtering at Gmail," including "70% of Gmail recipients never check that tab."
the four are presented as a list, not ranked or scored against each other, since the Almanac gives no weighting between them here. No complaint-rate number appears in this answer to cut, and none is shown.
makes the invisible mechanism concrete with the Almanac's own four causes, not a generic "spam filters are complicated" gesture.
05 · The gap named
Almanac ids in this scene: 002.002.004
two mono numbers land side by side: 98% delivery and 65% inbox placement. A bracket opens between them and expands into a red stat: 1 IN 3 GONE.
the bed thins to one held note under "disappearing."
Almanac 002.002.004: "If you're seeing 98% delivery but only 65% inbox placement, you're losing a third of your audience to filtering."
the fraction stays exactly as the Almanac states it, a third, not rounded up or dramatized further.
gives the myth-bust its receipt, a number straight from the source, not an invented shock stat.
06 · The decision
Almanac ids in this scene: 002.002.004
two mono cards side by side. Card A, MEASURE IT, under it "run an inbox placement test." Card B, WORK THE SIGNAL, under it "clean the list dragging your engagement down." A thin teal rule between them.
music returns, warmer, under "work the signal."
Almanac 002.002.004: "run an inbox placement test before your next campaign. You can't fix what you can't measure." Also: "Focus on the filtering signals. Check your engagement rates... Segment out unengaged subscribers and either re-engage them or suppress them."
no inbox-placement guarantee, the frame offers a test and a lever, never a promise of the inbox. Cleaning the list is shown as one lever for the engagement signal only, never implied to fix SPF, DKIM, DMARC, or a blocklist problem, those stay a separate, unmentioned signal in this shot.
ends on the Almanac's own two moves, a measurement and a lever, not a raw number.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" matches the approved CTA wording used in the first two scripts in this series rather than a generic "start for free," which is on the forbidden competitor list. The destination is /get-started, the confirmed working target. See "Needs YT's yes" on the launch wording.
V907What is sender reputation
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the earlier Almanac scripts in this series.
- The launch wording on the end card. RME-16 is still defining which posts read as waitlist, coming-soon, or live.
- Shot 4's density. The domain-versus-IP distinction (shared IP inheritance, and domain now outweighing IP because it is harder to fake) is genuinely the most underweighted point in the answer, but it is compressed into 8 seconds here to...
- Shot 5 right after shot 6's CTA. Shot 5 tells the viewer that checking blocklist status is "a symptom, not the score itself," and shot 6 immediately tells them to go run that same blocklist check.
01 · The hook · 0:00
On screen: paper. One address alone, mono, large: updates@reply-all-realty.example. Below it, a split card: left side "GMAIL: INBOX" in #10B981, right side "OUTLOOK: SPAM" in #ED5746. A single line beneath, dashed: "Same email. Same minute."
Same email. Same minute. One inbox landed it. One sent it straight to spam.
02 · The myth · 0:05
On screen: mono text types and strikes: one score, pass it once, safe everywhere. Each gets a thin strike as it is spoken.
So you assume it is one score. Clear it once, and every provider trusts you. That is not how this works.
03 · The real model · 0:11
On screen: the address moves up. A label builds beneath it: "SENDER REPUTATION", subtitle "credit, but for email." Six mono rows build one at a time as the VO names them: - list quality with "who's actually on your list" - engagement with "opens and clicks, or silence" - spam complaints with "marked as spam, it costs you" - bounce rate with "do you know who you're sending to" - sending consistency with "steady, not spiking" - authentication with "SPF, DKIM, DMARC, set up right"
Think of it like credit, but for email. It's built from what you actually do. Who's on your list, whether people open you or ignore you, every time someone marks you as spam, how many addresses bounce, whether your sending stays steady, and whether your authentication checks out.
04 · The turn · 0:26
On screen: two mono cards. Left, dimmed: IP reputation, subtitle "shared with strangers on your ESP's server." Right, glowing teal: domain reputation, subtitle "yours alone."
Most senders use a shared IP, so that reputation is not only yours, it is inherited from everyone else on that server. Your domain is yours alone, and it has become the reputation that matters more, because it is harder to fake.
05 · What you can't see · 0:34
On screen: the domain card from shot 4 shrinks to a corner. Centre frame: "YOUR SCORE:" followed by a redacted mono bar, blurred. Below it, small: blocklist status and reputation tools, stamped "proxies, not the score."
You can't see the real number. Providers never publish it. What you can check, like blocklist status, is a symptom, not the score itself.
06 · The decision · 0:41
On screen: two mono cards, side by side. check your domain over "free blocklist checker" and inbox rate dropping? over "free SOS hotline." A thin teal rule between them.
So check the two things you actually can. Run your domain through our free blocklist checker to see if you're flagged anywhere. And if your inbox rate is dropping and you don't know why, our SOS hotline helps you find what's broken.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.003.001-sender-reputation.md
01 · The hook
Almanac ids in this scene: 002.003.001
paper. One address alone, mono, large: updates@reply-all-realty.example. Below it, a split card: left side "GMAIL: INBOX" in #10B981, right side "OUTLOOK: SPAM" in #ED5746. A single line beneath, dashed: "Same email. Same minute."
no music yet. Room tone only.
Almanac 002.003.001: "Gmail, Outlook, and Yahoo each track your reputation independently, so you can have great reputation with Gmail and terrible reputation with Outlook at the same time."
the address is invented. Never a real one, never a client's.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A split verdict on the same email, at the same time, is the itch nobody scrolls past.
02 · The myth
Almanac ids in this scene: 002.003.001
mono text types and strikes: one score, pass it once, safe everywhere. Each gets a thin strike as it is spoken.
low pulse comes in under the first strike.
Almanac 002.003.001: "It's a score based on your past behavior, tracked at both the domain level... and IP level," read against the same line as shot 1 on independent provider tracking.
name the wrong model out loud so the correction in shot 3 lands as relief, not a lecture.
03 · The real model
Almanac ids in this scene: 002.003.001
the address moves up. A label builds beneath it: "SENDER REPUTATION", subtitle "credit, but for email." Six mono rows build one at a time as the VO names them: - list quality with "who's actually on your list" - engagement with "opens and clicks, or silence" - spam complaints with "marked as spam, it costs you" - bounce rate with "do you know who you're sending to" - sending consistency with "steady, not spiking" - authentication with "SPF, DKIM, DMARC, set up right"
music settles into a steady bed as the rows build.
Almanac 002.003.001: "Think of it like credit, but for email. Good history gets you into inboxes. Bad history gets you filtered, throttled, or blocked entirely," and the six-item list under "What shapes your reputation."
the Almanac's list-quality line also names spam traps. Cut, because spam-trap claims are banned on marketing surfaces and this is one. List quality is spoken as who is on the list and old contacts who never open, nothing else. Spam complaints are spoken qualitatively, "marked as spam, it costs you," with no complaint-rate number shown or said, because a threshold on a marketing surface is off limits.
naming all six honestly, in the Almanac's own order, is what makes shot 4's domain-versus-IP turn land as a genuine addition rather than a repeat.
04 · The turn
Almanac ids in this scene: 002.003.001
two mono cards. Left, dimmed: IP reputation, subtitle "shared with strangers on your ESP's server." Right, glowing teal: domain reputation, subtitle "yours alone."
the bed holds, one note rises as the domain card glows.
Almanac 002.003.001: "Most ESPs use shared IPs, which means your IP reputation is shared with other senders on that server. Your domain reputation is yours alone. Over time, domain reputation has become MORE important than IP reputation because it's harder to fake."
this is the underweighted point the companion script's review flagged reputation for. Most senders think about the tool they send through, not the domain name that is tracking them on its own.
05 · What you can't see
Almanac ids in this scene: 002.003.001
the domain card from shot 4 shrinks to a corner. Centre frame: "YOUR SCORE:" followed by a redacted mono bar, blurred. Below it, small: blocklist status and reputation tools, stamped "proxies, not the score."
the bed thins to one held note.
Almanac 002.003.001: "you can't see your exact reputation score. Mailbox providers don't publish it... You can also check external signals like blocklist status and domain reputation tools, but those are proxies, not the real score."
it is the shortest sentence in the script on purpose, "You can't see the real number," seven words, because it is the flattest, most deflating fact in the answer and deserves no ornament.
06 · The decision
Almanac ids in this scene: 002.003.001
two mono cards, side by side. check your domain over "free blocklist checker" and inbox rate dropping? over "free SOS hotline." A thin teal rule between them.
music returns, warmer, under "SOS hotline."
Almanac 002.003.001: "Run your domain through our free blocklist checker to see if you're flagged anywhere... hit up our SOS hotline and we'll help you figure out what's broken."
the blocklist check stays framed as one proxy signal about the sender's own domain, never a claim that a clean result equals a good score, and never a reason to suppress a recipient. Cleaning a list is not implied to fix authentication or blocklist standing anywhere in this shot.
ends the diagnostic section on the two moves the Almanac itself hands the reader, in the Almanac's own order, before the offer.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3), not an Almanac fact, so it carries no Source: line. "Get my list cleaned" is the approved CTA wording. The destination, reviewmyemails.com/get-started, is the confirmed CTA for this cluster and is not re-flagged here.
V908What causes a bad sender reputation
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the existing Review My Emails video precedents and the earlier Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- Keep or cut the volume-spike cause (part of shot 3 and the second move in shot 6). It is faithfully grounded and it is a cause the sender controls, but it is the one cause cleaning does not touch, so it splits the ending into two moves...
01 · The hook · 0:00
On screen: paper. One address alone, mono, large: news@barnacle-bloom.example. Above it a thin reputation bar sliding from teal down into #ED5746. Below, in Lora, ink, big: "It wasn't one email."
Your reputation dropped, and you are combing through your last send for the one thing that did it. Stop. It was never one thing.
02 · The pattern · 0:05
On screen: three guesses type out and cross through, one at a time, mono: the subject line, too many images, one bad link. Each gets a thin strike. Then a single word lands in Lora, ink: "pattern."
It is not one mistake that kills your reputation. It is a pattern. A run of signals that all tell a mailbox provider the same thing. This mail is not wanted.
03 · The three you built · 0:12
On screen: the address moves up. Three bars build under it, one per line as the VO names it, each a mono label with a short descriptor. - a stale or bought list with people who never asked, addresses that died - silent subscribers with no opens, no clicks, for months - a sudden spike with quiet, then one big blast
Three of these you built yourself. A list gone stale or bought in, full of people who never asked and addresses that quietly died. Subscribers who stopped opening months ago, still getting your mail every week. And a jump in volume out of nowhere.
04 · How it reads on the other side · 0:25
On screen: the three bars glow into #F59E0B then #ED5746. Around the address, small marks surface one by one: report spam, bounced, ignored. The reputation bar at the top sinks further into #ED5746.
Here is how it reads on the other side. When the people who never asked start hitting report spam, and the dead addresses keep bouncing, and the ones who went silent just delete you on sight, a mailbox provider stops giving you the benefit of the doubt.
05 · The part that helps · 0:34
On screen: the three bars turn back from #ED5746 toward #10B981, one at a time, a small hand-drawn tick landing on each. Under the word pattern, a subtitle types in: you built it, you can unbuild it.
And here is the part that helps. You built this pattern, which means you can take it apart. Every one of those causes is yours to fix.
06 · The decision · 0:40
On screen: the three bars clear to two cards, side by side, each mono. your list over "clean it" and your rhythm over "grow it slowly". A thin teal rule between them.
So stop staring at the last email. Find the pattern instead. Two moves you can make this week. Clean your list, so the dead weight and the people who never asked stop dragging you down. And grow your volume slowly, in a steady rhythm, instead of one big blast.
07 · End card · 0:49
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.003.007-bad-sender-reputation.md
01 · The hook
paper. One address alone, mono, large: news@barnacle-bloom.example. Above it a thin reputation bar sliding from teal down into #ED5746. Below, in Lora, ink, big: "It wasn't one email."
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A falling reputation bar and a flat denial is the itch nobody scrolls past.
the address is invented. Never a real one, never a client's.
02 · The pattern
Almanac ids in this scene: 002.003.007
three guesses type out and cross through, one at a time, mono: the subject line, too many images, one bad link. Each gets a thin strike. Then a single word lands in Lora, ink: "pattern."
low pulse comes in under the first strike.
Almanac 002.003.007: "It's not one mistake that kills you. It's a pattern." and "Your sender reputation tanks when mailbox providers see patterns that scream 'unwanted mail.'"
name the wrong search out loud so the correction lands as relief, not a lecture.
03 · The three you built
Almanac ids in this scene: 002.003.007
the address moves up. Three bars build under it, one per line as the VO names it, each a mono label with a short descriptor. - a stale or bought list with people who never asked, addresses that died - silent subscribers with no opens, no clicks, for months - a sudden spike with quiet, then one big blast
music settles into a steady bed as the bars rise.
Almanac 002.003.007: "Purchased lists are full of people who never asked for your mail... Old lists (untouched for 6+ months) decay fast. Addresses get abandoned... or just stop engaging." · "Mailing unengaged subscribers for months is one of the fastest reputation killers." · "If you normally send 10,000 emails a week and suddenly jump to 100,000, mailbox providers see that as suspicious."
the Almanac's list-decay line also names spam traps. It is cut, because spam-trap claims are banned on marketing surfaces and this is one. Engagement is spoken as opens and clicks only. No bounce number and no complaint number is shown or said. The spike is described qualitatively, not as a figure.
naming the three the viewer controls is what earns the turn. If they own the causes, the fix in shot 6 reads as theirs to make, not a pitch.
04 · How it reads on the other side
Almanac ids in this scene: 002.003.007
the three bars glow into #F59E0B then #ED5746. Around the address, small marks surface one by one: report spam, bounced, ignored. The reputation bar at the top sinks further into #ED5746.
the bed thins to one held note as the marks land.
Almanac 002.003.007: "Every 'Report spam' click tells [Gmail], [Outlook], and [Yahoo] that recipients don't want your mail." · "Sending to invalid addresses tells mailbox providers you don't maintain your list. Hard bounces (address doesn't exist) are the worst signal." · "If recipients consistently ignore your mail (no opens, no clicks, straight to trash), mailbox providers assume it's not wanted."
complaints and bounces are spoken qualitatively. The answer's 0.1, 0.3, and 2 percent figures are kept off screen and out of the VO, because a threshold on a marketing surface is off limits. No spam-trap claim. No blocklist is named, and nothing here frames a blocklist listing as a reason to drop a recipient.
this is the whole point in one beat, so it carries the longest sentence in the script, paced to the slow way a mailbox provider actually loses trust.
05 · The part that helps
Almanac ids in this scene: 002.003.007
the three bars turn back from #ED5746 toward #10B981, one at a time, a small hand-drawn tick landing on each. Under the word pattern, a subtitle types in: you built it, you can unbuild it.
a single soft knock as the first tick lands.
Almanac 002.003.007: "The fix starts with understanding your current state... stop mailing unengaged contacts, clean your list."
it releases the viewer from the doom of a reputation they think is out of their hands, which is the firemen-not-salesmen move, and it is the most shareable line in the answer.
06 · The decision
Almanac ids in this scene: 002.003.007
the three bars clear to two cards, side by side, each mono. your list over "clean it" and your rhythm over "grow it slowly". A thin teal rule between them.
music returns, warmer, under "clean it".
Almanac 002.003.007: "stop mailing unengaged contacts, clean your list" and "Volume changes need to be gradual... Regular cadence (even if it's just once a month) builds trust."
the two moves stay two separate sentences for two separate causes. Cleaning the list is never implied to fix the volume spike, and neither move is a promise of inbox placement. Authentication is left out on purpose (see "Rules checked"), so nothing here suggests cleaning repairs SPF, DKIM, or DMARC.
ends on a decision, not a number (voice guide section 6). It hands the viewer two of the moves the Almanac itself hands them, and it puts the list first because that is the biggest lever the viewer controls.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination reviewmyemails.com/get-started is the confirmed cluster CTA, so it is not re-flagged here. See "Needs YT's yes" on the launch wording.
V909The signals that beat your authentication
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the shrink-the-auth-ticks device, or a simpler swap.
01 · The hook · 0:00
On screen: paper. Two green ticks stacked, mono: SPF ok, DKIM ok, DMARC ok. A red arrow points past them to one word, Lora, big: "Irrelevant."
Your authentication can be perfect, and it can still count for almost nothing. Here is the signal that actually decides where you land.
02 · What the signals are · 0:06
On screen: two columns build, mono. Left, green: opens, clicks, replies, moved to inbox, rescued from spam. Right, grey: deleted unread, ignored, unsubscribed.
Engagement signals are what people do with your email. Open it, click, reply, drag it to the inbox. Those are green flags. Or delete it unread, ignore it, unsubscribe. Those are red flags. Every action gets tracked.
03 · The hard truth · 0:22
On screen: the three green auth ticks shrink to the corner. The engagement columns grow to fill the frame.
Here is the hard truth. Engagement matters more than authentication. Perfect SPF, DKIM, and DMARC still land you in spam if nobody engages. Authentication proves you are you. Engagement proves you are worth reading.
04 · The mistake · 0:34
On screen: a subscriber with "opened 0 of your last 10" gets emailed an 11th, which slides straight to spam.
And here is the mistake almost everyone makes. Someone has not opened your last ten emails. They will not open the eleventh. The provider knows that, and it starts filtering you to spam for them, then for others as the pattern spreads.
05 · The decision · 0:42
On screen: the dead subscriber is lifted off the list. The engagement meter rises.
So stop emailing people who stopped caring. Cut the silent ones, and the people who do want you get a better shot at your inbox.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.004.001-email-engagement-signals.md
01 · The hook
paper. Two green ticks stacked, mono: SPF ok, DKIM ok, DMARC ok. A red arrow points past them to one word, Lora, big: "Irrelevant."
room tone.
it undercuts the thing people are proud of and promises the real lever.
02 · What the signals are
Almanac ids in this scene: 002.004.001
two columns build, mono. Left, green: opens, clicks, replies, moved to inbox, rescued from spam. Right, grey: deleted unread, ignored, unsubscribed.
Almanac 002.004.001: "Positive signals include opens, clicks, replies, forwards, moving a message to the primary tab, and rescuing from spam. Negative signals include deletes without opening... unsubscribes, and sustained non-engagement."
the Almanac names a complaint-rate threshold. Cut, spoken as "marked as spam" only.
03 · The hard truth
Almanac ids in this scene: 002.004.001
the three green auth ticks shrink to the corner. The engagement columns grow to fill the frame.
Almanac 002.004.001: "engagement signals matter more than authentication... Authentication proves you're you. Engagement proves you're worth reading."
this reframe is the whole video, so it carries the longest line.
04 · The mistake
Almanac ids in this scene: 002.004.001
a subscriber with "opened 0 of your last 10" gets emailed an 11th, which slides straight to spam.
Almanac 002.004.001: "If someone hasn't opened your last 10 emails, they're not going to open the 11th... they'll start filtering you to spam for that subscriber (and eventually for others if the pattern spreads)."
05 · The decision
Almanac ids in this scene: 002.004.001
the dead subscriber is lifted off the list. The engagement meter rises.
Almanac 002.004.001: "Want better deliverability? Stop emailing people who stopped caring."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V910Why engagement affects deliverability
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching every prior script in this series.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, coming-soon, or live.
- Keep or cut the loop shot (shot 5). It is faithful to the Almanac's own feedback-loop language and it is what makes shot 6 feel urgent rather than optional, but it adds about eight seconds on its own.
01 · The hook · 0:00
On screen: paper. An invented address, mono, large: hello@kelp-street.example. Beside it three small checks, mono: SPF ✓ DKIM ✓ DMARC ✓. Below, in Lora, ink: "Still spam."
Every authentication check on this domain passes clean. It still lands in spam.
02 · The real judge · 0:05
On screen: the checks fade back. Two columns build under the domain, mono labels. Left, tinted toward keep green: opens clicks replies "not spam" clicks. Right, tinted toward suppress red: deletes unopened ignored marked as spam.
Because the mailbox provider is not grading your settings. It is grading your readers. Every open, every click, every delete without a glance, all of it trains the filter.
03 · The test · 0:14
On screen: the two columns fold into a small cluster of dots, mono label first slice of the list, which splits into two paths. One path warms (opens and clicks glow) and rises toward an inbox icon. The other path cools (grey, still) and drops toward a spam-folder icon. A larger, waiting cluster labelled everyone else sits behind a gate that swings toward whichever path lit up.
Before it ever commits to your whole list, the mailbox provider tests a small slice first, and if that slice opens the mail and engages with it the rest follows to the inbox, but if that slice mostly ignores it or marks it unwanted the rest follows straight to spam.
04 · The turn · 0:25
On screen: the domain from shot 1 returns, its three checks still green. Beside it the engagement column from shot 2 flips fully red. The word beneath, still reading "Still spam," now sits in the suppress colour.
This is the part that catches people out. Perfect SPF, DKIM and DMARC do not save you here. If your readers quietly started ignoring you, the algorithm noticed that shift long before you did.
05 · The loop · 0:33
On screen: a circular arrow diagram, two mono-labelled nodes, spam folder and fewer opens, connected in a loop that turns slowly and tightens with each rotation.
And it compounds. Land in spam once, fewer people ever see the next one. Fewer people see it, the next one looks even less wanted. The loop feeds itself.
06 · The decision · 0:41
On screen: the loop breaks. One card slides in, mono: remove who's gone quiet, with a smaller line under it, 90+ days unengaged. A thin teal rule, then: so what's left trains the filter in your favor.
Breaking the loop starts with the list. Cut the people who have gone quiet, so the readers left are the ones actually training the filter in your favor.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.004.005-engagement-and-deliverability.md
01 · The hook
Almanac ids in this scene: 002.004.005
paper. An invented address, mono, large: hello@kelp-street.example. Beside it three small checks, mono: SPF ✓ DKIM ✓ DMARC ✓. Below, in Lora, ink: "Still spam."
no music yet. Room tone only.
Almanac 002.004.005: "...no matter how perfect your SPF and DKIM records are."
the domain is invented. Never a real one, never a client's.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Three green checks next to a spam verdict is the contradiction nobody scrolls past.
02 · The real judge
Almanac ids in this scene: 002.004.005
the checks fade back. Two columns build under the domain, mono labels. Left, tinted toward keep green: opens clicks replies "not spam" clicks. Right, tinted toward suppress red: deletes unopened ignored marked as spam.
a low pulse begins under the columns.
Almanac 002.004.005: "Opens, clicks, replies, archives, and Not Spam clicks tell the filter your mail is wanted." And, on the other side: "deletes without opening, low read time, and spam complaints... tell it the opposite." Also: "Opens, clicks, replies, deletes without opening, spam complaints, how long someone reads before closing. All of that behavior feeds their filtering algorithms."
spam complaints are named as a category only, no rate or threshold attached to them anywhere in the frame or the VO.
naming the real inputs is the reveal that resets what "doing it right" actually means, ahead of the mechanism shot that follows.
03 · The test
Almanac ids in this scene: 002.004.005
the two columns fold into a small cluster of dots, mono label first slice of the list, which splits into two paths. One path warms (opens and clicks glow) and rises toward an inbox icon. The other path cools (grey, still) and drops toward a spam-folder icon. A larger, waiting cluster labelled everyone else sits behind a gate that swings toward whichever path lit up.
the bed settles into a steady rhythm as the gate swings.
Almanac 002.004.005: "Gmail delivers the first batch to 5,000 inboxes and watches what happens... [if the slice] open[s] within a few hours and several people click or reply, Gmail treats that as positive proof and delivers the rest to the inbox. If only [a small share open and some] mark it spam, Gmail routes the remaining... to the spam folder."
the source's own figures here (roughly 30 percent, 5 percent, and 2 percent marking it spam) are cut in full. The last one is a complaint-rate figure outright and the other two are engagement percentages, both off limits per this ticket's angle note. The mechanism is kept, the numbers are not.
this is the ranking made visible. The reader watches the algorithm decide in real time instead of being told a rule to trust.
04 · The turn
Almanac ids in this scene: 002.004.005
the domain from shot 1 returns, its three checks still green. Beside it the engagement column from shot 2 flips fully red. The word beneath, still reading "Still spam," now sits in the suppress colour.
the bed thins to one held note as the column flips.
Almanac 002.004.005: "...even if both have perfect authentication and clean list practices" and "The algorithm trusts user behavior more than it trusts your technical setup."
this stays a ranking claim, behavior outweighs setup, never a replacement claim. Nothing here says authentication stops mattering, and nothing implies cleaning a list repairs SPF, DKIM, DMARC or a blocklist problem.
the whole point lands in one beat, the reason shot 1's contradiction exists at all.
05 · The loop
Almanac ids in this scene: 002.004.005
a circular arrow diagram, two mono-labelled nodes, spam folder and fewer opens, connected in a loop that turns slowly and tightens with each rotation.
a low, repeating tick under the turning loop.
Almanac 002.004.005: "Low engagement causes spam folder placement. Spam folder placement means fewer people see your mail, which lowers engagement further... a feedback loop that's hard to escape."
names the cost of waiting, which is what earns the next shot's urgency.
06 · The decision
Almanac ids in this scene: 002.004.005
the loop breaks. One card slides in, mono: remove who's gone quiet, with a smaller line under it, 90+ days unengaged. A thin teal rule, then: so what's left trains the filter in your favor.
music returns, warmer, under "actually training."
Almanac 002.004.005: "Breaking that cycle requires aggressive list cleaning (remove everyone who hasn't engaged in 90+ days)..." and "the good news: engagement metrics are something you can directly control."
no inbox-placement guarantee. Cleaning the list stays scoped to the engagement signal only, never framed as a fix for SPF, DKIM, DMARC or a blocklist.
ends on a decision, not a number (voice guide section 6), and it is the Almanac's own first move, in the Almanac's own words.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
offer and CTA wording match the locked precedent, BIBLE section 3's 1,000 free credits, and "Get my list cleaned" over a generic "start for free," which is on the forbidden competitor list. The CTA destination, reviewmyemails.com/get-started, is confirmed for this cluster and not re-raised here.
V911Does the Promotions tab count as good deliverability
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the house precedent set by the gold-standard script.
- The launch wording on the end card. States the offer and the destination without claiming a launch state.
- Keep or cut shot 5, the trick list. It names three specific sneaky tactics (fake reply subject, reply-to swap, pulled unsubscribe link) because the Almanac names them directly and they are the real villain of the piece.
- The 2-to-3x stat in shot 4. It is accurate to the Almanac and it is what keeps the video honest rather than a flat "don't worry about it," but it is also the one beat that could read as undercutting the reassurance if a viewer stops...
01 · The hook · 0:00
On screen: paper. One invented address, mono, large: newsletter@brinewater.example. Below it a small Gmail-style tab strip, Promotions lit. Under that, ink, big: "Promotions." Dashed and hollow beneath: "Did I mess up?"
Your campaign landed in Promotions. Your stomach just dropped.
02 · The correction · 0:05
On screen: Promotions" holds. A second line drops in, struck through, red: "= spam". Then a clean line settles under it in teal: "= delivered.
Nothing broke. Promotions is not spam. It never was.
03 · What the tabs actually do · 0:11
On screen: a simple sort diagram. One bracket labelled INBOX, four mono tabs sliding into place under it: Primary, Promotions, Social, Updates.
Gmail's tabs sort mail that already got in. They are folders inside the inbox, not a gate deciding what gets through.
04 · The honest tradeoff · 0:19
On screen: two stacked bars, mono labelled Primary and Promotions, Primary roughly 2 to 3 times taller, both topped with a small label: opens.
Primary really is better. People see it first, and they open it two to three times more. For a flash sale or a webinar starting in an hour, that gap matters.
05 · The trap · 0:28
On screen: three lines type out and strike through, mono: fake "Re:" subject, reply-to swap, pull the unsubscribe link. Beneath them, ink: "tanks it worse."
So people chase Primary with tricks. A fake reply subject. A swapped reply-to. Ripping out the unsubscribe link. None of that moves you up. It tanks you.
06 · The decision · 0:38
On screen: two mono cards side by side. Left: low complaints, real engagement over "you're fine." Right: clean list, honest subject line over "the actual lever." A thin teal rule between them.
If your complaints stay low and people are actually opening and clicking your emails, you are already doing fine right where you are, and chasing Primary will not move the needle like cleaning your list or writing a subject line worth opening.
07 · End card · 0:49
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.006.003-promotions-tab.md
01 · The hook
paper. One invented address, mono, large: newsletter@brinewater.example. Below it a small Gmail-style tab strip, Promotions lit. Under that, ink, big: "Promotions." Dashed and hollow beneath: "Did I mess up?"
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). The worry is the itch nobody scrolls past.
the address is invented. Never a real one, never a client's.
02 · The correction
Almanac ids in this scene: 002.006.003
"Promotions" holds. A second line drops in, struck through, red: ~~"= spam"~~. Then a clean line settles under it in teal: "= delivered."
low pulse settles in.
Almanac 002.006.003: "Yes, landing in the Promotions tab counts as successful delivery. Your email made it to the inbox... Gmail didn't block it, bounce it, or send it to spam. That's good deliverability."
name the fear, then kill it fast, so the relief lands in the first six seconds instead of after a lecture.
03 · What the tabs actually do
Almanac ids in this scene: 002.006.003
a simple sort diagram. One bracket labelled INBOX, four mono tabs sliding into place under it: Primary, Promotions, Social, Updates.
music settles into a steady bed as the tabs slide in.
Almanac 002.006.003: "Gmail's tab system (Primary, Promotions, Social, Updates, Forums) sorts delivered mail. It does not filter it." (the Almanac joins those two clauses with a semicolon. Requoted here as two sentences, meaning unchanged, to hold the house no-semicolon rule on this surface.)
establishes the mechanism plainly, so the next beat reads as nuance rather than a contradiction of the reassurance just given.
04 · The honest tradeoff
Almanac ids in this scene: 002.006.003
two stacked bars, mono labelled Primary and Promotions, Primary roughly 2 to 3 times taller, both topped with a small label: opens.
bed holds, one accent as the taller bar settles.
Almanac 002.006.003: "Primary is better. Subscribers see Primary emails first. Open rates in Primary are typically 2-3x higher than Promotions. If you're selling something time-sensitive (a flash sale, a webinar starting in an hour), Primary matters a lot."
stated as a general open-rate comparison from the Almanac, not a promise that any specific send will land in Primary. No inbox-placement guarantee.
keeps the video honest. Pretending Promotions and Primary perform identically would undercut the reassurance the moment anyone checks their own numbers.
05 · The trap
Almanac ids in this scene: 002.006.003
three lines type out and strike through, mono: fake "Re:" subject, reply-to swap, pull the unsubscribe link. Beneath them, ink: "tanks it worse."
a thin dissonant note under each strike.
Almanac 002.006.003: "some senders obsess over getting into Primary and end up using tricks (reply-to manipulation, fake 'Re:' subjects, removing unsubscribe links) that actually tank deliverability. Don't do that."
this is the real villain of the video, not Promotions itself. It hands the viewer the one behavior actually worth avoiding.
06 · The decision
Almanac ids in this scene: 002.006.003
two mono cards side by side. Left: low complaints, real engagement over "you're fine." Right: clean list, honest subject line over "the actual lever." A thin teal rule between them.
music warms under "clean your list."
Almanac 002.006.003: "What actually hurts deliverability: landing in spam, getting blocked entirely, high bounce rates, high complaint rates. Promotions isn't on that list... if your complaint rate is low... and your engagement is decent, you're doing fine. Stressing over Primary vs Promotions won't move the needle as much as fixing your list quality or writing better subject lines."
the Almanac states an exact complaint-rate threshold here (under 0.1 percent). That number is cut. A complaint-rate threshold is banned on a marketing surface (Stage-1 pre-screen, hard content rules), so "low" replaces the figure, spoken qualitatively only. Cleaning the list is offered as a lever for engagement and subject-line credibility, never as a fix for SPF, DKIM, DMARC, MX, or a blocklist listing.
ends on the decision the Almanac itself hands over, list quality and subject lines, not tab-chasing, and that decision is the natural bridge into the offer.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording. The destination reviewmyemails.com/get-started is confirmed for this cluster (settled cluster fact), so it is used here without re-flagging.
V912How to land in the primary inbox
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- Keep or cut the reply-ask beat (shot 5). It is the most shareable line in the answer and it is faithfully grounded, including the "don't trick people" caveat that keeps it honest.
01 · The hook · 0:00
On screen: paper. Three stacked mailbox tabs, mono: Primary, Promotions, Updates. One envelope card sits in Promotions, sender hello@anchor-oar.example, straining up toward Primary against a dashed line it cannot cross. Above, Lora, ink, large: "You want Primary." Below, hollow and dashed: "There is no switch for it."
You want to land in the primary inbox. There is no button that puts you there.
02 · The myth · 0:05
On screen: three "hacks" type out and strike through one at a time, mono: the magic subject line, one hidden setting, a trick to force it. Each gets a thin strike.
So you go looking for the trick. The magic subject line. The one setting nobody told you about. You will not find it, because the mailbox provider is not watching you. It is watching them.
03 · What the provider actually watches · 0:12
On screen: the sender card moves up. Under it a row of recipient behaviours lights up as the VO names each, mono labels with small marks. On the keep-green side: opens, clicks, replies, drags you to Primary. On the suppress-red side: ignores, deletes unread, marks spam.
Your mailbox provider reads how real people treat your email. Whether they open it, click, reply, or drag it into Primary. Or whether they ignore it, delete it unread, and mark it as spam. That behaviour is the score, and it sets where you land next time.
04 · The gate · 0:24
On screen: in front of the behaviour row a gate slides in, labelled authentication, with SPF · DKIM · DMARC set small in mono beneath it. It swings open and lets the sender card through to where the behaviour is scored.
One gate sits in front of all of it. Authentication. Set up SPF, DKIM and DMARC, or Gmail will not even consider you for Primary. Get that wrong, and nothing you do downstream counts.
05 · The strongest move · 0:32
On screen: a recipient taps Reply. The sender card lifts out of Promotions and rises into Primary, glowing keep-green. A small caption fades in under it: "only if it was worth replying to."
The strongest signal a person can hand you is a reply. So in your welcome email, ask them to move this into their Primary inbox and to hit reply and say hi, but only ever if the email was genuinely worth it, because tricking people is the fastest way to teach a mailbox provider to bury you.
06 · The decision · 0:40
On screen: the screen clears to two mono cards side by side, a thin teal rule between them. authentication over "check it free", and who you send to over "only people who want you".
So stop hunting for the hack. Two moves today. Check your authentication with our free SPF and DMARC tools. And send only to people who actually opened you, not the ones who went quiet months ago. Earn the behaviour, and you raise your chances of Primary. Nobody honest can promise you the rest.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-002.006.004-land-in-primary-inbox.md
01 · The hook
Almanac ids in this scene: 002.006.004
paper. Three stacked mailbox tabs, mono: Primary, Promotions, Updates. One envelope card sits in Promotions, sender hello@anchor-oar.example, straining up toward Primary against a dashed line it cannot cross. Above, Lora, ink, large: "You want Primary." Below, hollow and dashed: "There is no switch for it."
no music yet. Room tone only.
Almanac 002.006.004: "you can't force primary inbox placement."
the address is invented, never a real one, never a client's. The frame states a wish and a limit, never a promise of placement.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A locked door with no handle is the itch nobody scrolls past.
02 · The myth
Almanac ids in this scene: 002.006.004
three "hacks" type out and strike through one at a time, mono: the magic subject line, one hidden setting, a trick to force it. Each gets a thin strike.
low pulse comes in under the first strike.
Almanac 002.006.004: "you can't force primary inbox placement. The mailbox provider watches what recipients do... no trick will save you."
name the wrong search out loud so the correction lands as relief, not a lecture, and hand the next shot its subject, them.
03 · What the provider actually watches
Almanac ids in this scene: 002.006.004
the sender card moves up. Under it a row of recipient behaviours lights up as the VO names each, mono labels with small marks. On the keep-green side: opens, clicks, replies, drags you to Primary. On the suppress-red side: ignores, deletes unread, marks spam.
music settles into a steady bed as the behaviours light.
Almanac 002.006.004: "The mailbox provider looks at how recipients behave with your email. If someone opens your messages regularly, clicks links, moves them to primary, or replies, that's a signal your content matters. If they ignore you, delete without opening, or mark as spam, you stay out of primary."
engagement is shown as behaviour only. No complaint-rate number is shown or spoken, and the answer carries none. No spam-trap language, none is used.
this is the mechanism the whole video rests on. If the viewer believes the provider is really watching behaviour, the moves in the next shots read as sense, not as tactics.
04 · The gate
Almanac ids in this scene: 002.006.004
in front of the behaviour row a gate slides in, labelled authentication, with SPF · DKIM · DMARC set small in mono beneath it. It swings open and lets the sender card through to where the behaviour is scored.
the bed holds. A soft latch as the gate opens.
Almanac 002.006.004: "Start with authentication. Set up SPF, DKIM, and DMARC correctly. Gmail won't even consider primary placement without proper authentication."
authentication and list quality are named as separate signals and never merged. Naming Gmail is fine, it is a mailbox provider, not a competitor. No placement is promised.
the answer's own first move, and it genuinely gates the rest, so it earns its own beat before the reward shot.
05 · The strongest move
Almanac ids in this scene: 002.006.004
a recipient taps Reply. The sender card lifts out of Promotions and rises into Primary, glowing keep-green. A small caption fades in under it: "only if it was worth replying to."
a single soft knock as the card lifts.
Almanac 002.006.004: "A simple 'Move this to your primary inbox' request in your welcome email works better than you'd think... Replies are one of the strongest positive signals a mailbox provider can see... only ask if you're sending content worth moving. Don't trick people."
the caveat stays in, spoken, not buried. The ask is framed as earning a real signal, never as gaming one. No placement guarantee, the reply raises the odds.
it is the most shareable line in the answer, it hands the viewer one concrete move, and the "don't trick people" turn is the firemen-not-salesmen move that keeps it honest.
06 · The decision
Almanac ids in this scene: 002.006.004
the screen clears to two mono cards side by side, a thin teal rule between them. authentication over "check it free", and who you send to over "only people who want you".
music returns, warmer, under "check it free".
Almanac 002.006.004: "Start with authentication... You can check your setup with our free SPF checker and DMARC generator... If someone hasn't opened in 90 days, move them to a re-engagement flow or suppress them entirely." And: "you can't force primary inbox placement... Focus on sending valuable content to engaged subscribers."
the two checks stay two separate sentences for two separate signals. Sending only to engaged people is never implied to fix authentication, and neither one is a promise of primary placement. The line lands on raised chances, not a result. No inbox-placement guarantee, ever.
ends on a decision, not a number (voice guide section 6). It hands the viewer the two moves the Almanac itself hands them, in the Almanac's own order, and names the honest ceiling on both.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor-phrase list (voice guide sections 2 and 3). The destination is reviewmyemails.com/get-started, the confirmed cluster CTA target that resolves. See "Needs YT's yes" on the launch wording only, the destination itself is settled.
V913What SPF actually is
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the earlier Almanac scripts.
- Keep or cut the trio beat (shot 5). It is faithful to the answer, which insists you need all three, and it seeds the DKIM and DMARC videos in the series.
- The SPF checker as the in-video funnel, and its URL. Shot 6 sends the viewer to the free SPF checker at reviewmyemails.com/tools/spf-checker, taken from the Almanac answer's own closing line, and the end card carries the app at...
- The end-card offer wording. The standing offer is 1,000 addresses cleaned free (BIBLE section 3), but this is an SPF explainer, and list cleaning is a different service from SPF.
01 · The hook · 0:00
On screen: paper. Two identical from-lines stacked, mono, large: From: billing@inkwell-tide.example and From: billing@inkwell-tide.example. One tagged in teal, small: you. The other tagged in suppress red: not you. Above them, Lora, ink, big: "Which one is really you?"
Anyone can type your address into the from line of an email. So how does the inbox on the other end know which one is really you?
02 · The one-line answer · 0:05
On screen: the two lines resolve into a single plain card titled "Allowed to send as inkwell-tide.example", with a short checkmarked list under it, mono: your email tool, your own mail server. A small stamp in the corner: published once. No raw record syntax on screen.
This is what SPF is. It is a list you publish once at your domain, naming the servers that are allowed to send email as you.
03 · The check · 0:13
On screen: four steps animate left to right. One, an envelope arrives stamped from: inkwell-tide.example. Two, the receiving server pulls up the card from shot 2. Three, it holds the actual sending server against the list. Four, a stamp lands, PASS in keep green when the sender is on the list, FAIL in suppress red when it is not.
Here is what happens. A message shows up claiming to be you, the receiving server looks up the list you published and checks the server that actually sent it, and if that server is on your list it passes, and if it is not, it fails.
04 · The honest caveat · 0:25
On screen: the FAIL stamp holds, but the envelope is not deleted or binned. A small meter labelled trust in this message ticks down one notch, not to zero. A dim note beneath it: depends on your other settings and the receiver.
A fail does not automatically bin your email. It is a mark against it. What happens next depends on your other authentication settings and the receiver's own rules.
05 · One of three · 0:34
On screen: three plain pillars rise, mono labels: SPF, DKIM, DMARC. One short job under each, in Lora: checks the sending server, signs the message, decides what to do on a fail. The SPF pillar lights teal as it is named.
And SPF is only one of three. SPF checks the sending server. DKIM signs the message. DMARC decides what to do when a check fails. You need all three.
06 · The decision · 0:42
On screen: the free SPF checker, plain, a single field with a domain typed in, and a green pass reading back beneath it. Small in mono: reviewmyemails.com/tools/spf-checker. Beside it: about 30 seconds.
So do not guess whether yours is set up right. Check it. Our free SPF checker reads your record in about thirty seconds, just type your domain.
07 · End card · 0:50
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get started", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-003.001.001-what-is-spf.md
01 · The hook
Almanac ids in this scene: 003.001.001
paper. Two identical from-lines stacked, mono, large: From: billing@inkwell-tide.example and From: billing@inkwell-tide.example. One tagged in teal, small: you. The other tagged in suppress red: not you. Above them, Lora, ink, big: "Which one is really you?"
no music yet. Room tone only.
Almanac 003.001.001: "someone tries to send an email with your domain in the 'from' field" and "the receiving server has to decide: is this message actually from who it claims to be from?"
the address is invented, never a real one, never a client's. No spoofing or phishing language beyond what this answer gives, which is only "someone tries to send an email with your domain," so the frame stays at that plain level.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Two identical lines and one question is an itch a curious person cannot leave alone.
02 · The one-line answer
Almanac ids in this scene: 003.001.001
the two lines resolve into a single plain card titled "Allowed to send as inkwell-tide.example", with a short checkmarked list under it, mono: your email tool, your own mail server. A small stamp in the corner: published once. No raw record syntax on screen.
a low pulse comes in under the card.
Almanac 003.001.001: "SPF (Sender Policy Framework) is a DNS record that lists which servers are allowed to send email on behalf of your domain. You publish it once in your DNS, and from that point on, receiving servers can check it."
the answer's "In short" box carries RFC 7208, the TXT record, the SMTP transaction and DMARC alignment. All of that is cut from what is spoken and shown, on purpose, to keep the definition plain per this ticket's angle. "DNS record" is spoken as "a list you publish at your domain," which is the same fact without the jargon.
give the viewer the one-sentence definition early, so everything after it is just the list being shown at work rather than a lecture building toward a point.
03 · The check
Almanac ids in this scene: 003.001.001
four steps animate left to right. One, an envelope arrives stamped from: inkwell-tide.example. Two, the receiving server pulls up the card from shot 2. Three, it holds the actual sending server against the list. Four, a stamp lands, PASS in keep green when the sender is on the list, FAIL in suppress red when it is not.
music settles into a steady bed as the four steps build.
Almanac 003.001.001: "someone tries to send an email with your domain in the 'from' field. The receiving server looks up your DNS, finds your SPF record, and checks whether the sending server's IP is on your approved list. If it is, the message passes SPF. If it isn't, it fails."
"looks up your DNS, finds your SPF record" is spoken plainly as "looks up the list you published." The IP address is spoken as "the server that actually sent it," no DNS jargon on the soundtrack, per the angle.
the answer's own step sequence is already the visual. This is the spine of the whole piece, so it carries the longest sentence in the script, paced to walk through the four steps one at a time.
04 · The honest caveat
Almanac ids in this scene: 003.001.001
the FAIL stamp holds, but the envelope is not deleted or binned. A small meter labelled trust in this message ticks down one notch, not to zero. A dim note beneath it: depends on your other settings and the receiver.
the bed thins to a single held note as the meter drops.
Almanac 003.001.001: "An SPF failure doesn't automatically mean your email gets blocked. What happens next depends on your DMARC policy and the receiving server's own rules. But failing SPF is a mark against your message, especially when combined with other weak signals."
no inbox-placement guarantee, and the reverse holds too, a pass is never sold as a guaranteed inbox. "DMARC policy" is spoken plainly here as "your other authentication settings," because DMARC gets named properly in the next shot.
this keeps the video honest. SPF is a signal, not a verdict, and saying so is the firemen-not-salesmen move, it lowers the panic instead of raising it.
05 · One of three
Almanac ids in this scene: 003.001.001
three plain pillars rise, mono labels: SPF, DKIM, DMARC. One short job under each, in Lora: checks the sending server, signs the message, decides what to do on a fail. The SPF pillar lights teal as it is named.
three soft notes, one as each pillar rises.
Almanac 003.001.001: "SPF works alongside DKIM and DMARC as part of the email authentication trio. SPF verifies the sending server. DKIM signs the message content. DMARC tells receivers what to do when either of those checks fail. You really do need all three."
DKIM and DMARC are named but not explained, one plain clause each, no jargon spoken. "Review My Emails" is spelled out in any on-screen or caption copy, never the initials.
the answer insists on all three, so leaving the trio out would let SPF read as enough on its own, which the Almanac flatly denies. Naming them also seeds the next videos in the series.
06 · The decision
Almanac ids in this scene: 003.001.001
the free SPF checker, plain, a single field with a domain typed in, and a green pass reading back beneath it. Small in mono: reviewmyemails.com/tools/spf-checker. Beside it: about 30 seconds.
music returns, warmer, under the green pass.
Almanac 003.001.001: "If you're not sure whether your SPF record is set up correctly, you can check it in 30 seconds with our free SPF checker."
the free SPF checker reads what is already published, it is a check and never a fix, and it is never a promise of inbox placement. Nothing here implies the checker or any other Review My Emails service sets up your SPF for you.
ends on a decision, not a number (voice guide section 6). It hands the viewer the exact next move the Almanac itself hands them, which is the funnel this video is built to feed, the free SPF checker.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get started", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
none. Product offer, not an Almanac fact, the 1,000 free credits are BIBLE section 3.
the end card is the app, and the app is not an SPF fix. The SPF move already happened in shot 6 at the free checker. The cut between shot 6 and this card gives the two a clear beat of separation, so the list-cleaning offer is never read as fixing SPF, per the hard rule that list validation does not fix SPF, DMARC, MX or blocklist problems. The end card carries no inbox promise. The CTA destination reviewmyemails.com/get-started is the confirmed cluster CTA. See "Needs YT's yes" on the offer wording.
the standing app CTA closes the piece, sitting after the SPF checker rather than in place of it.
V914How does SPF work?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Whether to point the description at the free SPF checker named in the source, or the clean-list link.
01 · The hook · 0:00
On screen: paper. An email arrives at a door marked Gmail. A bouncer holds a clipboard titled "Are you really allowed to send for this domain?"
Every email that arrives gets one question at the door. Is this sender actually allowed to send for that domain? SPF is the first check that answers it.
02 · SPF is a guest list · 0:07
On screen: a DNS record unrolls as a guest list, mono lines: ip4: a specific server, include: a service that sends for you, mx: your mail servers.
SPF is a public list you publish in your domain settings. It names every server allowed to send email for you. A specific address, the sending range of a service you use, your own mail servers. That is the guest list.
03 · The check at the door · 0:22
On screen: an incoming server's IP is held up against the list. A green pass when it matches, then a split showing ~all, soft fail, suspicious but accept and -all, hard fail, reject.
When your message lands at Gmail or Outlook, the receiving server looks up that list and checks whether the server it is talking to is on it. On the list, it passes. Not on the list, it soft fails, which means suspicious but let through, or hard fails, which means reject.
04 · The catch that trips people · 0:34
On screen: two "from" labels, mono: envelope from, what SPF checks and visible From, what you see. A spoofer passes the first while showing a different second.
Here is the catch almost everyone misses. SPF checks the hidden envelope address, not the from name you actually see in your inbox. So a spoofer can pass SPF and still show your recipients a completely different from. That gap is exactly why DMARC exists.
05 · The decision · 0:44
On screen: one clean SPF record with a correct ending qualifier, and a DMARC badge clicking into place beside it.
So publish one SPF record that lists everyone who sends for you, end it with the right qualifier, and pair it with DMARC. SPF is the guest list, DMARC checks the name on the door.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-003.001.004-how-spf-works.md
01 · The hook
paper. An email arrives at a door marked Gmail. A bouncer holds a clipboard titled "Are you really allowed to send for this domain?"
room tone.
it frames SPF as a doorman check, which the whole video pays off.
02 · SPF is a guest list
Almanac ids in this scene: 003.001.004
a DNS record unrolls as a guest list, mono lines: ip4: a specific server, include: a service that sends for you, mx: your mail servers.
Almanac 003.001.004: "The SPF record contains a list of authorized servers, written as mechanisms: things like ip4... include... or mx."
03 · The check at the door
Almanac ids in this scene: 003.001.004
an incoming server's IP is held up against the list. A green pass when it matches, then a split showing ~all, soft fail, suspicious but accept and -all, hard fail, reject.
Almanac 003.001.004: "The receiving server checks whether the IP address it's actually talking to matches any of them... ~all means soft fail... -all means hard fail (reject or heavily penalize it)."
04 · The catch that trips people
Almanac ids in this scene: 003.001.004
two "from" labels, mono: envelope from, what SPF checks and visible From, what you see. A spoofer passes the first while showing a different second.
Almanac 003.001.004: "SPF validates the envelope from domain, not the visible from header... a spoofer can pass SPF while still showing a different From to your recipients."
05 · The decision
Almanac ids in this scene: 003.001.004
one clean SPF record with a correct ending qualifier, and a DMARC badge clicking into place beside it.
Almanac 003.001.004: "DMARC checks whether SPF and DKIM actually align with the visible From domain."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V915How DKIM signing works
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "seal cracks" device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. An envelope gets a glowing wax seal pressed onto it, mono label: DKIM-Signature. Lora: "Proof it is really you."
SPF says which servers may send for you. DKIM does something different. It stamps a tamper-proof seal on every email, and that seal proves two things at once.
02 · Your server stamps the seal · 0:07
On screen: the message runs through a hash, mono body hash, SHA-256, bh=, then a private key stamps a signature, mono b=. A caption: "Only your private key can make this seal."
As your email leaves, your server takes the message, runs it through a hash, and then signs it with a private key that only you hold. That signature gets written into the email as the DKIM signature. Nobody else can forge it, because nobody else has your private key.
03 · The receiver checks the seal · 0:22
On screen: the receiving server reads a selector, looks up a public key in DNS at selector._domainkey, and matches it against the seal. A green check.
On the other end, the receiving server reads which key you used, looks up your public key published in your domain settings, and checks the seal against it. If it matches, the email really came from you.
04 · The seal breaks if touched · 0:34
On screen: a message is altered in transit, its recomputed body hash no longer matches bh=, and the seal visibly cracks, red DKIM fail.
Here is the clever part. The receiver also recomputes the hash of the message body and compares it to the one inside the seal. If a single thing was changed along the way, the hashes do not match and the seal breaks. So DKIM proves it is you, and that nothing was tampered with in transit.
05 · The decision · 0:44
On screen: a DKIM key clicks into place beside SPF, and a DMARC badge lights up over both.
So turn DKIM on, sign every send, and let it feed DMARC alongside SPF. Three checks, one story that you are really you.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-003.002.004-how-dkim-works.md
01 · The hook
paper. An envelope gets a glowing wax seal pressed onto it, mono label: DKIM-Signature. Lora: "Proof it is really you."
room tone.
it separates DKIM from SPF and sets up the two-part payoff.
02 · Your server stamps the seal
Almanac ids in this scene: 003.002.004
the message runs through a hash, mono body hash, SHA-256, bh=, then a private key stamps a signature, mono b=. A caption: "Only your private key can make this seal."
Almanac 003.002.004: "the body is hashed with SHA-256 and written to the bh= tag... the selected headers... are signed with the private key and the result goes into b=."
03 · The receiver checks the seal
Almanac ids in this scene: 003.002.004
the receiving server reads a selector, looks up a public key in DNS at selector._domainkey, and matches it against the seal. A green check.
Almanac 003.002.004: "the receiver fetches the public key at selector._domainkey.domain to verify... the server reads the selector, looks up the public key, verifies the signature."
04 · The seal breaks if touched
Almanac ids in this scene: 003.002.004
a message is altered in transit, its recomputed body hash no longer matches bh=, and the seal visibly cracks, red DKIM fail.
Almanac 003.002.004: "recomputes the body hash, and checks that everything matches. If it does, DKIM passes... canonicalization normalizes headers and body... so trivial whitespace changes don't break the hash."
05 · The decision
Almanac ids in this scene: 003.002.004
a DKIM key clicks into place beside SPF, and a DMARC badge lights up over both.
Almanac 003.002.004: "If it does, DKIM passes and the result feeds into DMARC evaluation."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V916SPF and DKIM done, still getting spoofed
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- The end-card CTA here is "Check my email" (auth-first) rather than "Get my list cleaned", confirm that fit for an authentication video, or keep the standard cleaning CTA.
01 · The hook · 0:00
On screen: paper. Two green ticks, mono: SPF ok, DKIM ok. Below, red, Lora: "So why is someone still sending as you?"
You set up SPF. You set up DKIM. And a phishing email still went out looking like it came from you. Here is the gap nobody warned you about.
02 · The gap · 0:06
On screen: an envelope. The technical "from" address underneath is fine and green. The big display name at the top, what a human reads, is a fake, and it is unchecked.
Here is the catch. SPF and DKIM check the plumbing underneath. Neither one checks whether that matches the name your reader actually sees at the top of the email. A spoofer lives in that gap.
03 · What DMARC does · 0:18
On screen: a third check appears, DMARC, doing two jobs shown as two icons: a magnifier over "does it match" and a switch with three settings.
DMARC does two things. First, alignment. It checks the name people see actually matches the domain that passed. Second, policy. You tell mailbox providers what to do with the fakes. Just report them, send them to spam, or reject them outright.
04 · The bonus · 0:34
On screen: a daily report lands, a list of every source sending under your domain, one flagged red as "not you".
And here is the part people love. DMARC sends you a daily report of everyone sending email using your domain. That report is usually how a business first discovers someone faking them.
05 · The decision · 0:42
On screen: one card: "start on report-only" over a teal button.
So start DMARC on report-only, watch who is really sending as you, then tighten it. Read those reports with our free tools before you turn the policy up.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Check your setup free." CTA in teal, "Check my email", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-003.003.001-what-is-dmarc.md
01 · The hook
paper. Two green ticks, mono: SPF ok, DKIM ok. Below, red, Lora: "So why is someone still sending as you?"
room tone.
it names the exact false comfort SPF and DKIM give.
02 · The gap
Almanac ids in this scene: 003.003.001
an envelope. The technical "from" address underneath is fine and green. The big display name at the top, what a human reads, is a fake, and it is unchecked.
Almanac 003.003.001: "neither SPF nor DKIM check whether the signing or sending domain actually matches what your recipients see in the From header. That's the gap DMARC fills."
03 · What DMARC does
Almanac ids in this scene: 003.003.001
a third check appears, DMARC, doing two jobs shown as two icons: a magnifier over "does it match" and a switch with three settings.
Almanac 003.003.001: "DMARC is a policy layer that sits on top of SPF and DKIM. It does two things: alignment and policy... p=none... p=quarantine... p=reject."
the record syntax and RFC number stay off screen, this is a plain explainer.
04 · The bonus
Almanac ids in this scene: 003.003.001
a daily report lands, a list of every source sending under your domain, one flagged red as "not you".
Almanac 003.003.001: "Every day, inbox providers that support DMARC send aggregate XML reports showing you who's sending email using your domain... often how organizations first discover unauthorized senders using their domain."
05 · The decision
Almanac ids in this scene: 003.003.001
one card: "start on report-only" over a teal button.
Almanac 003.003.001: "This starts collecting reports without affecting mail flow. You can parse these reports with our free DMARC parser."
ends on a decision. No inbox-placement guarantee. DMARC is spoken as anti-spoofing and reporting, never as a promise of inbox placement.
06 · End card
logo lockup, never an octopus. "Check your setup free." CTA in teal, "Check my email", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V917Is open rate still a useful metric?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "pixel loads on its own" device in shot 2, or a simpler swap.
01 · The hook · 0:00
On screen: paper. A big open-rate number ticking up, 42%, with a green up-arrow, then a small red label slides in beneath: "and it means less than you think."
Your open rate went up. Before you celebrate, know this. That number broke a few years ago, and it has been flattering you ever since.
02 · What broke it · 0:07
On screen: a tiny tracking pixel loads on its own inside a closed, unread email. Caption, mono: Apple Mail Privacy Protection, 2021. A meter jumps up with nobody touching it.
In twenty twenty-one, Apple Mail Privacy Protection started pre-loading the tracking pixel in the background, whether or not anyone actually opened the message. For senders with a big Apple audience, open rates jumped five to twenty points overnight and never came back down.
03 · What it is still good for · 0:24
On screen: two panels. Left, teal, useful: a line chart, last month versus this month, same list. Right, grey, not useful: a single big percentage with a question mark.
So it is not useless. If your open rate was thirty percent last month and fifteen this month, something changed, and that is worth chasing. The trend on the same audience still tells you something. The raw number on its own does not.
04 · What to trust instead · 0:36
On screen: three chips light up in teal: clicks, click to open rate, replies. A caption reads "a human had to do something."
What is honest now. Clicks, click-to-open rate, and replies. Each one takes a real human action, so it is much harder to inflate, and it tells you who actually cared.
05 · The decision · 0:44
On screen: the open-rate number shrinks to a small trend line in the corner, and the clicks and replies chips move to centre stage.
So keep the open rate as a trend line, and judge the campaign on clicks and replies.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-004.001.007-is-open-rate-still-useful.md
01 · The hook
paper. A big open-rate number ticking up, 42%, with a green up-arrow, then a small red label slides in beneath: "and it means less than you think."
room tone.
it takes a metric they trust and puts a crack in it, so they lean in.
02 · What broke it
Almanac ids in this scene: 004.001.007
a tiny tracking pixel loads on its own inside a closed, unread email. Caption, mono: Apple Mail Privacy Protection, 2021. A meter jumps up with nobody touching it.
Almanac 004.001.007: "Apple Mail started pre-loading tracking pixels in the background (regardless of whether anyone actually opened the email)... Open rates for many senders jumped 5-20 percentage points overnight and never came back down."
03 · What it is still good for
Almanac ids in this scene: 004.001.007
two panels. Left, teal, useful: a line chart, last month versus this month, same list. Right, grey, not useful: a single big percentage with a question mark.
Almanac 004.001.007: "Directional trends on the same audience... You can't read the absolute number, but the relative change is still meaningful."
04 · What to trust instead
Almanac ids in this scene: 004.001.007
three chips light up in teal: clicks, click to open rate, replies. A caption reads "a human had to do something."
Almanac 004.001.007: "Click rate, click-to-open rate (CTOR), and reply rate are now stronger engagement signals because they require deliberate human action."
05 · The decision
Almanac ids in this scene: 004.001.007
the open-rate number shrinks to a small trend line in the corner, and the clicks and replies chips move to centre stage.
Almanac 004.001.007: "Don't abandon open rate tracking entirely. Just don't let an inflated number fool you."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V918Hard bounces vs soft bounces
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the SMTP-code labels on screen, or drop them for a cleaner look.
01 · The hook · 0:00
On screen: paper. Two returned envelopes side by side, one stamped red permanent, one stamped amber try again later. Lora: "Not the same problem."
Two emails bounced back. They look identical, and treating them the same is one of the fastest ways to hurt your sending. Here is how they differ.
02 · The hard bounce · 0:06
On screen: the red envelope opens, mono reasons: address does not exist, domain expired, mailbox deleted, tagged 5xx, permanent. A suppress switch flips on.
A hard bounce is permanent. The address does not exist, the domain expired, the mailbox was deleted. There is no point retrying it, ever. Your email tool should suppress a hard-bounced address immediately, and if it does not, you do it yourself.
03 · Why hard bounces bite · 0:20
On screen: a reputation meter drops one notch each time a red envelope is kept and re-sent.
This is the one that actually costs you. Keep mailing addresses that hard bounce and you tell the mailbox providers you do not know who is on your list. That is the accumulation that drags your sender reputation down.
04 · The soft bounce · 0:30
On screen: the amber envelope, mono reasons: mailbox full, 452, server overloaded, rate limited, tagged 4xx, temporary. A retry clock spins 24 to 72 hours.
A soft bounce is temporary. The mailbox was full, the server was busy, your sending got rate limited. The tool just retries these for a day to three days, and most sort themselves out.
05 · The decision · 0:40
On screen: a calendar shows the same address soft bouncing week after week, then it gets moved onto the suppression list alongside the hard bounces.
But watch the ones that soft bounce again and again for weeks. That is usually an abandoned mailbox, and it belongs on your suppression list just like a hard bounce. So suppress the permanent ones now, and cut the repeat stallers too.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-004.004.002-hard-vs-soft-bounces.md
01 · The hook
paper. Two returned envelopes side by side, one stamped red permanent, one stamped amber try again later. Lora: "Not the same problem."
room tone.
it sets up the single distinction the whole video turns on.
02 · The hard bounce
Almanac ids in this scene: 004.004.002
the red envelope opens, mono reasons: address does not exist, domain expired, mailbox deleted, tagged 5xx, permanent. A suppress switch flips on.
Almanac 004.004.002: "A hard bounce is permanent. The address doesn't exist, the domain has expired, or the mailbox was deleted... Your ESP should suppress hard-bounced addresses immediately, and if it doesn't, do it manually."
03 · Why hard bounces bite
Almanac ids in this scene: 004.004.002
a reputation meter drops one notch each time a red envelope is kept and re-sent.
Almanac 004.004.002: "Hard bounces are the ones that actually damage your sender reputation if you keep accumulating them."
04 · The soft bounce
Almanac ids in this scene: 004.004.002
the amber envelope, mono reasons: mailbox full, 452, server overloaded, rate limited, tagged 4xx, temporary. A retry clock spins 24 to 72 hours.
Almanac 004.004.002: "A soft bounce is temporary... the inbox is full (452 error), the server is temporarily overloaded, or the receiving domain is rate-limiting your IP. Most ESPs retry soft bounces for 24-72 hours."
05 · The decision
Almanac ids in this scene: 004.004.002
a calendar shows the same address soft bouncing week after week, then it gets moved onto the suppression list alongside the hard bounces.
Almanac 004.004.002: "watch for addresses that soft bounce repeatedly over weeks... Consistent soft bouncers belong on a suppression list just like hard bounces."
ends on a decision. No inbox-placement guarantee, no bounce-rate threshold spoken.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V919What email list hygiene actually is
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "info at and support at" spoken form, or show them on screen only.
01 · The hook · 0:00
On screen: paper. Big Lora line: "Cleaning your list once does nothing." Below, mono: it is a habit, not an event.
Cleaning your list one time does almost nothing. Hygiene is a habit, and here is what it actually is.
02 · What it is · 0:05
On screen: a list of addresses. Three keep their colour, others fade as the VO names them.
List hygiene is keeping your list accurate, permission based, and free of the addresses that drag your sending down. Dead addresses that bounce. People who stopped opening months ago. Shared inboxes like info at and support at. Typos from your own signup form.
03 · Why it matters · 0:16
On screen: the whole list, then one arrow: a few bad addresses, and the WHOLE list tilts toward a "SPAM" label.
Here is the part that catches people. Mailbox providers judge you by who you send to. A list full of dead weight tells them you do not know or care who is on it, and that pushes more of your mail to spam, for everyone, not just the bad addresses.
04 · The good news · 0:34
On screen: four small habit cards appear: validate at signup, auto-suppress bounces, re-engage or sunset the quiet ones, full clean before a big send.
The good news is it is not constant manual work. Validate addresses when they sign up, suppress bounces automatically, re-engage or retire the quiet ones, and run a full clean before any big send.
05 · The decision · 0:42
On screen: one card: "not cleaned in a while?" over a teal button.
If your list has not been cleaned in a while, do it before your next big campaign, not after it costs you.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.001.001-what-is-list-hygiene.md
01 · The hook
paper. Big Lora line: "Cleaning your list once does nothing." Below, mono: it is a habit, not an event.
room tone.
it corrects the one-time-cleanup belief in the first breath.
02 · What it is
Almanac ids in this scene: 005.001.001
a list of addresses. Three keep their colour, others fade as the VO names them.
Almanac 005.001.001: "the ongoing practice of keeping your subscriber database accurate, permission-based, and free of addresses that will hurt your deliverability... removing addresses that hard bounce... role accounts like info@ and support@... syntax errors or typos."
the Almanac names spam traps and Spamhaus in this list. Cut, marketing surface.
03 · Why it matters
Almanac ids in this scene: 005.001.001
the whole list, then one arrow: a few bad addresses, and the WHOLE list tilts toward a "SPAM" label.
Almanac 005.001.001: "mailbox providers judge senders by the quality of who they send to... that signal pushes more of your mail toward spam folders, for everyone, not just the bad addresses."
this is the whole point, so it carries the longest sentence in the script.
04 · The good news
Almanac ids in this scene: 005.001.001
four small habit cards appear: validate at signup, auto-suppress bounces, re-engage or sunset the quiet ones, full clean before a big send.
Almanac 005.001.001: "proactive practices baked into your sending workflow: validating addresses at the point of capture, suppressing bounces automatically, setting re-engagement thresholds, and running a full list clean on any list that has been dormant or purchased."
05 · The decision
Almanac ids in this scene: 005.001.001
one card: "not cleaned in a while?" over a teal button.
Almanac 005.001.001: "if your list has not been cleaned in a while, our done-for-you list cleaning service is worth a look before your next big campaign."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V920Why list hygiene matters for deliverability
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first two Almanac scripts.
- Whether the illustrative 40,000 versus 15,000 pair is safe to carry as the driving hook number. The Almanac states it as an example inside a sentence about the commercial cost of sending to a dirty list, not as a claim about any real...
- Keep both secondary beats (shots 5 and 6) or trim toward the tighter end of the locked 0:45 to 0:55 band. As drafted the script runs about 0:52.
01 · The hook · 0:00
On screen: paper. Large mono number top centre: 40,000 with the small label subscribers beneath it. As the VO lands on "real," roughly two thirds of the number desaturates into pale grey dots that drift off screen, leaving 15,000 glowing in ink.
You have forty thousand subscribers. Only fifteen thousand of them are real.
02 · The myth · 0:05
On screen: the 40,000 figure returns, small, with a thought-bubble style tag beside it, = more reach, that gets a single strike through it.
More subscribers should mean more reach. That is not how mailbox providers see it.
03 · The signals build · 0:12
On screen: two gauges build side by side beneath the number, one per line of VO, each a mono label with a small dial that climbs into a red band. - bounce rate with addresses that don't exist - engagement with subscribers who never open
Every address that no longer exists comes back as a bounce, every subscriber who quietly stopped opening reads as the same warning in a different shape, and mailbox providers treat both as proof you do not actually know who is still there.
04 · The turn, shared reputation · 0:26
On screen: the two gauges collapse into a single shared dial labelled domain reputation. It swings into red. Around it, a row of small identical envelope glyphs, standing in for future campaigns, flip one by one from teal to grey.
Both signals feed one score, your domain reputation. And once that drops, it is not just the campaign that caused it. Every email after it inherits the damage.
05 · The money · 0:34
On screen: 15,000 holds steady in teal on one side. Beside it, 25,000 sits in a dimmed grey box with a small mono tag underneath, still billed.
You are still paying to send to the twenty five thousand dragging you down. Fewer real sends costs less and reads better.
06 · The decision · 0:41
On screen: a short horizontal timeline with two markers, cleaned every 6 months and left a year. A shaded wedge between them widens as the VO plays.
Leave it a year and the gap only gets wider. Clean it now, and it stays small.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.001.002-why-hygiene-matters.md
01 · The hook
paper. Large mono number top centre: 40,000 with the small label subscribers beneath it. As the VO lands on "real," roughly two thirds of the number desaturates into pale grey dots that drift off screen, leaving 15,000 glowing in ink.
no music yet. Room tone only.
"Sending to 40,000 subscribers when only 15,000 are real and engaged means you are spending money to damage your own deliverability."
the numbers are the Almanac's own illustrative pair, not invented and not a claim about any real client's list. No client is named or implied.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Watching two thirds of a number you were proud of turn to dust is the itch nobody scrolls past.
02 · The myth
the 40,000 figure returns, small, with a thought-bubble style tag beside it, = more reach, that gets a single strike through it.
a low pulse begins under the strike.
"Mailbox providers judge senders by who they send to, not just what they send."
names the assumption out loud before correcting it, so the correction reads as a reveal, not a scolding. Curiosity over accusation.
03 · The signals build
two gauges build side by side beneath the number, one per line of VO, each a mono label with a small dial that climbs into a red band. - bounce rate with addresses that don't exist - engagement with subscribers who never open
music settles into a steady bed as the dials rise.
"when you send to addresses that do not exist, you get hard bounces. High bounce rates tell mailbox providers your list is old or poorly maintained... When a large portion of your list never engages, providers interpret that as evidence that recipients do not want your email." Also: "A list full of dead addresses, abandoned inboxes, and disengaged subscribers is evidence that you do not know or care about your audience."
the Almanac names a third signal here, spam trap hits, which it says trigger Spamhaus and SURBL listings. Cut. Spam-trap claims and blocklist names are off limits on marketing surfaces, so this beat runs on two signals, not three. The Almanac's own "roughly 2 percent" hard-bounce threshold is also not shown or spoken, for the same reason the gold-standard script kept its complaint figure off screen. A number like that belongs on the Almanac page, not a marketing surface.
naming both real signals honestly is what makes the shared-score beat land as mechanism, not a scare tactic.
04 · The turn, shared reputation
the two gauges collapse into a single shared dial labelled domain reputation. It swings into red. Around it, a row of small identical envelope glyphs, standing in for future campaigns, flip one by one from teal to grey.
the bed thins to a single held note as the dial turns red.
"Each of these signals feeds into your sender reputation. Specifically, your domain reputation, which is now the primary signal most major providers use. Once domain reputation degrades, it affects all your sending, not just the campaign that triggered the problem."
this is the actual point of the video. A shared score, not a per-campaign judgment, is the reason a clean send can still suffer because of a dirty one sent last month.
05 · The money
15,000 holds steady in teal on one side. Beside it, 25,000 sits in a dimmed grey box with a small mono tag underneath, still billed.
a single soft tick per word on "still billed."
"The commercial argument is simpler: you pay per send on most platforms... Clean the list and send to fewer people for better results at lower cost."
no dollar figure, discount percentage, or ROI number is invented. The only numbers on screen are the Almanac's own 40,000 and 15,000, already used in shot 1.
pairs the reputation cost with the plain financial one, matching the Almanac's own two-track argument rather than picking just the scarier half.
06 · The decision
a short horizontal timeline with two markers, cleaned every 6 months and left a year. A shaded wedge between them widens as the VO plays.
music returns, warmer, under "clean it now."
"The timeline for damage compounds. A list that has not been cleaned in a year will have meaningfully more dead addresses and decayed engagement than one cleaned every six months... Proactive hygiene costs less in the long run than reactive cleanup after deliverability has already dropped."
the Almanac's own sentence here also lists "potential trap hits" as a third thing that compounds. Cut, same reasoning as shot 3. No inbox-placement promise is made, this is a cost-of-delay statement, not a guarantee of where mail lands.
ends on a decision, not a number (voice guide section 6). The choice is "now, small" against "later, wider," not a statistic to remember.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the CTA wording the first Almanac script in the series established rather than a generic "start for free," which is on the forbidden competitor list. The destination /get-started is the confirmed CTA target (CLAUDE.md rule 5, the 2026-09-21 launch-messaging decision), used here without re-flagging it.
V921How often should you actually clean your list
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Show the volume tiers as three cards, or animate them one replacing the next.
01 · The hook · 0:00
On screen: paper. Big Lora: "How often should you clean your list?" Below, mono: everyone says "regularly". here is the real answer.
How often should you clean your list. Everyone says regularly, which helps no one. Here is the actual answer.
02 · Why it moves · 0:06
On screen: a fresh list slowly speckles with grey dead addresses over a "2 years" timeline.
Your list decays whether you touch it or not. People change jobs, abandon inboxes, let domains lapse. The list you built two years ago has real dead weight in it today, even if you did everything right.
03 · The three tiers · 0:14
On screen: three stacked cards, each a volume band and a cadence, building as the VO names them. - high volume, over 100k a month over monthly - medium, 10k to 100k over quarterly - lower, under 10k over every six months
It scales with how much you send. Over a hundred thousand a month, review it monthly. Ten to a hundred thousand, quarterly. Under ten thousand, every six months at the least. Higher volume means the damage compounds faster, so you check more often.
04 · The triggers · 0:32
On screen: the calendar fades, three event cards flash: just imported a list, bounces spiked, first send after months quiet.
The calendar is the floor, not the ceiling. Clean the moment you import or buy a list, right after a campaign where bounces spiked, and before your first send if you have been quiet for months.
05 · The decision · 0:42
On screen: one card: "older than a year and never cleaned?" over a teal button.
So find your tier, mark those triggers, and if your list is over a year old and has never been cleaned, do it before the next send, not after it costs you.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.001.003-how-often-clean-list.md
01 · The hook
paper. Big Lora: "How often should you clean your list?" Below, mono: everyone says "regularly". here is the real answer.
room tone.
it calls out the useless advice and promises a specific one.
02 · Why it moves
Almanac ids in this scene: 005.001.003
a fresh list slowly speckles with grey dead addresses over a "2 years" timeline.
Almanac 005.001.003: "Email addresses decay at roughly 20-30% per year... A list you built two years ago has meaningfully more bad addresses in it today than it did the day you built it, even if you haven't done anything wrong."
the exact decay percentage is kept off screen and spoken as "real dead weight", the cadence is the point.
03 · The three tiers
Almanac ids in this scene: 005.001.003
three stacked cards, each a volume band and a cadence, building as the VO names them. - high volume, over 100k a month over monthly - medium, 10k to 100k over quarterly - lower, under 10k over every six months
Almanac 005.001.003: "high-volume senders (100K+ per month) should verify monthly, medium-volume senders (10K to 100K) quarterly, and low-volume senders (under 10K) at least every six months."
04 · The triggers
Almanac ids in this scene: 005.001.003
the calendar fades, three event cards flash: just imported a list, bounces spiked, first send after months quiet.
Almanac 005.001.003: "clean after any of these events: importing a new list or adding a new list source, buying or merging with another business's contacts, any campaign where bounce rate exceeded 2%, or a period of list inactivity."
05 · The decision
Almanac ids in this scene: 005.001.003
one card: "older than a year and never cleaned?" over a teal button.
Almanac 005.001.003: "If your list is older than a year and hasn't been cleaned, or if you're seeing rising bounce rates, we handle this."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V922The hygiene issues that never trip an alert
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two Almanac scripts already drafted (002.001.004, 005.003.016).
- Naming Apple MPP by name on a marketing surface. The Almanac itself names it with a link, so nothing here is off the Almanac-only rule, but it is a specific third-party product feature spoken and shown on screen in a 9-second beat (shot 4).
- Keep or cut shot 4 for runtime. Shots 1, 2, 3, 5 and 6 alone run to about 0:38 to 0:41, under the 0:45 floor of the locked runtime band.
01 · The hook · 0:00
On screen: paper. A dashboard card, mono: 0 bounces / 0 complaints. Under it, stamped in Lora, ink, large: "ALL CLEAR." Below that, dashed and hollow: "Then why is it getting worse?"
Zero bounces. Zero complaints. Your dashboard says the list is fine.
02 · The reason it's lying · 0:05
On screen: the two numbers from shot 1 circle and grey out: 0 bounces, 0 complaints. Beside them, small, mono: "these get reported."
Bounces and complaints get caught because your email tool reports them. The problems that don't report themselves are the ones actually dragging you down.
03 · The three ghosts · 0:11
On screen: three rows build one at a time under the greyed-out dashboard, each a mono label with one line under it: - engagement decay / "opens sometimes, clicks never, never unsubscribes" - role accounts / "info@, sales@, no person behind it" - stale data / "cold before it was ever imported"
Three things your dashboard will never flag. Subscribers who quietly stop opening and clicking but never unsubscribe. Shared inboxes like info@ and sales@ where nobody is actually reading. And addresses that went cold before you even switched email tools, imported with no history attached.
04 · The part that traps people · 0:29
On screen: the dashboard card returns, now reading 20% open rate in mono, circled green. The circle flickers, the number dims, and a caption slides under it, mono, small: "MPP counts some of these automatically."
Here's the trap. A 20% open rate looks fine on the surface. But if Apple MPP is inflating a good chunk of that number, your real engagement is sitting a lot lower than the number at the top of your dashboard right now.
05 · The fix · 0:38
On screen: the three ghost rows from shot 3 return, smaller, under one new label in teal: look at people, not averages.
You don't need a better dashboard. You need to check activity by the individual subscriber, not the campaign average, on a regular schedule. That's how you catch decay before it gets expensive.
06 · End card · 0:46
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.001.009-silent-hygiene-issues.md
01 · The hook
paper. A dashboard card, mono: 0 bounces / 0 complaints. Under it, stamped in Lora, ink, large: "ALL CLEAR." Below that, dashed and hollow: "Then why is it getting worse?"
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A clean report that is hiding a problem is the itch nobody scrolls past.
the dashboard numbers are illustrative only, not a claim about any real account.
02 · The reason it's lying
Almanac ids in this scene: 005.001.009
the two numbers from shot 1 circle and grey out: 0 bounces, 0 complaints. Beside them, small, mono: "these get reported."
low pulse comes in under the grey-out.
Almanac 005.001.009: "The ones that make the most noise, bounces and spam complaints, are actually easier to catch because your ESP reports them. The silent ones do their damage slowly, in the background, until your deliverability is noticeably worse."
"spam complaints" is named once, as the Almanac names it, purely as the noisy counter-example to the silent issues. No complaint-rate number or threshold appears anywhere in this script.
names the wrong place people watch, so the reveal in shot 3 lands as new information rather than a lecture.
03 · The three ghosts
Almanac ids in this scene: 005.001.009
three rows build one at a time under the greyed-out dashboard, each a mono label with one line under it: - engagement decay / "opens sometimes, clicks never, never unsubscribes" - role accounts / "info@, sales@, no person behind it" - stale data / "cold before it was ever imported"
music settles into a steady bed as the three rows land.
Almanac 005.001.009: "Subscribers who were once active gradually stop opening and clicking. They do not unsubscribe. They do not complain... Addresses like info@, sales@, support@, and admin@ are shared inboxes that no individual owns... some of those addresses will have decayed during the gap. The new ESP does not know their history."
"support@" and "admin@" from the Almanac's role-account list are dropped from the spoken line for pace. info@ and sales@ carry the point on screen and in the VO, and both are still invented examples of an account type, never a real address.
naming all three by what they are not, not a bounce, not a complaint, is what makes "silent" concrete instead of abstract. Rhythm note: "Three things your dashboard will never flag." is the under-8-word line for this script (7 words).
04 · The part that traps people
Almanac ids in this scene: 005.001.009
the dashboard card returns, now reading 20% open rate in mono, circled green. The circle flickers, the number dims, and a caption slides under it, mono, small: "MPP counts some of these automatically."
the bed thins to one held note as the circle flickers.
Almanac 005.001.009: "The challenge with silent issues is that standard metrics do not flag them clearly. A 20% open rate looks fine on the surface. But if [Apple MPP] is inflating a significant portion of those opens, the real engagement might be much lower."
the 20 percent figure is the Almanac's own illustrative number, not a claim about any real account and not a threshold of any kind. Apple MPP is named exactly as the source names it, with no added mechanism detail beyond what this answer states.
this is the sting in the tail. A number that looked reassuring in shot 1 gets reopened here and shown to be unreliable, which is the argument in one image. Rhythm note: the third sentence is the over-30-word line for this script (31 words).
05 · The fix
Almanac ids in this scene: 005.001.009
the three ghost rows from shot 3 return, smaller, under one new label in teal: look at people, not averages.
music holds, warmer.
Almanac 005.001.009: "Per-recipient reporting and cohort analysis are the tools that expose silent decay before it compounds... Quarterly reviews of subscriber activity at the individual level, not just campaign averages, are the best way to catch these before they become expensive to fix."
no promise that any tool fixes SPF, DMARC, MX or blocklist problems. This beat is about finding decayed and stale addresses, nothing else. No inbox-placement guarantee.
ends on a decision, not a number (voice guide section 6). It replaces "check your dashboard" with the actual practice the Almanac recommends. Rhythm note: "You don't need a better dashboard." is a second under-8-word line (6 words), bracketing the video's longest sentence in shot 4.
06 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). reviewmyemails.com/get-started is the confirmed CTA destination (CLAUDE.md rule 5), not re-flagged here per the settled cluster facts.
V923The ROI of a clean list
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first two Almanac scripts.
- The launch wording on the end card. RME-16 is still defining which posts read as waitlist, coming-soon, or live.
- Keep or trim the worked-example numbers. Shots 2 and 3 keep the Almanac's own 50,000 / 15,000-contact billing example and the 36-to-1 ratio, because they make the case concrete and are framed as illustrations, not promises.
- Keep or cut shot 4, the recovery-time beat. It is the strongest evidence for why "protect" outweighs "save," but it is not required by the two-sided spine itself and adds about 8 seconds.
01 · The hook · 0:00
On screen: paper. Top, mono, small: 10,000 contacts · billed monthly. Center, Lora, ink, large: "Your list charges you twice." Below, dashed and small: "Once on the invoice. Once in the inbox."
Every month, your email list charges you twice. Once on the invoice. Once in the inbox you never reach.
02 · What you save · 0:06
On screen: a mono ledger builds line by line: 50,000 contacts, then a strike-through -15,000 dead weight, then = 30% of the bill.
Most email tools bill you by the contact. One list: fifty thousand contacts, fifteen thousand of them invalid, unsubscribed, or gone quiet for good. That's thirty percent of the bill, paying for addresses that can never buy anything.
03 · What you protect · 0:16
On screen: the ledger dims. A new mono label rises: sender reputation. Then a large ratio appears: $1 in → $36 back, with a dashed line to small text: *if it reaches the inbox.
Email is famous for a thirty six to one return, every dollar back thirty six times over. But that number assumes the email actually lands in the inbox. Let your reputation slide, and that return is the first thing to go.
04 · The slow bleed · 0:29
On screen: a small clock ticks forward, days then weeks, beside a dimmed inbox row that stays dim.
A burst of hard bounces from a stale list can take days or weeks for your reputation to recover, and while it heals, the subscribers who actually want your emails stop seeing them too.
05 · The decision · 0:37
On screen: the ledger card and the ratio card from shots 2 and 3 shrink and sit side by side, a thin teal rule between them: what you save / what you protect. Both slide toward one mono button: clean it.
So the real question isn't whether a clean list is worth it. It's how much you're already losing by skipping it. Clean the list. Both sides start working for you instead of against you.
06 · End card · 0:46
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.001.010-clean-list-roi.md
01 · The hook
paper. Top, mono, small: 10,000 contacts · billed monthly. Center, Lora, ink, large: "Your list charges you twice." Below, dashed and small: "Once on the invoice. Once in the inbox."
no music yet, room tone only.
the contact count is a round illustrative figure, the same order of magnitude the Almanac uses in its own worked examples, never a real business's number.
the frame is the whole ad. It has to work muted, because the image earns the click (BIBLE section 8). Stating both halves of the cost before any data point lands is what makes the rest of the video feel like proof, not a pitch.
02 · What you save
Almanac ids in this scene: 005.001.010
a mono ledger builds line by line: 50,000 contacts, then a strike-through -15,000 dead weight, then = 30% of the bill.
one mono tick per line item, building a rhythm.
Almanac 005.001.010: "If you're paying for 50,000 contacts but 15,000 of them are invalid, unsubscribed, or completely unengaged, you're paying roughly 30% of your bill for addresses that can't convert."
this is the Almanac's own worked example, spoken as "one list," never as "your list." It states how per-contact billing works, not a guaranteed savings figure.
the save side is countable, so it should feel like arithmetic, not a claim.
03 · What you protect
Almanac ids in this scene: 005.001.010
the ledger dims. A new mono label rises: sender reputation. Then a large ratio appears: $1 in → $36 back, with a dashed line to small text: *if it reaches the inbox.
a bed settles in as the ratio appears.
Almanac 005.001.010: "Email's widely-cited 36-to-1 return on investment (every dollar spent yields roughly $36 in revenue) assumes your emails are actually being seen... The math only works if inbox placement holds up." Also: "A clean list keeps your sender reputation healthy, which keeps your emails landing in the inbox rather than the spam folder."
the Almanac ties a second 30% figure here to disengagement and complaint signals sending mail to spam. That figure is cut, restating it in this shot would read as a complaint-rate threshold, which is banned on marketing surfaces. Only the qualitative claim survives. The 36-to-1 line stays conditional, never a promise of inbox placement.
this is the harder-to-see half of the ROI case, so it gets the number that actually stops a scroll, paired immediately with the condition that makes it fragile.
04 · The slow bleed
Almanac ids in this scene: 005.001.010
a small clock ticks forward, days then weeks, beside a dimmed inbox row that stays dim.
the bed thins to one held note.
Almanac 005.001.010: "A single spam trap hit or a burst of hard bounces from stale addresses can take days or weeks to recover from. During that time, your good subscribers aren't seeing your emails either."
the spam-trap clause is cut per the Stage-1 pre-screen. Only the hard-bounce half of that sentence is spoken. No spam-trap claim appears anywhere in this script.
it is the reason "protect" outweighs "save" in this video's own spine. Cost recovers the moment you stop paying it. Reputation does not.
05 · The decision
Almanac ids in this scene: 005.001.010
the ledger card and the ratio card from shots 2 and 3 shrink and sit side by side, a thin teal rule between them: what you save / what you protect. Both slide toward one mono button: clean it.
music returns, warmer, under "Clean the list."
Almanac 005.001.010: "The ROI case for list cleaning has two sides: what you save and what you protect. Both matter, and most senders underestimate the second one."
no inbox-rate lift percentage or projected order count is shown or spoken here. The Almanac's own 75%-to-90% example reads as a guaranteed outcome on a marketing surface, so it stays off this shot. See "Rules checked."
ends on a decision, not a number (voice guide section 6). It names the fork the whole video has been building toward without doing new math on screen, then closes it.
06 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
CTA destination is the confirmed one for this fan-out (reviewmyemails.com/get-started), per the cluster's settled facts. Not flagged below.
V924What email validation actually checks
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching both existing Almanac scripts and the two Review My Emails video precedents.
- The launch wording on the end card. RME-16 is still defining which posts read as waitlist, coming-soon, or live, and 00-inbox/decisions/2026-09-22-app-live-before-webinar.md confirms the self-serve app is not live yet, it goes live...
- Whether valid, invalid and risky get their own colour treatment. The brand system defines colour only for Review My Emails' own Keep, Monitor, Suppress verdict trio, not for this generic three-word validator result.
01 · The hook · 0:00
On screen: paper. Large mono numbers build in two beats: 10,000 addresses, then smaller beneath, 3 days later, then large again, 800 bounced.
You send to ten thousand addresses. Three days later, eight hundred bounce.
02 · The reasons nobody sees coming · 0:04
On screen: three short mono lines strike in under the 800 figure: address was fake, domain didn't exist, mailbox was full. Then a dashed card: "How would you know, before you send?"
Some were fake. Some didn't exist. Some just had a full mailbox. You find out three days too late.
03 · The mechanism, three checks · 0:09
On screen: the Almanac's own example address appears, large, mono, on a reserved ending: captain@tidalmail.example. Three rows build underneath, one per VO beat, each getting a tick as it resolves: - format correct - domain active, mail servers running - limited SMTP handshake, with a small annotation, does the mailbox answer
Here's how it actually works. First, the shape of the address. Then the domain, is it real, does it have mail servers running. Then a short handshake with the mail server itself, the protocol mail servers use to talk, to see if that mailbox is really there.
04 · The three results · 0:22
On screen: the address clears. Three words land one at a time, ink on paper, no invented colour coding: valid, invalid, risky, each with one mono line underneath. - valid / syntax, active domain, mailbox all check out - invalid / failed at least one of the three - risky / passed most checks, pattern reads like a typo
The tool hands back one of three words. Valid means all three checks came back clean. Invalid means it failed at least one of them. Risky means it passed most of them, but something about the pattern reads like a typo waiting to happen.
05 · The turn, what the result actually promises · 0:33
On screen: everything clears. One line, ink, Lora: "reaches a mailbox." Beneath it, dashed and hollow: "lands in the inbox."
All three checks are about the address itself, its shape, its domain, its mailbox, so what comes back is a prediction that mail sent to it will actually reach a real mailbox, not a promise about where it lands once it gets there.
06 · The decision · 0:42
On screen: two cards side by side. at signup over "catch it as it happens". in bulk over "clean what's already on the list". A thin teal rule between them.
So run it both ways. At signup, to catch a bad address as it happens. In bulk, on the list you already have.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.003.001-what-is-validation.md
01 · The hook
paper. Large mono numbers build in two beats: 10,000 addresses, then smaller beneath, 3 days later, then large again, 800 bounced.
no music yet, room tone only.
"You hit send on a campaign to 10,000 addresses. Three days later, you notice 800 bounces."
no address shown yet, aggregate numbers only, both exact from the Almanac's own scenario.
matches BIBLE section 8, the frame has to work muted and as the thumbnail. A number that begs an explanation is the hook.
02 · The reasons nobody sees coming
three short mono lines strike in under the 800 figure: address was fake, domain didn't exist, mailbox was full. Then a dashed card: "How would you know, before you send?"
a low pulse starts.
"Some of those bounce because the address is fake or inactive. Some bounce because the domain doesn't exist. Some bounce because the mailbox is full or the server's down for the moment. How do you catch these problems before you send?"
names the actual reasons before the tool answers them, so the mechanism shot lands as the answer to a real question, not a feature dump.
03 · The mechanism, three checks
the Almanac's own example address appears, large, mono, on a reserved ending: captain@tidalmail.example. Three rows build underneath, one per VO beat, each getting a tick as it resolves: - format correct - domain active, mail servers running - limited SMTP handshake, with a small annotation, does the mailbox answer
music settles into a steady bed as the rows tick.
"A validation tool checks the syntax first. Is it actually formatted like an email address? captain@mailbox.example passes... Then it checks the domain using DNS records to confirm that mailbox.example is a real, active domain with mail servers running. Finally, it attempts limited SMTP interactions (that's the protocol mail servers speak) to see if the mailbox actually exists and can receive mail."
the address is the Almanac's own worked example, not a new invention, shown on the reserved .example ending (demo names rule 1), never a real or client address. SMTP appears on screen as a data label only, never spoken as jargon, the VO explains it in a clause instead ("the protocol mail servers use to talk").
this is the heaviest shot in the script, three real steps in order, so it gets the most time and the plainest language.
04 · The three results
the address clears. Three words land one at a time, ink on paper, no invented colour coding: valid, invalid, risky, each with one mono line underneath. - valid / syntax, active domain, mailbox all check out - invalid / failed at least one of the three - risky / passed most checks, pattern reads like a typo
bed holds steady.
"The tool gives you a result. Valid, invalid, or risky. A valid address has syntax, an active domain, and an accepting mailbox. An invalid address fails one or more checks. A risky address passes most checks but has patterns that suggest it might be a spamtrap or a typo waiting to happen."
the Almanac's "risky" definition names two patterns, a spam trap and a typo. The spam-trap half is cut, spam-trap claims are banned on marketing surfaces (Stage-1 pre-screen). Only the typo half survives. No colour is assigned to valid, invalid or risky, this is a generic industry result, not Review My Emails' own Keep, Monitor, Suppress verdict, and the brand system defines colour only for that trio, so nothing is invented here (see Needs YT's yes).
this is the whole payoff of the mechanism shot, three checks in, three words out, no partial credit.
05 · The turn, what the result actually promises
everything clears. One line, ink, Lora: "reaches a mailbox." Beneath it, dashed and hollow: "lands in the inbox."
bed thins to a single held note.
"It's a series of checks that run on an email address to predict whether mail sent to it will actually reach a real mailbox."
this is the definitional line the whole script is built to reach. It states the scope of what a validation result measures, reaching a mailbox, and does not claim or imply anything about inbox placement. No inbox-placement guarantee, ever.
this is the video's one idea, stated once, in the longest sentence in the script, paced slow on purpose.
06 · The decision
two cards side by side. at signup over "catch it as it happens". in bulk over "clean what's already on the list". A thin teal rule between them.
bed warms slightly.
"You can validate at signup (catch problems as they happen) or in bulk on your existing list (clean what you already have)."
nothing here claims validation fixes authentication, domain reputation or blocklist standing, it is presented only as what it is, a check on the address.
ends on a decision, not a number (voice guide section 6), and it hands over the Almanac's own two use cases in the Almanac's own order.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording, not a generic "start for free" (voice guide sections 2 and 3, forbidden competitor list). The destination reviewmyemails.com/get-started is confirmed, not a flag, per 00-inbox/decisions/2026-09-21-story-1-launch-messaging.md ("Panel 12 CTA confirmed as reviewmyemails.com/get-started"). The launch-state wording on the card itself is still open, see Needs YT's yes.
V925Why validation does not guarantee deliverability
draftedOpen questions for YT
- On camera or voice only. This is specced as voice over motion graphics, which is what the two existing Review My Emails video precedents do.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- The CTA destination. Specced as reviewmyemails.com/get-started.
- Whether the carousel or the video ships first. Carousels pull about twice what image posts do, but nothing in the repo compares a carousel against a video on this account.
01 · The hook · 0:00
On screen: paper. One address alone in the middle, mono, large: marina@tidewell-supply.example. A green tick sits beside it. Below, in Lora, the line lands in two beats: "Four checks passed." then, dashed and hollow, "Four were never run."
Your validator checked this address. It passed.
02 · The four checks · 0:04
On screen: the address slides to the top. A left column builds under it, one row at a time, each with a green tick as the VO names it. Mono rows, tight. - format correct - domain exists in DNS - domain set up to receive email - mailbox answered, with a small annotation, where the server answers
It confirmed the format was right. It confirmed the domain exists. It confirmed the domain is set up to receive email. And where the server would answer, it confirmed a mailbox is really there.
03 · The turn · 0:12
On screen: the four ticks hold, then desaturate slightly. The column does not disappear. It just stops being the point.
Four checks. All four about the address.
04 · What it cannot see · 0:15
On screen: a right column opens beside the first, same rows, no ticks. Each row arrives as the VO reaches it, in ink rather than green: - already marked you as spam - your domain's reputation with their provider - whether your content trips a filter - six months of silence
Here is what it did not look at. Whether the person behind it has already marked you as spam. Whether your sending domain carries a reputation problem with their mailbox provider. Whether your content trips a filter on the way in. Or whether that person stopped opening your emails six months ago, and their mailbox provider noticed that silence long before you did, and has quietly been routing you to spam ever since.
05 · Delivered against deliverable · 0:28
On screen: both columns clear. Two words, stacked, Lora, with their definitions in mono underneath. DELIVERED over "a server accepted it". DELIVERABLE over "a real person can read it". A thin teal rule between them.
There is a difference between delivered and deliverable. Delivered means a server accepted it. Deliverable means a real person can actually read it. Validation answers the first one.
06 · The wedge · 0:34
On screen: everything drops out. Paper, and one line full frame in Lora, ink: "Valid is not safe."
Valid is not safe.
07 · The decision · 0:38
On screen: the invented address returns, alone. Then the three verdict chips resolve under it, left to right, keep #10B981, monitor #F59E0B, suppress #ED5746. One line of plain-English reason sets under the chips as a mono row.
So stop asking whether the address exists. Ask whether you should send to it. Review My Emails gives every address one verdict, and the reason underneath it. Keep. Monitor. Suppress.
08 · End card · 0:44
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.003.016-validation-vs-deliverability.md
01 · The hook
paper. One address alone in the middle, mono, large: marina@tidewell-supply.example. A green tick sits beside it. Below, in Lora, the line lands in two beats: "Four checks passed." then, dashed and hollow, "Four were never run."
no music yet. Room tone only.
this frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Specific, unexpected, incomplete. A number the viewer cannot resist auditing.
the address is invented. Never a real one, never a client's.
02 · The four checks
the address slides to the top. A left column builds under it, one row at a time, each with a green tick as the VO names it. Mono rows, tight. - format correct - domain exists in DNS - domain set up to receive email - mailbox answered, with a small annotation, where the server answers
music starts under the first tick, low.
the four checks are the Almanac's own list, verbatim in substance. "Whether the email address is formatted correctly. Whether the domain exists in DNS. Whether the domain has MX records set up for email. In many cases, whether the specific mailbox responds to an SMTP probe."
naming all four honestly earns the turn. The tool did real work, and saying so is what makes the next beat land as a discovery instead of an attack.
03 · The turn
the four ticks hold, then desaturate slightly. The column does not disappear. It just stops being the point.
music thins to a single held note.
the pivot has to be a sentence short enough to hear. This is the shortest line in the script for that reason.
04 · What it cannot see
a right column opens beside the first, same rows, no ticks. Each row arrives as the VO reaches it, in ink rather than green: - already marked you as spam - your domain's reputation with their provider - whether your content trips a filter - six months of silence
music builds back under the fourth row.
all four are the Almanac's "what validation doesn't check" list. The last one is its own sentence there: "Whether the subscriber has been ignoring your emails for six months and the ISP has started routing you to spam as a result." Said as "mailbox provider" rather than "ISP", which is the house term (voice guide section 2).
the Almanac's list has a fifth item, spam traps. It is cut, because spam-trap claims are banned on marketing surfaces and this is one. Educational mentions belong in the Almanac, not here. Also, naming reputation and content as things validation misses must never tip into implying Review My Emails fixes them. It does not. That is infrastructure, and the free Email SOS Hotline is where it goes.
the long sentence lives here on purpose. Short bursts through the first three rows, then one 32-word run that mirrors the slow, quiet way the actual damage happens.
05 · Delivered against deliverable
both columns clear. Two words, stacked, Lora, with their definitions in mono underneath. DELIVERED over "a server accepted it". DELIVERABLE over "a real person can read it". A thin teal rule between them.
the Almanac states this distinction directly. "An email is 'delivered' if it's accepted by the receiving server. It's 'deliverable' (in the practical sense) if it reaches the inbox where a real person can read it. Validation addresses the first part."
this is a definition, not a promise. Nothing here claims Review My Emails puts anything in an inbox. No inbox-placement guarantee, ever.
06 · The wedge
everything drops out. Paper, and one line full frame in Lora, ink: "Valid is not safe."
music cuts out completely for the length of the line, then returns on the cut.
best performing angle to date, and it now has four green ticks and four blanks behind it instead of arriving as an assertion. Own frame, own silence.
07 · The decision
the invented address returns, alone. Then the three verdict chips resolve under it, left to right, keep #10B981, monitor #F59E0B, suppress #ED5746. One line of plain-English reason sets under the chips as a mono row.
the verdict trio and the reason-plus-action shape are BIBLE section 3. The "prerequisite, not a guarantee" landing is the Almanac's own closing frame: "Think of validation as a prerequisite, not a guarantee."
no count of how many labels exist, spoken or on screen. No bin icon on suppress. Never name the validation vendor, and if a vendor must be referred to at all it is "Sonar". "Review My Emails" spelled out, never the initials.
decision, not a number (voice guide section 6). The video does not get to end on a problem.
08 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free", which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is /get-started, which is the confirmed target and the one that resolves. See "Needs YT's yes" on the launch wording.
V926Cleaning versus validation
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first two Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- The CTA destination. Specced as reviewmyemails.com/get-started, the same flag raised on the first two scripts: CLAUDE.md rule 5 names platform.reviewmyemails.com as the main CTA, but that subdomain has no DNS record recorded anywhere in...
- Whether "you need both" undersells the product. Shot 6 tells the viewer they need two separate steps, validate then clean, because that is what the Almanac answer says.
01 · The hook · 0:00
On screen: paper. One address alone, mono, large: admin@saltmarsh-outfitters.example. Beside it a green tick and the word "VALID". Below, dashed and hollow: "Still shouldn't send."
This address passed validation. That does not mean you should send to it.
02 · Two questions · 0:05
On screen: the address slides up. Two mono labels build side by side, one at a time. VALIDATION with, underneath in Lora, "does this mailbox exist?" Then CLEANING with "should I send to it?"
Validation asks one question. Does this mailbox exist, can it receive mail. Cleaning asks a different one. Should you actually send to it.
03 · The doorman and the manager · 0:13
On screen: under VALIDATION, a mono line drops in: "the doorman checking IDs at the door." Under CLEANING, a second line drops in: "the manager deciding who stays."
Think of it this way. Validation is the doorman checking IDs at the door. Cleaning is the manager deciding who gets to stay, based on behavior and risk.
04 · What cleaning actually weighs · 0:22
On screen: under CLEANING, three mono rows build one at a time, each with a short Lora gloss beneath it: - engagement: "silent for two years?" - acquisition source: "where the address came from" - list tenure: "how long it's been on the list"
Cleaning weighs things validation never looks at. How long it has been since the person actually engaged, where the address originally came from, and how long it has been sitting on your list without anyone in the business noticing it was still there.
05 · Back to the address · 0:34
On screen: the hook address returns, full frame. The green "VALID" tick is still there, unchanged. Beside it, in ink: "Last opened: two years ago."
This is why a validated list is not a clean one. The mailbox is real. Nobody has opened an email from you in two years.
06 · The decision · 0:42
On screen: the two labels from shot 2 collapse into one row: validate first then an arrow to clean second. Under that, the three verdict chips resolve left to right, keep #10B981, monitor #F59E0B, suppress #ED5746.
So do both, in order. Validate first, to clear out addresses that never existed. Clean second, to decide what happens to what's left. Keep. Monitor. Suppress.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.004.005-cleaning-vs-validation.md
01 · The hook
paper. One address alone, mono, large: admin@saltmarsh-outfitters.example. Beside it a green tick and the word "VALID". Below, dashed and hollow: "Still shouldn't send."
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A pass that is not a green light is the itch nobody scrolls past.
the address is invented. Never a real one, never a client's.
02 · Two questions
Almanac ids in this scene: 005.004.005
the address slides up. Two mono labels build side by side, one at a time. VALIDATION with, underneath in Lora, "does this mailbox exist?" Then CLEANING with "should I send to it?"
music starts under the first label, low.
Almanac 005.004.005: "Validation is the technical check. It asks: does this mailbox actually exist? Can it receive mail?... Cleaning is the business decision. It asks: should we actually send to this address, even if it technically exists?"
naming both questions plainly, before either gets an answer, is what makes the gap land later instead of arriving as an accusation.
03 · The doorman and the manager
Almanac ids in this scene: 005.004.005
under VALIDATION, a mono line drops in: "the doorman checking IDs at the door." Under CLEANING, a second line drops in: "the manager deciding who stays."
held note, no percussion, so the line reads clean.
Almanac 005.004.005: "Think of it this way. Validation is the bouncer checking IDs at the door. Cleaning is the manager deciding who gets to stay in the club based on behavior and reputation risk." The Almanac's own word for the role is swapped to "doorman" in the shipped Frame and VO only, because that word is also a competitor's brand name (on the forbidden-phrase list), and the Voice Critic's automatic-fail rule 9 catches the literal string regardless of sense. The citation above stays verbatim because it is documentation, not broadcast copy.
this is the Almanac's own line, not an invented visual. It is the most quotable sentence in the answer, so it gets its own beat rather than being folded into the last one.
04 · What cleaning actually weighs
Almanac ids in this scene: 005.004.005
under CLEANING, three mono rows build one at a time, each with a short Lora gloss beneath it: - engagement: "silent for two years?" - acquisition source: "where the address came from" - list tenure: "how long it's been on the list"
music builds under the third row.
Almanac 005.004.005: "Cleaning considers engagement history, acquisition source, how long the address has been on your list... You might have a valid mailbox that's been silent for two years."
the Almanac's own list also names "whether it's a spamtrap" and "complaint rates" as things cleaning weighs. Both are cut. Spam-trap claims are banned on marketing surfaces and a complaint-rate figure is a threshold, also banned. What remains, engagement, source, and tenure, is enough to carry the point without either one.
this is the beat that earns the hook. It shows exactly what a validator cannot see, in the Almanac's own terms.
05 · Back to the address
Almanac ids in this scene: 005.004.005
the hook address returns, full frame. The green "VALID" tick is still there, unchanged. Beside it, in ink: "Last opened: two years ago."
the bed thins to almost nothing.
Almanac 005.004.005: "You might have a valid mailbox that's been silent for two years. Validation says 'the mailbox exists.' Cleaning says 'but you probably shouldn't send to it.'"
closing the loop on the hook address is what turns the abstract distinction into a single concrete case the viewer can hold onto.
06 · The decision
Almanac ids in this scene: 005.004.005
the two labels from shot 2 collapse into one row: validate first then an arrow to clean second. Under that, the three verdict chips resolve left to right, keep #10B981, monitor #F59E0B, suppress #ED5746.
Almanac 005.004.005: "Here's the thing: you need both. Validation catches syntax errors and dead addresses upfront. Cleaning protects your sender reputation by weeding out high-risk addresses that won't engage." The verdict trio and the order, validate then clean, is product truth from BIBLE section 3, not the Almanac answer, and is marked as such rather than sourced to 005.004.005.
no label count, spoken or on screen. Nothing here implies either step fixes SPF, DMARC, MX or blocklist problems. No inbox-placement guarantee.
ends on a decision, not a number (voice guide section 6). It resolves the two questions from shot 2 into one sequence instead of leaving the viewer with two tools and no order to run them in.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is /get-started, which is the confirmed target and the one that resolves. See "Needs YT's yes" on the launch wording.
V927The win-back before you delete them
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Show the three-email sequence as fanned cards, or one replacing the next.
01 · The hook · 0:00
On screen: paper. A list where a big grey chunk is labelled silent for 8 months. Line, Lora: "Do not delete them yet."
You have a pile of subscribers who have gone silent for months. Before you delete them or keep mailing them, there is a smarter move.
02 · What it is · 0:06
On screen: the silent chunk, then three email cards fan out over two weeks.
It is a win-back. A short sequence, two or three emails over a couple of weeks, sent only to the people who have not opened or clicked in six to twelve months. The message is simple. Do you still want to hear from us.
03 · The sequence · 0:20
On screen: the three cards, each with its line: we miss you, here is why you signed up, last chance to stay.
The first says we miss you, here is what is new. The next reminds them why they signed up. The last one is the stakes, this is your last chance to stay. If they do not engage after that, you remove them.
04 · Why it matters · 0:32
On screen: the silent chunk drags an "engagement" meter down. Removing it lets the meter rise.
Here is why it matters. Providers watch you mailing dead addresses and your reputation takes the hit. A win-back gives the silent ones a chance to opt back in. If they do not, you clean your list. Either way you win.
05 · The decision · 0:40
On screen: one card: "silent 6 months? win back or sunset".
So find everyone silent past six months, run one win-back, and suppress whoever still does not answer. Do not keep paying to reach people who left.
06 · End card · 0:46
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.010.001-what-is-re-engagement.md
01 · The hook
paper. A list where a big grey chunk is labelled silent for 8 months. Line, Lora: "Do not delete them yet."
room tone.
it names the exact stuck choice, delete or keep mailing, and promises a third path.
02 · What it is
Almanac ids in this scene: 005.010.001
the silent chunk, then three email cards fan out over two weeks.
Almanac 005.010.001: "a short sequence of two to three emails sent to subscribers who haven't opened or clicked in roughly 6 to 12 months, asking them to confirm they still want to receive mail."
03 · The sequence
Almanac ids in this scene: 005.010.001
the three cards, each with its line: we miss you, here is why you signed up, last chance to stay.
Almanac 005.010.001: "You send 2-3 emails over two weeks. The first might say We miss you... The next one could remind them why they signed up. The final one is usually the stakes, This is your last chance to stay. If they don't engage after that, you remove them."
04 · Why it matters
Almanac ids in this scene: 005.010.001
the silent chunk drags an "engagement" meter down. Removing it lets the meter rise.
Almanac 005.010.001: "ISPs see you mailing dead addresses and your reputation takes a hit. A re-engagement campaign gives inactive subscribers a chance to opt back in. If they don't, you clean your list."
the Almanac's "spam trap magnet" line is cut, the reputation drag carries the beat.
05 · The decision
Almanac ids in this scene: 005.010.001
one card: "silent 6 months? win back or sunset".
Almanac 005.010.001: "Identify subscribers who haven't opened anything in 6-12 months. Then decide: run a win-back sequence or sunset them outright."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V928Remove inactive subscribers, or just stop emailing them
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the existing Review My Emails video precedents and the earlier Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- How much legal detail on screen. The answer names "GDPR Article 17" and a "data subject erasure request".
- The end-card bridge. The video teaches engagement hygiene (suppress the silent) and the offer is validation hygiene (clean the invalid), so the end card pairs them as two separate jobs rather than claiming the product finds inactives.
01 · The hook · 0:00
On screen: paper. Two big buttons side by side, mono. Left, DELETE THEM, tinted suppress #ED5746. Right, STOP EMAILING, tinted monitor #F59E0B. A cursor hovers in the gap between them. Above, in Lora, ink, large: "They stopped opening." Below, dashed and hollow: "So which button?" Faint behind the buttons, a dimmed column of invented addresses.
A pile of your subscribers stopped opening. So you hover over two buttons. Delete them, or just stop emailing them?
02 · The false fork · 0:05
On screen: the cursor taps DELETE THEM, then jumps and taps STOP EMAILING, then back again, faster. A thin ? pulses between them.
It feels like a fork. Wipe them and lose the record, or leave them sitting there forever. That is the wrong question.
03 · Step one, not a choice · 0:12
On screen: both buttons slide up. STOP EMAILING locks under a solid teal bar labelled STEP ONE, with a small caption always. DELETE THEM greys out and waits below.
Here is the part that is not actually a choice. Stop emailing them. First. Always. It is step one, and it is what protects your sending reputation.
04 · The turn, the sorting step · 0:20
On screen: under STEP ONE, a flow draws itself. A card, re-engagement campaign, with a small caption two to four messages, about two weeks. Two arrows leave it. One to REPLIED, which glows keep #10B981 over "stays active". One to IGNORED IT, which slides toward a tray labelled suppress.
Then you run one re-engagement campaign, two to four messages over about two weeks, and it does the sorting for you, whoever replies stays on your active list, and whoever ignores it moves to suppression.
05 · The real fork · 0:31
On screen: the suppress tray opens into two mono cards, side by side. SUPPRESS over "stays in your do-not-send list, never emailed again". DELETE over "gone entirely". Under SUPPRESS, a thin line: record kept for compliance and history.
Now the real fork. Suppress, or delete. Suppressing keeps them in your do-not-send list. You never email them again, but the record stays for compliance and history. Deleting wipes them completely.
06 · The decision · 0:39
On screen: the SUPPRESS card glows and takes a check, tagged safest for most senders. The DELETE card dims, tagged only if law or policy says so. A thin teal rule between them.
For most senders, once they have ignored their last chance, suppression is the safest move. Delete only when your retention policy or an erasure request forces it. So decide your suppression policy now, before you are scrambling.
07 · End card · 0:47
On screen: small logo lockup, never a cartoon octopus. Above the offer, one line in Lora: "Suppress the silent. Clean out the invalid." Under it, the offer in mono: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.010.007-remove-vs-stop-inactives.md
01 · The hook
Almanac ids in this scene: 005.010.007
paper. Two big buttons side by side, mono. Left, DELETE THEM, tinted suppress #ED5746. Right, STOP EMAILING, tinted monitor #F59E0B. A cursor hovers in the gap between them. Above, in Lora, ink, large: "They stopped opening." Below, dashed and hollow: "So which button?" Faint behind the buttons, a dimmed column of invented addresses.
no music yet. Room tone only.
the beat frames the question. It rests on the answer's own title, Almanac 005.010.007: "Should I remove inactive subscribers or just stop emailing them?"
the two buttons are the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Everyone who runs a list has hovered in exactly this gap.
every address on screen is invented, never a real one, never a client's. "A pile" is illustrative framing, not a claimed statistic.
02 · The false fork
Almanac ids in this scene: 005.010.007
the cursor taps DELETE THEM, then jumps and taps STOP EMAILING, then back again, faster. A thin ? pulses between them.
low pulse comes in under the first tap.
Almanac 005.010.007: "Whether you delete them or just suppress them is a different question and depends on your business needs and legal obligations."
name the false fork out loud so the correction lands as relief, not a lecture. The whole turn only works if the viewer first agrees the fork feels real.
03 · Step one, not a choice
Almanac ids in this scene: 005.010.007
both buttons slide up. STOP EMAILING locks under a solid teal bar labelled STEP ONE, with a small caption always. DELETE THEM greys out and waits below.
music settles into a steady bed as the bar locks.
Almanac 005.010.007: "Stop emailing first. Always. That's step one and it's non-negotiable for protecting your sender reputation."
reputation is spoken as sending reputation only, never tied to a blocklist and never a promise of inbox placement. No count, no threshold.
settle the mandatory move before the real fork, so the fork reads as a later, separate decision. This is the beat that turns two buttons into a sequence.
04 · The turn, the sorting step
Almanac ids in this scene: 005.010.007
under STEP ONE, a flow draws itself. A card, re-engagement campaign, with a small caption two to four messages, about two weeks. Two arrows leave it. One to REPLIED, which glows keep #10B981 over "stays active". One to IGNORED IT, which slides toward a tray labelled suppress.
the bed holds steady as the two arrows draw.
Almanac 005.010.007: "send a re-engagement campaign first. Whoever responds stays active. Whoever ignores it gets suppressed. This two-step filter keeps your list healthy without losing data unnecessarily." The cadence "two to four messages over two weeks" is the answer's own (In short).
this is the whole point in one beat, so it carries the longest sentence in the script on purpose. The campaign is the hinge that removes the guesswork the two buttons implied.
05 · The real fork
Almanac ids in this scene: 005.010.007
the suppress tray opens into two mono cards, side by side. SUPPRESS over "stays in your do-not-send list, never emailed again". DELETE over "gone entirely". Under SUPPRESS, a thin line: record kept for compliance and history.
the bed thins to one held note as the two cards land.
Almanac 005.010.007: "Suppressing means they stay in your database (good for compliance and history) but you never send to them again. Deleting removes them entirely." And from the In short: "do-not-send table for audit trails and GDPR Article 17 documentation."
the spoken line says "do-not-send list", never "ESP". Compliance and history are the answer's own words, not a legal claim of our own.
only now, after stop and after the sorting step, does delete-versus-suppress actually matter. Putting it last is what proves it was never the first decision.
06 · The decision
Almanac ids in this scene: 005.010.007
the SUPPRESS card glows and takes a check, tagged safest for most senders. The DELETE card dims, tagged only if law or policy says so. A thin teal rule between them.
music returns, warmer, under "decide your suppression policy now".
Almanac 005.010.007: "If they never re-engage after you give them a chance, suppression is the safest move for most senders." And: "Hard deletion makes sense only when retention policy or a data subject erasure request requires it." And: "Your next move is deciding your suppression policy right now so you're not scrambling later."
ends on a decision, not a number (voice guide section 6). It hands the viewer the default and the one exception, in the answer's own order.
07 · End card
small logo lockup, never a cartoon octopus. Above the offer, one line in Lora: "Suppress the silent. Clean out the invalid." Under it, the offer in mono: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free", which is on the forbidden competitor list (voice guide sections 2 and 3). The destination reviewmyemails.com/get-started is the confirmed, resolving target for this cluster.
the video's action is engagement hygiene, suppressing the silent, done inside the sender's own email marketing tool. The cleaning offer is a separate job, validation hygiene, clearing addresses that are invalid or risky. "Clean out the invalid" is product truth (BIBLE), not an Almanac claim, and the end card must never imply cleaning finds or suppresses inactive subscribers, or that it fixes authentication or reputation. Two jobs, named as two.
V929What email list decay actually is
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and 002.001.004.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- The CTA destination. Specced as reviewmyemails.com/get-started, the same real conflict 002.001.004 flagged: CLAUDE.md rule 5 names platform.reviewmyemails.com as the main CTA, but that subdomain has no DNS record recorded anywhere in...
- The verdict-adjacent colour grammar on the hard and soft decay cards. Shots 1, 3, 4 and 5 use suppress red for hard decay and monitor amber for soft decay.
01 · The hook · 0:00
On screen: paper. Two invented addresses stacked, mono, large: bo.unce@coral-cove.invalid, struck through in suppress red #ED5746, small label beneath in ink: "bounced." Under it, kai@driftwood-goods.example, not struck, small label beneath in monitor amber #F59E0B: "gone quiet." Above both, Lora ink, large: "Same list. Two different kinds of dead."
One of these addresses bounced. The other just stopped opening a while back. Only one of them will ever tell you that.
02 · The false comfort · 0:05
On screen: a subscriber counter, mono, barely moving: 24,612 ticks down to 24,609. A dashed label beneath: "basically unchanged."
You think you will know when your list starts decaying. You won't. Decay does not announce itself, it just happens, quietly, from the moment you built the list.
03 · The two buckets · 0:12
On screen: split screen. Left card, mono label HARD DECAY, suppress-red accent: "the address is gone. bounced. domain dead." Right card, mono label SOFT DECAY, monitor-amber accent: "the address still works. nobody's home."
List decay splits into two kinds. Hard decay is the address itself dying. It bounces, the domain expires, it is structurally gone. Soft decay is different. The address still works, the inbox is real, the person is real. They have just stopped paying any attention.
04 · The turn · 0:27
On screen: the left card flashes suppress red with a small bounce-arrow icon. The right card stays visually calm, no alert, just a small greyed ghost icon fading in beside it.
The hard kind announces itself, it bounces and you see it in your report, but the soft kind never announces anything at all, it just sits on your list looking fine while it quietly drags your reputation and your inbox placement down.
05 · The decision · 0:35
On screen: the two cards clear to two fixes, side by side, each a mono card. HARD DECAY over "validation, before you send." SOFT DECAY over "engagement hygiene, before you lose them." A thin teal rule between them.
Different problem, different fix. Validation catches the dead addresses before you waste a send on them. Engagement hygiene catches the quiet ones, so you can win them back, or stop sending to them, before they cost you.
06 · End card · 0:45
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-005.011.001-what-is-list-decay.md
01 · The hook
paper. Two invented addresses stacked, mono, large: bo.unce@coral-cove.invalid, struck through in suppress red #ED5746, small label beneath in ink: "bounced." Under it, kai@driftwood-goods.example, not struck, small label beneath in monitor amber #F59E0B: "gone quiet." Above both, Lora ink, large: "Same list. Two different kinds of dead."
no music yet. Room tone only.
both addresses are invented. Never a real one, never a client's.
the frame is the whole idea in one image. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8).
02 · The false comfort
Almanac ids in this scene: 005.011.001
a subscriber counter, mono, barely moving: 24,612 ticks down to 24,609. A dashed label beneath: "basically unchanged."
low pulse comes in under "you won't."
Almanac 005.011.001: "You're not losing subscribers because you did something wrong. Well, not entirely. Email list decay is what happens to every list, by default, just from the passage of time."
no rate or percentage is shown or spoken here or anywhere in this script. The Almanac's own headline figure for how much a list decays each year is Almanac depth only.
names the false comfort, a steady number, out loud before the video corrects it.
03 · The two buckets
Almanac ids in this scene: 002.001.004, 005.011.001
split screen. Left card, mono label HARD DECAY, suppress-red accent: "the address is gone. bounced. domain dead." Right card, mono label SOFT DECAY, monitor-amber accent: "the address still works. nobody's home."
music settles into a steady bed as the two cards build.
Almanac 005.011.001: "Hard decay: the address is structurally gone. Bouncing, undeliverable, domain expired." And: "Soft decay: the address still works, but no human is paying attention. The inbox is real, the person is real, they've just stopped caring."
exactly the Almanac's own two buckets, no invented third category.
this is the answer's own structure, handed straight to the screen, the same move 002.001.004 used with its five named signals.
04 · The turn
Almanac ids in this scene: 002.001.004, 005.011.001
the left card flashes suppress red with a small bounce-arrow icon. The right card stays visually calm, no alert, just a small greyed ghost icon fading in beside it.
the bed thins to one held note as the ghost icon fades in.
Almanac 005.011.001: "This shows up in your bounce rate and needs to be removed promptly." And: "This is trickier to catch because it doesn't bounce. It just sits there, silently bringing down your engagement metrics and affecting your inbox placement."
"affecting your inbox placement" describes a mechanism the Almanac states directly. It is never turned into a promise about any specific inbox outcome. No inbox-placement guarantee, anywhere in this script.
this is the whole point in one beat, so it carries the longest sentence in the script on purpose, the same move 002.001.004 made at its own turn.
05 · The decision
Almanac ids in this scene: 005.011.001
the two cards clear to two fixes, side by side, each a mono card. HARD DECAY over "validation, before you send." SOFT DECAY over "engagement hygiene, before you lose them." A thin teal rule between them.
music returns, warmer, under "win them back."
Almanac 005.011.001: "Email validation handles hard decay: it identifies addresses that are no longer deliverable before you waste sends on them (or hurt your reputation with repeated bounces)." And: "Engagement hygiene handles soft decay: tracking who's actually engaging, running re-engagement campaigns, and suppressing the ones who don't come back."
the two fixes stay two separate sentences for two separate problems. Validation is never implied to fix soft decay, and engagement hygiene is never implied to fix hard decay. No inbox-placement guarantee.
ends on a decision, not a number (voice guide section 6). It hands the viewer the Almanac's own split fix, in the Almanac's own order.
06 · End card
Almanac ids in this scene: 002.001.004
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording, matching the wording locked in 002.001.004, rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is /get-started. See "Needs YT's yes" on the launch wording.
V930What is email segmentation?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "complaint ripples to the whole list" device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. One big envelope fires the same message at a crowd of very different people. Lora caption: "Same email. Everyone. Really?"
One message, blasted to your entire list. It is the default, and it is quietly costing you. Here is the first fix, and it is simpler than you think.
02 · What segmentation is · 0:06
On screen: the crowd splits into labelled groups, mono: what they bought, where they are, how engaged, what they clicked, how they signed up.
Segmentation is dividing your list into groups so each one gets content that fits. What they bought, where they are, how engaged they are, what they clicked. You find the meaningful differences, and you let those differences shape what each group receives.
03 · The one split that matters most · 0:22
On screen: the groups fade, and one clean line divides the list in two, teal opened or clicked in 90 days versus grey silent for 90 days.
If you only build one segment, build this one. Engaged versus unengaged. The people who opened or clicked in the last ninety days, split from the people who went silent. That single line shows you who your real audience is.
04 · Why it protects everyone · 0:36
On screen: an email sent to the grey silent segment triggers a complaint icon, which ripples out and dims the whole list, including the teal engaged people.
Here is why it matters beyond relevance. Mail the silent segment and you do not just get low clicks, you get complaints. And complaints drag your inbox placement down for the whole list, including your most loyal readers.
05 · The decision · 0:44
On screen: the engaged segment glows, the silent one is set aside for a separate plan. A checkmark on "mail the engaged, treat the silent differently".
So build the ninety-day split first. Keep mailing the engaged, and give the silent ones their own plan instead of the same blast.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-006.001.001-what-is-segmentation.md
01 · The hook
paper. One big envelope fires the same message at a crowd of very different people. Lora caption: "Same email. Everyone. Really?"
room tone.
it names the default the viewer is probably doing and promises one concrete fix.
02 · What segmentation is
Almanac ids in this scene: 006.001.001
the crowd splits into labelled groups, mono: what they bought, where they are, how engaged, what they clicked, how they signed up.
Almanac 006.001.001: "dividing your email list into groups so you can send more relevant content... what they've bought, where they are, how engaged they are, what they've clicked."
03 · The one split that matters most
Almanac ids in this scene: 006.001.001
the groups fade, and one clean line divides the list in two, teal opened or clicked in 90 days versus grey silent for 90 days.
Almanac 006.001.001: "the first segment worth building is an engaged vs. unengaged split. People who've interacted with your email in the last 90 days versus those who haven't."
04 · Why it protects everyone
Almanac ids in this scene: 006.001.001
an email sent to the grey silent segment triggers a complaint icon, which ripples out and dims the whole list, including the teal engaged people.
Almanac 006.001.001: "The worst-case outcome for a campaign sent to a dead segment isn't just low clicks. It's complaints, which hurt inbox placement for every subscriber on your list."
05 · The decision
Almanac ids in this scene: 006.001.001
the engaged segment glows, the silent one is set aside for a separate plan. A checkmark on "mail the engaged, treat the silent differently".
Almanac 006.001.001: "That split alone protects your sender reputation and shows you who your real audience actually is."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V931Should you use emojis in subject lines?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the fade-the-emoji device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. One inbox row, mono, with a flame-emoji example at the front of the subject. A cursor hovers over it. Lora, big, beside it: "Does this help?"
An emoji in your subject line. Sometimes it lifts opens, sometimes it costs you them. Here is how to tell which one you are doing.
02 · When it helps, when it does not · 0:06
On screen: two columns build, mono. Left, teal, header helps: relevant to the message, B2C audience, one, at the start or end. Right, grey, header flat or worse: B2B audience, finance, legal, health, an emoji on every send.
The research is genuinely mixed. A relevant emoji can give a small lift for a business-to-consumer audience. For a business-to-business audience, especially finance, legal, or healthcare, it often reads as out of place and does nothing, or a little harm.
03 · The two ways it backfires · 0:22
On screen: top half, a subject with a money-bag-emoji example slides toward a folder marked spam. Bottom half, the same emoji renders as an empty square in an older client, mono caption: Outlook desktop.
Two ways it backfires. Emojis tied to scammy mail, the money bag, the greedy face, can nudge spam filters when they pile on other red flags. And older clients can show a blank square where your emoji was. That looks broken, not friendly.
04 · The rule that keeps you safe · 0:36
On screen: one subject line, mono, with a party-popper-emoji example. It fades out and the words stay, reading perfectly on their own. Caption, Lora: "Still makes sense without it."
So if you use one, use one, at the start or the end, and make sure the line still makes complete sense if the emoji disappears. The words carry the message. The emoji is decoration.
05 · The decision · 0:44
On screen: an A and a B subject line, same words, one with an emoji, one without. A split arrow points to "let the audience answer".
Do not guess. Split test the same line with and without, and let your own audience tell you what works.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-007.002.005-emojis-in-subject-lines.md
01 · The hook
paper. One inbox row, mono, with a flame-emoji example at the front of the subject. A cursor hovers over it. Lora, big, beside it: "Does this help?"
room tone.
it names the exact thing they are unsure about and promises a real answer, not a rule of thumb.
02 · When it helps, when it does not
Almanac ids in this scene: 007.002.005
two columns build, mono. Left, teal, header helps: relevant to the message, B2C audience, one, at the start or end. Right, grey, header flat or worse: B2B audience, finance, legal, health, an emoji on every send.
Almanac 007.002.005: "Some studies show a small lift, especially when the emoji is relevant and the audience is B2C. Others show no difference, or even a slight drop for B2B audiences."
03 · The two ways it backfires
Almanac ids in this scene: 007.002.005
top half, a subject with a money-bag-emoji example slides toward a folder marked spam. Bottom half, the same emoji renders as an empty square in an older client, mono caption: Outlook desktop.
Almanac 007.002.005: "Certain emojis, especially ones historically used in scammy subject lines... can nudge spam filters" and "Older versions of Outlook can show a blank square where your emoji was supposed to be."
"nudge spam filters" only, as the Almanac states it. No spam-trap claim, no threshold.
04 · The rule that keeps you safe
Almanac ids in this scene: 007.002.005
one subject line, mono, with a party-popper-emoji example. It fades out and the words stay, reading perfectly on their own. Caption, Lora: "Still makes sense without it."
Almanac 007.002.005: "Use one emoji per subject line... Make sure the subject line still makes complete sense if the emoji disappears entirely."
05 · The decision
Almanac ids in this scene: 007.002.005
an A and a B subject line, same words, one with an emoji, one without. A split arrow points to "let the audience answer".
Almanac 007.002.005: "Split test the same subject line with and without, then let your audience tell you what works for them."
ends on a decision. No open-rate guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V932How many CTAs should an email have?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "one question over a blank email" device in shot 5, or a simpler swap.
01 · The hook · 0:00
On screen: paper. One email crammed with three competing buttons, mono: Buy the sale, Read the blog, Join referral. A reader's eyes dart between them, then close the email.
A sale, a new blog post, a referral program, all in one email. It feels efficient. It is actually the fastest way to lose the click you wanted most.
02 · One action wins · 0:07
On screen: the three buttons collapse into one bold teal button, Buy the sale. A meter labelled clicks on what matters rises as the clutter clears.
For a promotional or a transactional email, one call to action is almost always right. You want the reader moving toward a single outcome. Three options do not triple your chances. They split attention and slow the decision, so the one that matters gets fewer clicks.
03 · Repeat it, do not multiply it · 0:22
On screen: one email scrolls, the same button appears three times, mono labels: hero button, mid-body link, footer button, an arrow shows all three point to one URL.
One call to action does not mean one button. Repeat it. A hero button up top, a link in the middle, a button at the foot, all pointing to the very same place. Same action, more chances to take it.
04 · The one exception · 0:32
On screen: a newsletter roundup with several article links, but one is clearly bigger and brighter than the rest, labelled primary.
Newsletters are the exception. A roundup is meant to have several links, and readers know they are browsing. Even then, give one call to action the visual weight, bigger and bolder, and let the rest sit as plain text below it.
05 · The decision · 0:42
On screen: a writer asks one question over a blank email, Lora: "If they click one thing, what is it?" The email builds around that single answer.
So before you write, ask one question. If the subscriber clicks only one thing, what do you most want it to be? Build the email around that, and if you are reaching for a third button, the email is doing too much. Split it.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-007.006.006-how-many-ctas.md
01 · The hook
paper. One email crammed with three competing buttons, mono: Buy the sale, Read the blog, Join referral. A reader's eyes dart between them, then close the email.
room tone.
it shows the overloaded email everyone has sent, then names the cost.
02 · One action wins
Almanac ids in this scene: 007.006.006
the three buttons collapse into one bold teal button, Buy the sale. A meter labelled clicks on what matters rises as the clutter clears.
Almanac 007.006.006: "one CTA is almost always the right number... When you give someone three options, you're not tripling your chances of a click. You're splitting attention and slowing the decision."
03 · Repeat it, do not multiply it
Almanac ids in this scene: 007.006.006
one email scrolls, the same button appears three times, mono labels: hero button, mid-body link, footer button, an arrow shows all three point to one URL.
Almanac 007.006.006: "one primary CTA repeated as needed (hero button, mid-body link, footer button all pointing to the same URL)."
04 · The one exception
Almanac ids in this scene: 007.006.006
a newsletter roundup with several article links, but one is clearly bigger and brighter than the rest, labelled primary.
Almanac 007.006.006: "Newsletter formats are the main exception... it helps to have a primary CTA that gets the visual emphasis: bigger button, more prominent placement, contrasting color."
05 · The decision
Almanac ids in this scene: 007.006.006
a writer asks one question over a blank email, Lora: "If they click one thing, what is it?" The email builds around that single answer.
Almanac 007.006.006: "if you find yourself wanting three or more CTAs in a promotional email, that's often a signal the email is trying to do too much... Build the email around that answer."
ends on a decision. No click-rate guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V933Single vs double opt-in
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "names flip to reveal the junk" device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. Two paths from a signup form. Left, single opt-in, straight onto the list. Right, double opt-in, through a confirm-your-email gate first. Lora: "That gate is your best filter."
Single opt-in or double opt-in. That one extra confirmation click feels like friction you cannot afford. It is actually the best filter your list will ever have.
02 · What the click proves · 0:07
On screen: a confirmation email opens, a click lands, and three stamps drop: real address, reachable, actually wanted in.
With double opt-in, someone confirms by clicking a link before they land on your list. That single click tells you the address is real and reachable, and that a real person actually meant to sign up. No typos. No bots. No fake signups.
03 · Why it wins on deliverability · 0:22
On screen: a confirmed segment lights up with opens and clicks, and a caption: "Providers watch this signal."
It goes deeper than clean data. Confirmed subscribers open more, click more, and rarely complain. And that engagement is exactly the signal mailbox providers watch when they decide inbox or spam. A list of people who asked to be there sends a completely different signal.
04 · The objection, answered · 0:34
On screen: a counter shows 20 to 40% did not confirm, then those names flip over to reveal typo, not really interested, fake signup, and slide into a bin.
Now the objection. Twenty to forty percent never click confirm, and that feels like lost subscribers. But those are largely the ones who would have hurt you anyway. Typos that bounce. People who were never really interested. Single opt-in keeps all of it. Double opt-in screens it out first.
05 · The decision · 0:44
On screen: a checkmark on "trusted sources, long-term deliverability" points to double opt-in.
So if your signups come from your own site, events, or referrals, and you care about long-term deliverability, choose double opt-in and do not look back.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.003.006-single-vs-double-opt-in.md
01 · The hook
paper. Two paths from a signup form. Left, single opt-in, straight onto the list. Right, double opt-in, through a confirm-your-email gate first. Lora: "That gate is your best filter."
room tone.
it names the exact choice and flips the objection in the first line.
02 · What the click proves
Almanac ids in this scene: 008.003.006
a confirmation email opens, a click lands, and three stamps drop: real address, reachable, actually wanted in.
Almanac 008.003.006: "the confirmation click verifies the address is real, reachable, and intentionally subscribed... No typos. No bots. No fake signups."
03 · Why it wins on deliverability
Almanac ids in this scene: 008.003.006
a confirmed segment lights up with opens and clicks, and a caption: "Providers watch this signal."
Almanac 008.003.006: "Confirmed subscribers engage more. They open your emails, click your links, and rarely complain. ISPs watch that engagement signal closely when deciding whether to put your mail in the inbox or spam folder."
the source's complaint-rate figure and spam-trap line are pre-screened out. Not spoken.
04 · The objection, answered
Almanac ids in this scene: 008.003.006
a counter shows 20 to 40% did not confirm, then those names flip over to reveal typo, not really interested, fake signup, and slide into a bin.
Almanac 008.003.006: "the people who don't confirm are largely the ones who would've hurt your list anyway. Typos that would have bounced. Abandoned interest... SOI keeps all that junk. DOI screens it out before it damages your metrics or reputation."
05 · The decision
Almanac ids in this scene: 008.003.006
a checkmark on "trusted sources, long-term deliverability" points to double opt-in.
Almanac 008.003.006: "if your signups come from trusted sources... and you care about long-term deliverability, DOI is the smarter choice... Most professional senders choose DOI and never look back."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V934Should unsubscribe be one-click?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "page loads already unsubscribed" device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. A long unsubscribe maze, mono steps: click link, enter your email, pick a reason, confirm, wait for email. A red finger skips the whole maze and jabs one button: "Report spam."
This is the unsubscribe flow that quietly wrecks your sender reputation. Watch what the person does instead of finishing it.
02 · Why the maze costs you · 0:07
On screen: a meter labelled spam complaints climbs one notch with each extra step in the maze.
Every extra step between wanting to leave and being gone gives someone a reason to give up and press report spam. And a spam complaint hurts your reputation far more than a clean, quiet unsubscribe ever would. You made the exit hard, so they took the loud one.
03 · It is not optional anymore · 0:22
On screen: an email header area with a native unsubscribe button beside the sender name, mono caption: RFC 8058, one-click List-Unsubscribe. Two logos labelled in text: Gmail, Yahoo.
And for a lot of senders this is no longer a nice-to-have. If you send more than five thousand messages a day to Gmail or Yahoo, they require a one-click unsubscribe header, so the inbox can show a leave button right there. One tap and the person is out, without ever visiting your site.
04 · Fix the footer link too · 0:36
On screen: the footer "unsubscribe" link is clicked, and the page loads already reading "You are unsubscribed." No second button.
The link in your footer needs the same treatment. It should opt the person out the moment they click, not drop them on a page with another button to press. Show a confirmation if you like, but the job is already done when the page loads.
05 · The decision · 0:44
On screen: a preference center sits next to a plain "unsubscribe from everything" link, both easy to find. An arrow points to the plain link: "always keep this one".
Offer a preference center if you want, but always keep one clear leave-everything link. Make the exit one click, every time.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-008.004.003-one-click-unsubscribe.md
01 · The hook
paper. A long unsubscribe maze, mono steps: click link, enter your email, pick a reason, confirm, wait for email. A red finger skips the whole maze and jabs one button: "Report spam."
room tone.
it shows the failure in one image, the maze versus the one button they actually press.
02 · Why the maze costs you
Almanac ids in this scene: 008.004.003
a meter labelled spam complaints climbs one notch with each extra step in the maze.
Almanac 008.004.003: "Every extra step between 'I want to leave' and 'you're out' increases your spam complaint rate... Multi-step flows push frustrated subscribers toward the Report Spam button, which damages sender reputation far more than a clean opt-out."
03 · It is not optional anymore
Almanac ids in this scene: 008.004.003
an email header area with a native unsubscribe button beside the sender name, mono caption: RFC 8058, one-click List-Unsubscribe. Two logos labelled in text: Gmail, Yahoo.
Almanac 008.004.003: "Gmail and Yahoo Mail require bulk senders (anyone sending 5,000+ messages per day to their users) to support one-click List-Unsubscribe via RFC 8058... they're opted out immediately without visiting your site at all."
the five-thousand figure is a sender-volume rule, not a complaint threshold. No complaint rate number spoken.
04 · Fix the footer link too
Almanac ids in this scene: 008.004.003
the footer "unsubscribe" link is clicked, and the page loads already reading "You are unsubscribed." No second button.
Almanac 008.004.003: "The unsubscribe link in your footer should process the opt-out immediately on click... the opt-out should already be done when the page loads, not when they click a second button."
05 · The decision
Almanac ids in this scene: 008.004.003
a preference center sits next to a plain "unsubscribe from everything" link, both easy to find. An arrow points to the plain link: "always keep this one".
Almanac 008.004.003: "A preference center is a smart complement to a simple unsubscribe, not a replacement for it... you still need a clear 'unsubscribe from everything' option that's easy to find."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V935When should you get a dedicated IP?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the December-spike calendar device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. A shiny badge reads Dedicated IP = better deliverability, then a red stamp lands across it: "Not if you are small."
Someone tells you a dedicated IP means better deliverability, and it sounds like an obvious upgrade. For most senders, switching to one makes things worse, not better.
02 · Why it starts worse · 0:07
On screen: a brand-new IP with a reputation gauge sitting at zero, and mailbox providers eyeing it warily.
A dedicated IP is an address that only you send from. That sounds great, but a fresh one starts with zero sending reputation, and mailbox providers are cautious about an address they have never seen. Send ten thousand a month from a new dedicated IP and your delivery almost certainly gets worse before it gets better.
03 · The two numbers that decide it · 0:22
On screen: two dials, mono: volume, 50,000 to 100,000+ a month and schedule, every week, consistent. A warm-up bar reads 4 to 8 weeks, start with your most engaged.
Two things decide whether you are ready. Volume and consistency. Most providers suggest a dedicated IP above fifty to a hundred thousand emails a month, sent on a regular schedule, and only after a four to eight week warm-up that starts with your most engaged subscribers.
04 · Consistency is not optional · 0:36
On screen: a calendar shows a huge December spike, then silence through to March, and the IP's reputation gauge sags between sends.
And the schedule matters as much as the size. Blast three hundred thousand in December, then go quiet until March, and your dedicated IP reputation fades between sends. You will fight your way back every time you return.
05 · The decision · 0:44
On screen: a sender below the threshold rests happily on a shared pool, with a note: "ask your provider if you qualify".
So below that, stay on a well-managed shared pool. And ask your provider whether you qualify. If they say you are not ready, you are not ready.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-009.002.007-when-dedicated-ip.md
01 · The hook
paper. A shiny badge reads Dedicated IP = better deliverability, then a red stamp lands across it: "Not if you are small."
room tone.
it takes the common belief and reverses it, which is the whole video.
02 · Why it starts worse
Almanac ids in this scene: 009.002.007
a brand-new IP with a reputation gauge sitting at zero, and mailbox providers eyeing it warily.
Almanac 009.002.007: "A dedicated IP starts with zero sending reputation, and mailbox providers are cautious about IP addresses they've never seen before... if you're sending 10,000 emails a month... your deliverability will almost certainly get worse before it gets better."
03 · The two numbers that decide it
Almanac ids in this scene: 009.002.007
two dials, mono: volume, 50,000 to 100,000+ a month and schedule, every week, consistent. A warm-up bar reads 4 to 8 weeks, start with your most engaged.
Almanac 009.002.007: "dedicated IPs for senders above 50,000 to 100,000 emails per month who send on a regular schedule... The warm-up process typically takes four to eight weeks: you start by sending only to your most engaged subscribers."
04 · Consistency is not optional
Almanac ids in this scene: 009.002.007
a calendar shows a huge December spike, then silence through to March, and the IP's reputation gauge sags between sends.
Almanac 009.002.007: "If you send 300,000 emails in December and then go quiet until March, your dedicated IP's reputation will degrade between sends, and you'll face deliverability headaches when you ramp back up."
05 · The decision
Almanac ids in this scene: 009.002.007
a sender below the threshold rests happily on a shared pool, with a note: "ask your provider if you qualify".
Almanac 009.002.007: "If they say you're not ready, you're not ready, and pushing anyway creates more problems than staying on a well-managed shared pool."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V936Does volume alone cause spam filtering?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "looks like a spammer" tag device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. A myth card, Lora: "Send too many emails and you get flagged as spam." A red line strikes through it.
Send too many emails and you will get flagged as spam. It sounds logical. It is also not how any of this works.
02 · The proof · 0:07
On screen: a huge counter spins to billions per day, and the mail still lands in the inbox, not spam.
The biggest senders in the world push billions of emails every single day, and they land in the inbox, not spam. If sheer volume triggered filters, that would be impossible. The volume is not the problem. Volume without trust is.
03 · Filters score trust, not counts · 0:20
On screen: two senders. One, a full reputation gauge, pushes millions/day straight to inbox. The other, an empty gauge, sends 1,000 and hits a wall.
Filters do not count your messages and trip a wire at some number. They score your reputation. Your authentication, your bounces, your engagement history. A sender with a strong reputation clears every filter at millions a day. A sender with none can get blocked at a thousand.
04 · When volume does bite · 0:34
On screen: a brand-new domain suddenly blasts a huge list, and the pattern gets tagged looks like a spammer. Beside it, a warm-up ramp climbs slowly and stays green.
So when does volume actually bite. When it shows up suddenly, from a fresh domain that has not earned any standing. That looks exactly like what a spammer does, spin up a domain, blast, and vanish. That is why you warm up. Start small, build a clean track record, then scale.
05 · The decision · 0:44
On screen: a checklist ticks: send to people who want it, authenticate, clean list, scale slowly.
So the honest answer. Volume is not the sin. Irresponsible volume is. Send to people who want you, authenticate your domain, keep your list clean, and build up gradually. Then scale is just scale.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-011.013.003-does-volume-cause-spam.md
01 · The hook
paper. A myth card, Lora: "Send too many emails and you get flagged as spam." A red line strikes through it.
room tone.
it states the belief plainly and knocks it down, so the viewer leans in.
02 · The proof
Almanac ids in this scene: 011.013.003
a huge counter spins to billions per day, and the mail still lands in the inbox, not spam.
Almanac 011.013.003: "Gmail, Mailchimp, and Amazon send billions of emails every single day without landing in spam folders... The volume isn't the problem. The problem is volume without trust."
vendor names in the source are not spoken. "The biggest senders in the world" only.
03 · Filters score trust, not counts
Almanac ids in this scene: 011.013.003
two senders. One, a full reputation gauge, pushes millions/day straight to inbox. The other, an empty gauge, sends 1,000 and hits a wall.
Almanac 011.013.003: "They score senders based on sender reputation... A sender with a strong reputation can push millions of messages a day and clear every filter. A sender with no reputation who sends a thousand messages can trigger blocks immediately."
the source's complaint-rate figure is pre-screened out. Not spoken.
04 · When volume does bite
Almanac ids in this scene: 011.013.003
a brand-new domain suddenly blasts a huge list, and the pattern gets tagged looks like a spammer. Beside it, a warm-up ramp climbs slowly and stays green.
Almanac 011.013.003: "volume does become a problem when it arrives suddenly from a domain or IP that hasn't earned any standing yet... matches what spammers actually do... This is why warming up a new sending domain or IP matters so much."
05 · The decision
Almanac ids in this scene: 011.013.003
a checklist ticks: send to people who want it, authenticate, clean list, scale slowly.
Almanac 011.013.003: "volume isn't the sin. Irresponsible volume is. Send to people who actually want your email, authenticate your domain properly with SPF, DKIM, and DMARC, keep your list clean, and build your sending history gradually. At that point, scale is just scale."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V937What is A/B testing in email?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "meaningless stamp" device in shot 3, or a simpler swap.
01 · The hook · 0:00
On screen: paper. Two subject lines side by side, a person staring, a thought bubble: "Which one?" A coin hovers, about to be flipped, then a teal X crosses out the coin.
Two subject lines, and you cannot decide which your subscribers will open. Stop guessing. This is the exact moment A/B testing was made for.
02 · What it is · 0:07
On screen: the list splits into two random slices. Slice A gets version A, slice B gets version B, and a meter compares them.
A/B testing, also called split testing, means sending two versions of an email to two random slices of your list, and measuring which one performs better. Version A is your control. Version B changes one thing. Then you let the results tell you which your audience preferred.
03 · The one rule · 0:22
On screen: two variables change at once (subject AND send time), and the result panel stamps "meaningless" in red. Then it resets to one change, and the panel reads clear result.
Here is the rule that makes a test worth running. Change exactly one thing. Subject line, or send time, or the button, one of them. Change two at once and your data is meaningless, because you will never know which one moved the needle.
04 · Decide the winner first · 0:34
On screen: before the send, a metric is circled, mono options: opens, clicks, revenue. A rough note: about 1,000 per version.
And decide what winning means before you send, not after you see the numbers. Opens, clicks, or revenue, pick one. A rough starting point is about a thousand people per version. Smaller lists can still test, just treat the answer as a lean, not a law.
05 · The decision · 0:44
On screen: a subject-line test kicks off first, and a small note reads "opens lift everything downstream".
So start with subject lines. They are quick to write, easy to isolate, and they move opens, which moves everything after. Test one, learn, then move on.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-013.001.001-what-is-ab-testing.md
01 · The hook
paper. Two subject lines side by side, a person staring, a thought bubble: "Which one?" A coin hovers, about to be flipped, then a teal X crosses out the coin.
room tone.
it names the everyday stuck moment and offers the tool by name.
02 · What it is
Almanac ids in this scene: 013.001.001
the list splits into two random slices. Slice A gets version A, slice B gets version B, and a meter compares them.
Almanac 013.001.001: "sending two versions of an email to separate slices of your audience and measuring which one performs better. Version A is your control. Version B changes exactly one thing."
03 · The one rule
Almanac ids in this scene: 013.001.001
two variables change at once (subject AND send time), and the result panel stamps "meaningless" in red. Then it resets to one change, and the panel reads clear result.
Almanac 013.001.001: "Change two things at once and you'll never know which one moved the needle. Subject line and send time in the same test? Your data becomes meaningless."
04 · Decide the winner first
Almanac ids in this scene: 013.001.001
before the send, a metric is circled, mono options: opens, clicks, revenue. A rough note: about 1,000 per version.
Almanac 013.001.001: "A winner metric decided in advance... A rough starting point is 1,000 people per variation... treat the findings as directional rather than definitive."
05 · The decision
Almanac ids in this scene: 013.001.001
a subject-line test kicks off first, and a small note reads "opens lift everything downstream".
Almanac 013.001.001: "Subject lines are the highest-impact starting point for most senders. They're quick to write, easy to isolate, and they directly affect open rates which affect everything downstream."
ends on a decision. No open-rate guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V938What is send time optimization?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the three-clock fan-out in shot 2, or a simpler single-clock swap.
01 · The hook · 0:00
On screen: paper. A calendar with "Tuesday 10am" circled in red, then a big teal X drawn through the circle. Lora beside it: "Wrong question."
Everyone asks what is the best time to send an email. It is the wrong question, because the best time is not the same for any two people on your list.
02 · What it is · 0:07
On screen: one email icon fans out into three, each landing in a different person's inbox at a different clock time, mono: 7:00 am, 1:10 pm, 8:40 pm.
Send time optimization is a feature in many email marketing tools. Instead of one time for your whole list, it delivers your email to each person during their own peak window. The early riser gets it at seven. The after-dinner reader gets it at night. Same campaign, different arrival times, all automated.
03 · How it knows · 0:22
On screen: a subscriber row builds a small history strip of past opens, mono timestamps, then a held envelope releases at the matching hour.
Here is how it knows. The tool watches when each subscriber opened or clicked before, and builds a profile of their habits. When you send, it holds each message and lets it go at that person's moment. New subscribers with no history get a default time until the pattern fills in.
04 · Where it stops · 0:34
On screen: three short bars. One grows (opens up). One flat with caption needs history. One flat with caption will not fix weak content.
It lifts opens and it keeps you out of the Tuesday-morning crowd everyone else sends into. But it needs history to work, it adapts slowly when habits change, and it will not fix a weak subject line or a boring email. Timing helps at the margins, not the fundamentals.
05 · The decision · 0:44
On screen: a simple fork. Left: sending consistently, have history points to "turn it on". Right: new or patchy list points to "nail content and a baseline first".
So if you send consistently and have the history, turn it on. If your list is new, get your content and your baseline right first.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-013.010.002-send-time-optimization.md
01 · The hook
paper. A calendar with "Tuesday 10am" circled in red, then a big teal X drawn through the circle. Lora beside it: "Wrong question."
room tone.
it kills the assumption the viewer walked in with and sets up the real idea.
02 · What it is
Almanac ids in this scene: 013.010.002
one email icon fans out into three, each landing in a different person's inbox at a different clock time, mono: 7:00 am, 1:10 pm, 8:40 pm.
Almanac 013.010.002: "it delivers your email to each person when they're most likely to actually open it... Same campaign, different arrival times, all automated."
03 · How it knows
Almanac ids in this scene: 013.010.002
a subscriber row builds a small history strip of past opens, mono timestamps, then a held envelope releases at the matching hour.
Almanac 013.010.002: "The ESP tracks when each subscriber has opened or clicked past emails. Over time, it builds a profile... For new subscribers with no history, most platforms fall back to a default window."
04 · Where it stops
Almanac ids in this scene: 013.010.002
three short bars. One grows (opens up). One flat with caption needs history. One flat with caption will not fix weak content.
Almanac 013.010.002: "It needs historical data to work well... Behavior changes... It doesn't fix a bad subject line or uninteresting content. Timing helps at the margins, not the fundamentals."
05 · The decision
Almanac ids in this scene: 013.010.002
a simple fork. Left: sending consistently, have history points to "turn it on". Right: new or patchy list points to "nail content and a baseline first".
Almanac 013.010.002: "if you're still figuring out your baseline send time before enabling STO, the sister question on testing send times manually is worth reading first."
ends on a decision. No open-rate or inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V939Is automation set and forget?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Whether to point the description at the free SOS hotline named in the source, or keep the clean-list link.
01 · The hook · 0:00
On screen: paper. A welcome flow with a big green "Published" stamp, then a calendar flips forward and the same flow is now dusty, mono label: 6 months later.
You built the welcome flow, hit publish, and moved on. That is the dream. It is also the moment it starts to rot, quietly, with no error message.
02 · What actually rots · 0:07
On screen: three cards flip. One: an email offering a discount code stamped expired in March. Two: a personalization line reading "Hi" with a blank where the name should be, mono: {{first_name}}. Three: a subject line with a falling open-rate bar.
Here is what goes wrong while you are not looking. A discount code that expired months ago still sits in your welcome series. The link between your email tool and your other systems drifts, a field gets renamed, and your greeting now says Hi blank. And the subject lines that pulled forty percent last year are quietly pulling twenty-two. Nobody flagged any of it.
03 · Why you never see it · 0:26
On screen: the flow keeps firing green "sent" ticks while, underneath, the content is visibly wrong. A caption reads "It runs faithfully on the wrong instructions."
The cruel part is it all keeps sending. The trigger still fires, the emails still go out. Automation does not fail loudly, it runs faithfully on instructions that stopped being true. So it hides, until a customer replies confused.
04 · The fix is a rhythm · 0:36
On screen: a small three-row calendar builds, mono: weekly, glance at the numbers, monthly, read every email, quarterly, review the logic. A fourth line: and any time you change a product or price.
The fix is not heavy, it is just a rhythm. Weekly, glance at the numbers for a sudden drop. Monthly, actually read the emails and click every button. Quarterly, review the whole logic. And always right after you change a product, a price, or a tool.
05 · The decision · 0:44
On screen: the dusty flow gets a small recurring "review" badge and brightens back up.
So do not set and forget. Set, and put it on a review rhythm. That is the whole difference.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-014.017.005-automation-not-set-and-forget.md
01 · The hook
paper. A welcome flow with a big green "Published" stamp, then a calendar flips forward and the same flow is now dusty, mono label: 6 months later.
room tone.
it validates the thing they did, then puts a crack in it.
02 · What actually rots
Almanac ids in this scene: 014.017.005
three cards flip. One: an email offering a discount code stamped expired in March. Two: a personalization line reading "Hi" with a blank where the name should be, mono: {{first_name}}. Three: a subject line with a falling open-rate bar.
Almanac 014.017.005: "A discount code that expired in March is still sitting in your welcome series... the personalization tokens pull blank or wrong data. Your email says 'Hi {{first_name}}'... The subject lines that got 40% open rates last year might be pulling 22% now."
the merge tag is shown as an on-screen label and the source is quoted. Copy stays plain.
03 · Why you never see it
Almanac ids in this scene: 014.017.005
the flow keeps firing green "sent" ticks while, underneath, the content is visibly wrong. A caption reads "It runs faithfully on the wrong instructions."
Almanac 014.017.005: "It's not that it fails. It's that it runs faithfully on instructions that are no longer true... Nobody noticed until a customer replied confused."
04 · The fix is a rhythm
Almanac ids in this scene: 014.017.005
a small three-row calendar builds, mono: weekly, glance at the numbers, monthly, read every email, quarterly, review the logic. A fourth line: and any time you change a product or price.
Almanac 014.017.005: "Weekly (5 minutes): Glance at delivery and open rates... Monthly (30 minutes): Read through the emails... Click every CTA... Quarterly: Review the full logic... As needed: Any time you change a product, update pricing, rebrand, or migrate."
05 · The decision
Almanac ids in this scene: 014.017.005
the dusty flow gets a small recurring "review" badge and brightens back up.
Almanac 014.017.005: "The maintenance isn't heavy. It just has to exist."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V940What a bounce actually is
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the earlier Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- Keep or cut the SOS hotline mention (shot 6). The answer offers two next steps, clean the list and send a puzzling code to the SOS hotline.
01 · The hook · 0:00
On screen: paper. One address alone, mono, large: bo.unce@coral-cove.invalid. Above it, Lora, ink, big: "BOUNCED." Below, small: "It came right back."
You hit send. A minute later the same email is back in your inbox, stamped with an error.
02 · What it actually is · 0:05
On screen: the address stays. A small note slides out from behind it, mono, like a returned slip: delivery failed over a placeholder code line 5xx / 4xx.
It means the receiving server would not accept your message, so it sent one back explaining why, with an error code attached.
03 · The two kinds · 0:12
On screen: the screen splits into two mono cards. - Left, edged in suppress #ED5746, header "HARD": address does not exist / domain is gone / permanent. - Right, edged in monitor #F59E0B, header "SOFT": mailbox full / message too large / temporary.
Every bounce is one of two kinds. A hard bounce is permanent. The address does not exist, or the domain is gone, and it will fail the same way tomorrow. A soft bounce is temporary. The mailbox was full, or the message was too big, and it might go through fine next time.
04 · Why it costs you · 0:25
On screen: the hard card pulses. Behind both cards, a faint watching pair of eyes labelled mailbox providers. A thin bar labelled your whole sending domain dims from teal toward grey.
Here is the part that costs people. Keep sending to an address that hard bounced and the mailbox providers watching you read it as a messy list, and that judgment lands on your entire sending domain, not just the message that failed.
05 · Which one, and what to do · 0:34
On screen: two mono chips drop in. 550 user unknown snaps under the red card with a small tag "suppress." 451 try again later snaps under the amber card with "wait."
The error code tells you which one it is. A 550, user unknown, is a hard bounce. Suppress it, and never send there again. A 451, try again later, just needs patience. Most email marketing tools sort this for you, but the defaults run soft, so check yours.
06 · The decision · 0:42
On screen: the red card clears. In its place, three addresses stack and sort, two turning keep #10B981 (safe), one turning suppress #ED5746 (drop), under a header cleaned before you send.
The catch is, the hard bounces are addresses that should never have gotten a send. So clean the list first. A clean flags which addresses are safe and which to drop, before your reputation ever takes the hit. And a code you cannot read? Send it to our SOS hotline and we will decode it.
07 · End card · 0:49
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Clean my list", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-015.001.001-what-is-a-bounce.md
01 · The hook
Almanac ids in this scene: 015.001.001
paper. One address alone, mono, large: bo.unce@coral-cove.invalid. Above it, Lora, ink, big: "BOUNCED." Below, small: "It came right back."
no music yet. Room tone only.
Almanac 015.001.001: "You hit send, and instead of landing in someone's inbox, your email comes right back to you with an error. That's a bounce."
the address is invented. Never a real one, never a client's.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). The mail coming back to the sender is the itch nobody scrolls past.
02 · What it actually is
Almanac ids in this scene: 015.001.001
the address stays. A small note slides out from behind it, mono, like a returned slip: delivery failed over a placeholder code line 5xx / 4xx.
low pulse comes in.
Almanac 015.001.001: "It means the receiving mail server couldn't (or wouldn't) accept your message, and it sent back a notification explaining why." And its summary: the server "returns a notification (a DSN, or Delivery Status Notification) to the sender with an error code explaining why."
most people read a bounce as a dead end. Naming it as a message with the reason inside is the reframe the whole video needs before the fork makes sense.
03 · The two kinds
Almanac ids in this scene: 015.001.001
the screen splits into two mono cards. - Left, edged in suppress #ED5746, header "HARD": address does not exist / domain is gone / permanent. - Right, edged in monitor #F59E0B, header "SOFT": mailbox full / message too large / temporary.
music settles into a steady bed as the two cards land.
Almanac 015.001.001: "Hard bounces are permanent failures. The address doesn't exist, the domain is gone... You shouldn't send to those addresses again. Ever. Soft bounces are temporary failures. The mailbox is full, the receiving server had a blip, or your message was too large. The address might work fine tomorrow."
the two verdict colours are used as the product uses them, no label count is shown or spoken. The frame carries no spam-trap language and no complaint-rate number, because the answer has none and both are off limits on a marketing surface anyway.
the honest split is what makes the rest land. If the viewer believes the two kinds are real and different, the "opposite moves" payoff actually bites.
04 · Why it costs you
Almanac ids in this scene: 015.001.001
the hard card pulses. Behind both cards, a faint watching pair of eyes labelled mailbox providers. A thin bar labelled your whole sending domain dims from teal toward grey.
the bed thins to one held note as the bar dims.
Almanac 015.001.001: "Mailbox providers like Gmail and Outlook watch your bounce rate closely. A high bounce rate signals that your list is messy... Keep sending to bounced addresses and your sender reputation will take a hit that affects your entire sending domain, not just the messages going to bad addresses."
no inbox-placement guarantee, this states a cost, not a promise. No bounce-rate threshold is shown or spoken, the answer keeps it qualitative and so does this.
this is the stake in one beat, so it carries the longest sentence in the script, paced to how quietly the damage actually spreads.
05 · Which one, and what to do
Almanac ids in this scene: 015.001.001
two mono chips drop in. 550 user unknown snaps under the red card with a small tag "suppress." 451 try again later snaps under the amber card with "wait."
two soft clicks as the chips snap into place.
Almanac 015.001.001: "A 550 code with 'user unknown' is a clear hard bounce. A 451 'try again later' is the server asking you to be patient. Reading those codes is how you figure out whether to suppress an address or just wait it out." And: "Most ESPs handle bounce suppression automatically... it's worth checking your platform's bounce policy so you're not accidentally relying on defaults that are too lenient."
"email marketing tools," never "ESP" (BIBLE section 8). The codes are shown as data, not as a threshold anyone has to hit.
it turns the fork into a thing you can actually do at your desk, which is the firemen move, hand over the read, not the worry.
06 · The decision
Almanac ids in this scene: 015.001.001
the red card clears. In its place, three addresses stack and sort, two turning keep #10B981 (safe), one turning suppress #ED5746 (drop), under a header cleaned before you send.
music returns, warmer, as the addresses sort.
Almanac 015.001.001: "If your bounce rate feels higher than it should be, your list may need a clean... we'll flag what's safe to send to and what to suppress. Or if you're seeing specific error codes you can't interpret, drop them in our SOS hotline and we'll help you decode them."
the clean is spoken only about addresses, safe or drop. It is never implied to fix SPF, DKIM, DMARC, MX or a blocklist, that is a different service. No inbox-placement guarantee. "Review My Emails" is spelled out on the card, never the initials.
ends on a decision, not a number (voice guide section 6). It hands over the two moves the answer itself hands over, clean the list, and decode the odd code, in the answer's own order.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Clean my list", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). The destination is reviewmyemails.com/get-started, the confirmed self-serve target for the cluster. See "Needs YT's yes" on the launch wording.
V941Who counts as a bulk sender?
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Keep the "hover just under then spike over" device in shot 4, or a simpler swap.
01 · The hook · 0:00
On screen: paper. A big question over two logos labelled in text, Gmail, Yahoo: "Do the 2024 rules apply to me?" A single number waits below, blurred.
The Gmail and Yahoo twenty twenty-four rules. Everyone asks if they apply to them. One number answers it, and it is lower than you think.
02 · The line · 0:07
On screen: the number sharpens to 5,000 / day to Gmail. A gate labelled bulk sender swings open once it is crossed.
Here it is. Send five thousand or more emails in a single day to Gmail addresses, and you are officially a bulk sender under Google's rules. Yahoo uses a similar line. Cross it and the requirements kick in, authentication, one-click unsubscribe, and keeping your spam complaints in check.
03 · It counts your whole domain · 0:20
On screen: three separate campaigns from one domain flow into a single counter that ticks past 5,000, mono tags: promo, transactional, mixed.
And here is the part people miss. It counts per domain, not per campaign. Three separate sends from the same domain that add up to five thousand Gmail recipients in a day, that counts. Promotional, transactional, or a mix. It all goes in the same bucket.
04 · Do not game the line · 0:32
On screen: a sender tries to hover just under 5,000, then one big campaign spikes them over and a non-compliant flag drops.
You might think you will just stay under five thousand and skip the work. That is a bad plan. Your volume moves, and the day a big campaign pushes you over, you are suddenly out of compliance. And the rules are not busywork, they are what good senders already do.
05 · The decision · 0:44
On screen: a small sender at 500 / day still sits under a watching eye labelled engagement. A checklist ticks for everyone: authenticate, one-click unsubscribe, keep complaints low.
And even at five hundred a day, they still watch your engagement. The formal line is five thousand, but the best practices are for everyone. So authenticate, add one-click unsubscribe, and keep complaints low, whatever your size.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-019.007.002-who-is-a-bulk-sender.md
01 · The hook
paper. A big question over two logos labelled in text, Gmail, Yahoo: "Do the 2024 rules apply to me?" A single number waits below, blurred.
room tone.
it promises the exact line the viewer is unsure about.
02 · The line
Almanac ids in this scene: 019.007.002
the number sharpens to 5,000 / day to Gmail. A gate labelled bulk sender swings open once it is crossed.
Almanac 019.007.002: "any domain sending 5,000 or more messages per day to Gmail addresses, with Yahoo enforcing a parallel threshold... authentication, one-click unsubscribe, and keeping your spam complaint rate in check."
the source's complaint-rate figure is pre-screened out. "Complaints in check" only.
03 · It counts your whole domain
Almanac ids in this scene: 019.007.002
three separate campaigns from one domain flow into a single counter that ticks past 5,000, mono tags: promo, transactional, mixed.
Almanac 019.007.002: "The count is based on your sending domain, not individual campaigns... they add up to 5,000 Gmail recipients in a day, that counts. It doesn't matter whether the emails are promotional blasts, transactional messages, or a mix of both."
04 · Do not game the line
Almanac ids in this scene: 019.007.002
a sender tries to hover just under 5,000, then one big campaign spikes them over and a non-compliant flag drops.
Almanac 019.007.002: "Volume fluctuates, and the moment a big campaign pushes you over, you'd be out of compliance... they reflect what good senders already do."
05 · The decision
Almanac ids in this scene: 019.007.002
a small sender at 500 / day still sits under a watching eye labelled engagement. A checklist ticks for everyone: authenticate, one-click unsubscribe, keep complaints low.
Almanac 019.007.002: "Even if you're sending 500 emails a day, Gmail and Yahoo are still watching engagement signals. The formal enforcement line is 5,000, but the best practices apply to everyone."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V942Spammy words alone don't put you in spam
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and script #122.
- Launch wording on the end card. RME-16 is defining which posts read as waitlist, coming soon, or live.
- Secondary link to the Subject Line Tester. The Almanac answer itself closes on "our free Subject Line Tester can flag anything that looks risky," a tool that exists and is on-topic for exactly this question.
- Keep or cut the caveat beat (shot 5). It is the honest half of the myth-bust and it is what stops the video from overselling "words never matter" into a new myth, but it adds about six seconds and a second abstract idea right after the...
01 · The hook · 0:00
On screen: paper. A subject line in mono, struck through in three places where words were removed: FREE Buy now !!!, leaving a cautious, hedged line behind it. Under it, stamped in #ED5746: "SPAM."
You deleted every word they warned you about. It still went to spam.
02 · The myth, named · 0:05
On screen: the struck-through words from shot 1 float back up, whole again, circled in red like evidence on a board: FREE, BUY NOW, !!!.
This is what you have been told to hunt for. A list of banned words. It is not real. No filter running today works off a list like that.
03 · What actually gets scored · 0:13
On screen: three mono cards build under the subject line, one per VO beat: sender reputation, authentication with SPF · DKIM · DMARC, engagement with opens · replies · not spam marks.
What actually gets weighed is your sender reputation. Whether your authentication checks out. And whether the people you send to open you, reply, or mark you as spam.
04 · The same words, two verdicts · 0:25
On screen: split screen. Left card: the three cards from shot 3 all lit green, the hedged subject line from shot 1 restored to its original hypey wording, verdict #10B981 "INBOX." Right card: the same three cards dim and grey, the identical hypey line, verdict #ED5746 "SPAM."
Send that exact subject line from a sender with a strong reputation, clean authentication, and real engagement, and it moves through without much trouble, but send the identical words from an unauthenticated address on a cold list, and it gets filtered anyway, because the words were never what the filter was grading in the first place.
05 · The honest caveat · 0:35
On screen: the two verdict cards fade. One line of mono text types out: context still counts.
Words are not nothing. Pile hypey copy on top of weak engagement or missing authentication, and it can tip the balance. It is not the word that triggers the filter. It is the pattern the word fits.
06 · The decision · 0:41
On screen: the subject line clears from the screen entirely. Three mono cards remain, dimmed: reputation, authentication, engagement. A fourth, list, brightens in teal.
So stop rewriting the subject line. Look at your reputation, your authentication, and your engagement instead, starting with what is actually on your list.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned," with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.001.001-spammy-words-myth.md
01 · The hook
paper. A subject line in mono, struck through in three places where words were removed: ~~FREE~~ ~~Buy now~~ ~~!!!~~, leaving a cautious, hedged line behind it. Under it, stamped in #ED5746: "SPAM."
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). The paradox of doing the "right" thing and still losing is the itch nobody scrolls past.
no real subject line or address is used anywhere in this script.
02 · The myth, named
Almanac ids in this scene: 021.001.001
the struck-through words from shot 1 float back up, whole again, circled in red like evidence on a board: FREE, BUY NOW, !!!.
low pulse comes in under "hunt for."
Almanac 021.001.001: "Modern spam filters don't work like a list of forbidden words. They use machine learning to look at hundreds of signals at once."
name the wrong search out loud, the same release-valve move script #122 used, so the correction lands as relief and not a lecture.
03 · What actually gets scored
Almanac ids in this scene: 021.001.001
three mono cards build under the subject line, one per VO beat: sender reputation, authentication with SPF · DKIM · DMARC, engagement with opens · replies · not spam marks.
music settles into a steady bed as the cards land.
Almanac 021.001.001: "What filters actually weight heavily are things like your sender reputation, whether your domain passes authentication checks (SPF, DKIM, DMARC), and how your subscribers engage with your emails over time."
complaint rate is cut here even though the Almanac's own summary line groups it with these signals, because a complaint-rate mention is off limits on a marketing surface regardless of whether a number is attached. Engagement is spoken as open, reply, or Not Spam mark, nothing more specific.
naming the real signals is what makes the next beat land as a reveal instead of a claim nobody can picture.
04 · The same words, two verdicts
Almanac ids in this scene: 021.001.001
split screen. Left card: the three cards from shot 3 all lit green, the hedged subject line from shot 1 restored to its original hypey wording, verdict #10B981 "INBOX." Right card: the same three cards dim and grey, the identical hypey line, verdict #ED5746 "SPAM."
the bed thins to one held note as the second verdict lands.
Almanac 021.001.001: "A well-authenticated sender with healthy engagement can write hypey copy without much consequence. An unknown sender with no authentication and a cold list might get filtered even with the most neutral subject line imaginable."
this is the whole point in one beat, so it carries the longest sentence in the script on purpose, paced to let both halves of the paradox sit side by side.
05 · The honest caveat
Almanac ids in this scene: 021.001.001
the two verdict cards fade. One line of mono text types out: context still counts.
a single soft knock as the line completes.
Almanac 021.001.001: "That said, context still matters. Overly hypey copy in combination with other weak signals... can tip the balance. It's not that the words triggered the filter. It's that the words fit a pattern the filter associates with low-quality sending."
the Almanac's own parenthetical names "low engagement, missing authentication, high complaint rates" as the weak signals. Complaint rate is cut from what is spoken, leaving engagement and authentication only, per the same Stage-1 screen as shot 3.
without this beat the video oversells "words never matter," which the Almanac itself does not claim. This keeps the correction honest instead of turning it into a new myth.
06 · The decision
Almanac ids in this scene: 021.001.001
the subject line clears from the screen entirely. Three mono cards remain, dimmed: reputation, authentication, engagement. A fourth, list, brightens in teal.
music returns, warmer, under "your list."
Almanac 021.001.001: "Focus on the signals that actually move the needle: clean authentication, a healthy list, genuine engagement, and a consistent sending history. Get those right, and your copy has a lot more room to breathe."
list cleaning is presented as one of four separate signals to check, never as a fix for authentication, reputation, or engagement on its own. No inbox-placement guarantee anywhere in this beat.
ends on a decision, not a number (voice guide section 6). It hands the viewer the Almanac's own closing advice, in the Almanac's own order, with the one signal Review My Emails can actually act on picked out.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned," with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3), not sourced to the Almanac. This is product truth from the BIBLE, flagged as such per the template's own instruction. The destination reviewmyemails.com/get-started matches CLAUDE.md rule 5 in this repo's current copy, verified directly against the file rather than assumed, so unlike the earlier Almanac script in this series, there is no live conflict to flag here.
V943Is plain text safer than HTML?
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the earlier Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- Keep or cut the multipart line. The Almanac's own best-practice note is to send both a plain text and an HTML version in one message so the client picks.
01 · The hook · 0:00
On screen: paper. Top half, a styled email shell, mono sender news@preheader-pottery.example, buttons and an image block, shrinks and flattens into a bare wall of plain text. Over it, Lora, ink, big: "Stripped it to plain text." Below, dashed and hollow: "It still went to spam."
You deleted the buttons, the images, all of it. Sent it plain, to be safe. It still went to spam.
02 · The myth · 0:05
On screen: the belief types out in Lora, then a thin line strikes through it: spam looks like flashy HTML, real emails are plain, so plain must be safer.
The logic feels right. Spam looks like loud HTML. Personal notes are plain. So plain must be the safe one. It is not.
03 · What filters actually weigh · 0:11
On screen: the address moves up. Three mono cards build under it, one per line as the VO names it, each with a small dial reading well. - sender reputation with is your domain trusted - authentication with SPF, DKIM, DMARC - engagement with do people open and reply
Filters barely look at the format. They look at whether your domain is trusted, whether your authentication checks out, and whether real people open and reply. Well-built HTML from a trusted sender beats plain text from a shaky one every single time.
04 · The turn · 0:25
On screen: two envelopes slide in side by side from the same sender card, one HTML, one plain text. Both drop into the same tray, and the tray flips to "SPAM" in #ED5746.
So here is the part that traps people. From a struggling sender, the plain email and the HTML email land in exactly the same place. Stripping the format changed nothing, because the format was never what pulled you down.
05 · The grain of truth · 0:33
On screen: one HTML shell fills the screen with four faults flagged in #F59E0B: broken tags, all image, no text, hidden white-on-white text, links that do not match.
The myth has a grain of truth. HTML gives you more ways to mess it up. Broken code, an email that is one big image, hidden text, dodgy links. But that is bad code, not the format. Clean HTML trips none of it.
06 · The decision · 0:41
On screen: the faults clear to two mono cards side by side. authentication over "check it free" and your list over "clean it". A thin teal rule between them.
So stop stripping your email. Fix the things that actually move you. Check your authentication free. And clean your list, so the dead weight stops dragging your reputation down. Then send it however reads best.
07 · End card · 0:49
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.001.004-plaintext-vs-html-myth.md
01 · The hook
paper. Top half, a styled email shell, mono sender news@preheader-pottery.example, buttons and an image block, shrinks and flattens into a bare wall of plain text. Over it, Lora, ink, big: "Stripped it to plain text." Below, dashed and hollow: "It still went to spam."
no music yet. Room tone only.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Doing the careful thing and still failing is the itch nobody scrolls past.
the address is invented. Never a real one, never a client's.
02 · The myth
Almanac ids in this scene: 021.001.004
the belief types out in Lora, then a thin line strikes through it: spam looks like flashy HTML, real emails are plain, so plain must be safer.
low pulse comes in under the strike.
Almanac 021.001.004: "Plain text isn't inherently safer than HTML for deliverability. Both formats reach the inbox just fine when you're a legitimate sender with solid authentication behind you."
say the wrong belief out loud in the viewer's own words so the correction lands as relief, not a lecture.
03 · What filters actually weigh
Almanac ids in this scene: 021.001.004
the address moves up. Three mono cards build under it, one per line as the VO names it, each with a small dial reading well. - sender reputation with is your domain trusted - authentication with SPF, DKIM, DMARC - engagement with do people open and reply
music settles into a steady bed as the dials rise.
Almanac 021.001.004: "What spam filters actually evaluate is your sender reputation, your authentication setup (SPF, DKIM, DMARC), your engagement history... A beautifully coded HTML email from a trusted sender will outperform a plain text email from a sketchy domain every single time."
the Almanac line also names "how many complaints your emails generate." Engagement is spoken as open-and-reply only, and no complaint-rate number is shown or said, because a threshold on a marketing surface is off limits. No inbox-placement promise is made.
naming the real signals honestly is what earns the reframe. If the viewer believes these are what counts, the reveal that format is not on the list actually bites.
04 · The turn
Almanac ids in this scene: 021.001.004
two envelopes slide in side by side from the same sender card, one HTML, one plain text. Both drop into the same tray, and the tray flips to "SPAM" in #ED5746.
the bed thins to one held note as both envelopes land.
Almanac 021.001.004: "The format itself isn't what filters care about most... Both formats reach the inbox just fine when you're a legitimate sender with solid authentication behind you."
this is the whole point in one beat, so it carries the longest sentence in the script on purpose, paced to the quiet letdown of effort spent on the wrong thing.
05 · The grain of truth
Almanac ids in this scene: 021.001.004
one HTML shell fills the screen with four faults flagged in #F59E0B: broken tags, all image, no text, hidden white-on-white text, links that do not match.
a soft knock on each fault as it flags.
Almanac 021.001.004: "HTML does introduce more ways to mess things up... Broken or malformed HTML... Excessive image-to-text ratio... Hidden text. White text on a white background... Suspicious link structures... Well-built HTML from a reputable sender doesn't hit any of those."
these are content-scoring faults, presented as code quality, not a verdict on the reader. No spam-trap claim (the answer makes none). No named email platform, the Almanac's ESP examples are left off this surface.
it is the most honest beat in the answer and the most shareable. Conceding the grain of truth is what makes the reframe trustworthy instead of a sales line.
06 · The decision
Almanac ids in this scene: 021.001.004
the faults clear to two mono cards side by side. authentication over "check it free" and your list over "clean it". A thin teal rule between them.
music returns, warmer, under "clean it".
Almanac 021.001.004: "don't strip your HTML to chase some deliverability shortcut. Fix your authentication, keep your list clean, and write emails people actually want to open. That's what moves your sender reputation in the right direction."
the two checks stay two separate sentences for two separate signals. Cleaning the list is never implied to fix authentication, and neither one is a promise of inbox placement. No inbox-placement guarantee, ever.
ends on a decision, not a number (voice guide section 6). It hands the viewer the two moves the Almanac itself hands them, in the Almanac's own order.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is reviewmyemails.com/get-started, the confirmed cluster CTA. See "Needs YT's yes" on the launch wording.
V944No one can guarantee inbox placement
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the existing Review My Emails video precedents.
- End card destination: clean, or check. Specced to match the locked template's standard end card (/get-started, "Get my list cleaned"), the same offer every script in this fan-out uses.
- The launch wording on the end card. Same open item the gold-standard script flagged (RME-16, defining which posts read as waitlist, coming-soon, or live).
- Keep or cut shot 5 (the vendor test). It is the most actionable line in the answer and the direct payoff to the hook, but it adds about ten seconds.
01 · The hook · 0:00
On screen: paper. A pitch line types out in mono, like a DM or a sales email: "We guarantee 99% inbox placement." A stamp lands over it, hollow, ink: RED FLAG.
A vendor just promised guaranteed inbox placement. That's not a selling point.
02 · Who actually decides · 0:05
On screen: the stamped line fades. Three names sit in a row, mono, plain: Gmail, Outlook, Yahoo. Under them, dashed: signals you never see.
No one can guarantee it. Not an ESP, not a consultant, not a tool. The call sits with Gmail, Outlook, and Yahoo, on signals a sender never gets to see.
03 · What you actually control · 0:13
On screen: four cards build in a row, one per phrase, mono labels: authentication, list hygiene, engagement, content patterns. A thin teal rule ties them together under a header: your side of the equation.
Here's what's actually yours to run: authentication that proves your mail is legitimate, a list that's clean and engaged so mailbox providers know your mail is wanted, and content and sending habits that build your reputation over time.
04 · The honest limit · 0:28
On screen: the four cards settle into a single dial, needle rising but never touching a 100% mark at the top, which stays greyed out, unreachable.
None of it guarantees anything. It shifts the odds. That's the whole game.
05 · The real test · 0:35
On screen: the dial clears. A single line of mono text types out like a question being typed into a chat box: "What do you track, and how do you help me improve it?"
So stop shopping for a guarantee. Ask a vendor what they track instead, and how they help you improve it. Monitoring and a feedback loop is a real answer. A guarantee is not.
06 · End card · 0:45
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.001.009-no-inbox-guarantee.md
01 · The hook
Almanac ids in this scene: 021.001.009
paper. A pitch line types out in mono, like a DM or a sales email: "We guarantee 99% inbox placement." A stamp lands over it, hollow, ink: RED FLAG.
no music yet. Room tone only, then a single hard knock under the stamp.
Almanac 021.001.009: "If a vendor tells you they can guarantee your emails hit the inbox every time, that's a red flag. Not a sales tactic to overlook. A genuine red flag."
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Opening on someone else's false promise, not our own claim, keeps the hook honest from frame one.
the pitch line is invented, a generic vendor line, never a real competitor or a real client quoted. The 99% figure is someone else's false claim, stamped RED FLAG in the same beat it appears, never Review My Emails' own number and never on screen unchallenged. It does not reappear anywhere later in the script.
02 · Who actually decides
Almanac ids in this scene: 021.001.009
the stamped line fades. Three names sit in a row, mono, plain: Gmail, Outlook, Yahoo. Under them, dashed: signals you never see.
low pulse comes in.
Almanac 021.001.009: "No one can guarantee inbox placement. Not an ESP, not a deliverability consultant, not a magic tool... Mailbox providers like Gmail, Outlook, and Yahoo Mail make their own filtering decisions based on recipient behavior, their internal algorithms, individual user settings, and signals that change constantly."
names the actual decision-maker before the video says a word about what the sender can do, so the shift in shot 3 lands as fact, not reassurance.
03 · What you actually control
Almanac ids in this scene: 021.001.009
four cards build in a row, one per phrase, mono labels: authentication, list hygiene, engagement, content patterns. A thin teal rule ties them together under a header: your side of the equation.
music settles into a steady bed as the cards build.
Almanac 021.001.009: "What you can control is your side of the equation. Strong authentication (SPF, DKIM, DMARC) tells mailbox providers your mail is legitimate. A clean, engaged list tells them your mail is wanted. Relevant content and good sending habits build a reputation over time."
authentication is named as one lever among four, never as a fix for list problems or vice versa.
this is the video's whole reason to exist. Four concrete, ownable things, said plainly, right after the reader has been told the outcome is not theirs to promise.
04 · The honest limit
Almanac ids in this scene: 021.001.009
the four cards settle into a single dial, needle rising but never touching a 100% mark at the top, which stays greyed out, unreachable.
the bed thins to one held note.
Almanac 021.001.009: "None of that guarantees anything, but it shifts the odds meaningfully in your favor."
the dial never reaches or implies 100%. No number is shown on it, because a number here would read as a placement rate promise, which is exactly what this video is not allowed to make.
says the quiet part out loud instead of letting the four levers in shot 3 quietly imply a guarantee by accident. The short sentence is deliberate, it is the rule stated flat.
05 · The real test
Almanac ids in this scene: 021.001.009
the dial clears. A single line of mono text types out like a question being typed into a chat box: "What do you track, and how do you help me improve it?"
music holds steady.
Almanac 021.001.009: "When evaluating a vendor, ask them this instead: 'What deliverability metrics do you track, and how do you help me improve them over time?' A good answer involves monitoring, diagnostics, and feedback loops. A bad answer involves guarantees."
hands the viewer a tool for the next time they get pitched, which is the payoff to the shot 1 hook. It also closes the loop on the villain: the guarantee, not the sender.
06 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is /get-started, the confirmed target. See "Needs YT's yes" on whether this end card should instead route to the two free checkers (SPF, DKIM) that the Almanac answer itself names, since this page's own recommended next step is a check, not a clean.
V945Resending to non-openers, help or hurt
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- The soft promo fit, this is a tactics answer, so the clean-list end card is a softer tie. Keep it, or end on the tactic decision alone.
01 · The hook · 0:00
On screen: paper. A campaign with a low open rate, and a finger hovering over "resend to non-openers". Line, Lora: "Before you resend to non-openers, read this."
You checked the open rate, and now you are about to resend to everyone who did not open. That can help you or wreck you, and it comes down to how.
02 · The hidden problem · 0:06
On screen: the "did not open" pile. A chunk of it is quietly tagged "actually did open".
First, your non-opener list is a lie. Apple Mail pre-loads the tracking pixel for its users, so a chunk of your did-not-open pile actually did open. Resend blindly and you are re-emailing people who already saw it. That annoys them.
03 · The four rules · 0:18
On screen: four rule cards flip up one at a time, mono. - wait 3 to 5 days - rewrite the subject, do not tweak it - only recent engagers, opened or clicked in 90 days - one resend, never a third
So do it with discipline. Wait three to five days, not twenty four hours. Rewrite the subject line into a genuinely different angle, do not just swap a word. Only resend to people who opened or clicked something in the last ninety days. And do it once. A third email just annoys people into hitting spam.
04 · The version that hurts · 0:38
On screen: the opposite, in red: same subject, next day, sent to the whole cold list, and a spam meter climbs.
The version that hurts is easy to spot. Same subject, next day, blasted to everyone no matter how cold. Filters notice repeated sends to people who never engage, and your reputation pays for it.
05 · The decision · 0:44
On screen: one card: "recent engagers, fresh subject, once".
So resend to recent engagers only, with a fresh subject, one time. Otherwise leave the cold ones alone.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.001.013-resending-to-non-openers.md
01 · The hook
paper. A campaign with a low open rate, and a finger hovering over "resend to non-openers". Line, Lora: "Before you resend to non-openers, read this."
room tone.
it catches the exact moment the mistake is about to happen.
02 · The hidden problem
Almanac ids in this scene: 021.001.013
the "did not open" pile. A chunk of it is quietly tagged "actually did open".
Almanac 021.001.013: "Mail Privacy Protection (MPP) from Apple Mail pre-loads tracking pixels on behalf of users, which means some of the people in your did not open segment actually did open."
03 · The four rules
Almanac ids in this scene: 021.001.013
four rule cards flip up one at a time, mono. - wait 3 to 5 days - rewrite the subject, do not tweak it - only recent engagers, opened or clicked in 90 days - one resend, never a third
Almanac 021.001.013: "Wait at least 3-5 days... Change the subject line... Only resend to subscribers who have opened or clicked something from you in the last 90 days... One resend, not two or three."
04 · The version that hurts
Almanac ids in this scene: 021.001.013
the opposite, in red: same subject, next day, sent to the whole cold list, and a spam meter climbs.
Almanac 021.001.013: "no subject line change, same day or next day, sent to everyone who didn't open regardless of how cold they are. Spam filters notice repeated sends to unengaged addresses."
05 · The decision
Almanac ids in this scene: 021.001.013
one card: "recent engagers, fresh subject, once".
Almanac 021.001.013: "a tighter segment (recent engagers only), a fresh subject line, and a respectful wait. Done once, not repeatedly."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V946Is deliverability luck or logic?
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the standing format for this series.
- The end card wording and destination. Reused verbatim from the first two scripts in the series ("Your first thousand addresses, cleaned free," CTA to reviewmyemails.com/get-started).
- Two-check end card vs one-check end card. Shot 5 checks both SPF and DMARC free, matching the Almanac's own "those two alone" line.
01 · The hook · 0:00
On screen: paper. Two identical-looking sends, same invented sender, stacked: promo@bounceback-gym.example over two rows. Left row: address plus green tag "INBOX". Right row: same address, same day, red tag "SPAM". Under both, dashed and hollow, the question: "Same sender. Same day. Different result."
Same sender. Same day. One lands, one doesn't. That's not chance. That's a scoreboard you haven't seen yet.
02 · The myth · 0:05
On screen: the two rows fade. Large ink type, Lora: a sentence typing out then struck through, "it just ended up in spam", with a small shrug mark beside it that also gets struck. Below it, typed in clean: "Logic. Not luck."
You've heard someone shrug it off like it's the weather. It isn't. Mailbox providers aren't rolling dice. They're running a calculation.
03 · The four signals · 0:11
On screen: the sender address moves up. Four gauges build under it, one per line as the VO names it, each a mono label with a small dial. All four settle reading well. - authentication with SPF, DKIM, DMARC - reputation with your sending history - engagement with opens, replies, deletes - sending practices with list hygiene, opt-in, unsubscribes
Four things decide it, and you control all four. Your authentication. Your sending history. Whether people engage or ignore you. And how clean your sending practices are.
04 · The turn · 0:28
On screen: three dials hold and glow green. One, sending practices, drops into amber, then red. The right-hand row from shot 1 flickers back in, tag still reading "SPAM."
When it looks random, it's almost never random. One of these four slipped and nobody was watching it. Individual sends can still wobble, but the pattern across many doesn't lie.
05 · The decision · 0:37
On screen: the four gauges clear to two, side by side, each a mono card. SPF over "check it free" and DMARC over "check it free." A thin teal rule between them.
So stop guessing. Start with the two easiest to check today. Your SPF record. Your DMARC policy. Both free, both in minutes.
06 · End card · 0:45
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.001.016-luck-or-logic.md
01 · The hook
Almanac ids in this scene: 021.001.016
paper. Two identical-looking sends, same invented sender, stacked: promo@bounceback-gym.example over two rows. Left row: address plus green tag "INBOX". Right row: same address, same day, red tag "SPAM". Under both, dashed and hollow, the question: "Same sender. Same day. Different result."
no music yet, room tone only.
Almanac 021.001.016: "deliverability isn't luck. It's logic. And once you see the patterns, you can't unsee them."
the address is invented. Never a real one, never a client's.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Per the angle note, the hook is the flat assertion of control, not a weather image, the myth itself is named one beat later.
02 · The myth
Almanac ids in this scene: 021.001.016
the two rows fade. Large ink type, Lora: a sentence typing out then struck through, "it just ended up in spam", with a small shrug mark beside it that also gets struck. Below it, typed in clean: "Logic. Not luck."
low pulse comes in under the strike-through.
Almanac 021.001.016: "You've probably heard someone say their emails 'just ended up in spam' with a shrug, like it was the weather. But deliverability isn't luck. It's logic... Mailbox providers like Gmail and Outlook aren't rolling dice when they decide where your email lands. They're running calculations."
name the wrong belief out loud so the correction reads as relief, not a lecture, matching the shot-2 pattern from the first two scripts in this series.
03 · The four signals
Almanac ids in this scene: 021.001.016
the sender address moves up. Four gauges build under it, one per line as the VO names it, each a mono label with a small dial. All four settle reading well. - authentication with SPF, DKIM, DMARC - reputation with your sending history - engagement with opens, replies, deletes - sending practices with list hygiene, opt-in, unsubscribes
music settles into a steady bed as the dials rise.
Almanac 021.001.016, its four named signals: "Authentication... Reputation... Engagement... Sending practices." The detail line for each, in order. Authentication: "Does your sending domain have valid SPF, DKIM, and DMARC records?" Reputation: "What's your history? High complaint rates, lots of bounces, and sudden volume spikes all leave marks on your sender reputation." Engagement: "Are your subscribers opening, clicking, and replying? Or are they ignoring and deleting?" Sending practices: "Do you clean your list regularly? Do you send to people who actually opted in? Do you honor unsubscribes fast?"
reputation is spoken as "high complaint rates, lots of bounces, sudden volume spikes," never as the 0.1 percent complaint-rate figure the Almanac's summary carries. That number is cut from this surface per the pre-screen note. No spam-trap language appears anywhere in this signal, the Almanac answer itself does not raise one here.
naming all four honestly is what sets up the turn. If the viewer believes the four are real and checkable, the reveal that "random" is really one of the four slipping actually bites.
04 · The turn
Almanac ids in this scene: 021.001.016
three dials hold and glow green. One, sending practices, drops into amber, then red. The right-hand row from shot 1 flickers back in, tag still reading "SPAM."
the bed thins to one held note as the red dial lands.
Almanac 021.001.016: "When deliverability looks random, it almost always means one of these signals is off... The variables aren't mysterious. They're just not yet visible. Individual email outcomes can vary (complex filter interactions, domain-level quirks, inbox-specific rules), but the aggregate pattern is consistent. Good practices produce better results than poor ones, reliably and repeatedly."
no inbox-placement guarantee. The line stays at "the pattern doesn't lie," it never promises any single send will land.
this is the whole point in one beat, so it carries the longest sentence in the script on purpose, paced to match how quietly the damage actually happens.
05 · The decision
Almanac ids in this scene: 021.001.016
the four gauges clear to two, side by side, each a mono card. SPF over "check it free" and DMARC over "check it free." A thin teal rule between them.
music returns, warmer, under "both free."
Almanac 021.001.016: "If you want to start with a quick audit, check whether your SPF record and DMARC policy are set up correctly. Those two alone account for a surprising number of 'random' deliverability problems. You can run both checks free at our SPF checker and DMARC parser."
SPF and DMARC stay two separate checks for two separate records, and neither is framed as fixing engagement or sending practices. Checking authentication is never framed as a promise of inbox placement.
ends on a decision, not a number (voice guide section 6). It hands the viewer the exact first move the Almanac itself hands them.
06 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
this end card matches the standing wording from the first two scripts in the series (list credits, /get-started). See "Needs YT's yes" below, this beat only tells the viewer where the free SPF and DMARC checks live, and points list cleaning at the sending practices and engagement signals, not at authentication.
V947Bigger lists mean better results, right?
draftedOpen questions for YT
- On camera or voice only. Same open question as the first two scripts in the series: specced as voice over motion graphics.
- The launch wording on the end card. Same RME-16 dependency as the prior scripts: until that lands, this end card states the offer and the destination without claiming a launch state either way, and needs re-checking against RME-16...
- The CTA destination and wording diverge from the Almanac page itself. The live Almanac page's own CTA points to the RME Clean service (/done-for-you) and to /sos.
- Keep or cut the honesty beat in shot 6. "Growing a smaller, highly engaged list is genuinely harder than just accumulating addresses" is in the Almanac, and the script keeps its spirit in "Growing the right number is the work." A beat...
01 · The hook · 0:00
On screen: paper background. Two stacked counters in mono, right-aligned: 50,000 large, ink #013b3b, dimmed to low opacity. Below it 500 in teal #0f766e, full opacity, same type size. Between them, Lora, ink: "Which list actually works?"
Fifty thousand subscribers. Five hundred subscribers. Only one of these is actually working for you.
02 · The myth · 0:05
On screen: the 50,000 counter ticks upward on screen, mono, a satisfying climb. A dashed line beneath it reads: "the number every dashboard shows you."
Every dashboard makes list size look like the score. Bigger number, better email marketing, right?
03 · The correction · 0:12
On screen: the ticking counter freezes. Cut to a split screen. Mono labels rise one at a time on the left, in teal: opens, clicks, replies, forwards. On the right, in #ED5746: spam reports, deletes without opening, unsubscribes. Centered above both, Lora: "Gmail and Outlook do not count. They watch."
Mailbox providers like Gmail and Outlook do not care how many people are on your list, because what they actually track is whether those people open your email, click on it, reply to it, or delete it without ever opening it at all.
04 · The benchmark · 0:24
On screen: two gauge cards, mono. open rate needle sits above a marked line at 20%. click rate needle sits above a marked line at 2%. Both glow teal, holding steady.
A healthy list clears twenty percent opens and two percent clicks. Drop under fifteen, and your list has aged, or your content stopped landing, or both.
05 · The floor · 0:33
On screen: the open-rate needle drops hard, past the 15% mark to 10%, and glows red #ED5746. A small label appears beneath: "your own reputation, damaged."
Under ten percent opens, you are not just wasting sends. You are actively damaging your own reputation.
06 · The real fix · 0:40
On screen: two mono labels side by side. Left, dimmed and struck through: "buy a list, rent a list, run a giveaway." Right, glowing teal: "clean the one you have." Beneath both, Lora: "Growing the number is easy. Growing the right number is the work."
So stop chasing size. A smaller list of people who actually opted in beats a bought or scraped one every time. Clean what you already have.
07 · End card · 0:47
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.001-bigger-lists-myth.md
01 · The hook
Almanac ids in this scene: 021.002.001
paper background. Two stacked counters in mono, right-aligned: 50,000 large, ink #013b3b, dimmed to low opacity. Below it 500 in teal #0f766e, full opacity, same type size. Between them, Lora, ink: "Which list actually works?"
room tone only, no music yet.
Almanac 021.002.001: "A list of 500 people who open, click, and occasionally reply is a healthier sending asset than a list of 50,000 where only a few hundred ever engage."
the two counts are the Almanac's own illustrative contrast, not a named business or a client's real numbers. No address or company name appears in this shot.
the frame has to work muted and function as the thumbnail, because the image earns the click (BIBLE section 8). A bigger number that turns out to be the loser is the itch nobody scrolls past.
02 · The myth
Almanac ids in this scene: 021.002.001
the 50,000 counter ticks upward on screen, mono, a satisfying climb. A dashed line beneath it reads: "the number every dashboard shows you."
a light upward chime tracks the counter, almost playful.
Almanac 021.002.001: "Somewhere along the way, 'grow your list' became the default email advice. More subscribers, more reach, more revenue. It sounds logical." Also: "that's frustrating when every dashboard shows you a subscriber count like it's a score."
name the belief before correcting it, so the reveal in shot 3 lands as relief, not a lecture.
03 · The correction
Almanac ids in this scene: 021.002.001
the ticking counter freezes. Cut to a split screen. Mono labels rise one at a time on the left, in teal: opens, clicks, replies, forwards. On the right, in #ED5746: spam reports, deletes without opening, unsubscribes. Centered above both, Lora: "Gmail and Outlook do not count. They watch."
the chime cuts. A low steady pulse takes over and holds through the long line.
Almanac 021.002.001: "mailbox providers like Gmail and Outlook don't care how many people are on your list. They care what those people do with your emails." Also: "The main ones are opens, clicks, replies, and forwards (positive signals), plus spam reports, deletes-without-opening, and unsubscribes (negative signals)."
"spam reports" appears here as the Almanac's own signal-category label, not as a spam-trap claim or a complaint-rate number, so it stays. No percentage is shown or spoken in this shot.
this is the mechanism, stated once, in the video's longest sentence, paced slow because it is the whole reversal the video exists to make.
04 · The benchmark
Almanac ids in this scene: 021.002.001
two gauge cards, mono. open rate needle sits above a marked line at 20%. click rate needle sits above a marked line at 2%. Both glow teal, holding steady.
pulse continues, steady.
Almanac 021.002.001: "a rough industry benchmark for marketing email is an open rate above 20% and a click rate above 2%." Also: "If your open rate is sitting below 15%, that's a signal your list has aged, your content isn't connecting, or both."
the three numbers (20%, 2%, 15%) are stated exactly as the Almanac gives them. Nothing is rounded up or dramatized.
gives the viewer a number to go check today, not just a feeling that something is off.
05 · The floor
Almanac ids in this scene: 021.002.001, 021.002.002
the open-rate needle drops hard, past the 15% mark to 10%, and glows red #ED5746. A small label appears beneath: "your own reputation, damaged."
the pulse thins to a single held note as the needle drops.
Almanac 021.002.001: "Below 10%, and you're actively hurting your own deliverability." (This line links onward in the Almanac to 021.002.002, "Do inactive subscribers hurt deliverability?")
stated exactly as the Almanac states it. Not rephrased into an inbox-placement guarantee or a promise about where mail lands, only about reputation damage, which is what the source says.
this is the stakes beat. It is the reason the myth is not just wrong, it is costly, and it is what justifies acting on it now.
06 · The real fix
Almanac ids in this scene: 021.002.001
two mono labels side by side. Left, dimmed and struck through: "buy a list, rent a list, run a giveaway." Right, glowing teal: "clean the one you have." Beneath both, Lora: "Growing the number is easy. Growing the right number is the work."
a warmer chord comes in under "clean the one you have."
Almanac 021.002.001: "Did someone genuinely opt in to receive your emails? Or did they end up on your list through a giveaway, a scraped form, or a list you bought or rented? Contacts added through low-intent methods tend to be the ones who never open, mark as spam, or have addresses that have gone cold." Also: "Growing a smaller, highly engaged list is genuinely harder than just accumulating addresses."
"mark as spam" here is the Almanac's own phrase for a reader-filed complaint, not a spam-trap address, so it is left as the source frames it. The Almanac's next clause, naming a "compromised or trap address," is cut here, because spam-trap language is banned on marketing surfaces even as an aside. Cleaning a list is presented only as sorting existing contacts by engagement and intent, never as a fix for authentication, MX, or blocklist problems.
hands the viewer the decision the whole video has been building to, in the Almanac's own order, intent first, then the engaged core it produces.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" matches the house CTA wording confirmed in the first proof script rather than the Almanac page's own "RME Clean" phrasing, because "RME" is never spoken out (hard content rules) and "Get my list cleaned" is already the confirmed wording. The destination is /get-started, matching CLAUDE.md rule 5's self-serve app framing, not the Almanac page's own links to /done-for-you and /sos. See "Needs YT's yes" below.
V948Do inactive subscribers hurt deliverability?
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the first two scripts in this fan-out.
- The launch wording on the end card. RME-16 (launch messaging framework, waitlist versus coming-soon versus live) is still todo on the Ops Board as of this draft.
- The "four months" invented duration in the hook. It is chosen to sit inside the Almanac's own 90-to-180-day window rather than past it, so the hook's tension lines up with shot 5's real threshold.
- The shared-pool dial visual (shots 3 to 4). One dial with two engagement rows feeding it is the clearest way found to show "scored as one list, not per subscriber," but it is more abstract than a straight before-and-after inbox shot.
01 · The hook · 0:00
On screen: paper background. One invented sender address, mono, small, top of frame: hello@saltmarsh-outfitters.example. Below it, two rows build side by side. Left, teal #0f766e, full opacity: opens every send. Right, ink #013b3b at low opacity: silent, four months. Between the two, Lora: "Only one of these looks like a problem."
Same list. One subscriber opens every send. One has gone quiet for four months. Only one of them looks like the problem.
02 · The reveal · 0:05
On screen: the "silent, four months" row gets a thin #ED5746 edge. Above both rows, Lora, large: "Yes." Beneath it, smaller, dashed: "But not the way you'd expect."
Yes, inactive subscribers hurt your deliverability. Not with a bounce. Not with a complaint. Quietly.
03 · The mechanism · 0:12
On screen: the two rows from shot 1 rise into a single dial, Lora label above it: "sender reputation." Mono tags feed into the dial one at a time from both sides: opens, clicks, replies, moved to inbox. The dial reads one needle, not two.
Gmail and Outlook watch what people do with your email. Every open, every click, every reply, even a message getting moved to the inbox, all of it rolls into one score. Not scored subscriber by subscriber. Scored as one list.
04 · The turn · 0:26
On screen: the single dial from shot 3 drops from teal to #ED5746. The "silent, four months" row grows to fill more of the dial's ring. The "opens every send" row, still teal, gets swept along with it, its small mail icon flipping from an inbox glyph to a spam-folder glyph.
So when a big piece of your list goes quiet, that low engagement tells the provider your mail is not wanted, and the drop does not stay with the quiet ones. It reaches every send you make, including the subscriber who opens every single one.
05 · The threshold · 0:33
On screen: a mono timeline, left to right: day 0, then day 90 marked with a #F59E0B flag labelled warning, then day 180 marked #ED5746 labelled suppression range. Small caption beneath, Lora: "Your own cadence moves this line."
Most senders treat ninety days of silence as a warning, and a hundred eighty as the point most start suppressing. Your own sending cadence moves that line.
06 · The decision · 0:41
On screen: three mono steps build in sequence, each with a small check as it lands: win them back, set a sunset, segment the rest. Beneath the third, Lora: "Fix the pool. Not just the quiet ones."
So do not just delete them. Try one honest win-back email first. Then set a sunset policy, so the quiet ones do not linger. And keep your openers in their own segment, away from the ones dragging the pool down.
07 · End card · 0:48
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.002.002-inactive-subscribers.md
01 · The hook
paper background. One invented sender address, mono, small, top of frame: hello@saltmarsh-outfitters.example. Below it, two rows build side by side. Left, teal #0f766e, full opacity: opens every send. Right, ink #013b3b at low opacity: silent, four months. Between the two, Lora: "Only one of these looks like a problem."
room tone only, no music yet.
the frame has to work muted and function as the thumbnail, because the image earns the click (BIBLE section 8). A quiet subscriber who turns out to be the real cost is the itch nobody scrolls past.
the sender address is invented, never a real one, never a client's. No subscriber name or address is shown, only an engagement state, so nothing here reads as a real person's data.
02 · The reveal
Almanac ids in this scene: 021.002.002
the "silent, four months" row gets a thin #ED5746 edge. Above both rows, Lora, large: "Yes." Beneath it, smaller, dashed: "But not the way you'd expect."
a low, held pulse enters under "quietly."
Almanac 021.002.002: "Yes, inactive subscribers hurt deliverability."
states the Almanac's own direct answer as the turn, so shot 3 can spend its time on the mechanism instead of re-litigating whether the myth is true.
03 · The mechanism
Almanac ids in this scene: 021.002.002
the two rows from shot 1 rise into a single dial, Lora label above it: "sender reputation." Mono tags feed into the dial one at a time from both sides: opens, clicks, replies, moved to inbox. The dial reads one needle, not two.
the pulse settles into a steady bed as the dial fills.
Almanac 021.002.002: "Mailbox providers like Gmail and Outlook watch engagement signals closely. Opens, clicks, replies, and even moves to the inbox all feed into your sender reputation."
engagement is spoken as the plain actions themselves, opens, clicks, replies, never as an invented percentage. No complaint count or complaint-rate figure appears, because this particular Almanac answer does not carry one to withhold, none is invented for the video.
teaches the shared-pool mechanism once, calmly, before the emotional turn in shot 4.
04 · The turn
Almanac ids in this scene: 021.002.002
the single dial from shot 3 drops from teal to #ED5746. The "silent, four months" row grows to fill more of the dial's ring. The "opens every send" row, still teal, gets swept along with it, its small mail icon flipping from an inbox glyph to a spam-folder glyph.
the bed thins to a single held note as the dial flips red.
Almanac 021.002.002: "When a big chunk of your list never responds to anything, those low engagement rates tell providers that your emails aren't wanted. Over time, that pushes more of your mail toward spam, even for the subscribers who do want to hear from you."
this states a reputation and placement risk, exactly as the Almanac states it, and promises no placement outcome either way. No inbox-placement guarantee.
this is the whole point in one beat, "quietly," so it carries the longest sentence in the script on purpose, paced to the slow way the damage actually happens.
05 · The threshold
Almanac ids in this scene: 021.002.002
a mono timeline, left to right: day 0, then day 90 marked with a #F59E0B flag labelled warning, then day 180 marked #ED5746 labelled suppression range. Small caption beneath, Lora: "Your own cadence moves this line."
pulse holds steady under the timeline.
Almanac 021.002.002: "Most deliverability practitioners treat 90 days of zero engagement as a yellow flag and 180 days as a red one. Six months of silence is the point where many senders start suppressing contacts. That said, this varies by industry. A tax software company might reasonably email someone once a year and see normal opens. A daily deal newsletter sending to someone who hasn't opened in 90 days has a problem."
these are the Almanac's own engagement-inactivity windows, not a complaint-rate threshold and not a label count, so they stay, stated exactly (90, 180), nothing rounded up. The Almanac's next paragraph raises recycled spam trap risk past a year of silence. Cut entirely. Spam-trap claims are banned on marketing surfaces even as an aside, and this video never reaches the one-year mark the Almanac ties it to.
gives the viewer a number to go check today, not just a feeling that something is off.
06 · The decision
Almanac ids in this scene: 021.002.002, 021.002.003
three mono steps build in sequence, each with a small check as it lands: win them back, set a sunset, segment the rest. Beneath the third, Lora: "Fix the pool. Not just the quiet ones."
a warmer chord enters under "their own segment."
Almanac 021.002.002: "Run a win-back campaign before suppressing anyone. One or two emails asking if they still want to hear from you. Keep it honest and make the unsubscribe easy to find." Also: "Set a sunset policy that automatically suppresses contacts who haven't engaged after a defined window (90 to 180 days is a reasonable range for most senders)." Also: "Segment before you send. Pulling your active openers into a separate segment and sending to them first protects your reputation while you figure out what to do with the rest."
nothing here implies win-back, sunsetting, or segmenting fixes SPF, DMARC, MX, or blocklist problems, those are a different problem (the free SOS hotline). No deletion is recommended as a first step, matching the Almanac's own order and staying out of 021.002.003 territory, which is its own answer with its own four-step sequence.
ends on the decision the whole video has been building to, in the Almanac's own order, win-back, sunset, segment, not a number.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" matches the confirmed house CTA wording rather than the Almanac page's own "RME Clean" phrasing, because "RME" is never spoken out (hard content rules). The destination, reviewmyemails.com/get-started, is the confirmed CTA for this fan-out, so it is used here without re-flagging it.
V949Does SPF alone protect your domain
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the house precedent set by the first two Almanac scripts.
- The end card doing double duty. This script's subject is authentication (SPF/DKIM/DMARC), but the house CTA is the list-cleaning offer, because that is the confirmed funnel (settled cluster fact).
- Card 6 combining shots 6 and 7. The carousel table compresses the two-checks beat and the end card into one card to keep the deck at six rather than seven.
01 · The hook · 0:00
On screen: paper. One invented domain, mono, large: mail@driftwood-goods.example. Beside it a green check mark and the word "SPF: PASS" in #10B981. Below, dashed and hollow: "So you're protected. Right?"
Your SPF record passes. Green check, every time. So you're covered. Right?
02 · What SPF actually checks · 0:06
On screen: the green check splits into two rows, mono. Row one, lit: envelope sender with the invisible mail-transfer address. Row two, dim and greyed: the From address you see with a question mark instead of a check.
Here's the catch. SPF checks the envelope sender. That's a behind-the-scenes address. The From line your recipient actually reads is a separate field, and SPF never looks at it.
03 · The spoof · 0:16
On screen: the dim row lights up red. Mono label: display-name spoof. A second invented address slides in underneath the first, visually near-identical: mail@driftwoodgoods.example.
A spammer can pass that same SPF check and still put your name on the address your recipient sees. SPF has no answer for that.
04 · The other two layers · 0:24
On screen: three cards build left to right, mono labels over a one-line job each. - SPF over checks who's allowed to send - DKIM over signs the content, proves it wasn't altered - DMARC over matches the From address, decides what happens on failure DKIM and DMARC cards land in teal as they are named.
SPF checks who's allowed to send, DKIM signs the message content so a receiving server can tell it wasn't tampered with, and DMARC forces the From address to match and tells mailbox providers what to do when a check fails.
05 · The line that lands it · 0:38
On screen: all three cards pull together into one row under a single word, teal: "aligned." The green check from shot 1 returns, now spanning all three cards instead of one.
SPF is the bouncer at the door. DKIM is the wax seal on the envelope. DMARC is the manager who checks both are using your real domain, not a lookalike.
06 · The decision · 0:44
On screen: two mono cards side by side. SPF over "check it free" and DMARC over "check it free." A thin teal rule between them, echoing shot 4's row.
One green check was never the finish line. Check your SPF and your DMARC, both, free, and see the gap for yourself.
07 · End card · 0:50
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.003.001-spf-alone-myth.md
01 · The hook
Almanac ids in this scene: 021.003.001
paper. One invented domain, mono, large: mail@driftwood-goods.example. Beside it a green check mark and the word "SPF: PASS" in #10B981. Below, dashed and hollow: "So you're protected. Right?"
no music yet. Room tone only.
Almanac 021.003.001: "SPF is a great first step. But it only checks one thing: whether the server that sent your email was allowed to send from your domain."
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A green check that turns out to mean less than people think is the itch nobody scrolls past.
the domain is invented. Never a real one, never a client's.
02 · What SPF actually checks
Almanac ids in this scene: 021.003.001
the green check splits into two rows, mono. Row one, lit: envelope sender with the invisible mail-transfer address. Row two, dim and greyed: the From address you see with a question mark instead of a check.
low pulse comes in under the split.
Almanac 021.003.001: "SPF checks the envelope sender, which is a behind-the-scenes address used during mail transfer. The From address your recipients see is a separate field entirely."
the split frame makes the abstract gap literal. One row lit, one row dark, is the whole myth in a single image.
03 · The spoof
Almanac ids in this scene: 021.003.001
the dim row lights up red. Mono label: display-name spoof. A second invented address slides in underneath the first, visually near-identical: mail@driftwoodgoods.example.
a single low knock as the red label lands.
Almanac 021.003.001: "A spammer can pass SPF while still showing your domain in the visible From header. That's called a display-name spoof, and SPF has no answer for it."
both addresses are invented, built to only resemble each other, never a real brand or client domain.
this is the turn. It proves the gap named in shot 2 is not theoretical.
04 · The other two layers
Almanac ids in this scene: 021.003.001
three cards build left to right, mono labels over a one-line job each. - SPF over checks who's allowed to send - DKIM over signs the content, proves it wasn't altered - DMARC over matches the From address, decides what happens on failure DKIM and DMARC cards land in teal as they are named.
music settles into a steady bed as the three cards land.
Almanac 021.003.001: "DKIM... signs your email content with a cryptographic key... SPF doesn't touch the message content at all. DKIM does." And: "DMARC is the policy layer that ties everything together. It tells receiving servers what to do when SPF or DKIM fail, and crucially, it enforces alignment."
one clause per layer, no deep jargon, keeps three acronyms from turning into a lecture. The visual does the explaining, the VO stays plain.
05 · The line that lands it
Almanac ids in this scene: 021.003.001
all three cards pull together into one row under a single word, teal: "aligned." The green check from shot 1 returns, now spanning all three cards instead of one.
the bed lifts slightly on "manager."
Almanac 021.003.001: "SPF is the bouncer checking the guest list at the door. DKIM is the wax seal on the envelope proving it wasn't opened. DMARC is the manager who decides what happens when either check fails, and makes sure both checks are using your real domain, not a lookalike."
the Almanac's own analogy is the most portable line in the answer. It is what a viewer repeats to a colleague, so it gets its own beat rather than living inside the VO of shot 4.
06 · The decision
Almanac ids in this scene: 021.003.001
two mono cards side by side. SPF over "check it free" and DMARC over "check it free." A thin teal rule between them, echoing shot 4's row.
music returns, warmer, under "both."
Almanac 021.003.001: "You can check your current SPF record in seconds with our free SPF checker." The SPF-checker mention is sourced directly from this answer. The DMARC checker is not named in 021.003.001 itself, it is product truth (the tool exists on the live site, per the WU tools list) pulled in per this ticket's own angle note ("funnels to the free SPF and DMARC checker tools"), not an Almanac claim. Flagging the distinction so the Source line stays honest per hard rule 1.
the two checks stay two separate sentences for two separate layers. Neither checker is framed as a guarantee of inbox placement, and nothing implies checking a record fixes what it finds. No inbox-placement guarantee, ever.
ends on a decision, not a number (voice guide section 6). It hands the viewer the exact next move the Almanac itself hands them.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording. This video's own subject is authentication, not list cleaning, so the end card is doing double duty (the site CTA, not a claim that cleaning fixes SPF/DKIM/DMARC). See "Needs YT's yes" below.
V950DKIM and DMARC do not auto-lift your inbox placement
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the earlier Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- The CTA destination. Specced as reviewmyemails.com/get-started.
- Keep or cut the honesty beat (shot 5). It is the most quotable line in the answer and it keeps the video accurate by refusing to say authentication is pointless, but it adds about eight seconds and it is the one beat a careless watcher...
01 · The hook · 0:00
On screen: paper. One address, mono, large: hello@coral-cove.example. Under it two mono rows, each with a tick in keep-green #10B981: DKIM passed and DMARC passed. Above it all, Lora, ink, big: "Still in spam." Below, dashed and hollow: "You did everything the guide said."
You set up DKIM. You set up DMARC. You waited. Your placement did not move an inch.
02 · The myth · 0:05
On screen: an arrow labelled authentication tries to drag the address from a tray marked spam up to one marked inbox. The arrow strains, thins, and fades before it reaches. The address does not move.
The setup was not wrong. The belief was. You turned it on to get lifted into the inbox. That is not the job it does.
03 · What they actually do · 0:12
On screen: two mono cards build side by side. DKIM over "proves the message was not changed on the way." DMARC over "tells the receiver what to do if a check fails." A small mono caption under each, dimmed, for authenticity: RFC 6376 and RFC 7489. Between the cards, a key turning in a door.
Here is what they actually do. DKIM proves your message was not altered on its way to the inbox. DMARC tells the receiving server what to do when a check fails. Both are essential. Neither one picks your inbox.
04 · The turn · 0:25
On screen: a building. authentication is the key already in the door, glowing. Inside, a slow meter labelled reputation fills from three thin streams: opens, clicks, reports. The spam / inbox sign at the top is wired to the meter, not to the key.
Authentication gets you into the building, but what happens next depends on how you behave once you are inside, and that behaviour is your reputation, built slowly from whether people open you, click you, or hit the report button.
05 · The honest part · 0:35
On screen: two senders side by side, their reputation meters level with each other. A small feather labelled authenticated settles onto one side and tips the balance a hair. Caption in mono: a tiebreaker, not a shortcut.
So does authentication do nothing for placement? Not quite. Pass it consistently and it builds a track record that backs your reputation. When two senders are otherwise even, some filters lean toward the authenticated one. That is a tiebreaker, not a shortcut.
06 · The decision · 0:43
On screen: the scene clears to two mono cards. your DMARC over "check it is set up right, free." engagement and list quality over "the signals that move placement." A thin teal rule between them.
So get authentication right, because it is non-negotiable, then spend your energy where placement is actually decided. Check your DMARC is set up correctly with our free parser. Then work the signals that move the needle, your engagement and your list quality.
07 · End card · 0:51
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.003.002-dkim-dmarc-auto-inbox.md
01 · The hook
Almanac ids in this scene: 021.003.002
paper. One address, mono, large: hello@coral-cove.example. Under it two mono rows, each with a tick in keep-green #10B981: DKIM passed and DMARC passed. Above it all, Lora, ink, big: "Still in spam." Below, dashed and hollow: "You did everything the guide said."
no music yet. Room tone only.
Almanac 021.003.002: "You've set up DKIM and DMARC, waited a few weeks, and your inbox placement looks... exactly the same."
the address is invented. Never a real one, never a client's.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). Two green ticks next to the word spam is the contradiction nobody scrolls past.
02 · The myth
Almanac ids in this scene: 021.003.002
an arrow labelled authentication tries to drag the address from a tray marked spam up to one marked inbox. The arrow strains, thins, and fades before it reaches. The address does not move.
low pulse comes in as the arrow strains.
Almanac 021.003.002: "authentication is not a placement booster. It's a trust floor."
name the wrong expectation out loud so the correction lands as relief, not a scolding. The sender is not careless, they were sold the wrong promise.
03 · What they actually do
Almanac ids in this scene: 021.003.002
two mono cards build side by side. DKIM over "proves the message was not changed on the way." DMARC over "tells the receiver what to do if a check fails." A small mono caption under each, dimmed, for authenticity: RFC 6376 and RFC 7489. Between the cards, a key turning in a door.
steady bed settles under the two cards.
Almanac 021.003.002: "DKIM (RFC 6376) cryptographically proves the message wasn't altered in transit, and DMARC (RFC 7489) tells receivers how to handle authentication failures... Both are essential. Neither one tells Gmail or Outlook to route your email to the primary inbox."
the Almanac names Gmail and Outlook here. Kept generic on screen and in the VO as "the receiving server" and "your inbox," because naming real providers on a public video is a brand call, not a default. It is grounded if YT wants it added (see "Needs YT's yes"). The RFC numbers appear as dimmed data only, never spoken, so the VO stays jargon-free.
the viewer has to believe the two protocols are real and useful before the turn, or the reveal reads as "authentication is pointless," which the Almanac itself refuses to say.
04 · The turn
Almanac ids in this scene: 021.003.002
a building. authentication is the key already in the door, glowing. Inside, a slow meter labelled reputation fills from three thin streams: opens, clicks, reports. The spam / inbox sign at the top is wired to the meter, not to the key.
the bed thins to one held note as the meter fills.
Almanac 021.003.002: "Authentication gets you into the building. What happens next depends on how you behave once you're inside." And: "reputation is built from signals mailbox providers collect over time. The big ones are open rates, click rates, and complaint rates... Authentication doesn't change those numbers at all."
the Almanac attaches a 0.1 percent complaint-rate threshold to this. It is cut, because a complaint-rate threshold on a marketing surface is off limits. "Hit the report button" is the qualitative stand-in, no number shown or said. No spam-trap claim: the answer's list-hygiene line names spam traps and that mention is dropped entirely.
this is the whole point in one beat, so it carries the longest sentence in the script on purpose, paced to the slow way reputation actually accrues.
05 · The honest part
Almanac ids in this scene: 021.003.002
two senders side by side, their reputation meters level with each other. A small feather labelled authenticated settles onto one side and tips the balance a hair. Caption in mono: a tiebreaker, not a shortcut.
a single soft note as the feather lands.
Almanac 021.003.002: "Over time, consistently passing authentication builds a track record that supports your reputation. Some filters weigh authenticated mail slightly more favourably when reputation signals are roughly equal. But that's a tiebreaker, not a shortcut."
no inbox-placement guarantee. "Lean toward" and "tiebreaker" describe a weighting the Almanac states, not a promise of placement.
the firemen-not-salesmen move. It stops the video overcorrecting into "authentication is pointless," which would be as wrong as the myth it is busting, and it is the most quotable line in the answer.
06 · The decision
Almanac ids in this scene: 021.003.002
the scene clears to two mono cards. your DMARC over "check it is set up right, free." engagement and list quality over "the signals that move placement." A thin teal rule between them.
music returns, warmer, under the second card.
Almanac 021.003.002: "get authentication right because it's non-negotiable, then focus on the things that actually move the needle, which are your engagement rates, your list quality, and your content." And: "our free DKIM checker and DMARC parser will tell you in seconds."
two separate moves in two separate sentences. The free parser confirms the setup, it is never sold as a placement lift. Cleaning the list improves the list-quality signal only and is never implied to fix DMARC, SPF, MX or a blocklist. No inbox-placement guarantee.
ends on a decision, not a number (voice guide section 6). It hands over the two moves the Almanac itself hands over, in the Almanac's own order, and bridges to the offer on the end card.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is /get-started, which is the confirmed target and the one that resolves. See "Needs YT's yes" on the launch wording and the destination.
V951Is the word Free a spam trigger
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the Review My Emails video precedents and the sibling Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- The product bridge in shot 6. This answer, unlike some siblings, never names Review My Emails or list cleaning.
- Keep or cut the origin-story beat (shot 2). Granting the myth its 1990s history makes the correction credible, and it costs about eight seconds.
01 · The hook · 0:00
On screen: paper. A subject line in mono, large: Your free trial ends tonight. The word free is ringed in a red pen circle, suppress #ED5746, the way an old rule would mark it. Above it in Lora, ink: "Never use the word 'free'." Below, dashed and hollow: "That rule is from the 1990s."
You were told the word free sends you to spam. That warning has not been true since the 1990s.
02 · Why it was ever true · 0:05
On screen: the look shifts to a crude old terminal. A mono list scrolls and each line gets a clumsy flag: FREE MONEY, FREE PILLS. A label underneath: 1990s keyword filter.
It was true once. Back then, filters literally scanned your email for suspicious words. Say free money or free pills, and a keyword list flagged you.
03 · What filters weigh now · 0:13
On screen: the red-ringed free shrinks and drops to the bottom of a stack. Above it, three mono rows build one at a time, each with a small dial reading well. - sender reputation with your domain and IP history - engagement with do people open you, or ignore you - authentication with SPF, DKIM, DMARC The word free sits dimmed at the foot of the stack.
Filters today run on machine learning. They weigh dozens of signals at once. Your sending reputation. Whether the people on your list open you or quietly ignore you. Whether your authentication checks out. Your content is in there too, near the bottom of the pile.
04 · The proof · 0:27
On screen: three subject lines slide in, mono, each landing in a green #10B981 inbox row: Your free trial starts today, Earn free miles this month, Free shipping this weekend. No brand names on any of them.
Free trial. Free miles. Free shipping. These land in inboxes every single day. Not because of the words, but because the people getting them actually wanted them.
05 · So what actually sinks you · 0:35
On screen: the three green rows flip to suppress red as a mono caption types beside them: ignored, marked as spam, broken auth. The word free at the foot of the stack stays exactly as it was, untouched and now beside the point.
Now flip it. If the people on your list ignore you, mark what you send as spam, and your authentication stays broken, no careful word choice on earth will save you, because the word was never the thing being judged.
06 · The decision · 0:44
On screen: the red pen circle lifts clean off the word free, leaving it plain black like any other word. Two mono cards slide up in its place, a thin teal rule between them: send only to people who want it and clean the list down to them.
So stop editing the word. Edit the list. Send to the people who actually want your email, and free goes back to being just a word.
07 · End card · 0:50
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.004.001-free-spam-trigger-myth.md
01 · The hook
Almanac ids in this scene: 021.004.001
paper. A subject line in mono, large: Your free trial ends tonight. The word free is ringed in a red pen circle, suppress #ED5746, the way an old rule would mark it. Above it in Lora, ink: "Never use the word 'free'." Below, dashed and hollow: "That rule is from the 1990s."
no music yet. Room tone only.
Almanac 021.004.001: "'Never use the word "free" in your subject line or you'll land in spam.' It's one of the most persistent myths in email marketing. And it's wrong." And: "That was the 1990s."
the subject line is invented, never a real or client send. The word is presented as a myth to bust, not as advice.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A rule everyone repeats, stamped out of date, is the itch nobody scrolls past.
02 · Why it was ever true
Almanac ids in this scene: 021.004.001
the look shifts to a crude old terminal. A mono list scrolls and each line gets a clumsy flag: FREE MONEY, FREE PILLS. A label underneath: 1990s keyword filter.
a low pulse comes in under the first flag.
Almanac 021.004.001: "The idea comes from the early days of spam filtering, when filters literally scanned emails for suspicious words. If your subject said 'FREE PILLS' or 'FREE MONEY,' a keyword list flagged you. That was the 1990s."
grant the myth its history rather than mocking it, curiosity over accusation. No filter product is named, the Almanac's own body says "keyword list," not a brand.
giving the myth its due is what makes the correction credible instead of preachy.
03 · What filters weigh now
Almanac ids in this scene: 021.004.001
the red-ringed free shrinks and drops to the bottom of a stack. Above it, three mono rows build one at a time, each with a small dial reading well. - sender reputation with your domain and IP history - engagement with do people open you, or ignore you - authentication with SPF, DKIM, DMARC The word free sits dimmed at the foot of the stack.
music settles into a steady bed as the dials rise.
Almanac 021.004.001: "Modern spam filters use machine learning. They're looking at dozens of signals at once: your sender reputation, your engagement rates, whether your authentication is properly set up... and yes, your content. But 'free' as a standalone word in context? That's not going to sink you."
the answer's summary also carries a complaint-rate threshold figure. It is cut, a complaint-rate number on a marketing surface is off limits, so engagement is spoken as open-or-ignore only. Authentication is named as SPF, DKIM, DMARC and never implied to be fixed by cleaning a list. No spam-trap language, none is in this answer to begin with.
naming the real signals honestly is what lets the demoted word land. The viewer has to see the word sink under things that actually carry weight.
04 · The proof
Almanac ids in this scene: 021.004.001
three subject lines slide in, mono, each landing in a green #10B981 inbox row: Your free trial starts today, Earn free miles this month, Free shipping this weekend. No brand names on any of them.
the bed lifts a little as each line lands green.
Almanac 021.004.001: "Airlines send 'earn free miles' campaigns to millions of subscribers every day. Retailers use 'free shipping' in subject lines constantly... They're landing in inboxes because their subscribers actually want those emails." And the summary: "'Free shipping' and 'free trial' land in inboxes daily from senders with clean reputation and engaged lists."
the Almanac names specific companies to make this point, including one email tool by name. Those are cut, the examples run generic. This describes what already happens for engaged senders, it is not a promise that the viewer's mail will reach the inbox. No inbox-placement guarantee.
the proof beat, and the most screenshot-friendly frame in the script. Three lines everyone has received, all sitting in the inbox, kills the fear faster than any argument.
05 · So what actually sinks you
Almanac ids in this scene: 021.004.001
the three green rows flip to suppress red as a mono caption types beside them: ignored, marked as spam, broken auth. The word free at the foot of the stack stays exactly as it was, untouched and now beside the point.
the bed thins to one held note as the rows turn red.
Almanac 021.004.001: "If your subscribers ignore you, mark you as spam, and your authentication is a mess, no amount of careful word choice will save you."
broken authentication is named as its own separate problem. Nothing here says cleaning a list fixes authentication, SPF, DMARC or anything of the kind. Two problems stay two problems.
this is the whole point in one beat, so it carries the longest sentence in the script, paced to the slow way real damage happens.
06 · The decision
Almanac ids in this scene: 021.004.001
the red pen circle lifts clean off the word free, leaving it plain black like any other word. Two mono cards slide up in its place, a thin teal rule between them: send only to people who want it and clean the list down to them.
music returns, warmer, under the second card.
Almanac 021.004.001: "So go ahead and tell people about your free trial, free shipping, or free webinar. Just make sure the people receiving that email actually want to hear from you. That's what moves the needle." And: "'Avoid this word' is easier advice to follow than 'build genuine engagement over time.'"
ends on a decision, not a number (voice guide section 6). Cleaning the list is framed as focusing on the people who want the email, the answer's own closing move, never as a fix for authentication, SPF, DMARC, MX or blocklists, and never as an inbox guarantee.
it hands the viewer the exact lever the Almanac ends on, and swaps the busywork of editing a word for the one move that changes the outcome, which is the firemen-not-salesmen turn.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is reviewmyemails.com/get-started, the confirmed cluster CTA. See "Needs YT's yes" on the launch wording.
V952Switching email tools does not fix deliverability
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the existing Review My Emails video precedents.
- The launch-state wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- Keep or cut the exception beat (shot 5). It adds about seven seconds and it is the one beat a careless watcher could misread.
01 · The hook · 0:00
On screen: paper. Two blank tool cards side by side, mono labels your old tool and your new tool, a teal arrow from the first to the second. Above both, one word in Lora, ink, big: "SPAM." It does not move when the arrow lands. Small below, mono: newsletter@double-opt-in.example.
You switched email marketing tools to fix your deliverability. The email still went to spam.
02 · The hope · 0:05
On screen: the new tool card lights up, clean and empty. A small mono tag fades in under it: fresh IPs. For a beat it glows green, like a clean slate.
A new tool does hand you a clean set of sending addresses. And for a moment, that helps.
03 · What you carry over · 0:12
On screen: three moving boxes slide from the old card to the new one, each a mono label as the VO names it. domain reputation. your list with a small line under it, bounces, complaints. engagement history. The new card's green fades as each box lands on it.
But you packed the real problem into the moving boxes. Your domain reputation moves with you. Your list, with its bounces and its complaints, moves with you. So does every subscriber who quietly stopped opening. Same list, same content, same schedule, and the same pattern shows up on the new setup.
04 · The turn · 0:27
On screen: the fresh IPs tag from shot 2 comes back, and a slow bar fills beside it: warmup: 4 to 6 weeks. As it fills, the placement word up top flips back to "SPAM" in #ED5746 and a small mono tag reads throttled.
And that clean set of addresses? It has no reputation yet. Send your usual volume through it and you hit throttling and filtering you were never hitting before, on top of the problem you already had, for the four to six weeks it takes to warm up.
05 · When the tool really is the problem · 0:37
On screen: a small exception card slides in low, dimmed, mono: real infrastructure fault and a feature you actually need. It sits under the stack, not on top of it.
Sometimes the tool genuinely is the problem, a real fault, or a feature you need and it does not have. That is a fair reason to move. It is just rarely the first one when deliverability is what hurts.
06 · The decision · 0:44
On screen: the boxes and cards clear to two mono cards, side by side. your list over "clean it" and authentication over "check it free". A thin teal rule between them.
So ask what is actually dragging you down, then fix that. Clean your list, so the dead weight stops pulling your reputation down. And check your authentication, free, with our SPF and DMARC checkers. Two fixes, and neither one needs a new tool.
07 · End card · 0:52
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.005.001-change-esp-myth.md
01 · The hook
Almanac ids in this scene: 021.005.001
paper. Two blank tool cards side by side, mono labels your old tool and your new tool, a teal arrow from the first to the second. Above both, one word in Lora, ink, big: "SPAM." It does not move when the arrow lands. Small below, mono: newsletter@double-opt-in.example.
no music yet. Room tone only.
Almanac 021.005.001: "Can I fix deliverability by changing ESPs?... Probably not. And the reason matters more than the answer."
the sender address is invented, never a real or client one. The tools are blank cards, never a named platform, so no competitor is named. "ESP" stays out of the spoken line, it is "email marketing tools."
the frame is the whole ad. It works muted and it works as the thumbnail, because the image earns the click (BIBLE section 8). A fix that changed nothing is the itch nobody scrolls past.
02 · The hope
Almanac ids in this scene: 021.005.001
the new tool card lights up, clean and empty. A small mono tag fades in under it: fresh IPs. For a beat it glows green, like a clean slate.
low pulse comes in under the glow.
Almanac 021.005.001: "The new ESP gets you a clean set of IP addresses, and that helps briefly."
grant the hope honestly before taking it apart, so the correction lands as truth, not as a sales rebuttal. The answer itself concedes this point, so the video does too.
03 · What you carry over
Almanac ids in this scene: 021.005.001
three moving boxes slide from the old card to the new one, each a mono label as the VO names it. domain reputation. your list with a small line under it, bounces, complaints. engagement history. The new card's green fades as each box lands on it.
music settles into a steady bed as the boxes land.
Almanac 021.005.001: "Your domain reputation goes with you. Your subscriber engagement history (or lack of it) goes with you... if your list has a high bounce rate... or a history of generating complaints, those problems travel with you to the next ESP... if you're sending the same list, the same content, at the same frequency, the same patterns will emerge on the new infrastructure."
the answer's list line also names spam traps. It is cut, because spam-trap claims are banned on marketing surfaces and this is one. Complaints are spoken as a plain signal, no rate and no threshold number, because a complaint-rate threshold is off limits here.
naming the carry-overs honestly is what sets up the turn. If the viewer accepts that the problem travels, the reveal that the one new thing makes it worse actually bites.
04 · The turn
Almanac ids in this scene: 021.005.001
the fresh IPs tag from shot 2 comes back, and a slow bar fills beside it: warmup: 4 to 6 weeks. As it fills, the placement word up top flips back to "SPAM" in #ED5746 and a small mono tag reads throttled.
the bed thins to one held note as the bar fills.
Almanac 021.005.001: "Every new IP address starts with no reputation... If you move to a new ESP and try to send at full volume immediately, you'll hit throttling and filtering that you weren't hitting before, on top of the original problem." Summary: "fresh IPs that need four to six weeks of warmup, during which throttling often worsens the original problem."
the four-to-six-weeks warmup is grounded in this answer's own summary. No warmup tool is named or recommended, that is a locked ban.
this is the whole point in one beat, so it carries the longest sentence in the script, paced to the slow way the damage compounds during warmup.
05 · When the tool really is the problem
Almanac ids in this scene: 021.005.001
a small exception card slides in low, dimmed, mono: real infrastructure fault and a feature you actually need. It sits under the stack, not on top of it.
a single soft knock as the exception card settles.
Almanac 021.005.001: "Changing ESPs sometimes makes sense if the platform genuinely has infrastructure problems or you need features it doesn't offer. But it's rarely the right first move when deliverability is the concern."
the answer makes this concession, so the video keeps it. It stops the piece from reading as "never switch," and being fair about the exception is the firemen-not-salesmen move.
06 · The decision
Almanac ids in this scene: 021.005.001
the boxes and cards clear to two mono cards, side by side. your list over "clean it" and authentication over "check it free". A thin teal rule between them.
music returns, warmer, under "clean it".
Almanac 021.005.001: "what's actually causing the deliverability issue? If it's your list quality, that's fixable without changing ESPs. If it's your authentication setup, that's fixable... our free tools can check your authentication setup."
the two fixes stay two separate sentences for two separate signals. Cleaning the list is never implied to fix authentication, SPF, DMARC, MX or a blocklist. Neither is a promise of inbox placement. No inbox-placement guarantee, ever.
ends on a decision, not a number (voice guide section 6). It hands over the two moves the Almanac itself names, in the Almanac's own framing, both done without changing platforms.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is reviewmyemails.com/get-started, the confirmed cluster CTA. See "Needs YT's yes" on the launch-state wording.
V953Your open rate is mostly robots
draftedOpen questions for YT
- On camera or voice only.
- Launch wording on the end card, pending RME-16.
- Confirm the soft promo fit, this answer is about metrics, so the clean-list end card is a softer tie than usual. Keep it, or end on the metric decision alone.
01 · The hook · 0:00
On screen: paper. Big Lora: "Your 60 percent open rate?" Below, mono, revealing: mostly robots.
That 60 percent open rate you are proud of. A lot of it is not people. It is machines.
02 · How opens work · 0:05
On screen: an email opens, a tiny invisible pixel highlighted, then a hand NOT touching it while the pixel still fires.
An open is counted when a tiny invisible image in the email loads. The catch is that image can load with no human in the room. Security scanners fetch it. And since 2021, Apple Mail pre-fetches every image automatically, before anyone opens a thing.
03 · The scale · 0:18
On screen: a bar. Roughly half of it shades out as "phantom opens".
And it is not a rounding error. Apple Mail drives forty to fifty five percent of tracked opens. When that protection rolled out, some senders watched their open rate jump twenty points overnight. That is not engagement. That is automation.
04 · The turn · 0:30
On screen: the open-rate number greys out. Three cards brighten: clicks, replies, conversions.
So what can you trust? Clicks, because a human has to reach out and tap. Replies. And conversions. Those are people. Opens are a barometer at best, they tell you if pressure is rising, not the real temperature.
05 · The decision · 0:40
On screen: a "suppress by opens" toggle flicks OFF. Text: "do not gate on opens".
So stop suppressing people, or keeping them, based on opens. A phantom open and a real one look identical, and gating on them makes bad list decisions. Decide on clicks and replies instead.
06 · End card · 0:48
On screen: logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
silent.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.006.001-are-open-rates-accurate.md
01 · The hook
paper. Big Lora: "Your 60 percent open rate?" Below, mono, revealing: mostly robots.
room tone.
it puts a number they trust on screen and undercuts it in one line.
02 · How opens work
Almanac ids in this scene: 021.006.001
an email opens, a tiny invisible pixel highlighted, then a hand NOT touching it while the pixel still fires.
Almanac 021.006.001: "Your ESP embeds a tiny invisible image (a tracking pixel)... it counts as an open... Apple Mail's Mail Privacy Protection (MPP) pre-fetches every image in every email, automatically, before a subscriber even opens the message."
the Almanac says "ESP". On this marketing surface it is spoken as "the email", the tracking mechanism, never "ESP".
03 · The scale
Almanac ids in this scene: 021.006.001
a bar. Roughly half of it shades out as "phantom opens".
Almanac 021.006.001: "Apple Mail handling 40 to 55% of email opens... your reported open rate can be inflated by 20 percentage points or more... That's not engagement. That's automation."
04 · The turn
Almanac ids in this scene: 021.006.001
the open-rate number greys out. Three cards brighten: clicks, replies, conversions.
Almanac 021.006.001: "Clicks are a much stronger signal... clicks, replies, conversions, and unsubscribe rates are all closer to the truth... Treat them like a barometer."
05 · The decision
Almanac ids in this scene: 021.006.001
a "suppress by opens" toggle flicks OFF. Text: "do not gate on opens".
Almanac 021.006.001: "What you shouldn't do is set an open rate threshold to trigger re-engagement campaigns or suppress contacts... both lead to bad list decisions."
ends on a decision. No inbox-placement guarantee.
06 · End card
logo lockup, never an octopus. "Your first thousand addresses, cleaned free." CTA in teal, "Get my list cleaned", reviewmyemails.com/get-started small in mono beneath. Hold.
the end card points to /get-started, per the launch-messaging decision (call 3, 2026-09-23). Generic call in-video, specific links in the description.
V954Do open rates still matter post-MPP
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the existing Review My Emails video precedents and the first Almanac scripts.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, which as coming-soon, and which as live.
- How directly the end card should tie to this question. The cluster CTA is reviewmyemails.com/get-started (confirmed), and that is what the end card carries.
- Keep or cut the CTOR tell (the flat click line behind shot 5). It is the single most useful diagnostic in the answer and it is faithfully grounded, but it adds a couple of seconds and a second visual layer to shot 5.
01 · The hook · 0:00
On screen: paper. One line, mono, large: a sender newsletter@open-rate-opticians.example above a single stat card that reads OPEN RATE 71% with a small green up-arrow. Below it, dashed and hollow, in Lora, ink: "So why does it feel fake?"
Your open rate just hit an all-time high. And you can feel the number is lying.
02 · The myth · 0:05
On screen: the stat card splits into two wrong doors. Left, mono, a green tick: trust it. Right, a red cross: bin it. A thin strike goes through both.
So you either celebrate a number that is partly fake, or decide opens are dead and bin them. Both are wrong.
03 · The machine · 0:12
On screen: an envelope icon flies into a box labelled Apple proxy, a pixel dot inside it lights up, and a counter ticks OPENS +1. A small human figure beside it stays asleep, unmoved.
Here is what happened. Apple Mail Privacy Protection, the setting that routes your email through Apple's own servers, fires your tracking pixel the second the mail lands, read or not.
04 · The turn · 0:22
On screen: a single bar labelled your open rate splits into two stacked segments, Apple Mail in monitor amber #F59E0B and everyone else in keep green #10B981. A slider drags the Apple segment from a sliver up to half, and as it grows the top number visibly loses its footing.
But it only hits Apple Mail. Gmail and Outlook opens stay real. So how much of your list is on Apple? Half, and your headline rate is fiction. A sliver, and the rest still holds.
05 · What a proxy cannot fake · 0:32
On screen: three mono cards deal out in a row, each with a small icon: clicks (a cursor), replies (a return arrow), revenue (a receipt). Behind them, a faint line chart shows the open line soaring while the click line stays flat, and the gap between them is shaded.
So stop leading with opens. Lead with what a proxy can never fake. A click. A reply. Revenue. Someone had to choose each one. And when opens soar while clicks stay flat, that gap is your tell.
06 · The decision · 0:41
On screen: the record stat card from shot 1 returns, now demoted to a small footnote reading opens: trend line only, while the three cards from shot 5 move up to headline size. One last card fades in beneath, mono: check clicks before you cut anyone.
So here is the decision. Keep opens only for trends inside one steady audience, split your Apple readers out from everyone else, and score real engagement on the clicks, the replies and the revenue a proxy can never invent for you. And before you cut a quiet subscriber, check their clicks. Some so-called non-openers click every week.
07 · End card · 0:50
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.006.002-open-rates-post-mpp.md
01 · The hook
Almanac ids in this scene: 021.006.002
paper. One line, mono, large: a sender newsletter@open-rate-opticians.example above a single stat card that reads OPEN RATE 71% with a small green up-arrow. Below it, dashed and hollow, in Lora, ink: "So why does it feel fake?"
no music yet. Room tone only.
Almanac 021.006.002: "Your dashboard says opens are up. But you know something's off."
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). A record that feels wrong is the itch nobody scrolls past.
the sender address is invented. Never a real one, never a client's. The 71% is an illustrative figure, not a claim about any real account.
02 · The myth
Almanac ids in this scene: 021.006.002
the stat card splits into two wrong doors. Left, mono, a green tick: trust it. Right, a red cross: bin it. A thin strike goes through both.
low pulse comes in under the strike.
Almanac 021.006.002: "So no, open rates don't mean what they used to. But that doesn't mean you throw them out entirely." and, from the summary, "Open rates still matter post-MPP, but only as a segmented signal, not a headline metric."
name both wrong reactions out loud so the correction lands as relief, not a lecture. The viewer is almost certainly standing in one of the two doorways.
03 · The machine
Almanac ids in this scene: 021.006.002
an envelope icon flies into a box labelled Apple proxy, a pixel dot inside it lights up, and a counter ticks OPENS +1. A small human figure beside it stays asleep, unmoved.
the pulse resolves into a steady bed as the counter ticks.
Almanac 021.006.002: "Apple's proxy servers pre-fetch email content the moment it hits a subscriber's device, whether they actually read your email or not. That pre-fetch fires your tracking pixel, and your ESP logs it as an open." and, from the summary, "Apple Mail's Mail Privacy Protection, launched in 2021, pre-fetches tracking pixels via proxy and inflates opens for that segment regardless of actual reads."
MPP and Apple are named because the answer names them and the myth is about them. The name is explained in a clause ("the setting that routes your email through Apple's own servers") so no jargon goes by unexplained. No inbox-placement language anywhere in this beat.
the sleeping figure is the whole point in one image. The open fired and nobody read. Show it, do not assert it.
04 · The turn
Almanac ids in this scene: 021.006.002
a single bar labelled your open rate splits into two stacked segments, Apple Mail in monitor amber #F59E0B and everyone else in keep green #10B981. A slider drags the Apple segment from a sliver up to half, and as it grows the top number visibly loses its footing.
the bed thins to one held note as the slider reaches half.
Almanac 021.006.002: "MPP only affects Apple Mail users. Subscribers reading on Gmail, Outlook, or other clients aren't affected by this (at least not yet)... the more Apple Mail users you have in your list, the more inflated your overall open rate looks." and "If 40 or 50 percent of your list is on Apple Mail, you can't trust your aggregate open rate at all. If it's closer to 10 or 15 percent, opens from your non-Apple segments are still reasonably accurate."
Gmail, Outlook and Apple Mail are mailbox clients named in the answer, not competitors of Review My Emails, so naming them is fine. The "half" and "sliver" are the answer's own device-mix figures spoken plainly, not a complaint-rate threshold and not a deliverability promise.
this is the reframe. The problem was never "opens are dead," it was "what is your Apple share," and once the viewer sees the bar split they can locate their own list on it.
05 · What a proxy cannot fake
Almanac ids in this scene: 021.006.002
three mono cards deal out in a row, each with a small icon: clicks (a cursor), replies (a return arrow), revenue (a receipt). Behind them, a faint line chart shows the open line soaring while the click line stays flat, and the gap between them is shaded.
music settles back, warmer, as the three cards land.
Almanac 021.006.002: "shift primary reporting to clicks, replies, and revenue attribution, which a proxy cannot fabricate" and "Clicks require a human to actually choose to interact. They can't be faked by a proxy server. Same goes for replies, purchases attributed to email, and form completions." The soaring-opens-flat-clicks tell is the answer's CTOR point: "A high open rate with very low clicks is a red flag that your opens are inflated."
the count is exactly three, matching the answer's summary. Form completions are folded into the spoken "someone had to choose" rather than listed, to keep the count clean at three on screen. No metric here is presented as an inbox guarantee.
naming the three honestly is the correction, and the flat click line is the diagnostic the viewer can run tonight on their own dashboard.
06 · The decision
Almanac ids in this scene: 021.006.002
the record stat card from shot 1 returns, now demoted to a small footnote reading opens: trend line only, while the three cards from shot 5 move up to headline size. One last card fades in beneath, mono: check clicks before you cut anyone.
the held note releases under "check their clicks."
Almanac 021.006.002: "Opens still work reasonably well for directional trends over time within the same audience" and, from the summary, "Filter your ESP's client-detection data to isolate Gmail, Outlook, and other non-Apple opens (which remain reliable)." The suppression caution is the answer's own: "If you're about to sunset a segment of 'unengaged' subscribers based purely on open data, that logic breaks down fast. Some of those 'non-openers' might be clicking every week. (Check clicks before you suppress anyone.)"
the "check clicks before you cut anyone" line is a metric-reading caution from the answer, not a claim that any Review My Emails product measures engagement or decides who is engaged. Nothing here promises inbox placement.
ends on a decision, not a number (voice guide section 6). It hands the viewer the three moves the Almanac itself hands them, in the Almanac's own order, and leaves them with one thing not to do until they have checked.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" is the approved CTA wording rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is reviewmyemails.com/get-started, the confirmed cluster CTA. See "Needs YT's yes" on how directly this end card should tie to a question about reading your own metrics.
V955Can good engagement override poor authentication
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the two existing Review My Emails video precedents and the first two Almanac scripts.
- End-card button copy and destination. Specced as "Check my authentication" routing to reviewmyemails.com/get-started, matching the CTA rule and the first script's button pattern.
- Keep or cut the grid beat (shot 5). It is the Almanac's own structure and the strongest visual in the script, but it is dense, four labelled outcomes in about 12 seconds.
01 · The hook · 0:00
On screen: paper. Invented sender, mono, small: newsletter@pearl-diver.example. Below it, large in Lora, ink: "25% open rate." Under that, dashed and hollow: "So why fix SPF or DMARC?"
A 25 percent open rate. Loyal readers. Real replies. So why bother fixing your SPF or DMARC?
02 · The myth · 0:05
On screen: the sender line stays. Under it, one word types in, mono, then gets a thick circle around it: ENOUGH? An arrow tries to point from a small "engagement" tag toward a small "authentication" tag, and gets a strike through it.
The theory is that good numbers cover for a broken record. They do not.
03 · The two checks · 0:11
On screen: two mono cards build side by side, joined by a plus sign, not a versus sign. - IDENTITY CHECK with SPF · DKIM · DMARC - BEHAVIOR CHECK with opens · clicks · replies
Every email gets checked twice. Once for identity, SPF, DKIM, DMARC. Once for behavior, opens, clicks, replies. They do not replace each other. They only stack.
04 · The turn · 0:21
On screen: the behavior card slides toward the identity card, reaching. It hits a thin teal wall labelled, mono: CANNOT VOUCH FOR IDENTITY. The behavior card stops there.
A loyal, engaged audience cannot vouch for your identity, because opens and clicks are behavior signals, not proof of who you are, and only a properly aligned DMARC record can make that proof for you.
05 · The grid · 0:32
On screen: a 2x2 grid builds, one quadrant per VO beat, each a small mono card: - AUTHENTICATED + STRONG ENGAGEMENT, labelled "best placement" (#10B981) - AUTHENTICATED + WEAK ENGAGEMENT, labelled "recoverable" (#F59E0B) - UNAUTHENTICATED + STRONG ENGAGEMENT, labelled "fragile" (#F59E0B) - UNAUTHENTICATED + WEAK ENGAGEMENT, labelled "almost certain problems" (#ED5746)
Lay out every combination and the pattern holds. Authenticated and engaged is the best spot there is. Authenticated with weak engagement is recoverable. Unauthenticated with strong engagement only looks fine, it is fragile. Unauthenticated and weak is almost certain trouble.
06 · The decision · 0:44
On screen: the grid clears to two mono cards side by side. spf checker over "check it free" and dmarc generator over "build it free". A thin teal rule between them.
Since February 2024, Gmail and Yahoo reject or junk unauthenticated mail past five thousand messages a day, loyal audience or not. Check your SPF. Generate a clean DMARC record. Both free, both today.
07 · End card · 0:50
On screen: small logo lockup, never a cartoon octopus. Under it: "Check your authentication. Two minutes, no cost." Then the CTA in teal, "Check my authentication", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.006.012-engagement-vs-auth.md
01 · The hook
Almanac ids in this scene: 021.006.012
paper. Invented sender, mono, small: newsletter@pearl-diver.example. Below it, large in Lora, ink: "25% open rate." Under that, dashed and hollow: "So why fix SPF or DMARC?"
no music yet. Room tone only.
"You've got a 25% open rate, loyal readers, and real engagement... So why bother fixing SPF or DMARC?" (021.006.012)
the address is invented. Never a real one, never a client's.
the frame is the whole ad. It has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). The question it asks is the exact question the video spends the next 45 seconds answering.
02 · The myth
Almanac ids in this scene: 021.006.012
the sender line stays. Under it, one word types in, mono, then gets a thick circle around it: ENOUGH? An arrow tries to point from a small "engagement" tag toward a small "authentication" tag, and gets a strike through it.
low pulse begins under the strike.
"No, strong engagement cannot override broken authentication." (021.006.012, In short)
name the wrong belief out loud so the correction in the next shot lands as information, not a scold.
03 · The two checks
Almanac ids in this scene: 021.006.012
two mono cards build side by side, joined by a plus sign, not a versus sign. - IDENTITY CHECK with SPF · DKIM · DMARC - BEHAVIOR CHECK with opens · clicks · replies
music settles into a steady bed as the second card lands.
"Gmail, Outlook, and Yahoo Mail run two separate checks on every email you send. First, they verify your authentication (SPF, DKIM, and DMARC). Then they look at engagement signals like opens, clicks, and replies. These checks don't replace each other. They stack." (021.006.012)
the plus sign is the whole argument in one glyph. Two checks that add together, never one that covers for the other.
04 · The turn
Almanac ids in this scene: 021.006.012
the behavior card slides toward the identity card, reaching. It hits a thin teal wall labelled, mono: CANNOT VOUCH FOR IDENTITY. The behavior card stops there.
the bed thins to one held note as the card hits the wall.
"a highly-engaged audience can't vouch for your identity. Only proper DMARC alignment can do that." (021.006.012)
the sharpest line in the answer, so it carries the longest sentence in the script on purpose, read slowly enough for the wall to register before the next shot moves on.
05 · The grid
Almanac ids in this scene: 021.006.012
a 2x2 grid builds, one quadrant per VO beat, each a small mono card: - AUTHENTICATED + STRONG ENGAGEMENT, labelled "best placement" (#10B981) - AUTHENTICATED + WEAK ENGAGEMENT, labelled "recoverable" (#F59E0B) - UNAUTHENTICATED + STRONG ENGAGEMENT, labelled "fragile" (#F59E0B) - UNAUTHENTICATED + WEAK ENGAGEMENT, labelled "almost certain problems" (#ED5746)
four short, even beats, one per quadrant landing.
"Authenticated + strong engagement = best possible inbox placement. Authenticated + weak engagement = filtering risk, but recoverable. Unauthenticated + strong engagement = short-term OK, long-term fragile. Unauthenticated + weak engagement = almost certain problems." (021.006.012)
"best possible inbox placement" is shown as the Almanac's own label for one quadrant of a comparison grid, not spoken as a promise to the viewer. No inbox-placement guarantee is made about the viewer's own mail.
this is the Almanac's own structure, handed to us almost card for card. It is the clearest possible way to show that engagement changes the outcome inside a category, strong or weak, but never moves you out of the unauthenticated column.
06 · The decision
Almanac ids in this scene: 021.006.012
the grid clears to two mono cards side by side. spf checker over "check it free" and dmarc generator over "build it free". A thin teal rule between them.
music returns, warmer, under "both free."
"since Gmail and Yahoo's February 2024 bulk sender requirements, unauthenticated mail from senders above 5,000 messages per day gets rejected or junked regardless of how loyal the audience is... our free SPF checker and DMARC generator are a quick place to start." (021.006.012)
the two tools stay two separate sentences for two separate checks. Neither is framed as fixing the other, and neither is a promise of inbox placement. The 5,000 messages a day figure is a bulk sender policy threshold, not a complaint rate or a spam trap, so it is not one of the banned figure types, and it is quoted exactly as the Almanac states it.
ends on a decision, not a number (voice guide section 6). It hands the viewer the two checks the Almanac itself names, in the Almanac's own order.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Check your authentication. Two minutes, no cost." Then the CTA in teal, "Check my authentication", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the CTA destination is /get-started, the confirmed target (CLAUDE.md rule 5, the 2026-09-21 launch-messaging decision). The button copy names the action this video is about, matching the pattern the first script set with "Get my list cleaned" rather than a generic "start free." See "Needs YT's yes" on whether that button should instead route straight to the two tool pages.
V956Cleaning your list does not fix deliverability immediately
draftedOpen questions for YT
- On camera or voice only. Specced as voice over motion graphics, matching the earlier Almanac scripts and the two existing Review My Emails video precedents.
- The launch wording on the end card. RME-16 is defining which posts read as waitlist, coming-soon, or live.
- Keep or cut the authentication line in shot 6. It is the safest way to mention SPF, DKIM, DMARC here, because it explicitly says cleaning does not fix them rather than implying it does.
- Keep or cut the bounce-rate figure (above 2 percent) in shot 5. It is sourced and it is not the banned complaint-rate metric, but it is still a threshold number on a marketing surface, and this cluster has been careful about those.
01 · The hook · 0:00
On screen: paper. A small mono sender line, FROM: newsletter@subject-line-salon.example. A big teal stamp crosses the frame: "LIST CLEANED." Half a beat later, same sender, ink text: "STILL IN SPAM." A dashed question beneath: "Didn't that fix it?"
You cleaned your list this morning. Tonight's campaign still landed in spam.
02 · The myth · 0:05
On screen: a large toggle switch snaps to ON, a green tick blinks over it, then greys out and slides back to OFF as the VO lands.
You expected it to flip back on like a switch. It does not work that way.
03 · What Gmail, Outlook, and Yahoo remember · 0:11
On screen: three mono provider names stack in, each with a small ledger line ticking upward: bounces, complaint signals, unopened campaigns.
Gmail, Outlook, and Yahoo already logged the bounces, the complaint signals, the campaigns nobody opened.
04 · The wet floor · 0:19
On screen: the ledger clears. A hand shuts off a dripping tap (the clean). The floor beneath stays visibly wet, a soft sheen across the paper background.
Plugging the leak is still the right move. The floor just takes time to dry.
05 · The timeline · 0:24
On screen: two horizontal bars fill left to right, mono labels. moderate damage above bounce rate above 2%, filling to 4 to 8 weeks. Below it worse damage filling to 2 to 3 months.
Moderate damage, a bounce rate above two percent, clears in four to eight weeks of clean, steady sending. Worse than that, plan on two to three months.
06 · The decision · 0:33
On screen: a teal tick lands next to list cleaning, already done. Three more mono lines build in beneath, unchecked: consistent openers first, volume stays low, authentication still holds.
Cleaning was the right move, not the whole fix. Send to the people who open you consistently first, keep the volume down while the reputation slowly rebuilds, and keep your authentication solid, because cleaning your list was never going to fix that part for you.
07 · End card · 0:46
On screen: small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
silent. Music tails out.
For the chats backed-by ids, on-screen notes, visual notes. YT can skip this.
Script file: social-media/video-scripts/almanac-script-021.008.007-cleaning-not-instant.md
01 · The hook
paper. A small mono sender line, FROM: newsletter@subject-line-salon.example. A big teal stamp crosses the frame: "LIST CLEANED." Half a beat later, same sender, ink text: "STILL IN SPAM." A dashed question beneath: "Didn't that fix it?"
no music yet, room tone only.
the address is invented. Never a real one, never a client's.
the frame is the whole ad, it has to work muted and it has to work as the thumbnail, because the image earns the click (BIBLE section 8). The gap between "cleaned" and "still in spam" is the itch nobody scrolls past.
02 · The myth
a large toggle switch snaps to ON, a green tick blinks over it, then greys out and slides back to OFF as the VO lands.
low pulse starts under "flip."
"So now you sit back and watch your inbox placement recover, right? Not quite."
name the wrong expectation out loud so the correction reads as relief, not a scold.
03 · What Gmail, Outlook, and Yahoo remember
three mono provider names stack in, each with a small ledger line ticking upward: bounces, complaint signals, unopened campaigns.
pulse continues, one tick per ledger line.
"mailbox providers like Gmail and Outlook don't forget. They've already recorded the bounces, the complaint signals, the unopened campaigns." Yahoo from the summary line: "Gmail, Outlook, and Yahoo retain reputation history... for weeks."
"complaint signals" is named only as a category, exactly as the Almanac names it, with no rate or threshold attached. No percentage for complaints appears anywhere in this script.
this is the beat that explains why "clean" and "instant" cannot both be true, stated as fact rather than excuse.
04 · The wet floor
the ledger clears. A hand shuts off a dripping tap (the clean). The floor beneath stays visibly wet, a soft sheen across the paper background.
pulse drops out, a single held note.
"Think of it like stopping a leak. Plugging the hole is the right move, but the floor is still wet." Also: "List cleaning is a necessary first step, not a complete solution. It clears the path."
this is the line that keeps the honesty from tipping into undersell. Cleaning is not demoted here, it is only not instant.
05 · The timeline
Almanac ids in this scene: 002.001.004
two horizontal bars fill left to right, mono labels. moderate damage above bounce rate above 2%, filling to 4 to 8 weeks. Below it worse damage filling to 2 to 3 months.
bed returns, warmer, rising with the bars.
"if your list was moderately unhealthy (bounce rate above 2%...), you can expect to see meaningful improvement in inbox placement within 4 to 8 weeks of clean, engaged sending. If things were worse than that, 2 to 3 months is more realistic."
the bounce-rate figure is kept because it is a bounce-rate threshold, not the complaint-rate threshold the pre-screen flags. No complaint-rate number appears anywhere on screen or in the VO. No inbox-placement guarantee, "meaningful improvement" is spoken as a range of weeks, never a promised placement.
the count is load-bearing, so it is stated exactly, matching the house pattern of an exact number carrying the video (see the 002.001.004 proof's five signals).
06 · The decision
a teal tick lands next to list cleaning, already done. Three more mono lines build in beneath, unchecked: consistent openers first, volume stays low, authentication still holds.
bed holds steady under the list, no swell.
"Send only to your most engaged subscribers first. The people who open consistently are your best asset right now... Drop your sending volume temporarily... Check your authentication is solid. If SPF, DKIM, and DMARC aren't properly set up, list cleanliness won't matter much." Also: "List cleaning is a necessary first step, not a complete solution."
authentication is named only to say cleaning does not fix it, never the reverse. Nothing implies list cleaning fixes SPF, DKIM, DMARC, MX, or a blocklist listing. No inbox-placement guarantee. "Consistently" is spoken, not just "openers," matching the Almanac's own qualifier: a recently-and-reliably-engaged segment, not a stale "ever opened" one, per the harmful-advice check that a warm-up-first recommendation needs a recency caveat to be safe advice.
ends on a decision, not a number (voice guide section 6). It hands over the moves the Almanac itself hands over, in the Almanac's own order, and it closes the "not magic" honesty with the reassurance that cleaning was still correct.
07 · End card
small logo lockup, never a cartoon octopus. Under it: "Your first thousand addresses, cleaned free." Then the CTA in teal, "Get my list cleaned", with reviewmyemails.com/get-started set small in mono beneath it. Hold.
the offer is 1,000 free credits (BIBLE section 3). "Get my list cleaned" matches the approved CTA wording used in the earlier Almanac scripts rather than a generic "start for free," which is on the forbidden competitor list (voice guide sections 2 and 3). The destination is reviewmyemails.com/get-started, confirmed for this cluster, so it is used here without a flag.