Google Workspace Email Not Working? A Complete Troubleshooting Guide

Posted by: Perplexity

Quick overview

If your Google Workspace email is failing—you’re not receiving messages, sent mail lands in spam, or you can’t send at all—this guide walks you through every common cause and the exact steps to fix it. The primary keyword for this article is “Google Workspace email not working.” Follow the checklist in order to diagnose and resolve issues quickly.

Identify the symptom first

Different symptoms point to different root causes. Match your problem to the likely cause and jump to the relevant section.

Not receiving any emails → MX records wrong or missing
Emails arriving in recipients’ spam → SPF/DKIM/DMARC missing or incorrect
Cannot send emails → Account suspension or authentication failure
Emails bouncing → DNS misconfiguration or recipient issues
Only some emails missing → Routing rules or Gmail filters
Email delays → DNS propagation or greylisting

If you’re unsure, start with MX records—this is the most common cause and the fastest check.

Check for a Google outage

Before changing DNS or account settings, rule out a Google-side issue.

Visit the Google Workspace Status Dashboard and look for Gmail incidents.
If the dashboard shows an outage, wait for Google to resolve it.
Determine whether the problem affects all users or just one. Global failures usually indicate DNS or account-level problems; single-user issues often stem from filters or storage limits.

Check your MX records

MX (Mail Exchange) records tell other mail servers where to deliver email for your domain. Incorrect MX records cause lost or misdelivered mail.

How to check:

Use MXToolbox or a similar DNS lookup tool.
Run an MX lookup for your domain.

Correct Google MX records (standard older setup):

Priority 1: ASPMX.L.GOOGLE.COM
Priority 5: ALT1.ASPMX.L.GOOGLE.COM
Priority 5: ALT2.ASPMX.L.GOOGLE.COM
Priority 10: ALT3.ASPMX.L.GOOGLE.COM
Priority 10: ALT4.ASPMX.L.GOOGLE.COM

Newer Google Workspace accounts may use different hostnames (for example, SMTP.google.com). Confirm the values in your Admin Console documentation.

Common problems and fixes:

Old MX records from a previous provider: delete non-Google MX entries.
No MX records: add Google MX records in your DNS manager.
Wrong priorities: ensure the primary Google MX has the highest priority (lowest number).
Where to change them: log into your domain registrar or DNS host (GoDaddy, Namecheap, Cloudflare, etc.) and update MX records. Allow 24–48 hours for DNS propagation.

Fix email authentication: SPF, DKIM, DMARC

If outbound mail lands in spam, missing or incorrect SPF, DKIM, and DMARC records are usually to blame. These DNS records prove your mail is legitimate.

SPF (Sender Policy Framework)

Purpose: Lists servers authorized to send on behalf of your domain.
Check with: MXToolbox SPF lookup.
Typical SPF value for Google Workspace:
- v=spf1 include:_spf.google.com ~all
If you use third-party services (Mailchimp, HubSpot, CRMs), include them: merge includes into a single SPF record.
Critical rule: Only one SPF TXT record per domain. If you have multiple, merge them.

DKIM (DomainKeys Identified Mail)

Purpose: Adds a cryptographic signature to outgoing mail.
Setup steps:
1. In Admin Console: Apps → Google Workspace → Gmail → Authenticate email.
2. Generate a 2048-bit key and copy the TXT value.
3. Create a DNS TXT record named google._domainkey with the provided value.
4. Wait 24–48 hours for propagation, then click “Start Authentication” in Admin Console.
Tip: Don’t click “Start Authentication” immediately—wait for DNS propagation, or Google will report an error.

DMARC (Domain-based Message Authentication)

Purpose: Tells receivers what to do when SPF or DKIM fail and provides reporting.
Start in monitoring mode:
- Example: v=DMARC1; p=none; rua=mailto:[email protected]
Monitor reports for 2–4 weeks, add missing senders to SPF, then move to quarantine (p=quarantine) and eventually reject (p=reject) only after confirming legitimate senders are covered.
Do not jump straight to p=reject or you may block legitimate mail (invoices, support notifications, etc.).

Fix sending issues

Account suspension

Common causes: billing problem, terms violations, or suspicious activity.
Fix: In Admin Console, check Billing; update payment methods. Suspensions usually lift within an hour after resolving billing issues.

Message rejected by server

Usually indicates SPF doesn’t include the sending service.
Add the service’s SPF include to your domain SPF record.

Daily sending limits

Google Workspace limits (standard): ~2,000 emails per day per user.
For bulk messaging, use a dedicated email marketing provider and add their SPF include.

Fix bouncing emails

Common bounce messages and responses:

550 User not found / Mailbox unavailable: Verify recipient address and retry; receiver mailbox may be full.
421 Too many connections: Throttle sending rate or use queued delivery.
554 Message rejected due to SPF: Check SPF record, ensure it exists and stays under the 10-DNS-lookup limit.

Run diagnostics with MXToolbox and examine bounce codes to identify root cause.

Check routing rules and filters

If only some messages are missing, investigate internal filters and routing.

Gmail filters (per user)

In Gmail: Settings → See all settings → Filters and Blocked Addresses.
Look for filters that delete, archive, or forward messages.
Watch for overly broad filters (e.g., matching from: or to:).

Admin Console routing (organization-wide)

Admin Console → Apps → Google Workspace → Gmail → Routing.
Review default routing, inbound gateway, and any custom routing rules for redirects, rejections, or quarantines.

Google Groups

Problems: moderation queues, posting restrictions, or incorrect member forwarding.
Admin Console → Groups → select group → review moderation and posting permissions.

Fix delayed email delivery

DNS propagation

After DNS changes, propagation can take 24–48 hours. Delays are normal.

Greylisting

Some recipient servers temporarily defer the first delivery attempt (typical delay: 5–30 minutes). This is server-side and not within your control.

Large attachments

Google Workspace limit: 25 MB per email; use Google Drive links for larger files.

Prevent future email problems

Adopt these practices to reduce downtime and troubleshooting:

Document DNS records: keep a snapshot or export of your working DNS configuration.
Monitor DMARC reports: start in p=none to catch authentication failures early.
Audit before adding new services: add SPF includes for any tool that sends mail for your domain before you use it.
Keep billing current: enable auto-pay for Google Workspace to avoid service suspension.
Review filters quarterly: filters created months ago can behave unexpectedly as workflows change.
For ongoing support: consider managed services or a Cloud Concierge plan for proactive monitoring.

Quick diagnostic checklist

Run these checks in order—most issues are resolved in the first three steps.

☐ 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 p=none)
☐ No conflicting routing rules in Admin Console
☐ No overly broad Gmail filters deleting or archiving mail
☐ Account billing and status are in good standing
☐ Domain verification is active in Admin Console

Use MXToolbox for quick checks of MX, SPF, DKIM, and DMARC in under a minute.

Conclusion and next steps

Most Google Workspace email issues stem from incorrect MX records or missing authentication (SPF, DKIM, DMARC). Start with an outage check, verify MX records, then confirm SPF/DKIM/DMARC and routing rules. Document your DNS configuration and enable DMARC reporting for early warnings. If you prefer hands-off support, consider managed services that handle DNS and email authentication for you.

Call to action: Run the Quick Diagnostic Checklist now, or contact a Google Workspace specialist if you’d like help implementing SPF, DKIM, and DMARC correctly.

Office IT Tips