Email Deliverability News, October 2026: Sending Limits, Warmup, and EWS
Email deliverability updates entering October 2026 include Microsoft’s phased Exchange Online EWS retirement, revised tenant sending quotas, and Validity’s Heatwave blocklist for synthetic domain warmup.

This early-October edition reviews September announcements and the changes they carry into October. Sources and published schedules were checked on October 4, 2026.
The main updates entering October
| Date | Update | Affected service or sending practice |
|---|---|---|
| September 2 announcement | Microsoft raised its minimum Exchange server update level, with rollout scheduled from September’s second week. | Exchange 2016/2019 submitting through an inbound OnPremises connector. |
| September 3 | Validity introduced Heatwave to identify artificial domain warming. | Domains associated with manufactured engagement. |
| September 4 guidance | Microsoft explained the EWS application allow list required under its October access changes. | Applications using Exchange Online EWS. |
| September 8 | Mailgun added subaccount usage-limit alerts. | Subaccounts with configured usage limits. |
| September 10 incident | Brevo reported unauthorized account access and phishing sends. | Customer accounts affected by its SAML SSO scoping flaw. |
| September 14 scheduled rollout | Microsoft scheduled lower allowances for newly created tenants. | Exchange Online tenant-wide external sending. |
| September 17 | Amazon SES added tenant-level deliverability insights. | SES tenants with Virtual Deliverability Manager enabled. |
Microsoft sending limits: tenant age reduces the allowance
Microsoft’s August 13 update scheduled revised Tenant External Recipient Rate Limit (TERRL) calculations to begin rolling out on September 14, 2026. Its published allowances are:
| Tenant category | External-recipient allowance |
|---|---|
| Trial tenant | 500 per day, regardless of license count. |
| Non-trial tenant under 31 days old | 10% of the standard calculated quota. |
| Non-trial tenant 31–60 days old | 25% of the standard calculated quota. |
| Non-trial tenant over 60 days old | 100% of the standard calculated quota. |
The same Microsoft announcement postpones TERRL rollout for GCC, GCCH, DoD, and 21Vianet and says repeated sends to an external address count separately. A unique-contact total therefore understates consumption when recipients receive multiple messages.
Microsoft’s service limits documentation defines TERRL as a tenant-wide allowance measured over a sliding 24-hour window and points administrators to Exchange admin center → Reports → Mail flow → Tenant Outbound External Recipients. Use that report to check the actual quota; Microsoft’s rollout guidance also identifies its enforcement status. The September start date alone does not establish the configuration of an individual tenant.
Heatwave targets synthetic warmup, with lasting listing records
In its September 3 launch announcement, Validity said Heatwave had already identified more than one million domains displaying artificial-warming behavior. The company describes synthetic warming as exchanges that manufacture engagement through controlled accounts, including simulated opens, clicks, and replies, in its explanation of the detected behavior.
Validity says the signal is available through its existing reputation feeds and is being used or evaluated by partners including Comcast, Proofpoint, Spamhaus, and SURBL. That wording describes partner access and evaluation; it does not establish that every mailbox provider blocks every listed domain.
The Heatwave listing policy, checked October 4, says an accurate synthetic-warming observation remains on record after activity stops. Its review policy allows removal when the original classification or attribution was wrong, while active-outreach status can change independently of the underlying warming record.
Resend’s September 30 follow-up recommends avoiding synthetic warmup services and instead verifying the sending domain, obtaining consent, and increasing legitimate volume gradually. Check the actual warming method and related domains before relying on a vendor’s promise to improve reputation.
EWS changes affect application access during October
Microsoft’s published retirement plan describes phased Exchange Online EWS disablement beginning in October 2026 and a final shutdown in 2027. EWS in on-premises Exchange Server remains outside that retirement, according to the same plan’s scope statement.
Under the September 4 access guidance, EWSEnabled=True requires an EWSAllowedAppIDs list when the updated behavior reaches a tenant. Microsoft says it preserves administrator-maintained lists; automatically populated lists use the preceding 60 days of activity and may miss infrequent applications or include unwanted ones.
For continued access, Microsoft instructs administrators to list the required application IDs and enable EWS explicitly, while continuing migration to Microsoft Graph. Review the latest tenant-specific rollout notice in Microsoft 365 Message Center and test applications that run less frequently than the usage window. The published October schedule describes a per-tenant transition rather than a simultaneous shutdown.
Hybrid Exchange has specific dependencies
Microsoft’s September 30 hybrid clarification says Graph-based hybrid rich coexistence requires Exchange Server Subscription Edition with at least its May 2026 update. For on-premises mailboxes with online archives, the same notice says Graph support is incomplete and directs administrators to retain EWS permissions, enable EWS in the cloud tenant, and allow the dedicated hybrid application.
The notice also identifies cross-organization sharing dependencies: an on-premises organization sharing free/busy and related information with a different Exchange Online organization still needs that receiving cloud tenant to keep EWS enabled. Check these documented dependencies before removing access.
Older Exchange relays face a higher update baseline
Microsoft’s September 2 server-enforcement announcement raised the minimum accepted Exchange 2016/2019 version to the October 2025 public update, with rollout scheduled from September’s second week. The affected route is a server connecting to Exchange Online through an inbound OnPremises connector.
Microsoft also warned of a later baseline increase, estimated in several months, that would exceed publicly available Exchange 2016/2019 updates and require Extended Security Updates or migration to Exchange SE. For mail using this route, examine the submitting server’s build and connector before attributing throttling to domain reputation.
Amazon SES adds tenant-level diagnostics
Amazon’s September 17 SES release adds a Tenants view to Virtual Deliverability Manager (VDM), with sends, deliveries, bounces, complaints, opens, and clicks. The new view breaks metrics down by mailbox provider, sending identity, and configuration set; programmatic queries can use the TENANT_NAME dimension in BatchGetMetricData.
The release prerequisites are tenant management and enabled VDM. These metrics support investigation of a particular sending stream, but their stated scope does not establish inbox-folder placement.
AWS’s Mail Manager implementation guide explains that tenant attribution requires the TenantName API parameter or the X-SES-TENANT SMTP header on a send processed by SES. Its routing guidance says a relay to a third-party SMTP server does not activate SES tenant attribution. Confirm the actual sending route and tenant mapping before interpreting missing metrics.
Mailgun adds alerts before subaccounts reach usage limits
Mailgun’s September 8 release adds alerts at 50%, 75%, and 100% of a subaccount’s configured usage limit; the first two thresholds are editable. The supported resources are Messages Sent, Email Previews, Email Validations, and Inbox Placement Tests, with notifications delivered by email, Slack, or webhook.
Mailgun’s setup instructions require a usage limit, an enabled alert, and configured notification channels. Check which resource an alert monitors: a sending-capacity warning and an inbox-placement test allowance describe different limits.
Brevo’s incident exposed authenticated phishing sends
Brevo’s incident write-up reports that an attacker exploited a SAML SSO scoping flaw on September 10, gaining access to 138 accounts. According to Brevo’s account-impact figures, six accounts were used for phishing and contacts were exported from 43.
Brevo says it closed the attack route and reset active sessions at 08:30 UTC that day. Its explanation of the phishing messages states that they passed ordinary email authentication checks because they used legitimate infrastructure. The incident demonstrates that authentication alone cannot establish whether account access was authorized. Review sending, invitation, and contact-export permissions alongside domain authentication.
Gmail monitoring and account migrations remain relevant
Google’s Postmaster Tools transition page, checked October 4, says retirement of the legacy web interface is postponed and that further timing information will follow. The same page’s API guidance says API v2 is available, uses a different data schema, and excludes Domain and IP Reputation. Reporting integrations need to account for those differences rather than assume the new API returns every old field.
Separately, Google’s third-party account support schedule sets January 2027 for removal of “Send as” support for non-Google accounts and says new configurations may be restricted during the transition. Its scope statement preserves Gmail-to-Gmail and Google Workspace identities. This is a sending-interface migration, not evidence of a new October spam-filtering rule.
Aggregate performance reporting remains a draft
The September 8 Aggregate Performance Reporting revision proposes JSON feedback reports tied to a DKIM signing domain and selector, with destinations discovered through DNS. Its report-content specification makes classification and engagement fields optional, leaving the report generator to decide what data to share.
The document’s status notice identifies it as an Internet-Draft and work in progress. Publication of the draft does not establish universal receiver participation or an obligation for senders to deploy it. Evaluate actual report coverage before using this format to support placement decisions.
Frequently asked questions
How much external email can a Microsoft 365 tenant send?
The allowance depends on licensing and tenant category. Microsoft’s TERRL documentation measures external-recipient volume over a sliding 24-hour window and directs administrators to the tenant’s report for the actual limit.
Will stopping synthetic warmup remove a Heatwave listing?
An accurate warming observation remains on record under Validity’s listing policy. Removal follows a review finding that the original determination was wrong; active-outreach classification can change separately.
What must an EWS application do to retain access during October?
Microsoft’s access guidance calls for the required application ID in EWSAllowedAppIDs and explicit EWS enablement. Confirm the tenant’s rollout notice and test the application while its Graph migration continues.
Does SES’s tenant dashboard measure inbox placement?
The SES feature announcement lists sending, delivery, bounce, complaint, and engagement metrics. That feature list does not establish which folder received an accepted message; a placement claim requires separate evidence.
Why might a Mailgun usage alert fail to trigger?
A subaccount must have a usage limit, and the alert and notification channel must be configured, according to Mailgun’s setup instructions. Check those prerequisites and the resource being monitored.
Has Google retired the old Postmaster Tools web interface?
Google’s current transition notice says retirement is postponed, with timing still to come. Its API migration guidance says API v2 is available and requires client updates.