Sender reputation and IP warming
Authentication proves who you are. Reputation decides what that identity is worth. It is built from how recipients behave: what they open, what they ignore, what they report, and how many of the addresses you send to do not exist. No provider publishes the formula, but each one exposes enough of its own view that the picture can be assembled. This category covers building that reputation from zero, reading the dashboards that report it, and recovering when it has already gone wrong.
Two reputations, and they do not move together
The sending IP and the domain in your signature are scored separately. An IP can be rented, shared or replaced; the domain follows you and carries its history across every platform you ever move to. That asymmetry decides what a migration costs and whether a fresh IP fixes anything at all.
Which of the two weighs more depends on the receiver and on your volume, and the practical consequences are worked through in domain reputation versus IP reputation. The one number every major provider now judges you on directly is the complaint rate, and Gmail publishes a threshold: keep the spam rate below 0.30 percent, measured in its own dashboard rather than in your platform’s.
Starting from zero
A new IP has no history, and to a receiver a sudden large volume from an unknown source is indistinguishable from a compromised host. Warming is the practice of raising volume slowly enough that each step is judged on the engagement of the step before it, which is why the schedule matters less than the order: the most engaged recipients go first.
The ramp
A day-by-day plan with volume caps per provider, and the checkpoints where you hold rather than increase.
The arithmetic
How to size a ramp for your own list rather than copying a table: the formulas, ready-made schedules and code to generate one.
The repair
Diagnosing a damaged IP, the recovery playbook, and the point at which starting again costs less than continuing.
Where the providers show their view
Each large receiver runs its own portal, each shows something the others do not, and all three are free. Google Postmaster Tools reports domain and IP reputation, spam rate and authentication pass rates. Microsoft SNDS and JMRP expose per-IP data and a complaint feed for Outlook traffic. Yahoo Sender Hub covers the same ground for Yahoo and its associated domains. Reputation scoring from third parties, such as Sender Score, is a useful cross-check but is not what any receiver actually filters on.
Monitoring is only half of it: enrol in the complaint feeds as well, so that a spam button press reaches you as data rather than as silence. The mechanism is covered in feedback loops and ARF, and the categories of tooling that surround all of this are compared in what each type of deliverability tool actually fixes.
When reputation is already the problem
Falling delivery rates usually show up as codes before they show up in a dashboard: deferrals, throttling and policy rejections, all documented one rejection at a time in the SMTP code reference. If the rejection names an operator, the listing and its removal procedure belong to blocklists and spam monitoring. If undeliverable addresses are driving the fall, the fix is upstream in bounce handling. And the whole chain, from records to list quality to inbox placement, is set out end to end in email deliverability 101.
