Notes from operating it.
One operational note a week: an incident, an architecture trade-off, a deliverability finding, or a decision and what it cost. Written by the people who run the infrastructure.
Gmail, Yahoo and Microsoft bulk sender requirements, side by side
What the three biggest mailbox providers require from anyone sending 5,000 or more emails a day, where they differ, and the error you get when you miss one.
How to warm up a new sending domain
Why a new domain or IP has to earn its volume, a ramp that works, and the signals that mean you should stop and wait.
Why are my emails going to spam?
A diagnosis order that starts with the evidence you already have, instead of rewriting subject lines and hoping.
Publishing the method before the numbers
Why our transparency methodology went live before we had a single report to show.
What reputation isolation actually costs
Pooled sending is better economics. We do not do it, and here is the bill.
Acceptance is not delivery
The single most useful distinction in email, and the one almost every dashboard blurs.
One email when we publish.
The same notes, delivered. No drip sequence, no product announcements dressed up as writing, and no sales cadence hiding behind a subscribe button.
Ready to see where your email goes?
Free for 3,000 emails a month. No card to start, and everything we claim is checkable.
Never venture-backed · operated by Martin Business Consultants