Already have a rejection code? Use the evidence paths for Gmail 550 5.7.26 or Outlook 550 5.7.515.
Which sender requirements apply? Start with the receiving service, the message type and provider-specific volume. Personal Gmail, Yahoo and consumer Outlook.com have different applicability; “5,000 a day” is not a universal rule. Use the sourced comparison below before assigning a fix.
This dated comparison covers selected authentication, alignment, and unsubscribe requirements for personal Gmail, Yahoo consumer mail, and consumer Outlook.com. It is a decision aid for one launch path, not a compliance certification or an inbox-placement guarantee.
Start with the route, not the number
Before changing DNS, record the destination, message type, provider-specific volume, domains shown by a real received message, ESP or CRM, and next operator.
Consider a constructed example. An agency sends 2,500 messages from client.example and
2,500 from promotions.client.example to personal Gmail accounts in one 24-hour period.
Google’s FAQ groups those subdomains under the same primary domain, so the sender is classified as bulk.
Once met, Google says that status is permanent; a later quiet day does not remove it.
Now imagine 2,000 messages going to Yahoo consumer addresses. Yahoo describes a bulk sender as sending a “significant volume” and says it will not specify a volume threshold. Do not copy Google’s number into the Yahoo row. Record the destination mix and the actual evidence, then mark applicability as unresolved until the sender’s case is clear.
Microsoft’s current Outlook.com support page describes 5,000 or more messages to Microsoft consumer email
services using the same 5322.From domain as high volume. The support page does not state a
time period in that definition; the linked announcement describes more than 5,000 per day. Do not infer
a guaranteed safe edge case from the wording difference. A non-compliant path can be rejected with
550 5.7.515. That consumer scope does not establish a cutoff for Microsoft 365, another
provider, or every sender.
Selected provider requirements
| Recipient service and scope | Baseline and selected bulk controls | What an operator should collect |
|---|---|---|
|
Personal Gmail ( @gmail.com, @googlemail.com)Guidelines · FAQ |
Google’s baseline includes SPF or DKIM, forward and reverse DNS, TLS, RFC 5322 formatting, and
spam-rate guidance. Its FAQ defines bulk as close to 5,000 or more messages to personal Gmail in
24 hours, aggregated across the same primary domain, with permanent classification once met. Bulk
mail needs SPF and DKIM, a DMARC record (Google says p=none is acceptable), and
From: alignment with SPF or DKIM. Marketing or subscribed messages need one-click
unsubscribe and a visible body link; transactional messages are excluded from that one-click
requirement.
|
Recipient type and provider-specific volume; the received message’s SPF and DKIM domains; DMARC record and alignment mode; PTR/TLS ownership; unsubscribe headers and body link for marketing. Do not transfer this row to Google Workspace inbound mail. |
| Yahoo consumer mail Best practices · FAQ |
Yahoo requires SPF or DKIM for all senders and describes bulk as “significant volume” without
publishing a numeric threshold. Its bulk row calls for SPF and DKIM, a valid DMARC policy of at
least p=none, DMARC alignment, and one-click unsubscribe plus a visible body link
for marketing or subscribed mail. Yahoo says to honor unsubscribe requests within two days.
Transactional mail is outside the stated one-click requirement.
|
Which Yahoo consumer brands receive the mail; actual volume and message type; SPF/DKIM results and aligned domains; DMARC policy; unsubscribe headers, link, and processing path. Yahoo Japan is a separate entity. |
| Consumer Outlook.com ( outlook.com, hotmail.com, live.com)Current NDR guidance |
Microsoft’s current support guidance defines high volume as 5,000 or more messages to Microsoft
consumer services with the same 5322.From domain. SPF and DKIM must pass, a DMARC
record must exist, and at least one authenticated method must align with the From:
domain. Microsoft’s updated announcement records rejection with 550 5.7.515 beginning
5 May 2025; the earlier Junk-first wording is no longer current. The cited rule is
consumer-scoped.
|
The NDR or receiver header, 5322.From domain, SPF/DKIM results and domains, DMARC
record, destination type, volume, and ESP ownership. These sources do not establish a Microsoft
one-click unsubscribe requirement; check the current provider guidance for your path.
|
The matrix intentionally selects authentication, alignment, and unsubscribe checks. Provider documents also cover transport, DNS, complaint, list-hygiene, and message-format controls. A row is a starting point for evidence collection, not an exhaustive certification checklist.
Read a result in context
Suppose a received message shows spf=pass for bounce.vendor.example and
dkim=pass for vendor.example, while the visible From: domain is
client.example. Those passes authenticate vendor identities; they do not, by themselves,
show alignment with the client. Under RFC 9989,
DMARC needs an aligned SPF or DKIM pass: relaxed alignment uses the same organizational domain, while
strict alignment requires identical domains. The companion
alignment guide works through this
three-domain question. If the real header or its provenance is missing, write “message-level
authentication not observed” rather than turning a DNS badge into a pass.
The next action depends on the row. For a Gmail bulk path, confirm both SPF and DKIM plus DMARC and
one-click handling for marketing mail. For a Yahoo path, document why the sender believes its volume is
significant enough to trigger the bulk row; there is no published number to cite. For an Outlook.com
rejection, preserve the NDR, confirm that the path is consumer mail, and inspect the
5322.From domain and aligned authentication. In each case, record one owner and a recheck
through the same ESP path.
If the launch is still blocked
This article may be enough for an operator who can identify the applicable row and make the supported change. If one real domain or subdomain, one ESP or CRM path, and one named blocker still need interpretation and an accountable handoff, request scope for Folderly Launch Audit. The manual service is US$495 and includes a report within 48 hours from the agreed start after payment and complete intake, up to five prioritized actions with owners, a 45-minute operator handoff, and one recheck within seven days of the report. It is read-only advice; your authorized operator makes DNS and ESP changes. There is no inbox-placement guarantee, warming, reputation recovery, list repair, or multidomain review. Do not send credentials, raw headers, or customer lists in the request.
The request form prepares an editable email draft. Review it and send it from your mail app; nothing is sent automatically.
Sources and applicability. Primary sources reviewed 28 September 2026: Google sender guidelines, Google sender FAQ, Yahoo Sender Best Practices, Yahoo Sender FAQs, Microsoft Outlook.com NDR guidance, Microsoft’s updated high-volume announcement, and RFC 9989. This is dated documentation synthesis, not an original sending test, survey, benchmark, or customer result. Provider wording and enforcement can change; check the linked source before acting.