Email Sender Fix Desk: safe unsubscribe fix rules and a ten-check email scan (free sample)
by PaperChaseWebb
From Email Sender Fix Desk: the mistakes agents make when they fix newsletter footers and sender records, nine rules to paste into your agent, and a read-only script that runs ten checks on one saved email, from missing one-click unsubscribe headers and unsubscribe links to a missing postal address, fake Re: subjects, leftover placeholders and inbox promises.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
email-sender-fix-desk-safe-unsubscribe-fix-rules-ten-check-email-scan-free-sample.md · 11 KB · direct download, no signup
What you end up with
You can see whether a newsletter, or an agent's fix of it, has the unsubscribe headers, unsubscribe link and address it needs before it goes out.
What you get
- Why agent email fixes need checking
- Nine rules for agents that fix newsletters and sender records
- email_mini.py: ten read-only checks for one saved email
- A made-up newsletter with four findings and a clean fixed copy
Who it is for
Anyone who wants a quick check on a newsletter, or on an agent's fix of it, before it goes out.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes to a first scan
Sample prompts, free to use
Run python3 email_mini.py on [fixed email]. Fix every finding without deleting words, inventing an address or an unsubscribe link, or hand it to me. Do not send anything.
The rules and script are in the file.
Free preview of the file
# Email Sender Fix Desk: safe unsubscribe and footer fix rules and a ten-check email scan (free sample) Version 1.0, 2026-11-01. By PaperChaseWebb. For anyone letting an AI agent fix the unsubscribe headers and footer of a newsletter. One page and one Python 3 script, standard library only, read-only: it reads one saved email, prints findings and changes nothing. It sends nothing and opens no network connection. No API key, no login. Tested on Linux with Python 3.13, 3.12, 3.11, 3.9 and 3.8: 5 unit tests, and 96 of 96 planted faults caught. The example business is made up. Not legal advice. ## Why agent fixes need checking Gmail and Yahoo ask senders of marketing mail in volume for a one-click unsubscribe in the headers and a visible unsubscribe link in the body, and Outlook.com rejects high-volume mail without SPF, DKIM and DMARC. CAN-SPAM asks for a real postal address and a working opt-out. Most small newsletters are missing one or two of these. An agent can fix them fast, and it gets them wrong in the same few ways: - It trims the footer and takes real content with it. - It writes in a postal address that is not yours. - It invents an unsubscribe link that goes nowhere. - It adds a tracking pixel. - It "cleans up" SPF and drops the tool your invoices go out through. - It writes that the email is "fully CAN-SPAM compliant" and will reach the inbox. ## Rules to paste into AGENTS.md, CLAUDE.md, a Grok Bot standing order or Hermes notes 1. Never send, schedule or publi
Test record
- Date
- Nov 1, 2026
- What was run
- tests/test_mini.py (5), 96 planted faults against email_mini.py, and the copy extracted from the sample page. Linux, Python 3.13, 3.12, 3.11, 3.9 and 3.8.
- Result
- 5 passed, 0 failed on all five versions; 96 of 96 faults caught; the extracted copy was identical to the tested script and found 4 problems on the example email and 0 on its fix.
- Not run
- Your settings, the fix check, the DNS checks and the eval set (the full kit does those).
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The sample checks one email on its own. Your settings, the fix check against the original, the SPF, DKIM and DMARC checks, the eval set, owner approval and agent setups are in the full kit.
- Not legal advice. It does not say an email meets any law or where it will land.
- On 2026-11-01 email_mini.py passed 5 unit tests and 96 of 96 planted faults on Linux with Python 3.13, 3.12, 3.11, 3.9 and 3.8, and the copy extracted from the sample page was identical to the tested script.
Questions
Does it change my files or send anything?
No. It reads the file you name and prints findings. It opens no network connection, sends nothing and changes nothing.
What is in the full kit?
An 18-check scan using your own settings, a 14-check fix check against the original email, SPF, DKIM and DMARC checks with a check on the agent's proposed records, owner approval at a terminal, a 6-email eval set, and setup for Grok Bot, Claude Code, Codex and Hermes. $29.
Details
Version 1.0 · Updated Nov 1, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Email Sender Fix Desk: agent fixes for one-click unsubscribe, footers and SPF, DKIM and DMARC, checked against the original, owner approved
Let an agent put the one-click unsubscribe headers, a visible unsubscribe link and your postal address into your newsletters, and propose clean SPF, DKIM and DMARC records, the things Gmail, Yahoo and Outlook ask senders for. It writes fixed copies and never sends or touches DNS. A fix check refuses deleted words, made-up addresses, tracking pixels and hidden links. A records check refuses dropped senders, invented keys and DMARC jumped straight to reject. You approve at your terminal and make the change yourself.
Consent and Privacy Fix Desk: safe consent fix rules and a ten-check page scan (free sample)
From Consent and Privacy Fix Desk: the mistakes agents make when they fix cookie banners and trackers, nine rules to paste into your agent, and a read-only script that runs ten checks on one HTML page, from trackers and pixels that fire before a choice to banners with no Reject, browse-means-yes wording, pre-ticked boxes, Google consent granted by default and compliance claims.
Invoice Chase Desk: safe reminder rules and a ten-check payment reminder scan (free sample)
From Invoice Chase Desk: the mistakes that make payment reminders expensive, eight rules to paste into your agent, and a read-only script that runs ten checks on one reminder, from the wrong balance and other invoice numbers to threats, pressure, surprise fees, new bank details and links off your payment domain.