Delivery and inbox placement are different
A receiving server accepting a message does not prove that it landed in the main inbox. Deliverability work combines evidence from sending logs, authentication, mailbox-provider feedback and subscriber behavior. Recipient verification addresses only one part: mailbox risk.
Locate the failing stage
- Before sending: inspect collection source, consent, suppression rules and stale or malformed contacts.
- During SMTP: group rejections and temporary deferrals by provider, reply code and sending stream.
- After acceptance: review complaints, engagement and controlled inbox tests. A small test is diagnostic, not a universal placement guarantee.
- Over time: compare the same metrics and audience definitions. Sudden changes in volume or contact mix can make a previous baseline misleading.
Build a sender baseline
Keep an inventory of domains, IPs and authorized sending platforms. Test authentication on messages sent from every stream; a correct DNS record alone does not prove that the platform signs outgoing messages correctly. Use the authentication guide to distinguish SPF, DKIM and alignment problems.
Document normal volume, collection sources, bounce categories and complaint trends. Use Google Postmaster Tools when your sending volume provides usable data, and Microsoft SNDS for relevant sending IPs. Missing dashboard data is not proof that reputation is healthy or unhealthy.
Choose the fix that matches the evidence
Illustrative incident: a new campaign is rejected only for one sending platform, while messages from another platform work. Investigate the failing stream's configuration before verifying the entire audience again. If failures instead concentrate in an old import with confirmed recipient rejections, collection quality and suppression deserve attention.
Separate content and audience changes when possible so the team can interpret the outcome. Keep a written hypothesis, the change made and a comparable observation period. Avoid promising a fixed recovery date: recipients and providers can respond differently.
A practical pre-send review
- Confirm the intended audience and suppression lists.
- Check a real message from the actual sending platform.
- Make unsubscribe and preference handling easy to use.
- Review new volume against the established sending pattern.
- Assign an owner to watch failures and pause a problematic stream.
Primary references
Gmail sender guidelines describe authentication and unsubscribe requirements for bulk senders. Consult the current policy for the audience you send to rather than applying a single provider's thresholds to every mailbox service.