How to Fix Gmail Not Receiving Emails |Complete 2025 Guide

Quick preview: If Gmail stopped receiving messages, the cause is almost always one of a small set of problems — client sync, storage quota, filters/forwarding, account suspension or DNS/MX issues for custom domains. This guide walks you from fastest to deepest checks, with reproducible commands, admin checks, and recovery steps you can follow start-to-finish.

Why this guide (and why 2025 matters)

Gmail’s core delivery model hasn’t changed: senders hand mail to MX records → Google’s mail servers accept and route → the mailbox (user account or Workspace account) stores it. But the environment around Gmail has evolved — more integrations, stronger auto-filters, widespread Workspace adoption, and heavier attachment/storage usage — so troubleshooting must cover both the classic causes and the newer, platform-level pitfalls. This guide merges official Google troubleshooting, community evidence, and field-tested steps so it stays relevant for years.

High-level checklist (run this in order)

  1. Confirm sender's delivery status (ask sender for bounce message or delivery logs).
  2. Check simple local issues: internet, device sync, app updates.
  3. Inspect Gmail folders: Spam, All Mail, Trash, and filters/forwarding.
  4. Verify account storage (15 GB free Google quota or Workspace limits).
  5. If using a custom domain/Workspace: check MX records, DNS, and routing rules.
  6. Check Google Workspace status & admin console for suspensions or routing rules.
  7. Advanced: examine headers, logs, or ask sender to run SMTP tests (EHLO/MAIL FROM/RCPT TO) or check third-party blocking or reputation lists.

Detailed step-by-step troubleshooting

1. Confirm the problem from the sender side (fastest verification)

Before changing anything, ask whoever sent the email to confirm they didn't get a bounce. If the sender has a bounce message, it usually contains the reason (e.g., mailbox full, user unknown, or MX lookup failed). If there’s a bounce, copy the bounce text exactly — it’s the single most helpful diagnostic.

If the sender reports successful delivery (no bounce), ask them to forward the original message or to send a plain-text test message to your address right now (subject: TEST). That helps separate a one-off delivery failure from a persistent routing problem.

2. Quick local checks (client, device, network)

These steps fix many user-level problems quickly. Lifewire’s troubleshooting checklist is a good reference for device-level steps.

3. Check Gmail folders and search comprehensively

Gmail can hide mail via filters, archiving, or automatic classification. Run these checks:

Community threads and Google support repeatedly show filters/forwarding and mis-specified rules are frequent stealth causes. Always run a full text search first — the message may be present but not visible.

4. Verify storage: free Google accounts and Workspace quotas

If Google storage is full (Google Drive + Gmail + Photos share the same quota), you cannot receive new messages. A full mailbox often prevents delivery and causes silent failures until the sender receives a bounce. Steps:

5. Check for account suspension, disabled domain, or billing problems (Workspace)

For Google Workspace accounts, messages can bounce if the account or domain is suspended (billing, TOS, domain expiry). Admins should:

6. DNS and MX records (custom domains / Workspace) — the critical infrastructure check

If you can send but not receive for a domain-based address (you@yourdomain.com), the most common root cause is misconfigured or missing MX records in DNS. Quick verification steps:

  1. From any terminal or online tool, run an MX lookup: dig MX yourdomain.com +short or use Google’s MX check tool at toolbox.googleapps.com/apps/checkmx/.
  2. Confirm MX records point to Google’s servers (e.g., ASPMX.L.GOOGLE.COM and secondary hosts) and priority values are correct per Google’s setup instructions.
  3. Check for stray MX records from old providers — multiple providers can create routing confusion or rejection.
  4. Verify no “A” or “CNAME” records accidentally override mail routing for mail subdomains.

Multiple admins on Reddit and specialist blogs confirm that incorrect MX records are the single most frequent cause for domain-hosted Gmail to stop receiving messages. If records were recently changed, DNS propagation (TTL) can delay recovery by up to 48 hours in rare cases.

7. Email routing, transport rules and third-party filtering (Workspace & hosted mail)

Workspace admins may set routing rules, compliance filters, or partner gateways that block or divert incoming mail. Steps to audit:

If you rely on a third-party filter, the issue may be upstream of Google — ask the provider for delivery logs. Reco.ai and other Workspace-focused writeups emphasize that routing rules and security appliances are a common enterprise failure point.

8. Authentication, reputation, and DMARC/DKIM/SPF failures (sender-side causes)

Sometimes your mailbox is fine; the sender’s domain fails authentication and remote servers reject the message before it reaches Gmail. Confirm with the sender that they pass SPF, DKIM, and DMARC checks. As the recipient you can:

9. Test with a controlled experiment

Run a short experiment to narrow the fault domain:

  1. Ask Sender A (external, e.g., Gmail/Outlook) to send a plain-text email to youraddress@gmail.com.
  2. Ask Sender B to send from a different provider (e.g., Outlook or Yahoo).
  3. If you have a secondary account, send from your Gmail to that account and back again.

Record which messages arrive and which do not. If only a subset fails, you can identify patterns: one provider, one geographic region, large attachments, or certain content types.

