Why Your Emails Go to Spam When You Send From Gmail (And How to Fix It)

You send from your own Gmail address. Replies used to arrive. Then one campaign goes out and half of it disappears — no bounce, no error message, just silence. A week later someone mentions they found your email in spam.

Almost every time we investigate this for a customer, the cause isn't the words in the email. It's that the email cannot prove it came from you.

This guide is for people who send from a Google Workspace mailbox on their own domain — using Gmail directly, a CRM that sits inside Gmail, or a mail merge tool. Most of what follows takes half an hour, once, and then keeps working.

What actually decides whether you reach the inbox

Three things, in order of how often they turn out to be the problem.

Identity. Can the receiving server verify the message is genuinely from your domain and hasn't been tampered with? This is SPF, DKIM and DMARC. It is binary, it is fixable in an afternoon, and it is broken more often than anything else.

Behaviour. Does your sending look like a person doing business, or like a machine that just woke up? Volume patterns, bounce rates, complaints.

Content. Does the message look like the kind of mail people want? This matters least, though it is what everybody worries about first.

Most advice online starts with content — subject lines, spam words, emoji. That is backwards. A perfectly worded email from an unauthenticated domain still lands in spam.

Step one: find out what is actually wrong

Do not guess. Diagnose.

Send one email to any Gmail address you can open — a personal account works. In that received message, click the three dots and choose Show original.

At the top you will see three lines:

• SPF — is this server allowed to send mail for your domain?
• DKIM — is the message cryptographically signed, proving it came from you unaltered?
• DMARC — have you published a policy telling receiving servers what to do when a message fails those checks?

Three PASS lines mean your identity setup is sound and the problem lies in behaviour or content, so skip ahead. Anything else, and you have found your cause.

One trap: this only works on a received copy. Opening Show original on a message in your own Sent folder tells you nothing useful, because those results are added by the receiving server, not the sending one.

Fix 1: Turn on DKIM — the gap almost nobody knows about

Google Workspace does not sign your outgoing mail by default. Someone has to switch it on. Most small businesses never do, because nothing prompts them and nothing visibly breaks until a campaign disappears.

Here is the whole job:

1. Go to admin.google.com → Apps → Google Workspace → Gmail → Authenticate email
2. Select your domain, click Generate new record, keep the defaults (2048-bit, prefix google), and click Generate
3. Google shows you two things: a name, google._domainkey, and a long value starting v=DKIM1
4. Add that as a TXT record wherever your domain's DNS lives — Squarespace, GoDaddy, Cloudflare, Namecheap, or your web designer's account
5. Go back to Google and click Start authentication

Three things trip people up. The name field takes only the prefix — google._domainkey, not the full domain, because most DNS hosts append it for you. If Google's long key arrives wrapped across several lines, paste it as one continuous string with no quotes. And if your DNS host rejects the length, regenerate at 1024-bit.

After Start authentication the screen simply reads "Authenticating email" and stays that way. There is no progress bar and nothing finishes — Google begins signing from that moment. Do not click Stop; that switches it off again.

Where your DNS lives may surprise you. Google runs your mailbox. Your domain host runs the public address book that tells the world where your mail goes. Those are usually two different companies, so you copy from one and paste into the other. If someone else built your website, they may hold that login.

Fix 2: Publish a DMARC record

DMARC tells Gmail, Outlook and Yahoo what to do with mail claiming to be from you that fails authentication. Without one you are an unknown quantity — and since February 2024, Google has expected bulk senders to have it.

Add a second TXT record. Name: _dmarc. Value:

v=DMARC1; p=none; rua=mailto:you@yourdomain.com

p=none is monitoring mode: it reports, it blocks nothing. That is deliberately where you start. Once a few weeks of reports confirm that everything legitimate passes, you can tighten to quarantine and eventually reject.

Watch the mailto: prefix. Leave it out and the record publishes, looks fine at a glance, and is technically invalid — checkers will flag it and you will never receive a single report. It is a small typo that costs people weeks.

Fix 3: Check you have exactly one SPF record

