Most common causes
- SPF did not pass for the actual envelope-sender path
- DKIM validation failed or no valid signature was present
- DMARC alignment did not have a passing aligned path
- A third-party sender is using an unconfigured bounce or signing domain
What to verify next
- Paste the full bounce into Mail Failure Doctor
- Analyze the domain’s SPF dependency graph
- Confirm the DKIM signing domain and selector from a real message
- Test DMARC alignment for the real sending service
Best diagnostic path
Live analysis
Mail Failure Doctor
Classify the complete rejection and preserve provider-specific diagnostic context.
Open analysis → Live analysisDMARC Alignment Lab
Compare visible From, envelope sender and DKIM identities without reducing the result to a pass/fail label.
Open analysis → Live analysisEmail Infrastructure Digital Twin
Map the domain’s public mail infrastructure and provider relationships before remediation.
Open analysis →Why the exact message matters
The same status family can be triggered by different conditions, and providers frequently add diagnostic text that narrows the issue. Use the complete rejection text rather than treating the numeric code as a complete diagnosis.
Provider reference
For the provider-defined meaning and current requirements, review Gmail SMTP errors and codes.