10. App/IMAP/POP issues — client-specific sync problems

If web Gmail shows mail but your desktop/mobile mail client doesn’t, the issue is client configuration:

Many forum posts show removing + re-adding cleans a corrupted local cache and restores message flow.

11. Security incidents — compromised account or account hijack

If your account was recently accessed from an unfamiliar device, Google may temporarily restrict incoming mail for protection or attackers may have set forwarding rules to siphon mail. Immediate steps:

Community support and official pages show attackers commonly create hidden forwarding rules — remove any you don’t recognize.

12. When to contact Google support or your domain host

Contact Google support (or your Workspace admin) when:

For domains, also open a support ticket with your DNS provider if MX records appear incorrect or you suspect DNS-level blocking. Provide timestamps, sender IPs, and sample message headers to make their log search effective.

Recovery examples & real-world playbooks

Scenario A — Personal Gmail: “No mail from one contact”

  1. Ask sender for bounce/test email. If none, search in Gmail: in:anywhere from:sender@example.com.
  2. Check Spam, Filters, and Blocked Addresses; remove block or filter.
  3. If still not found, ask sender to send a tiny test message. If that fails but others succeed, temporarily disable any forwarding or third-party add-ons and retry.

Scenario B — Workspace domain: “All inbound mail stopped”

  1. Admin: check Admin Console for suspended users or billing issues.
  2. Run MX lookup and confirm Google MX records are present and correct (use Google’s MX check tool).
  3. Check routing rules and third-party gateways; temporarily bypass them.
  4. If DNS/records are correct and problem persists, open a Google Workspace support case with your diagnostic headers and timestamps. 9

Scenario C — Intermittent delivery / some messages missing

  1. Audit content compliance and spam rules for patterns (attachments, keyword blocks, sender domains).
  2. Look at sender SPF/DKIM/DMARC; ask the sender for headers if possible.
  3. Set up a temporary catch-all or test alias to see if messages route elsewhere.

Tools and commands (quick reference)

Preventive steps (reduce future recurrence)

Diagnosing with message headers — a primer

When a sender shares the raw message or your own received mail, examine the headers for the SMTP relay path (Received: lines). Key checks:

Understanding headers lets you tell whether the message reached Google and was routed elsewhere (e.g., quarantined) or whether it was never accepted. If Google accepted it, there will be a Received line from Google’s servers — if not, the failure is upstream. This is the most robust way to avoid guesswork when mail appears lost.

Troubleshooting checklist you can copy & paste

  1. Confirm sender bounce or successful send (get the raw bounce if present).
  2. Search Gmail: in:anywhere from:sender@example.com.
  3. Check Spam, All Mail, Trash.
  4. Inspect Filters and Forwarding (Settings).
  5. Verify storage at https://one.google.com/storage.
  6. For domains: run dig MX yourdomain.com or Google MX check.
  7. Check Admin Console for suspensions, routing rules, or third-party gateways.
  8. If compromised: change password, remove unknown forwarding, enable 2FA.
  9. Contact Google Support / domain host with headers and timestamps when stuck.

Common myths & mistakes

Frequently Asked Questions

Q: Why am I not receiving emails in my Gmail but can still send them?

A: Common causes: full Google storage quota, filters/forwarding moving messages out of Inbox, or (for custom domains) incorrect MX/DNS records. Run a full search (in:anywhere), check storage at one.google.com, and verify MX records if you use a domain.

Q: How do I check if Google experienced an outage that affected receiving mail?

A: Check the Google Workspace Status Dashboard and the Gmail Help Community. If Google has a wider outage, many users will report it and Google shows it on the status dashboard. For account-level issues, the Admin Console will also show disruptions.

Q: Messages from one company never reach my inbox — what should I ask them to check?

A: Ask them for the SMTP bounce or delivery logs, and ask them to verify their SPF, DKIM, and DMARC configurations. Also have them send a plain-text test message (no attachments or HTML) — that rules out attachment-size or content filters.

Q: I found unknown forwarding in my Gmail — is my account hacked?

A: Possibly. Remove the forwarding rule immediately, change your password, sign out all devices from your Google Account security page, and enable 2-Step Verification. Review recent security events and run the Google Security Checkup.

Q: I use Google Workspace and recently changed DNS — how long until mail works again?

A: DNS propagation is usually quick (minutes–hours) but can take up to 48 hours depending on TTL values and upstream DNS caches. If MX records are correct but mail still doesn't arrive after a few hours, re-check records for typos and consult your DNS provider.

Conclusion — where to start now

Start with the simplest checks: run a search in Gmail, confirm sender bounce status, and verify storage. If you use a custom domain or Workspace, then prioritize MX and routing checks next. Keep records of timestamps, sender addresses, and any bounce text — they are the keys for fast resolution. If you reach support, providing headers and a clear timeline will move the case from “weird” to solvable.

Call to action: Run the checklist above now — begin with a targeted search (in:anywhere from:sender@example.com) and check your Google storage at https://one.google.com/storage. If you want, paste a sample bounce message or header here and I’ll help interpret it step-by-step.

Related Articles