Internal Email Going to Spam in Google Workspace: How to Fix It

The short answer
Internal Google Workspace mail goes to spam when it is sent as your domain by an app, alias or relay that fails SPF, DKIM or DMARC alignment, so Gmail's spoofing protection flags it. Open Show original to read the Authentication-Results header, authenticate the sending source, then check safety settings and compliance rules. Allowlisting only hides the symptom.
Own-domain or alias mail landing in spam in Google Workspace? Check SPF, DKIM and DMARC alignment first, then safety settings and rules. Allowlist last.
On this page
- 01How to tell which cause you have
- 02What 'internal email going to spam' actually means
- 03Why your own-domain mail gets filtered: the causes
- 04Why is my Google Workspace alias going to spam?
- 05Fix 1: Authenticate the app or server that sends as your domain
- 06Fix 2: Check what your spoofing and authentication safety settings are doing
- 07Fix 3: Find the compliance rule or split-delivery route that mislabels internal mail
- 08Preventing it from happening again
- 09Where a client-side layer helps after the gateway
Mail from your own domain landing in spam inside Google Workspace feels like a contradiction: sender and recipient are on the same domain, so why would Google distrust it? Because Gmail does not treat a From: address as proof of anything. It checks how the message was actually sent.
Start with a three-line diagnosis. Open the filtered message and choose Show original. If spf, dkim or dmarc shows fail or none, go to Fix 1 (authenticate the sender). If all three pass, the cause is a safety setting or a rule: go to Fix 2 or Fix 3. If the problem only affects an alias or a group address, read the alias section first.
How to tell which cause you have#
Do not guess. Two tools give a definitive answer: Show original on the message itself, and Email Log Search in Admin console. Reading the header is step one for everyone.
- 1
Open the message in Gmail
Find the filtered message in Spam (or ask the recipient to), and open it.
- 2
Choose Show original
Click the three-dot menu in the message header, then choose Show original. A new tab opens with the raw message and a summary of its authentication results.
- 3
Read the Authentication-Results lines
Look for spf=, dkim= and dmarc=. Each reads pass, fail, softfail, neutral or none. Check dmarc= as well as spf=, because a message can pass SPF for another domain and still fail DMARC for yours.
| Header result | What it means | What to do |
|---|---|---|
| spf=pass; dkim=pass; dmarc=pass | The message is fully authenticated and aligned to your domain | Authentication is not the cause: check a compliance rule or a safety setting (Fix 2 or 3) |
| spf=fail or spf=softfail | The sending IP is not listed in your domain's SPF record | Add the app or server's sending source to SPF (Fix 1) |
| dkim=none or dkim=fail | The message is not signed with your domain's DKIM key, or the signature did not verify | Turn on DKIM for the domain and configure the app to sign as your domain (Fix 1) |
| dmarc=fail with spf=pass for a different domain | SPF or DKIM passed for the app's own domain, not yours, so alignment failed | Align the Return-Path and the DKIM d= domain to your domain (Fix 1) |
Email Log Search names the exact action taken
What 'internal email going to spam' actually means#
Gmail authenticates inbound messages with three checks: SPF (is the sending server allowed to send for this domain?), DKIM (is the message signed with the domain's key, and does the signature verify?), and DMARC (do those results line up with the visible From: address?). None of them care whether the From: address happens to match your own domain.
'Internal' is not a trust level on its own. The moment a third-party app sends as [email protected] from its own servers, the message re-enters Google as outside mail claiming your domain, which is exactly the pattern Gmail's spoofing protection exists to stop. The message is not punished for being internal. It is flagged because it looks like an outside party impersonating you.
Why your own-domain mail gets filtered: the causes#
There are four common causes, and they need different fixes. The first two are authentication problems and account for most cases; the last two are configuration problems you confirm in Email Log Search.

| Cause | How to confirm it | The fix |
|---|---|---|
| A third-party app or server sends as your domain, but its sending IP is not in your SPF record and it is not DKIM-signed for your domain | In Show original: spf=fail or softfail, dkim=none, dmarc=fail | Add the app's sending source to SPF and turn on DKIM so DMARC aligns to your domain (Fix 1) |
| A Gmail safety setting, 'Protect against inbound emails spoofing your domain' or 'Protect against any unauthenticated emails', is set to move the message to spam or quarantine | Email Log Search shows the message was actioned by a safety setting, and the same sender passes once it is authenticated | Authenticate the sender first; only then decide whether the setting's action needs changing (Fix 2) |
| A content compliance or routing rule catches internal mail because its message direction includes Internal - receiving | Email Log Search lists the rule by name against the message in the delivery log | Narrow the rule's direction, expression, or org-unit scope (Fix 3) |
| A split-delivery or dual-delivery setup routes internal mail out to another server and back, so Gmail re-evaluates it as external mail claiming your domain | Message headers show an external Received hop, and SPF/DKIM are evaluated against the relay rather than your domain | Authenticate the relay and register it as an inbound gateway (Fix 3) |
Why is my Google Workspace alias going to spam?#
An alias is just another address that delivers to the same mailbox, so mail from an alias normally rides on the same authentication as your main address. When an alias lands in spam, one of these four things is usually behind it. Check the From: domain in Show original first, because that domain is the one that has to authenticate.
- The alias is on a secondary domain with no DKIM key of its own. Google says you must get a unique DKIM key from Admin console for each domain: go to Apps > Google Workspace > Gmail > Authenticate email, pick the alias domain from the Selected domain menu, publish the record and start authentication for that domain too. Publish SPF and DMARC records on that domain as well.
- You send as the alias through an outside app or SMTP service. Google's guidance is that your SPF record should include all senders for the domain, and that you turn on DKIM for the domain that sends the mail. An app that sends as the alias without being in SPF or signing with that domain fails alignment (Fix 1).
- Mail to the alias is being forwarded onward. Forwarding changes the sending server, so SPF often fails at the final hop. Google points forwarders to its best practices for forwarding email to Gmail; see why forwarded mail fails SPF.
- The alias is a Google Group address. The safety setting 'Protect Groups from inbound emails spoofing your domain' can move spoofed-looking mail to spam or quarantine, and Google lets you apply it to all groups or only private groups. Authenticate whatever is sending to the group, then review the setting (Fix 2).
Sending as an alias from Gmail is a different problem
Fix 1: Authenticate the app or server that sends as your domain#
This resolves most cases, and it is the one allowlist advice skips. The goal is that every source sending as your domain passes SPF or DKIM in a way that aligns to your domain, so DMARC passes.
- 1
Inventory every source that sends as your domain
List each app and server allowed to send as [email protected]: CRM, help desk, marketing platform, billing, monitoring and alerting, scan-to-email printers, and any departmental mail server. You cannot authenticate a source you have not identified, and a single unlisted printer is enough to keep tripping the spoofing rule.
- 2
Add each source to your SPF record
Google's recommended base record is v=spf1 include:_spf.google.com ~all. Add each third-party sender with its own include: mechanism from the vendor, for example v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all. SPF evaluation is capped at 10 DNS-querying mechanisms (RFC 7208); go over that and the record returns a permerror and SPF fails outright. See fixing SPF too many DNS lookups if you are close to the limit.
- 3
Turn on DKIM for your domain
In Admin console, go to Apps > Google Workspace > Gmail > Authenticate email. Choose the domain from the Selected domain menu, generate a key (choose 2048-bit if your DNS provider supports it), publish the TXT record at the host google._domainkey (google is the default selector prefix), then start authentication for the same domain. Google notes DKIM can take up to 48 hours to begin working after you add the record.
- 4
Make the third-party app sign as your domain
Google's DKIM key signs the mail your users send through Gmail, not the mail an outside app sends from its own servers. For each third-party sender, either configure it to DKIM-sign with a key published on your domain (the vendor supplies the selector and value), or route its mail through Google's SMTP relay service so it is sent through Google. One of the two has to be true for DKIM to align.
- 5
Confirm DMARC alignment, then publish or tighten DMARC
DMARC builds on SPF and DKIM, so set those up first and allow time before adding DMARC; start with p=none while you read the aggregate reports. Alignment is the part people miss: SPF aligns when the Return-Path (envelope) domain matches the From: domain, and DKIM aligns when the signature d= domain matches it. Point the app's bounce address at a subdomain of yours, or give it a DKIM key on your domain, so a technical pass becomes an aligned pass. For what changed in the DMARC standard, see DMARC under RFC 9989.
Passing SPF is not the same as aligning
Fix 2: Check what your spoofing and authentication safety settings are doing#
These Workspace anti-spam settings are what file your mail into spam or quarantine. They are doing their job, and the real fix is authentication above, but you need to know which one is firing and you may need to soften its action while you finish Fix 1.
- 1
Open the safety settings
Sign in to Admin console as an administrator and go to Apps > Google Workspace > Gmail > Safety. Scroll to the Spoofing and authentication section. Scope the account selector to the affected organisational unit first if you only want to change it for some users.
- 2
Read each setting and its action
The settings include: 'Protect against domain spoofing based on similar domain names', 'Protect against spoofing of employee names', 'Protect against inbound emails spoofing your domain', 'Protect against any unauthenticated emails', and 'Protect Groups from inbound emails spoofing your domain'. The last three offer the same actions: Keep email in inbox and show warning, Move email to spam, or Quarantine.
- 3
Identify the one catching your mail
Google describes 'Protect against inbound emails spoofing your domain' as targeting mail that is not authenticated with SPF or DKIM while pretending to be from your domain, and 'Protect against any unauthenticated emails' as covering mail with no SPF or DKIM authentication from any domain. Google describes both in terms of inbound mail, which is why the usual trigger is a source outside Google sending as your domain. If either is set to Move email to spam or Quarantine, that is where your message went. Email Log Search names the setting that acted.
- 4
Soften the action temporarily, not permanently
While you finish authenticating the sender, you can set the action to Keep email in inbox and show warning so mail is delivered with a banner instead of hidden. Restore Move to spam or Quarantine once authentication is in place. Leaving the setting permanently relaxed is not a fix: it weakens the protection for every spoofed message, not just yours.
An allowlist is a symptom fix, not the cure
Fix 3: Find the compliance rule or split-delivery route that mislabels internal mail#
If authentication is clean and the safety settings are not the cause, a rule or a routing quirk is. Both are visible in Email Log Search, so confirm before you change anything.
- 1
Confirm what acted on the message
Open Apps > Google Workspace > Gmail > Email Log Search, find the message by sender, recipient, or subject, and expand the Delivery section. It shows whether a named compliance rule or a safety setting acted on the message, and what action it took.
- 2
Narrow an over-eager compliance rule
If a content compliance or objectionable-content rule is named, open Apps > Google Workspace > Gmail > Compliance and find it. A rule with the 'Internal - receiving' direction checked acts on user-to-user mail. Uncheck the directions it should not cover, tighten the matching expression, or scope the rule to the correct organisational unit. More on this in content compliance rules.
- 3
Fix split or dual delivery re-authentication
If headers show the message left Google and came back through another server, Gmail re-evaluated it as external mail claiming your domain. Register the relay's IP addresses as an inbound gateway under Apps > Google Workspace > Gmail > Spam, phishing, and malware > Inbound gateway, so Gmail reads authentication from the correct hop, and make sure that source is covered by your SPF record and DKIM.
- 4
Watch the inbound-gateway and allowlist interaction
One documented gotcha: if an IP address is already used in an inbound gateway configuration, adding that same IP to the email allowlist does nothing, because Gmail resolves the true source IP before applying the allowlist. Configure the gateway correctly rather than stacking an allowlist entry on top of it.
Preventing it from happening again#
Most recurrences trace back to a new sending source nobody authenticated, or a DNS change that quietly broke alignment.
- Authenticate every app and server allowed to send as your domain before it goes live, and keep SPF under the 10-lookup limit.
- Publish DMARC at p=none, read the aggregate reports, then tighten once every legitimate source aligns.
- Re-check the safety settings and DKIM after any migration, domain change, new sending vendor or DNS edit.
Where a client-side layer helps after the gateway#
Everything above happens at the domain gateway, and that is where authentication gets fixed. AI Emaily does not fix SPF, DKIM or your Workspace settings; it is an AI email client that scores every inbound message server-side, weighing SPF, DKIM and DMARC results alongside other signals, and quarantines risky mail with a reason you can read and reverse. If you want to try that on top of Gmail, there is a 7-day free trial on Pro and Autopilot.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Google Workspace Admin Help: Advanced phishing and malware protection (spoofing and authentication settings)
- Google Workspace Admin Help: Define your SPF record
- Google Workspace Admin Help: Turn on DKIM for your domain
- Google Workspace Admin Help: Add a DMARC record
- Google Workspace Admin Help: Email sender guidelines
- RFC 7208: Sender Policy Framework (SPF)

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.