Most Workspace domains already carry v=spf1 include:_spf.google.com ~all and need nothing done.

The failure mode is having two SPF records, added at different times by different people — one when the website went up, another when a marketing tool was connected. Two SPF records invalidate each other and you fail SPF entirely. If another service sends on your behalf, it is merged into the single existing record as another include:, never added as a second record.

Fix 4: Slow down, and stay slow

Authentication makes you legitimate. It does not make you welcome. Your sending pattern does that.

A mailbox that normally sends twenty emails a day and suddenly sends three hundred looks exactly like a compromised account, which is how filters treat it. The volume itself is not the issue; the jump is.

If your reputation is already damaged, the sequence that works is:

• Pause cold outreach entirely for two to three weeks. Not reduce — pause.
• Keep normal one-to-one correspondence flowing. Real conversation with real replies is the fastest repair mechanism there is.
• Then rebuild: roughly 20 a day in week one, 40 in week two, back to normal in week three.

Know your ceiling too. Google Workspace allows 2,000 messages a day, and 1,500 when you are doing a mail merge. Very few small businesses come near that. If your plan requires it, that is a signal the work belongs on a separate domain with a dedicated cold email platform — not on the address your clients use to reply to you.

Fix 5: Clean the list before you send, not after

Two numbers from your last campaign tell you most of what you need to know.

Bounce rate. Above 2% and mailbox providers start treating you as a careless sender. Dead addresses are the clearest available signal that a list was not earned — nobody's real subscribers evaporate at that rate.

Blocks. These differ from bounces. A bounce means the address does not exist; a block means the receiving server knows it exists and refused you anyway. Any meaningful number of blocks means your reputation is already in question, not heading that way.

Treat a suspiciously high open rate with suspicion too. When 98% of a cold list "opens" your email within hours, that is not human enthusiasm — it is security scanners opening every link and image to inspect them. Those same systems are deciding whether to deliver you.

Before the next send: remove every previous bounce, remove anyone who has never engaged across several campaigns, and run the list through a verification service if it came from anywhere other than your own inbox.

Fix 6: Write like a person, not a campaign

Filters read your email roughly the way a wary recipient would.

Keep the signature plain — name, one line of role, one link. Not six social icons, a logo image and a banner. Avoid sending a message that is one large image with a button; that is the classic shape of mail nobody asked for. Do not stack a shortened link inside a tracked link, which looks like exactly what phishing does. And write a subject line that describes the email rather than shouting at it.

The strongest positive signal available to you is a reply. Emails people answer teach filters that you are worth delivering — which is why a small, specific, genuinely personal send outperforms a large anonymous one on every measure that matters, including the ones you cannot see.

Fix 7: Watch your own numbers

Set up Google Postmaster Tools for your domain. It is free, needs one DNS record to verify, and shows you the number you otherwise cannot see: your spam complaint rate as Google itself measures it.

Google's threshold is 0.3%. Above it, you are throttled. Roughly three complaints per thousand emails is all it takes — far less tolerance than most people assume. The reason to watch it is that the number moves before your delivery collapses, not after.

What about warm-up tools?

Warm-up services connect to your mailbox and exchange messages with a network of other inboxes, replying to each other, marking mail as important, rescuing anything that lands in spam. The theory is that this builds a history of positive engagement so your real sending looks normal.

Here is an honest assessment, because most writing on this subject comes from companies selling warm-up.

Where they genuinely help. A brand new domain with no sending history. A mailbox coming back after a long silence. As a supporting measure alongside a gradual ramp — not instead of one.

Where they do not. They do not fix missing authentication. They do not clean a bad list. They do not undo spam complaints. If your DKIM is not on, a warm-up tool is building reputation for a sender that still cannot prove its identity: motion without progress.

The Gmail complication. Google treats warm-up tools connected through its API as a violation of its terms. Growbots, for example, disabled API-based warm-up for Gmail accounts in 2023 at Google's instruction. Tools that still offer warm-up for Gmail connect by IMAP/SMTP instead, which means enabling IMAP in Gmail and generating an app password — and that route needs 2-Step Verification switched on for the account first. Expect lower daily caps for Gmail accounts than for other providers.

