What this analysis does
Model authentication, alignment, unsubscribe, TLS and sending-pattern inputs against maintained provider policy profiles, with separate findings for major mailbox ecosystems.
Major mailbox providers publish sender requirements that differ in detail and in the volume at which they apply. Scoring a sending profile against those published expectations before a campaign leaves the queue is cheaper than interpreting rejections afterwards.
Requirements scale with volume
Provider guidance distinguishes ordinary senders from bulk senders, and the obligations tighten sharply at the higher tier. Authentication that is merely recommended at low volume becomes required above the threshold, along with one-click unsubscribe and a complaint rate kept below a published ceiling.
Volume is counted per sending domain and per provider, which surprises organizations that spread traffic across several platforms. Aggregate volume to one recipient provider can cross a threshold even when no individual platform appears to send in bulk.
- Authentication requirements tighten at bulk-sending volume.
- Thresholds are evaluated per provider and per sending domain.
- Traffic split across platforms still aggregates at the receiver.
Complaint rate is the metric with the least tolerance
Published complaint thresholds are low, and the consequence of crossing them is immediate and difficult to reverse. Reputation recovers slowly, so the practical approach is to keep the rate well below the stated ceiling rather than treating the ceiling as a target.
Complaint rate is driven by list acquisition and expectation setting more than by message content. Recipients who did not clearly opt in, or who receive something different from what they expected, complain at rates that no amount of template optimization offsets.
Unsubscribe handling is a hard requirement, not a courtesy
Bulk senders are expected to support one-click unsubscribe through the standard list headers and to honour requests within a short published window. Both the header and a working in-body mechanism are needed, because clients differ in what they surface.
The failure mode that draws enforcement is a header that is present but not functional. A List-Unsubscribe-Post header that returns an error, or an endpoint that requires the recipient to log in first, does not satisfy the requirement and can be worse than omitting the header.
Validate the unsubscribe headersCompile a full pre-send readiness report
Example: an authenticated sender that still falls short
Evidence supplied
A profile with SPF, DKIM and DMARC configured, sending above the bulk threshold, with no one-click unsubscribe header.
How to read the result
The score reports authentication as satisfied and flags the missing unsubscribe mechanism as a bulk-sender requirement gap. Authentication alone does not satisfy provider expectations above the volume threshold.
Known limits
- Provider requirements change; scoring reflects published guidance at the review date shown above.
- Scoring uses the profile you describe and cannot observe your actual complaint or engagement rates.
- Meeting published requirements improves eligibility but does not guarantee inbox placement.
Common questions
Do these requirements apply below the bulk threshold?
Authentication expectations increasingly apply to all senders. The additional obligations around unsubscribe handling and complaint rate are directed at bulk volume.
How is sending volume counted?
Per sending domain, per recipient provider, over the provider’s own measurement window. Traffic sent through multiple platforms still aggregates at the receiver.
Does passing this simulation guarantee inbox placement?
No. It indicates eligibility against published requirements. Placement additionally depends on reputation, engagement and per-recipient signals.