Email Deliverability News, September 2026: Sender Requirements and Filtering

Published Sep 2, 20264 min read
Written by Orthotropy TeamReviewed by Orthotropy Team

August 2026 changed what Gmail senders could see and which sending paths they could keep. Deliverability analysis showed a documented 0.1% spam warning and separate user-feedback verdicts on August 3, 2026; legacy Domain and IP Reputation views were reported unavailable on August 20–21, 2026. Gmail also scheduled third-party non-Google Send as for January 2027 removal and the Verified Sender Program for eligible U.S. political committees for September 8, 2026. Senders need the From-domain claim, sending system, provider response, and recipient result—not one reputation label—to assess message health.

What changed in August—and what is scheduled next

This September 1, 2026 email deliverability news snapshot covers four developments, not one Gmail rule. Preserve August signals, distinguish acceptance from placement, and prepare affected Send as paths before January 2027. The September 8 program remains scheduled for eligible U.S. political committees, not as a general route around filtering.

Date and statusDevelopmentOperational consequence
August 3 — practitioner-documented observationGmail’s Deliverability analysis began warning above the recommended 0.1% spam rate and separated user-feedback verdicts.Store each verdict with bounce, traffic, and placement evidence.
August 7 — public notice; removal scheduled for January 2027Kyoto University’s dated notice and Google’s support page document the end of third-party non-Google Send as.Assign every affected dependency a migration path and owner.
August 20–21 — independently observed; official completion timing unresolvedInbox Monster and Mailgun reported the v1 interface and Domain and IP Reputation charts unavailable; Google’s deprecation page confirms those views are slated for retirement.Keep separate compliance, authentication, delivery-error, complaint, feedback, and placement records.
September 8 — scheduled to beginThe Verified Sender Program requires eligible U.S. political committees to verify their domain, use Postmaster Tools, authenticate, follow sender policy, and keep the 14-day average spam rate below 0.3%.Record eligibility, verification, and 14-day spam-rate status.
A practitioner documented the August 3 diagnostic; two vendors observed the August 20–21 loss of legacy views. Google confirms planned retirement, not account-wide completion timing. [S1], [S2], [S5], [S6], [S7]
The January 2027 Send as removal changes a sending path, not Gmail’s bulk baseline. As of September 1, 2026, the September 8 program remained scheduled, limited to qualifying political committees, and subject to existing controls. [S3], [S4], [S11]

Why a reputation label is no longer enough

An ESP “delivered” count records server acceptance, not inbox placement. Accepted mail can still land in spam because Microsoft’s anti-spam FAQ documents sender reputation, content triggers, complaint level, overrides, and upstream filtering. MailReach’s terminology guide makes the same distinction.

Gmail’s Postmaster Tools documentation separates Compliance Status, Deliverability analysis, spam rate, Feedback Loop, authentication, encryption, and delivery errors. Deliverability analysis can flag requirement or delivery failures, complaint-threshold breaches, and low or positive interaction. Gmail still makes the filtering decision.

InferredGmail documents its diagnostic categories; Microsoft documents tenant-filter inputs; MailReach supplies vendor terminology. None establishes a provider-wide August filtering change or cross-provider placement measure. [S2], [S10], [S12]

Trace the message before naming the category

On failure, check the visible From address and authentication, then the sending system and provider response. For accepted mail, inspect placement and recipient reaction. Identity, path, and response are shorthand for those concrete records, not an explanation by themselves.

For personal Gmail, all senders need SPF or DKIM, valid forward and reverse DNS, TLS, and RFC 5322 formatting. Bulk senders also need SPF and DKIM, DMARC, From-domain alignment, and one-click unsubscribe for marketing and subscribed mail. Gmail defines that group as senders sending close to 5,000 messages to personal Gmail accounts from the same primary domain in 24 hours; it recommends keeping user-reported spam below 0.1% and preventing it from reaching 0.3%.

