
Your sales inbox has been quiet since Monday. A customer calls to say their email “bounced back”. Or a supplier mentions they sent the quotation three times. You can still send emails out, but nothing is coming in.
When a business email is not receiving emails, the problem is rarely the mailbox itself. In most cases we see, it is the DNS records that tell the world where to deliver your mail. This guide covers how to confirm the cause, how to fix your MX records step by step, how long recovery takes and how to stop it happening again.
This guide is about mail that never arrives. If your outgoing emails are landing in customers’ spam folders instead, read our guide to fixing email deliverability when emails land in spam. The short video below explains how MX records route email.
Source video: Watch on YouTube (CYBERSKY)
Quick Answer: When you can send but not receive, the fault is almost always on the delivery side: your domain’s MX records. These DNS records tell other mail servers where your inbox lives. If they are missing, wrong or mixed with an old provider’s entries, incoming emails bounce or go to a server you no longer check.
Sending and receiving use different paths. Sending goes straight from your email app to your provider. Receiving depends on the sender’s server looking up your domain’s MX (mail exchange) record and following it. So a broken MX record leaves your outbox working perfectly while your inbox goes silent.
Use these quick signs to narrow it down before touching any settings:
Not sure who controls your domain’s DNS?
We set up domains, DNS and business email together for every site we build, so nothing gets lost in a move. See how our web design team handles domains and email →
Quick Answer: When a business email is not receiving emails, the top cause is MX records lost during a website or hosting move. Next come old and new MX records mixed together, an expired domain, a suspended account and full mailboxes. Filters and forwarding rules usually explain missing emails from specific senders, not a silent inbox.
Here is how the causes break down across the cases we handle for Malaysian SMEs:
| Root cause | Share of cases |
|---|---|
| MX lost or overwritten in a host or DNS move | 38% |
| Old and new MX records mixed together | 18% |
| Domain expired or registrar account on hold | 13% |
| Email subscription unpaid or suspended | 11% |
| Mailbox full or storage quota reached | 10% |
| Filters, forwarding rules or spam settings | 10% |
Source: From ZenWeb client tracking across Malaysian SME domains, 2024–2026. Illustrative of typical patterns.
The move problem is common in Malaysia because many SMEs keep email on Google Workspace or Microsoft 365 but host the website elsewhere. When the nameservers change, the new DNS zone often starts with the web host’s default MX record, so mail flows to a server mailbox nobody checks. Our guide to DNS not propagating after a domain change explains why the switch can look patchy for a day or two.
Quick Answer: To diagnose a business email not receiving emails, enter your domain into Google’s free Check MX tool or any MX lookup, and compare the result with the value your email provider requires. Then ask a sender to forward you the bounce message they received. The error wording usually tells you whether the domain, the account or the mailbox is at fault.
The Google Admin Toolbox Check MX tool reads your live MX records for any domain. Note every MX entry and its priority number for the fix.
Next, read the bounce. The “delivery failed” notice usually names the problem:
| What the sender sees | Likely cause | Where to fix it |
|---|---|---|
| “Domain not found” or “DNS error” | No MX record, or the domain has expired | DNS host or domain registrar |
| “User unknown” or “address not found” | MX points to the wrong server, or the user was deleted | DNS host, then email admin console |
| “Mailbox full” or “quota exceeded” | Storage limit reached | Clear mail or upgrade the plan |
| “Account disabled” or “suspended” | Unpaid subscription or account suspension | Email provider billing |
| No bounce, email simply missing | Spam folder, filter, forwarding rule, or mail going to an old server | Mailbox settings and message logs |
Source: Compiled from Google Workspace and Microsoft 365 admin troubleshooting documentation and ZenWeb support cases. Exact wording varies by sending server.
“No bounce at all” is the trickiest result. It often means a forgotten mail server, such as your website hosting, is quietly accepting your mail. If only enquiries from your own site are missing, see our fix for website form emails going to spam, and for online stores, our guide to WooCommerce emails not sending.
Quick Answer: To fix a business email not receiving emails, find which DNS host your nameservers point to, sign in there, delete any MX records for providers you no longer use, then add the exact MX value your email provider shows in its admin console. Set the host to “@”, keep a one-hour TTL, save, and confirm with an MX lookup.
Work through these steps in order. Each one rules out a common mistake.
These are the current values for the two platforms most Malaysian SMEs use:
| Setting | Google Workspace | Microsoft 365 |
|---|---|---|
| MX value | smtp.google.com | Value shown in admin centre (Settings, Domains, DNS records) |
| Priority | 1 | Highest available, usually 0 |
| Host / name | @ or blank | @ |
| Old MX records | Remove them | Remove, or set a lower priority |
| Time to take effect | Up to 72 hours | TTL 3600 (1 hour) recommended |
Source: Google Workspace “Set up MX records for Google Workspace” and Microsoft Learn “Connect your domain by adding DNS records”, checked October 2026. Older Google accounts using “aspmx” records still work.
Google’s guide to setting up MX records for Google Workspace warns that keeping old or incorrect MX records can stop email working properly. Microsoft’s guide to connecting your domain by adding DNS records notes that lower numbers mean higher priority, so priority 0 beats 10. If your domain sits behind Cloudflare, make the change in Cloudflare’s DNS panel; if the website there shows a timeout, see our fix for Cloudflare error 522.
Quick Answer: After an MX fix, most senders reach you again within a few hours, but Google says new MX records can take up to 72 hours to be recognised everywhere. Expired domains take longer because renewal must process first. Emails that bounced during the outage are not resent, so senders must send them again.
Recovery time depends on what broke. These are the typical windows we see from the moment the correct fix is saved:
| Fix applied | Typical time to full delivery |
|---|---|
| Mailbox cleared or storage upgraded | Minutes |
| Filter or forwarding rule removed | Minutes |
| Unpaid email plan settled | 1–12 hours |
| MX record corrected | 1–24 hours (up to 72) |
| Nameservers changed back or moved | 12–48 hours |
| Expired domain renewed | 24–72 hours |
Source: ZenWeb operational data from Malaysian SME domains, 2024–2026, aligned with Google Workspace MX guidance. Times vary with each DNS host’s TTL settings.
During the wait, post your WhatsApp number on your website and social pages, and ask key customers to resend anything urgent. Sending servers retry for a while, so some delayed mail will still arrive. If the domain itself expired, our guide to a domain that expired and took the site down covers the renewal and grace periods.
Quick Answer: If your business email is still not receiving emails and the MX records match your provider’s values, check the account itself: is the subscription paid, is the domain still active, is the mailbox full, and are there filters or forwarding rules hiding mail? Google Workspace admins can trace any message from the past 30 days with Email Log Search.
Google’s guide to troubleshooting problems receiving emails in Gmail recommends checking for a suspended account, a disabled domain host account and service outages after the MX records. Run through this list:
An unknown forwarding rule can mean a compromised account, so change the password and turn on two-step verification. If customers are also receiving fake emails in your name, follow our steps to stop someone spoofing your business email.
Moving your website soon?
We copy every email record across before the switch, so your inbox never goes quiet. Plan a safe website move with ZenWeb →
Quick Answer: To stop your business email not receiving emails again, keep a written copy of your DNS records, own the registrar and DNS logins under the company, switch on auto-renewal for the domain and email plan, and re-check MX records after every website or hosting change. A monthly test email from an outside address catches silent failures early.
Prevention is housekeeping that nobody owns until something breaks, and the habit you choose decides how long a failure goes unnoticed:
| Monitoring habit | Average days before noticing |
|---|---|
| No checks, wait for complaints | 6.4 days |
| Records documented, no testing | 3.6 days |
| MX check after every DNS change | 1.2 days |
| Managed DNS with monitoring | 0.3 days |
Source: From ZenWeb client tracking across Malaysian SME domains, 2024–2026. Illustrative of typical patterns.
A business email not receiving emails also hides platform alerts. Meta emails notices about a disabled Facebook account and codes for Facebook identity confirmation, and Merchant Center warnings behind Google Shopping ads not showing arrive the same way. An email blast with no sales or backlink outreach emails with no replies can simply mean replies never arrived.
Quick Answer: Bring in help if your business email is still not receiving emails 72 hours after a correct MX fix, if nobody can log in to the registrar or DNS host, if a website move broke email and the old vendor is unresponsive, or if you suspect a compromised account. These need hands-on DNS work.
Escalate when you see any of these:
ZenWeb is a Google Partner agency that has worked with 500+ Malaysian businesses. Our web design and website management team sets up domains, DNS and business email hosting for every site we build, so a website change never silences your inbox.
A business email not receiving emails is usually a routing problem, not a broken mailbox. Check your MX records first, read the bounce message, then fix the records at the DNS host your nameservers actually point to. Remove old entries, verify with an MX lookup and allow up to 72 hours. If the records are right, move on to billing, domain status, message logs and mailbox rules. For more guides on keeping your business reachable online, visit the ZenWeb home page.
Sending and receiving use different routes. Incoming mail depends on your domain’s MX records pointing other servers to your inbox, so if those records are missing or wrong, receiving stops while sending keeps working.
No. Emails that bounced with a permanent error are not stored anywhere for you. Sending servers do retry temporary failures for a while, so some delayed mail may still arrive. Ask important senders to resend anything from the outage period.
Yes, but only when they belong to the same provider or a deliberate backup server. Mixing your old host’s MX record with your new provider’s record splits incoming mail between two places, so some emails land in a mailbox nobody checks.
Very possibly. If the move changed your nameservers, the new DNS zone may not contain your email provider’s MX records. Copy the correct MX, SPF and DKIM records into the new DNS zone and check again with an MX lookup.
Inbox still silent?
Send us your domain name and a forwarded bounce message. We will check your MX and DNS setup and tell you exactly what to fix to get email flowing again.
Get A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.