Blog
Field notes from the sending layer.
Analysis of what is actually changing in deliverability — provider enforcement, authentication, infrastructure — and what it means for senders. Sourced and dated, written by the people who run this layer rather than watch it.
Queues and backoff: how retries and deferrals actually work
A deferral is not a rejection — it is the receiver asking you to come back later, and how your server answers decides whether the mail delivers or dies in the queue. Deferrals, backoff, greylisting, and when a 4xx becomes a bounce.
Read the postHow IP warm-up actually works: building a sending reputation from zero
A new dedicated IP has no reputation, and the big providers distrust strangers who arrive sending at volume. What warm-up does, who actually needs it, the schedule that is safe, and the metrics that decide when to push and when to hold.
Read the postHow to get off a blacklist: Spamhaus and others, step by step
If your IP or domain is on a blacklist, mail bounces with a 550 before it reaches anyone. What the Spamhaus lists are — SBL, CSS, XBL, PBL, DBL — how to find which one you are on, and how to get off without going back on.
Read the postSMTP rejection codes explained: what 421, 451, 550 and the 5.7.x family mean
A clear reference for the error codes mail servers return: temporary 4xx versus permanent 5xx, what the enhanced status code adds, and the authentication rejections that dominate 2026.
Read the postGmail’s permanent rejections: the end of the deliverability grace period
In November 2025 Gmail moved from soft enforcement to outright SMTP rejection of non-compliant bulk mail. The requirements did not change — the consequence did.
Read the postMore field notes are on the way. Want us to cover something specific? Tell us.