Deliverability · Practical guide
Cold email going to spam: isolate the failing layer
Separate authentication failures, recipient selection, message construction and mailbox-specific placement before changing a campaign.
Reviewed · Examples are illustrative
Who this helps: Operators diagnosing authentication, receiving-policy and delivery failures.
Define the decision
One test account is a useful symptom, but it is not a representative sample of every recipient. Preserve the original message, full headers, sending mailbox and observation time before making changes that erase your baseline.
Work through the procedure
- Determine whether the message was rejected, accepted into spam or absent from the receiving account.
- Check authentication on the received copy, not only DNS scanner results.
- Compare the affected provider, audience source and campaign version with an unaffected control.
- Change one plausible cause and repeat a controlled observation before expanding.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
Control: same mailbox, relevant known recipient, no new attachment
Variant: current campaign message
Observation: only the variant lands in spam
Next investigation: message links and construction, while retaining authentication evidenceRead the result
This comparison narrows the next investigation; it does not prove that a single word triggered a filter. Recipient history, provider rules and timing can still differ. Record what remained constant as carefully as what changed.
Check before moving on
- Exclude warmup exchanges from prospect-placement claims.
- Preserve negative replies and opt-outs as audience-quality evidence.
Limits and next action
Avoid repeatedly sending to unresponsive people to obtain more data. Pause an affected segment when the cause remains uncertain and use provider diagnostics alongside controlled tests.
Source: Google: email sender guidelines
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Email deliverability audit checklist with evidence and owners →
- Deliverability incident response: contain, diagnose and restart deliberately →
- Read email authentication headers without trusting the wrong hop →