A receiver-specific view
Google Postmaster Tools provides reputation, spam, authentication and delivery-error views for messages to personal Gmail accounts. Its visibility depends on the traffic and reporting conditions. A low complaint figure is not automatically evidence of inbox success: Google warns that messages already filtered to spam can reduce user reports. [Google: Postmaster Tools dashboards]
The corporate investigation
Our recommended comparison records the sending domain, IP/provider, application, traffic type, date and affected destination. Compare a known-good period with the incident window. Preserve exact responses and configuration history before making changes.
| Question | Evidence we request |
|---|---|
| Did the route change? | Provider and IP history, connector records |
| Did the audience or purpose change? | Application owner’s explanation and subscription records |
| Is the issue destination-specific? | Examples grouped by receiving organisation |
| Did a technical change coincide? | DNS and configuration change records |
This is a diagnostic method, not an estimate of a receiver’s hidden scoring weights.
Choosing the next action
Avoid buying a new domain or dedicated IP merely because one score looks poor. Establish the actual failure and the responsibility for the sending stream first. Trace evidence and the deliverability framework help structure the investigation. We present findings, limits and proposed changes in the incident record.
Primary sources
Provider requirements and product capabilities can change. Check the linked source before a production change.