Different problems need different fixes
A rejected message, a delayed message, and a message in spam are not the same problem. We start by separating these symptoms and looking at the evidence available.
What a review can cover
- SPF, DKIM, and DMARC configuration and alignment.
- Bounce responses and patterns by recipient provider.
- Sending history, volume changes, and suppression practices.
- Domain and IP configuration where relevant to your setup.
- A prioritized discussion of remediation steps and access requirements.
Useful information to bring
Share your sending platform, when the problem began, and a redacted example of a bounce response or message header. Remove personal addresses, tokens, and other private information before sharing examples.
Authentication is not a guarantee
Passing authentication helps establish sender identity; it does not guarantee inbox placement. Content, recipient expectations, complaints, and sender reputation can still influence delivery.
A practical outcome
The aim is to distinguish likely causes from assumptions and agree what should be checked or changed next. The review scope and any implementation work are agreed before starting.
Before you increase volume
Review current provider requirements and resolve persistent failures first. See Google's sender guidelines for requirements that apply to personal Gmail recipients.