Reading time: 8 min · Last verified: August 2026 · SMTPedia editorial team
An inbox that has gone quiet is not one problem. It is three problems that look identical from where you are sitting, and the fixes have nothing in common. Most checklists answer the question by listing ten things to click, in no particular order, hoping one of them is yours.
There is a faster way in. A missing message stops in exactly one of three places, and you can find out which in about a minute without touching a setting. This page answers why am i not receiving emails by locating the stop first and fixing it second, because half the fixes below are useless if the message never reached your provider.
Ask the sender whether they got a bounce. If they did, the message never reached your provider and nothing you change inside your mailbox will help. If they did not, the message was accepted, and it is either filed somewhere that is not your inbox or sitting on the server while your app fails to show it. That single answer eliminates two thirds of the checklist.
Start With One Question, Not Ten Settings
Mail passes three custodians: the sending server, your provider’s server, and the app on your screen. Any of them can stop it, and only the first stop produces a notification, which goes to the sender rather than to you. That asymmetry is the whole reason this problem is confusing. From your chair, a refused message and one quietly filed into Junk look identical: silence.
Never reached your provider
The sender receives a bounce carrying a numeric reply code. Evidence exists, but only on their side.
Accepted, then routed elsewhere
Junk, a filter, a block, or a forward. No bounce, no notice, and sometimes a deletion clock.
On the server, not on your screen
Sync, fetch schedule, or the wrong account in view. Webmail proves it in ten seconds.
Open your provider’s website in a browser and sign in there, not in your usual app. If the message is visible in webmail, you are in Layer 3 and the server is fine. If it is not and the sender got no bounce, you are in Layer 2. If they did get a bounce, you are in Layer 1, and the bounce names the cause.
Layer 1: The Message Never Reached Your Mail Server
When a receiving server refuses a message during the SMTP conversation, it answers with a numeric reply, and the sending system turns that reply into a bounce notice. Ask the sender to forward you that notice verbatim. The three digits and the text after them identify the cause precisely, and the full reference of SMTP reply codes maps each one to what the receiving side was objecting to. Whether the failure is permanent or temporary matters too, and the difference between a hard bounce and a soft one tells you whether retrying is pointless or simply slow.
A Full Account Refuses Mail Rather Than Holding It
This is the most common Layer 1 cause and the most widely misunderstood. People assume a full mailbox queues messages until space is freed. It does not. Google’s documentation on account storage is blunt: “You can’t send or receive emails,” and “Messages sent to you go back to the sender.” The mail is not waiting for you. It was handed back.
Why this trips people up: Google storage is shared across Drive, Gmail and Photos, so a photo library can fill the quota that stops your mail. Nothing in your inbox changes appearance when it happens. The only visible symptom is silence, and the only party who learns about it is whoever wrote to you. The reply they receive is the 452 4.2.2 out of storage response, or a permanent variant of it.
On Your Own Domain, DNS Decides Before Anything Else
If your address ends in a domain you control rather than a consumer provider, the diagnosis starts one step earlier. Google Workspace’s own troubleshooting sequence for administrators puts it first: step one is “Make sure MX records are set up correctly,” because, as the same document says, “Mail Exchange (MX records) direct your domain’s email to the servers that host your domain’s user accounts.” A domain with no valid MX record has nowhere to deliver to, and senders are told so immediately. Configuring and testing your domain’s MX records is the first thing to verify, before touching a single mailbox setting.
Administrators have one tool consumers do not: Google’s Email Log Search, which exists to “find specific messages sent to people in your organization in the past 30 days.” That turns a guessing game into a lookup. Either the message reached the domain or it did not.
Layer 2: It Arrived, and Something Filed It Somewhere Else
Once a server accepts a message it has taken responsibility for it and will not bounce it back. Everything after that is invisible to the sender and unannounced to you. This is where most missing mail actually is, and where “not receiving emails” becomes a filing problem rather than a delivery problem.
The Junk Folder Runs a Deletion Clock
Checking Junk is the advice everyone gives and nobody time-stamps. Microsoft states the rule plainly: “Junk email is retained for 30 days before it is automatically deleted and is not recoverable.” A message misfiled six weeks ago is gone. That deadline is why this check belongs early rather than last, and it is worth understanding what pushes a legitimate message into the spam folder so the same sender does not land there again next month.
A Rule You Wrote Once Can Delete Mail Outright
Filters are not limited to sorting. Google lists what a Gmail filter can do to an incoming message: “send email to a label, or archive, delete, star, or automatically forward your mail.” Two of those five remove the message from view without a trace in the inbox, and a rule written years ago against a forgotten keyword is still running today. Review the filter list before blaming the sender.
Blocking Is Stickier Than People Expect
If exactly one sender has gone silent while everything else arrives, a block is the likely cause, and blocks outlive the moment you created them. Google warns that “when you block a sender, even when you remove their emails from Spam, Gmail still automatically identifies their emails as spam.” Microsoft’s mechanism is equally durable: adding an address or domain to the blocked senders list will “move these messages directly to your Junk Email folder.”
The reverse trap: Microsoft notes that “when you mark a message as phishing, the sender is reported but is not blocked from sending you additional messages.” Reporting and blocking are separate actions, so people who believe they blocked someone often did not, and people who believe they merely reported someone often did block them. Read the blocked senders list rather than trusting your memory of it. If unwanted mail is the actual complaint, the practical ways to cut down incoming spam covers the recipient-side controls in order of effectiveness.
Forwarding Fails Quietly at the Far End
An address that forwards elsewhere adds a second delivery that can fail on its own while the first succeeded. The original account shows the message as handled; the destination never receives it, because it is full, rejected the forwarded copy, or the forward broke authentication in transit. How forwarding rewrites a message on its way through explains why forwarded mail is refused far more often than mail sent directly.
Layer 3: It Is on the Server and Your App Is Not Showing It
If webmail shows the message and your phone or desktop client does not, the mail system worked and the client did not. This is the answer to “why is my email not working” on one device while the same account behaves normally on another, and the only layer where reinstalling anything makes sense.
Apple’s guidance for iPhone and iPad starts outside the app: “Make sure that your device is connected to the internet,” then “Check with your email service provider to find out if there’s a service outage.” After that it points at the retrieval schedule, under Settings, Apps, Mail, Mail Accounts, Fetch New Data, where you “choose a setting like Automatically or Manually or choose a schedule.” An account set to Manually looks broken forever to someone who never pulls to refresh. If credentials and schedule both check out, Apple’s last resort is to remove the account and add it again.
The Order That Saves the Most Time
Run these in sequence rather than picking the one that sounds likeliest. Each step either ends the investigation or eliminates a layer.
| Step | Check | What it rules out |
|---|---|---|
| 1 | Did the sender get a bounce, and what does it say | Splits Layer 1 from Layers 2 and 3 |
| 2 | Sign in to webmail in a browser | Splits Layer 3 from Layer 2 |
| 3 | Storage usage on the account | The commonest silent refusal |
| 4 | Junk and Trash, dated within 30 days | Misfiling, before the deletion clock expires |
| 5 | Filters, rules, blocked senders, forwarding | Self-inflicted routing |
| 6 | Fetch schedule and sync on the device | Client-side display failures |
| 7 | MX and DNS, if you own the domain | Infrastructure, for custom domains only |
Reporting It, and Reading the Proof
People searching for how do i report mail delivery problems usually want an authority to escalate to, and for consumer mail there is not one: the provider’s support channel is the whole path, and it will ask for evidence. Useful evidence is the bounce notice, the exact timestamp, and the full headers of any message that did arrive somewhere unexpected. Reading the Received headers as a trace chain shows which servers handled the message and when, which turns “my email is not working” into a claim a support agent can act on.
One distinction worth keeping: none of the above explains why is my email not sending. Outbound failure is a separate diagnosis, since there you receive the bounce yourself.
Frequently Asked Questions
Why have I suddenly stopped receiving emails?
A sudden stop usually means a threshold was crossed rather than a setting changed. The most common is storage: once the account is full, Google states that “messages sent to you go back to the sender.” Check storage first, then whether a filter or forwarding rule was added around the same date.
Why am I suddenly not getting emails on my iPhone?
If the same account shows the mail in a browser, the account is fine and the device is not. Apple points first at the internet connection and a possible provider outage, then at Settings, Apps, Mail, Mail Accounts, Fetch New Data, where an account set to Manually will not retrieve anything until you refresh it yourself.
Why are my emails not showing up in my inbox?
Because something moved them. A Gmail filter can “send email to a label, or archive, delete, star, or automatically forward your mail,” and archived mail still sits in All Mail. Search across all folders rather than browsing the inbox, then review your filter list.
How do I start receiving emails again?
Fix the layer you identified, not all three. Free storage if the account is full, remove the filter or block if one is routing the sender away, or repair sync if webmail already shows the mail. Changing everything at once makes it impossible to know what worked.
Why have my emails stopped coming through on my phone but not my laptop?
That pattern is conclusive on its own: the server has the mail, so the problem is in the phone’s client. Check background refresh, the fetch schedule, and whether the account is still authenticated there. Nothing on the server needs changing.
Why can’t I receive email from one specific person?
If you can’t receive email from one address while the rest arrives, a block or filter is the cause, not a fault. Blocks persist: Google notes that a blocked sender’s mail is still identified as spam even after you pull it out of the spam folder, and Microsoft’s blocked senders list moves matching messages “directly to your Junk Email folder.”
Can messages be gone permanently rather than misplaced?
Yes, in two cases. Junk is on a timer: Microsoft states that “junk email is retained for 30 days before it is automatically deleted and is not recoverable.” And a filter with a delete action removes the message on arrival. Anything older than a month in either case is beyond recovery from your side; ask the sender to send it again.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
