Why Is My Google Workspace Email Not Working?
Q: What is the main problem this article solves?
A: Your Google Workspace email has stopped working – you are not receiving messages, emails are landing in spam, or you cannot send. This guide walks you through every common cause and the exact steps to fix it.
Q: Who is this guide for?
A: Business owners, office managers, and IT admins using Google Workspace who need their email working again. No deep technical knowledge required – we explain everything in plain English first.
Q: What are the key steps to solving this problem?
A:
- Identify your symptom (not receiving, going to spam, cannot send, or bouncing)
- Check that your MX records point to Google
- Verify SPF, DKIM, and DMARC are correctly configured
- Review email routing rules and filters in the Admin Console
- Test deliverability and monitor for 24-48 hours
Q: What is itGenius?
A: itGenius is an IT consultancy that helps small businesses scale effectively by providing affordable and effective technology services, specializing in Google Workspace support and strategy. We offer both transactional support and an “all-you-can-eat” Cloud Concierge subscription.
Start Here: Identify Your Email Problem
When your Google Workspace email is not working, the first thing to do is figure out exactly what is happening. Different symptoms have different root causes, and jumping straight to DNS changes when the problem is a Gmail filter will waste your time and potentially make things worse.
Find your symptom in the table below and jump to the right section:
| Symptom | Most Likely Cause | Jump To |
|---|---|---|
| Not receiving any emails | MX records wrong or missing | Check MX Records |
| Emails going to recipients’ spam | SPF/DKIM/DMARC not configured | Fix Email Authentication |
| Cannot send emails | Account suspended or SPF failing | Sending Issues |
| Emails bouncing back | DNS misconfiguration or recipient issues | Fix Bouncing Emails |
| Only some emails missing | Routing rules or filters | Check Routing & Filters |
| Emails delayed by hours | DNS propagation or greylisting | Fix Delayed Delivery |
If you are not sure which symptom matches yours, start with MX records. That is the most common cause of Google Workspace email not working, and the fastest to check.
Is It a Google Outage or Your Configuration?
Before you start changing DNS records, take 30 seconds to rule out a Google-side issue. If Google’s email servers are down, no amount of DNS troubleshooting will help.
Check the Google Workspace Status Dashboard: Visit Google Workspace Status Dashboard and look for any incidents on Gmail. If there is a red or orange indicator, the problem is on Google’s end. Wait for their engineering team to resolve it.
Check if it affects all users or just one: If every user in your organization cannot send or receive, it is likely a DNS or account-level issue. If only one user is affected, look at their individual filters, forwarding settings, or storage quota first.
Check when it started: Did you recently change your domain registrar, update DNS records, or add a new email service? If yes, the change almost certainly caused the problem. If nothing changed, check for Google outages or account suspensions.
Check Your MX Records
MX (Mail Exchange) records tell the internet where to deliver email for your domain. Think of them as the postal address for your email – if they point to the wrong place, your messages go to the wrong destination or disappear entirely.
This is the single most common reason Google Workspace email stops working, especially after a domain transfer or registrar change.
How to Check Your MX Records
- Go to MXToolbox.com
- Enter your domain (e.g., yourbusiness.com)
- Click “MX Lookup”
What Correct Google MX Records Look Like
For newer Google Workspace accounts (post-2023):
| Priority | Server |
|---|---|
| 1 | SMTP.google.com |
For older or standard configurations:
| Priority | Server |
|---|---|
| 1 | ASPMX.L.GOOGLE.COM |
| 5 | ALT1.ASPMX.L.GOOGLE.COM |
| 5 | ALT2.ASPMX.L.GOOGLE.COM |
| 10 | ALT3.ASPMX.L.GOOGLE.COM |
| 10 | ALT4.ASPMX.L.GOOGLE.COM |
Common MX Record Problems
- Old MX records from a previous provider still present. Remove all non-Google MX records. If you have records pointing to Microsoft, GoDaddy email, or any other provider alongside Google records, mail will split between them unpredictably.
- No MX records at all. Your domain registrar may have reset them during a transfer or renewal. Add the Google MX records above.
- Wrong priority numbers. The Google primary record must have the lowest number (highest priority). If another record has priority 0 or 1, email goes there instead.
Where to Fix MX Records
Log in to your domain registrar (GoDaddy, Namecheap, Cloudflare, or wherever you bought your domain) and find DNS Management. Delete the old MX records and add the Google records shown above.
Important: DNS changes take 24-48 hours to fully propagate across the internet. Do not panic if email does not work immediately after making the change. Check again in a few hours.
Still stuck? Our DNS Fix service gets your email working again, usually same-day.
Fix Email Authentication: SPF, DKIM, and DMARC
If your MX records are correct but emails you send keep landing in recipients’ spam folders, the problem is almost always missing email authentication records. These three DNS records – SPF, DKIM, and DMARC – work together to prove that your emails are legitimate and not forged by a spammer.
Think of it like a three-part ID check. Without all three, receiving mail servers treat your messages as suspicious.
To understand how DNS works and why it matters, check out our full guide on DNS fundamentals.
SPF (Sender Policy Framework)
SPF tells the world which servers are authorized to send email on behalf of your domain. Without it, anyone can pretend to send email from your address.
Check it: Go to MXToolbox, select SPF Record Lookup, and enter your domain.
What you need:
v=spf1 include:_spf.google.com ~allIf you also send email through other services (Mailchimp, HubSpot, Freshdesk, or any CRM), add their SPF includes too:
v=spf1 include:_spf.google.com include:servers.mcsv.net include:mail.zendesk.com ~allCritical rule: You can only have ONE SPF record per domain. If you have two separate SPF records, both break. Merge all your include: directives into a single record.
The #1 mistake we see: Adding a second SPF record instead of editing the existing one. This is the most common cause of SPF failures across the thousands of domains we have worked with.
DKIM (DomainKeys Identified Mail)
DKIM adds a digital signature to every outgoing email, proving it has not been tampered with in transit. Setting it up requires both a DNS record and an activation step in Google Admin.
How to set it up:
- Go to Google Admin Console, then Apps, then Google Workspace, then Gmail, then Authenticate email
- Select your domain
- Click “Generate new record” (use the default 2048-bit key)
- Copy the long TXT value Google gives you
- In your DNS provider, create a TXT record with the name
google._domainkeyand paste the value from step 4 - Wait 24-48 hours for DNS propagation
- Return to the Admin Console and click “Start Authentication”
Do not click “Start Authentication” immediately after adding the DNS record. Google needs time to detect it. Clicking too early will show an error, and many people assume DKIM setup has failed when they just needed to wait.
DMARC (Domain-based Message Authentication)
DMARC tells receiving mail servers what to do when SPF or DKIM checks fail. Without a DMARC record, every receiving server makes its own decision – and many will aggressively filter your messages.
Start with monitoring mode:
v=DMARC1; p=none; rua=mailto:[email protected]This sends you reports about authentication failures without blocking any email. Run monitoring mode for 2-4 weeks, review the reports to catch any legitimate services you missed in your SPF record, then gradually tighten the policy:
p=quarantine– failed emails go to the recipient’s spam folderp=reject– failed emails are blocked entirely
Do not jump straight to p=reject. You will block legitimate email from services you forgot to add to your SPF record. We have seen businesses accidentally block their own invoicing system this way.
Fix Sending Issues
“Your account has been suspended”
Google suspends Workspace accounts for three main reasons:
- Unpaid bills (check Billing in Admin Console)
- Terms of service violations
- Suspicious activity detected on the account
Fix: Go to Admin Console, then Billing. If the suspension is a payment issue, update your payment method and the account usually reactivates within an hour.
“Message rejected by server”
This usually means your SPF record does not include the server you are sending from. If you send email through a CRM, helpdesk, or marketing tool, that service’s SPF needs to be included in your record. Check the “Fix Email Authentication” section above.
“Daily sending limit reached”
Google Workspace has built-in sending limits:
- Standard accounts: 2,000 emails per day per user
- New accounts (first 24 hours): Significantly lower limits
If you are sending bulk email through Gmail, stop. Use a dedicated email marketing platform (Mailchimp, Sendinblue, etc.) and add its SPF include to your DNS record.
Fix Bouncing Emails
“550 User not found” or “Mailbox unavailable”
The recipient’s email address does not exist or their mailbox is full. Double-check the address for typos and try again. If the address is correct, contact the recipient through another channel – their mailbox may genuinely be at capacity.
“421 Too many connections”
You are sending too many emails too quickly. Slow down or use a mail queue. This commonly happens with marketing automation tools that blast thousands of messages at once.
“554 Message rejected due to SPF”
Your SPF record is either missing, incorrect, or has too many DNS lookups. SPF has a hard limit of 10 DNS lookups – if you exceed this, the entire record fails. Run an SPF check at MXToolbox and fix any errors.
Check Routing Rules and Filters
If only some emails are missing while others arrive fine, the problem is likely internal – not DNS. A misconfigured filter or routing rule can silently swallow messages without any bounce notification.
Check Gmail Filters
- Open Gmail, click the gear icon, then “See all settings”, then “Filters and Blocked Addresses”
- Look for filters that auto-delete, archive, or forward emails
- A filter matching “from:*” or “to:*” can silently eat all incoming mail
Check Admin Console Routing
- Go to Admin Console, then Apps, then Google Workspace, then Gmail, then Routing
- Review all routing rules – look for rules that redirect, reject, or quarantine messages
- Check “Default routing”, “Inbound gateway”, and “Email routing” sections
Check Google Groups
If an email alias (e.g., [email protected]) is set up as a Google Group, check these common problems:
- The Group might have moderation enabled, which means messages are stuck in an approval queue
- The Group might restrict who can post to it (external senders may be blocked)
- The Group might not be forwarding to the correct members
Go to Admin Console, then Groups, select the group in question, and review its settings.
Fix Delayed Email Delivery
DNS Propagation Delays
If you recently changed DNS records, email delays of up to 24-48 hours are normal. Different mail servers around the world cache DNS data for different lengths of time. This is not something you can speed up – it resolves on its own.
Greylisting
Some receiving servers temporarily reject the first email from a new sender and only accept it on the second attempt. This is a spam prevention technique called greylisting, and it causes 5-30 minute delays. There is nothing you can do about it on your end – it is the recipient’s server being cautious.
Large Attachments
Emails with large attachments take longer to process and deliver. Google Workspace allows up to 25MB per email. For anything larger, use Google Drive sharing links instead.
How to Prevent Email Problems in the Future
Most Google Workspace email problems are preventable. Once you have your email working again, take these steps to make sure it stays that way:
- Document your DNS records. Take a screenshot or export of your current DNS configuration. When something breaks six months from now, you will know exactly what “working” looked like.
- Set up DMARC monitoring. Even in
p=nonemode, DMARC reports tell you when authentication fails. You will catch problems before your recipients do. - Audit before adding new services. Every time you add a new tool that sends email (CRM, helpdesk, invoicing), add its SPF include to your record before you start sending.
- Keep your billing current. Set up auto-pay for Google Workspace. An expired payment method can suspend your entire organization’s email without warning.
- Review filters quarterly. Gmail filters created months ago can cause unexpected behavior as your email patterns change. A quick review every few months catches problems early.
If you want proactive monitoring and someone to handle all of this for you, Cloud Concierge members get unlimited Google Workspace support so you never have to troubleshoot email on your own again.
The Quick Diagnostic Checklist
Run through this in order. Most email problems get solved in the first three checks:
- ☐ MX records point to Google (and ONLY Google)
- ☐ SPF record exists and includes
_spf.google.com - ☐ DKIM is set up and authenticated in Admin Console
- ☐ DMARC record exists (even if just
p=none) - ☐ No conflicting routing rules in Admin Console
- ☐ No overly broad Gmail filters deleting or archiving incoming mail
- ☐ Account is in good standing (billing current, no suspensions)
- ☐ Domain verification is still active in Admin Console
Use MXToolbox.com to check the first four items in under 60 seconds.
Key Takeaways
- The most common cause of Google Workspace email not working is incorrect MX records – check these first using MXToolbox before changing anything else.
- SPF, DKIM, and DMARC all need to be configured correctly for reliable email delivery – missing even one can send your messages to spam.
- Always check the Google Workspace Status Dashboard before troubleshooting to rule out a Google outage.
- DNS changes take 24-48 hours to propagate – do not keep making changes if your fix does not appear to work immediately.
- Document your working DNS configuration now so you have a reference point when something breaks in the future.
Email Down? We Fix It – Fast.
Trusted by 10,000+ small businesses across 50+ countries. We fix Google Workspace email problems every day.
Fix My Email Now: Get rapid, fixed-price support for DNS, MX, SPF, DKIM, and DMARC issues. Most problems resolved same-day. Get Quick Fix
Stop This From Happening Again: Cloud Concierge members get proactive monitoring, priority support, and unlimited help so you are never stuck again. Start My Membership
