IP Warmup by ISP: Gmail, Outlook, Yahoo, AOL Specifics

The universal 6-week IP warmup schedule is the right starting point — but each major ISP grades senders by different signals on different timescales. A schedule that lands High reputation at Gmail by Day 21 might still be Yellow at Outlook on Day 35; pushing volume to chase the Gmail signal will lock you out at Outlook. This article covers what each ISP actually weighs, how to read its dashboard, and the corrective action when one ISP lags the rest.

Gmail — engagement-driven, dashboard-rich#

Gmail dominates B2C inboxes (≈ 30 % of recipients in many lists) and is the most reputation-sensitive of the four. The signals it weighs:

1. Engagement rate — opens + clicks within the first 12 hours after delivery. Gmail uses cohort engagement to grade sender reputation per IP and per from-domain.
2. Spam-rate floor — user-reported spam under 0.10 % is "good," 0.10-0.30 % is "yellow zone," > 0.30 % is the rejection cliff.
3. Authentication consistency — every message must pass SPF or DKIM (one is enough for Gmail to accept; both is enough to inbox).
4. TLS adoption — STARTTLS opportunistic is fine; modern Gmail also weighs MTA-STS adoption (boosts reputation slightly when present).

Read the dashboard at postmaster.google.com (free; verify your sending domain via DNS TXT). The graphs that actually matter:

• IP Reputation — the top-line graph. Targets: High by Day 21 of warmup, sustained High through steady state.
• Domain Reputation — independent of IP, increasingly weighted in Gmail's grading. A domain warmed alongside the IP scores higher.
• Spam Rate — must stay under 0.30 % with intermittent 0.10 % spikes. Sustained > 0.30 % triggers grey-listing across the program.
• Authenticated Traffic — should be 100 %; anything less indicates SPF or DKIM is intermittently failing.

Gmail-specific corrective actions when reputation lags:

• If IP reputation is Low/Medium but Domain reputation is High, send only to the engaged 50 % of the list for 7 days — engagement-from-known-domain repairs IP reputation faster than blanket sending.
• If both are Low, pause new IP additions and rotate sending to your warmest existing IP. Re-introduce the cold IP at 25 % of the previous day's volume after 3 days.

Outlook / Hotmail / Live / MSN — Microsoft SNDS, throttle-heavy#

Microsoft groups Outlook.com, Hotmail, Live, MSN, and Office 365 consumer accounts under one reputation system. The product surface for senders is Smart Network Data Services (SNDS) at sendersupport.olc.protection.outlook.com — not as polished as Gmail's, but the data is the most actionable across all four ISPs.

What SNDS reports per IP:

The Microsoft-specific gotcha is that Outlook will throttle aggressively on a YELLOW IP — connections accepted, then 421 RP-002 deferral on every message. AcelleMail's bounce log surfaces this as soft bounces with the RP-002 substring. Stop sending to Outlook IPs immediately when you see RP-002 above 5 % of attempts — continuing accelerates the YELLOW → RED transition.

Outlook also runs Junk Email Reporting Program (JMRP) — a feedback loop that delivers complaints to a postmaster mailbox you register. Configure AcelleMail's Feedback Loop Handler to ingest JMRP messages so per-recipient complaints show up in BounceLog with bounce_type unknown and the FBL feedback_type=abuse.

Yahoo / AOL — black-box, FBL-driven#

Verizon Media owns Yahoo and AOL; their reputation system is opaque (no public dashboard like Gmail/Microsoft). What you can do:

1. Register for the Yahoo / AOL FBL at postmaster.yahooinc.com — feedback-loop reports for spam complaints arrive at a mailbox of your choice. Configure AcelleMail's FBL Handler to ingest those reports.
2. Watch for 421 4.7.0 [TSS04] in AcelleMail's bounce log — this is Yahoo's "deferred, sender reputation issue" code. Any sustained presence is a stop signal.
3. Audit From: consistency — Yahoo penalizes sudden from-domain or from-name changes. If you rotate "from" addresses for branded campaigns, do it gradually (one new from per week).