For Outlook.com consumer services, Microsoft’s 550 5.7.515 support page defines high volume as 5,000 or more messages using the same 5322.From domain. SPF and DKIM must pass, a DMARC record must be published, and DMARC validation must pass through alignment.

The Gmail and Outlook requirements are current baselines rather than new August rules. [S2], [S8], [S9], [S10], [S12]

Turn the checks into one evidence ledger

Create one ledger row for every visible From domain and sending stream before the next health report.

GateRequired recordPass condition
From-domain claimOwner, From domain, provider scope, SPF and DKIM result, DMARC record and alignment where required, and unsubscribe status for relevant Gmail bulk traffic.The row records pass or fail against the applicable Gmail or Outlook.com baseline.
Sending routeESP, SMTP relay, or Gmail interface; authenticated domain; provider destination; response and bounce codes; any third-party non-Google Send as dependency.The route has an owner; each affected Send as path also has a migration owner and date before January 2027.
Provider and recipient resultGmail Deliverability analysis, spam rate, Feedback Loop data where available, and provider-specific placement observations, reported separately from server acceptance.Complaint rate remains below Gmail’s documented warning threshold; accepted mail is never labeled inboxed without placement evidence.
DecisionReport date, owner, status for each prior row, and any missing field marked unknown.No program receives a healthy status while a required field is unknown.
The decision
At the next review, work the ledger in deadline order: first any third-party non-Google Gmail Send as row without a migration date, then any accepted stream without placement evidence.

