All blogs & guides

DELIVERABILITY

Cold Emails Landing in Spam: What to Check First

By TransmitInbox team
Published July 16, 2026 · Updated October 11, 2026

You check the campaign dashboard, see messages marked ‘sent,’ and then discover they’re sitting in junk. Changing the subject line is tempting, but it may have nothing to do with the fault. First work out which messages are affected and what changed before the trouble started.

Pin down where the trouble started

If problems seem concentrated in North America or Europe, compare recipient providers, list sources, and message versions within each market. Geography is a useful reporting field, not a diagnosis. Save the error or recipient-confirmed folder placement, with UTC timestamps, so colleagues in different time zones can trace the same event without guessing when it happened. Separate acceptance, junk placement, rejection, and pending retries before choosing a fix.

Write down when the issue started and what changed: a new sending tool, contact source, message, link, or volume increase. Break results down by recipient provider and campaign segment instead of treating one dashboard percentage as the whole story.

• Retain message headers from an authorised test recipient.
• Save rejection and deferral text separately from spam-folder reports.
• Record the actual sending domain and IP, not just the website address.
• Pause the affected campaign while material problems remain unexplained.

Keep a few details beside each report: the campaign, sending account, recipient’s provider, message version, and time. If one sequence is affected, look at that sequence on its own. Mixing it with ordinary customer replies can make the totals look reassuring while the campaign keeps failing. You want to know where the trouble is concentrated, not just how the overall account performed.

Follow the message and the recipient feedback

First confirm the sender is authenticated and aligned. Then examine the provider response and any specific reputation information available. Gmail's sender guidelines cover authentication, transport, complaint levels, and unsubscribe requirements. Meeting technical requirements doesn’t make unwanted outreach welcome.

Next review who received the message and why. Can you explain its relevance without using only a job title or a generic industry label? Remove excluded and opted-out contacts before any restart. If your platform doesn’t permit the planned outreach, don’t use a workaround to send it anyway.

Start with a change that fits the pattern. If only one platform is affected, check a new tracking domain or integration there. If one account is failing, inspect that account’s settings. If trouble began with a list import, look at the audience. The timing doesn’t prove the cause, but it gives you a sensible place to start rather than changing everything at once.

For a suspected technical fault, send a test to someone who has agreed to help and keep the received message. Compare its authentication, links, and actual sending service. A green badge in the platform tells you less than that message does. If those checks look right, return to the audience: would these recipients recognise the sender and understand why you contacted them?

Make the next test answer one question

Keep the test small enough to review manually, within provider rules, and limited to a relevant, permitted audience. Log what you changed. Don’t rotate domains or accounts to escape enforcement; this leaves the underlying issue unresolved.

Changing the list, copy, sender, and tracking settings together leaves you with a result you can’t explain. Pick one question first. For example, does this particular integration change the links or authentication on the received message? Save the settings you started with, make the relevant change, and compare the result. If you need to restore something, you’ll know exactly what was there before.

Test accounts are handy for checking how a message looks and what’s in its headers. They don’t stand in for your whole audience. A mailbox that already knows you may behave differently from a stranger’s inbox, and an automatic open isn’t a customer reaction. Use those accounts to check the mechanics, then look at genuine feedback from the people you may appropriately contact.

What needs to happen before a restart?

• The known technical fault has been corrected and checked on an actual message.
• Invalid addresses, exclusions, and opt-outs are respected.
• A named person can review replies and stop further sends.
• Provider responses and recipient feedback are reviewed before expanding.

Don’t treat a seed test as proof of universal inbox placement. Use it as one observation alongside real delivery evidence. When asking for help, share a redacted message, the timeline, and exact error text rather than passwords or an entire recipient list.

Before restarting, look at the follow-up queue. Some tools stop new enrolments while leaving scheduled messages running. Check what your pause button actually did, make sure earlier opt-outs are still excluded, and put someone in charge of new replies and errors. Otherwise you can be investigating a paused campaign while its reminders continue going out in the background.

Give someone responsibility for the next check and agree when you’ll look at the results. Avoid promising that a certain number of quiet days will restore delivery. If you’ve fixed the faults you can identify and filtering persists, the repair-or-retire guide can help with the next decision. That’s a wider business choice than diagnosing today’s spam report.

Common mistakes

• Changing audience and infrastructure together.
• Relying on one seed mailbox.
• Restarting with unresolved failures.
• Leaving scheduled follow-ups active during a pause.

Start with the messages that failed and follow the clues from there. If you need another pair of eyes on the setup, TransmitInbox can help investigate the sending tools and campaign habits before you commit to another change.