Authenticate first
Know what SPF authorizes, what DKIM signs, and what DMARC alignment actually tests.
v=DMARC1; p=none;FIELD NOTES FOR SMALL OUTBOUND TEAMS
Cold email systems that survive contact with the inbox.
Practical deliverability, DNS authentication, mailbox warmup, list hygiene and IMAP operations — written for founders and small agencies who operate the stack themselves.
SPF / DKIM / DMARCIMAP4rev2RFC-backed
live diagnostichealthy
$ check auth --then reputation --then volume
START WITH THE FAILURE MODE
One question per field note.
No generic “marketing tips.” Each guide isolates one operational decision and shows what to inspect next.
Ramp from signals
Use bounces, replies, complaints and filtering as health gates instead of chasing one universal daily cap.
5 → 9 → 18 → 31 → 57*Keep state clean
Suppress dead addresses, dedupe leads, and make reply detection idempotent before automation scales mistakes.
UID + BODY.PEEK + state*Illustrative operating ramp, not a provider guarantee or universal safe limit.
SEVEN TECHNICAL CLUSTERS
Built around the work small senders actually do.
01
Warmup & ramping
Build volume without sudden reputation shocks.
02SPF / DKIM / DMARC
Understand the records behind sender identity.
03Sending volume
Use health gates instead of magic daily limits.
04List hygiene
Reduce invalid, stale, duplicate, and risky targets.
05IMAP operations
Read, classify, and move mail without brittle automation.
06Follow-up systems
Space touches and stop when replies change state.
07Reputation recovery
Recognize damage early and change one variable at a time.
RECENT FIELD NOTES
Read the mechanism, then the number.
Examples use concrete volumes and failure rates, but they are presented as scenarios rather than promises.
You fixed the mail DNS but some receivers still fail: negative caching can outlive the edit
Resolvers cache negative DNS answers as well as positive records. After correcting a missing MX or related name, some paths can continue seeing the earlier negative result until its cache lifetime expires.
Read field note →SMTP 4xx means retry later, not retry immediately: keep temporary deferrals from becoming a resend storm
Temporary SMTP failures invite a future retry, but aggressive immediate retries can amplify the rate pattern that triggered deferral in the first place. Queue discipline matters.
Read field note →Build the one-click unsubscribe endpoint idempotently: duplicate POSTs should not resurrect or error on an opt-out
RFC 8058 defines the one-click POST shape. The application behind the URL still needs safe repeat handling because receivers, users, or retries can submit the same opt-out more than once.
Read field note →Auto-Submitted is also a loop-prevention signal: do not let two autoresponders keep each other alive
RFC 3834 recommends Auto-Submitted markers on automatic responses and says automatic responders should not blindly answer messages that are themselves automatically submitted.
Read field note →The reply/send race: what if a prospect replies after the follow-up job is locked but before the provider call?
Polling for replies and dequeuing follow-ups are concurrent processes. Without a final state check, a perfectly detected reply can still lose a race to a job that was already claimed.
Read field note →A prospect can reply from a different alias: stop follow-ups from thread evidence, not From-address equality alone
People reply from delegated accounts, aliases, assistants, or another mailbox. A detector that requires the inbound From address to equal the original lead can miss a real conversation.
Read field note →FREE OPERATING SHEETS
Useful enough to print, not banner-shaped lead magnets.
PDF · 3 pages
Outbound Deliverability Preflight Checklist
A printable pre-send check covering authentication, DNS, list hygiene, mailbox state, reply handling, and measurement.
PDF · 2 pages
SPF / DKIM / DMARC DNS Cheat Sheet
A compact record-by-record worksheet with alignment notes and a current RFC 9989 DMARC reminder.
PDF · 2 pages
Bounce Code Triage Sheet
A decision sheet for 2.x.x, 4.x.x, and 5.x.x enhanced status codes with actions for a small sender.