Sources

  1. Beyond Open Rate, “Gmail turned its 0.1% spam threshold into an active warning”Supports: An August 3 practitioner report documented the active 0.1% warning and user-feedback verdicts in Gmail Postmaster Tools Deliverability analysis; The report describes the change as an unannounced rollout observed in dashboards rather than a formally dated Google launch. Checked 2026-09-01.Limitation: This is a practitioner report, not a Google announcement. It does not establish one global rollout date, and its causal claims about filtering are not treated as official policy statements.
  2. Gmail Help, “Postmaster Tools dashboards”Supports: Deliverability analysis can issue recommendations for delivery failures, exceeding the recommended spam threshold, low interaction, positive interaction, and sender-requirement failures; Compliance data is delayed, primary-domain scoped, and may be absent at low volume; Spam-rate and reputation views can diverge from actual inbox placement. Checked 2026-09-01.Limitation: The help page does not display a publication or rollout date and may lag operational interface changes. It describes Gmail data only, not cross-provider inbox placement.
  3. Institute for Information Management and Communication, Kyoto University, “[Important] Specifications Change: Discontinuation of Sending from External Email Addresses via Web Gmail (Starting January 2027)”Supports: An August 7 public notice documented Google's third-party Send as change and linked the official support page; The notice period runs in Q3-Q4 2026 and complete removal is scheduled for January 2027. Checked 2026-09-01.Limitation: This is an institutional notice for affected university users. It establishes a dated public notice, not worldwide completion or inbox-placement effects.
  4. Gmail Help, “Learn about changes to third-party email account support in Gmail”Supports: Third-party non-Google Send as support is scheduled to end in January 2027; The Q3-Q4 2026 transition may restrict new configurations; Gmail-to-Gmail aliases and Google Workspace Send as remain supported. Checked 2026-09-01.Limitation: The page provides a schedule but no visible publication date. It concerns a Gmail sending feature, not a new bulk-sender authentication rule or a guarantee of delivery.
  5. Inbox Monster, “Gmail Reputation Data Is Removed: For Real This Time?”Supports: On August 20, the vendor reported that the v1 Postmaster Tools interface was unavailable and redirecting to v2; The vendor reported v1 reputation API data through August 17 and described v2 Deliverability analysis. Checked 2026-09-01.Limitation: This is a vendor observation, not a formal Google completion notice. The page contains an internally impossible future date for a developer-preview launch; that claim is excluded.
  6. Mailgun, “Gmail Reputation Data Is Dead. Now What?”Supports: Mailgun independently reported that the v1 link and Domain and IP Reputation charts had disappeared; The remaining v2 evidence includes Compliance Status, Deliverability analysis, spam rate, Feedback Loop, authentication, encryption, and delivery errors. Checked 2026-09-01.Limitation: This is a sending vendor's operational interpretation, not a Google announcement. Its troubleshooting recommendations do not independently measure every sender's inbox placement.
  7. Gmail Help, “Learn about the deprecation of the old Postmaster Tools interface”Supports: Google says the legacy interface will eventually retire and v2 excludes the old Domain and IP Reputation data; The v2 API is available and the v1 API is slated for retirement; Google's page still says web-interface deprecation timing was postponed. Checked 2026-09-01.Limitation: The page gives no current retirement date and does not resolve whether every account lost v1 access in August.
  8. Gmail Help, “Email sender guidelines FAQ”Supports: Gmail's bulk-sender threshold, permanent designation, authentication, alignment, unsubscribe, and enforcement baseline; Google recommends keeping user-reported spam below 0.1% and preventing it from reaching 0.3%. Checked 2026-09-01.Limitation: This is the current Gmail baseline, not evidence that those long-standing requirements first appeared in August 2026. It applies to personal Gmail recipients, not Google Workspace inbound mail.
  9. Microsoft Support, “Fix NDR error 550 5.7.515 in Outlook.com”Supports: Microsoft defines a high-volume sender as 5,000 or more messages to its consumer services using the same 5322.From domain; Both SPF and DKIM must pass, a DMARC record must be published, and DMARC validation must pass through alignment; 550 5.7.515 identifies rejection for insufficient authentication. Checked 2026-09-01.Limitation: The support page has no visible publication date and does not establish a new August 2026 rule. It applies to Microsoft consumer services, not every Microsoft 365 tenant.
  10. Microsoft Learn, “Anti-spam protection FAQ”Supports: Authentication failure is only one possible reason legitimate email is classified as spam; Other documented inputs include sender reputation, content triggers, bulk complaint level, overrides, and upstream-filter interference. Checked 2026-09-01.Limitation: This documentation concerns Microsoft Defender for Office 365 and tenant filtering. It does not describe Gmail behavior or prove a provider-wide August algorithm change.
  11. Gmail Help, “Gmail Verified Sender Program eligibility & policies”Supports: The program is scheduled to start September 8, 2026; Eligibility is limited to verified U.S. political committees and requires domain verification, Postmaster Tools, authentication, and policy compliance; A spam rate above 0.3% over a 14-day average violates program policy. Checked 2026-09-01.Limitation: The event had not occurred at the September 1 evidence cutoff. The program is not available to ordinary B2B SaaS senders and does not remove recipient controls or all filtering.
  12. MailReach, “Email Deliverability vs Inbox Placement: How to Measure and Improve Both”Supports: Server acceptance and post-acceptance inbox or spam placement are distinct outcomes; An ESP delivered count does not establish inbox placement. Checked 2026-09-01.Limitation: This is vendor educational content, and industry usage of the umbrella term deliverability is not perfectly uniform. It does not measure the August events.

Continue the evidence path

Related reading

  • Related

    Email Marketing Operations: Permission, Calendar, and Send QA

    Connect Email Deliverability News, September 2026: Sender Requirements and Filtering with Email Marketing Operations: Permission, Calendar, and Send QA to place sender identity, infrastructure checks, provider feedback, and suppression inside a recurring ledger-calendar-gate system while keeping delivery health separate from campaign performance.

  • Related

    Cold Email Explained: Sequences, Deliverability, Replies, and Compliance Boundaries

    Connect Email Deliverability News, September 2026: Sender Requirements and Filtering with Cold Email Explained: Sequences, Deliverability, Replies, and Compliance Boundaries to see how identity, authentication, provider response, opt-out handling, and stop conditions change in unsolicited outreach without importing cold-email permission assumptions into lifecycle sends.

Run your growth team from one screen.

Invite only