Why Is Email Not Received? | Fix The Hidden Causes

You send a test message. Nothing lands. You ask a friend to write you. Still nothing. At that point, “my email isn’t coming in” feels like one problem, but it can come from a pile of different faults. Some sit inside your inbox. Some sit on your device. Some sit on the sender’s side. And if you use a custom domain, the issue can sit in DNS, far away from the screen you keep refreshing.

The good news is that email failures leave clues. A message might be in Spam, All Mail, Trash, Quarantine, a different tab, or another mailbox linked by forwarding. Your mail app might be stuck offline. Your storage might be full. A filter might be archiving new mail before you ever see it. On a business domain, the MX records might point mail to the wrong server, which means the inbox itself never gets a shot at delivery.

This article walks through the usual causes in the order that saves the most time. Start with the fast checks. Then move into account settings, app sync, sender-side issues, and domain setup. By the end, you should know not just what broke, but where it broke.

Why Is Email Not Received? Common causes

Most missing-email cases fall into one of six buckets: placement, blocking, syncing, storage, routing, or sender reputation. Placement means the message arrived but landed somewhere else, such as Spam, Promotions, Trash, or an archive folder. Blocking means you or your provider rejected the sender. Syncing means the message exists on the server, but your app has not pulled it down. Storage limits can stop new mail from arriving. Routing points to forwarding rules, aliases, and domain records that send mail to a different mailbox. Sender reputation covers spam filters, failed authentication, and mail that never gets accepted.

If you’re using Gmail or Outlook on the web, start in the browser before touching the phone app or desktop client. Web access shows what the mailbox itself holds. If the web inbox has the missing message, the fault is usually your app, device, or local sync. If the web inbox also shows nothing, the fault is farther upstream.

Check the folders people forget first

Start with Spam, Trash, Archive, All Mail, Updates, Promotions, and any custom folders you made months ago and forgot. Search by sender address, subject line, and a unique word from the message. If the sender wrote from a company domain, search that domain too. Filters often move mail while keeping it unread, which makes it look like nothing arrived.

Gmail’s own missing-message steps point people to search all mail, check Spam, Trash, and filters before assuming delivery failed. Microsoft says much the same for Outlook.com when mail does not send or receive. Those are boring checks, but they solve a lot of cases because the message was never gone in the first place; it was just sorted out of sight.

Look for filters, rules, and forwarding

A single rule can make your inbox feel dead. Maybe all mail from a client gets auto-archived. Maybe receipts get forwarded to an old address you no longer open. Maybe a mobile app created a focused inbox split and you only look at one tab. Open your rules and filters and read them line by line. If you see actions like archive, skip inbox, mark as read, forward, delete, or move to folder, test by turning those off for a moment.

Forwarding adds another layer. If your account forwards mail to another address, and that second mailbox is full or failing, you may think the first account is broken. It may be doing exactly what you told it to do.

Check blocked senders and safe lists

Blocked addresses are easy to miss because they often sit in a quiet settings page you rarely open. If one sender cannot reach you but others can, this is one of the first places to check. Also look at domain blocks, not just single addresses. A block on an entire domain can wipe out every message from that company.

Why your inbox stops receiving new mail

When nothing new arrives from anyone, think bigger than one bad message. That pattern usually points to sync failure, account storage, sign-in trouble, or server routing.

Storage can stop delivery cold

Mailboxes have limits. Once you hit them, incoming mail can bounce, queue, or disappear into provider-side error handling. This hits people who never delete large attachments, share cloud storage across mail and files, or run an old business plan with a smaller quota. Check your available space before chasing fancy fixes.

Low storage has a nasty side effect: it can look random. One sender may get a bounce notice while another gets silence. That makes the fault feel mysterious when it’s just a full mailbox.

Apps can go offline while the mailbox stays fine

If the web inbox shows new mail but your desktop app does not, the issue sits in the app. Outlook can slip into Work Offline mode. Mobile mail apps can pause background refresh to save battery. Old passwords can break sync after an account security change. A damaged profile can also block new mail even while old mail still shows.

That’s why a clean test matters. Sign in on the web. If the message is there, you do not have a delivery issue. You have a device or app issue.

Start with a clean test before changing settings