The corrective action when Yahoo throttles: pause Yahoo-targeted sending for 24 hours, send the next campaign only to the 30-day engaged Yahoo segment, and watch the bounce log for the TSS04 signal to drop. Forcing volume during throttling is the worst path.

Apple iCloud — Mail Privacy Protection complications#

Apple's Mail Privacy Protection (launched iOS 15, Sep 2021) pre-fetches images on a privacy-relay server. The consequence for AcelleMail's open-tracking: Apple opens look like 100 % open rates with sub-second open times. This is the major reason for the "open rates jumped to 80 %" effect operators saw post-2021.

The Apple-specific reputation guidance:

• Don't grade list health by Apple-recipient open rates — they're not behavioral signals anymore.
• Do filter Apple-pre-fetch opens before computing engagement scores — AcelleMail's Tracking Log records the IP that fetched the open pixel; Apple's relay IPs are detectable (mp.maileroute.net patterns).
• Apple's spam rate is invisible (no dashboard at all), but bounces follow standard SMTP codes — 5xx hard bounces show in AcelleMail's BounceLog like any other.

Per-ISP send-volume targeting in AcelleMail#

Use AcelleMail's per-server quota to throttle by ISP slice. Common pattern:

Sending Server "SES-Hot" (the warmed IP)
  → assigned to engaged-segment campaigns

Sending Server "SES-Cold" (the warming IP)
  → assigned to a Gmail-only segment
  → daily quota matches the warmup schedule
  → bounce-rate threshold tighter (Gmail penalizes harder than Yahoo)

When you split servers per ISP-segment, the AcelleMail dashboard's per-server stats become per-ISP throughput visibility — much more diagnostic than the all-ISPs-mixed default view.

Recovery recipes#

When one ISP's reputation lags ≥ 14 days behind the others:

1. Pause new volume to that ISP at the application layer (segment by domain).
2. Send 3 days of engagement-only campaigns (engaged < 30 days) to the lagging ISP.
3. Audit authentication specifically for that ISP — sometimes a DKIM key rotation or DMARC policy mismatch only fails at one ISP due to selector handling.
4. Re-introduce broader sending at 25 % of the daily volume from before the pause.
5. Watch the dashboard / bounce log for 7 days — if it doesn't recover, escalate to ISP postmaster contact (Microsoft has a "mitigation request" form, Gmail does not).

Related reading#

• IP Warmup Schedule for New Sending Servers — the universal 6-week plan
• Domain Warmup for Self-Hosted Email Sending — companion to IP warmup
• Gmail Postmaster Tools Walkthrough — deep-dive on the Gmail dashboard
• Microsoft SNDS Walkthrough — deep-dive on SNDS
• Setting up Feedback Loops (FBL) — registering with each ISP's FBL
• Sender Reputation Monitoring Stack — the tooling around all four

FAQ#

Why does Gmail score better than Outlook on the same IP?#

Different reputation models. Gmail weighs engagement; Outlook weighs complaints + trap hits. A list with high opens but high complaints (e.g. content disliked but content compelling enough to open) scores high at Gmail and low at Outlook simultaneously.

Can I read Yahoo's reputation anywhere?#

No public dashboard. The closest signals: AcelleMail bounce log for SMTP-level deferrals, FBL reports for complaints, and seed-list tests via Glock Apps or Litmus.

How long should each ISP's warmup take?#

Gmail: 21-28 days to High at 100k/day target. Microsoft: 30-45 days to GREEN. Yahoo: 35-45 days, but harder to measure. AOL: similar to Yahoo.

What if one ISP fully blocks me (RED at Microsoft, blacklist at Spamhaus)?#

That's beyond ordinary throttling — the recovery is days/weeks of zero volume to that ISP plus a delisting petition. Continued sending into a block extends the cooling-off period.