Which warm-up tools are actually free

Most tools marketed as free turn out to be a seven- or fourteen-day trial. Two exceptions worth knowing:

Growbots (Warmbots) offers warm-up free, and it is the one we have used ourselves. For a Gmail or Workspace mailbox you will need to connect it as an IMAP/SMTP account rather than through the Google option — the Google connection looks like it works and then warms nothing up.

emailwarmup.com advertises unlimited free warm-up with spam testing across providers. We have not tested it, so we cannot tell you whether it is any good — but it is free, so it costs nothing to find out.

Lemwarm, Warmbox, Warmup Inbox, Instantly and Mailivery are paid tools with trials attached. MailReach, InboxAlly and Mailwarm are paid outright. None of them do anything that a correctly configured domain and a fortnight of patience will not, so do not spend money here before the DNS records are right.

And the free option nobody sells: email twenty real people who know you and ask them to reply. Genuine engagement, no subscription, no terms-of-service grey area.

How to run a warm-up tool sensibly

• Connect the mailbox you actually send campaigns from — not a different address on the same domain, a mistake we see often.
• Start low and let it ramp gradually rather than jumping to the maximum.
• Set up a filter so warm-up mail skips your inbox. Archive it, do not delete it — the tool needs to read those messages.
• Run it for three to four weeks minimum, and keep it running while you resume real sending rather than switching it off on day one.
• Watch its spam dashboard. High spam rates are a signal to stop sending campaigns and look at your list, not to push harder.

What this looked like in practice

A customer came to us after a campaign to 268 recipients started landing in spam. She had done nothing obviously wrong: her own domain, her own Gmail, a list she had built herself. The campaign report showed 3% bounced and 4.5% blocked outright.

We checked her domain's public records before suggesting anything. SPF was correct. DKIM had never been switched on — no signing key existed. There was no DMARC record at all. Her mail had been going out unsigned, with no policy, for as long as she had been sending it. Gmail-to-Gmail had tolerated it; everything else increasingly had not.

Twenty minutes in the admin console and her domain settings, and a test email came back with all three checks passing. The list still needed cleaning and the volume still needed rebuilding — but the thing that made everything else futile was fixed first.

The checklist

1. Send a test email to a Gmail address, open Show original, and read the SPF, DKIM and DMARC lines
2. Turn on DKIM in the Google Admin console and publish the record at your DNS host
3. Add a _dmarc TXT record with p=none — and do not forget mailto:
4. Confirm exactly one SPF record exists
5. Send a second test; all three checks should now read PASS
6. Set up Google Postmaster Tools and watch the 0.3% line
7. Remove bounces and unengaged contacts before the next send
8. Ramp volume gradually, and pause cold outreach for two to three weeks if you are already in trouble

Common questions

How long until my domain recovers?

Two to four weeks of consistent, modest, engaged sending. There is no button. Reputation is built from behaviour over time, which is also why it cannot be bought.

Do I need DMARC if I only send a few hundred emails a week?

Google only requires it above 5,000 a day. But it costs one DNS record, it is how you find out when something is impersonating your domain, and more filters look for it every year. Add it.

Can I just use a different email address?

You can, and it resets nothing. A brand new address with no history is treated with more suspicion than an established one, not less. Fix the domain you have.

Does an unsubscribe link hurt my reply rate?

It is required for bulk marketing mail, and it is better than the alternative: someone who cannot unsubscribe clicks spam instead, and that single complaint costs you more than the lost contact.

Should I buy a dedicated IP?

No. Below roughly 100,000 emails a day, a dedicated IP means carrying a reputation you are too small to maintain. Shared infrastructure works in your favour at your volume.

Sending from Gmail with Teamopipe

Teamopipe is a CRM that lives inside Gmail, so your emails go from your own mailbox and your own domain — carrying the reputation you have built, with replies landing on the deal instead of disappearing into a separate tool. Once your authentication is in place, that is the setup with the best odds of reaching an inbox.