Do one controlled test. Ask someone you trust to send three plain emails: one with no attachment, one with a small image, and one replying to a thread you already have. Send them five minutes apart. That pattern tells you a lot. If only replies arrive, a thread filter may be involved. If plain text arrives but the image message does not, attachment scanning or size limits may be in play. If none arrive, look at account-wide issues.

Midway through your checks, it helps to compare your settings against official provider steps. Google’s Gmail messages are missing page walks through search, Spam, filters, forwarding, and recovery. Microsoft’s Outlook.com send or receive checklist covers storage, device sync, and account status.

Read bounce messages when you can get them

If the sender gets a bounce notice, don’t ignore it. That message often names the fault in plain text: mailbox full, user unknown, domain not found, rejected by policy, message too large, or authentication failed. A bounce can cut an hour of guesswork down to a minute. Ask the sender for the full error, not a cropped screenshot.

Check aliases and old addresses

Some people send to an address that looks right but is not the one your mailbox actually receives. Old aliases, misspelled addresses, retired staff accounts, and typo-prone domain names can all send mail into a void. If you run a business domain, verify that the exact address exists and still points to the mailbox you expect.

When the fault sits with the sender

Plenty of missing email is not your fault at all. The sender may have a bad address, a full outbox, a failed DNS setup, or spam-heavy sending habits that make providers distrust the message. If one company never reaches you while everything else arrives, their side deserves a hard look.

Mail providers score incoming messages. A sender using broken SPF, DKIM, or DMARC records can trigger spam treatment. A sender with a poor track record can get throttled or rejected. So can a domain that was just set up and has no history yet. From your seat, that looks like “nothing arrived.” On the server side, the message may have been blocked long before your inbox came into play.

That’s also why resending the same message ten times rarely helps. If the message keeps failing the same checks, ten copies just create ten failures.

Custom domain problems that block all incoming mail

If you use your own domain, DNS enters the story. This is where many “email not received” cases turn from simple to stubborn. Your domain needs MX records that point mail to the right host. If those records are missing, wrong, duplicated badly, or still pointing to an old provider, incoming mail will not land where you think it should.

A common trap shows up after a migration. You switch from one provider to another, update the web site, maybe even update the outgoing mail settings, but the MX records still point to the old service. Users can sign in, send mail, and assume all is well. Then incoming mail vanishes because the internet is still delivering to the last mailbox listed in DNS.

Propagation delays can add confusion. You fix the records, test too soon, and think the change failed. Give DNS changes enough time, then test again from an outside address.

Check the whole route, not one line

On a domain mailbox, receiving mail depends on more than the inbox itself. The chain includes the registrar or DNS host, the MX records, any inbound gateway, the provider mailbox, and any rules after delivery. A break in any link can stop mail. If you run email for a team, check whether the issue hits one user, one alias, or the whole domain. That split tells you whether to look at mailbox settings or domain routing.

A practical order that fixes most inbox failures

1. Search all folders and all mail for the sender and subject.
2. Check Spam, Trash, Archive, Promotions, and custom folders.
3. Review filters, forwarding, blocked senders, and aliases.
4. Check mailbox storage and account alerts.
5. Test on the web version of the mailbox.
6. If web works, fix the app: sign in again, refresh sync, or rebuild the profile.
7. If web fails too, ask the sender for any bounce message.
8. On a custom domain, verify MX records and any recent DNS changes.

That order works because it moves from easiest to hardest while splitting “delivered but hidden” from “never accepted.” Once you know which side of that line you’re on, the repair gets a lot simpler.

What to do when the problem keeps coming back

If mail breaks, comes back, then breaks again, look for changing conditions. Maybe storage fills up every few weeks. Maybe one device keeps failing authentication and locking the account. Maybe a rule gets recreated by a synced app. Maybe a security tool or gateway flags whole classes of messages at certain times.

Recurring faults need a log. Write down the date, sender, subject, device used, and whether the message showed on the web. That turns a fuzzy complaint into a pattern you can trace. Once you spot the pattern, you can fix the cause instead of tapping refresh and hoping for the best.

Missing email feels slippery because the inbox is the last stop in a longer chain. But the chain is still traceable. Check where the message should have landed, where it may have been moved, whether your app can still talk to the server, and whether your domain still points mail to the right place. In most cases, the answer is not hidden at all. It’s sitting in the first failed step.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback