Declare the incident and preserve the evidence
Set a trigger such as a sharp rise in permanent rejections, authentication failures, spam complaints or a sudden drop in delivered volume for a major mailbox provider. Record the first affected send, sending domain, provider, campaign, IP pool, audience segment and recent configuration changes. Save SMTP response codes and headers from authorized test messages.
Separate accepted by the receiving server from inbox placement. A provider reporting 'delivered' generally means the recipient server accepted the message, not that a human saw it in the inbox. Opens are also an imperfect diagnostic because privacy features and image loading affect them. Start with hard evidence: error codes, authentication results, complaint feedback and recipient-domain patterns.
Contain risk before changing DNS or volume
Pause the affected promotional stream when complaints or rejections indicate ongoing harm. Keep genuinely necessary transactional messages on an appropriately configured path if they are unaffected, but do not use a transactional stream to bypass marketing restrictions. Suppress invalid addresses, unsubscribed recipients and recent complainers immediately.
Assign an incident lead and restrict ad hoc changes. Multiple people editing DNS, ESP settings and campaign audiences simultaneously can obscure the cause. Preserve a rollback copy of DNS records and sending configuration. If there is evidence of unauthorized sending, escalate to security and rotate compromised credentials before resuming.
Test authentication and sender identity
Verify the actual sending domain and selector in message headers. Check SPF authorization, DKIM signature validation and DMARC alignment against the visible From domain. Review DNS propagation, recent domain changes, forward and reverse DNS where relevant, TLS and any ESP subdomain configuration. A passing SPF record on a different domain may not satisfy alignment.
Gmail's sender guidelines require authentication and infrastructure hygiene for senders, with additional SPF, DKIM, DMARC and unsubscribe obligations for higher-volume senders. Its published spam-rate guidance uses 0.3% as an important ceiling, not a target to approach. Confirm current mailbox-provider requirements before diagnosing an incident from an outdated checklist.
Distinguish reputation from a technical rejection
Group failures by provider and enhanced status code. Authentication-related rejects suggest a technical configuration issue; unknown-user bounces suggest list hygiene; complaint spikes suggest consent, targeting or content relevance. A sudden Gmail-only issue differs from failures across all destinations. Review recent audience imports, reactivation campaigns, frequency changes and sending-volume jumps.
Check provider postmaster dashboards and any ESP reputation indicators available. Do not assume a blocklist listing explains all failures; confirm the listing's relevance to the sending IP or domain and whether the recipient provider actually uses it. Avoid paying an unverified delisting service or rotating domains to evade recipient protections.
Recover with controlled sends
Fix the root cause, then resume with a small, recently engaged and properly consented segment if the provider permits it. Watch SMTP rejection rate, complaints, unsubscribes and accepted delivery by provider before expanding. Do not promise that a specific warm-up schedule guarantees inbox placement; reputation recovery depends on recipient behavior and provider evaluation.
Keep a daily incident log with change, owner, test cohort, send volume and outcome. If complaints remain elevated, stop and reassess consent and targeting rather than increasing volume. For a compromised domain or severe policy enforcement, work through the mailbox provider's documented remediation process.
Prevent the next incident
Create pre-send gates for list provenance, suppression sync, frequency caps, authentication checks, unsubscribe function, campaign audience and sudden volume changes. Monitor domain-level complaint and rejection trends and establish who receives alerts outside campaign launch hours. Test a sample message after any DNS or ESP migration.
Pair this playbook with the site's SPF/DKIM/DMARC guide, list-health monitoring and email frequency cap article. Use the UTM Validator to check campaign attribution after recovery, but do not treat click tracking as a substitute for deliverability diagnostics. Close the incident with a root-cause summary, customer impact and assigned prevention work.