From 5ffd406ede2c9d20a82332732d1a43ecd3474f1f Mon Sep 17 00:00:00 2001 From: Jared Zwick <52264361+jaredzwick@users.noreply.github.com> Date: Sat, 2 May 2026 19:42:15 -0400 Subject: [PATCH] README: link to smtp-warmer for self-hosted-relay troubleshooting Coldflow's #1 deliverability blocker for self-hosted senders is transport-layer misconfiguration (TLS, AUTH, DNSBL, reverse DNS). Surface smtp-warmer right under "connect google smtp accounts" so users hit it the moment they wonder "why is my mail landing in spam?". One npx command, zero deps, no API keys. Mirrors the dmarc-doctor sub-bullet pattern under the SPF/DKIM/DMARC line. Co-Authored-By: Paperclip --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index dea9fd3..fa87724 100644 --- a/README.md +++ b/README.md @@ -22,6 +22,10 @@ ✅ - enter a domain and see SPF / dkim / dmarc records - connect google smtp accounts + Mail landing in spam from a self-hosted relay? Diagnose the transport + layer in 30s with [`npx smtp-warmer test --host smtp.example.com --port 587 --user me@example.com`](https://github.com/pypesdev/smtp-warmer) + — TLS handshake, AUTH+RCPT sandbox (no mail sent), DNSBL reputation, + reverse-DNS alignment. Zero deps, zero API keys, composite 0–10 score. - upload a csv of contacts - Create a single-step email sequence with basic personalization ({first_name}). - Send the emails (with a strict, safe sending limit).