Business email not arriving: Why do incoming messages fail to reach domain-based email?

Where does email go if the MX record is wrong or missing?

If MX is wrong, incoming email goes to an old or unrelated server; if MX is absent, sending servers try the domain’s own address record, usually the website’s server. An MX (Mail Exchanger) record is the DNS record specifying which mail server receives email for a domain. RFC 5321 calls the behavior used when MX is missing “implicit MX”; for a business with its website and email hosted separately, mail is directed to a server that does not accept it.

The most common situation after migration

In practice, a substantial share of incoming email problems starts immediately after changing hosting, domain, or email provider. When nameservers are switched to a new company, email appears lost if the old DNS zone’s MX was not copied to the new zone, a default MX was created there, or MX points to the new server while email should remain in its old location.

At Onur Freelance, in WordPress website migration work, we compile the full DNS record list before migration; we do not change nameservers until MX and other email records have been transferred to the new DNS zone. Old mailboxes should also remain open until DNS propagation is complete.

How does MX priority work?

A domain can have multiple MX records, each with a preference value; according to RFC 5321, lower numbers are preferred. The sending server tries the lowest-value record first, moves to the next if it cannot reach it, and distributes load randomly among records with equal values. If an old provider’s MX is forgotten, some email can go to the old server; removing the old record is as important as adding the new one when configuring MX.

Ask the following questions when checking MX:

• Does the record point to the service where email is actually hosted?
• Is an old provider’s MX still present, and are priorities correct?
• Is the MX target a server name? Do not enter an IP address here.
• Are edits being made in the panel that actually manages the domain’s DNS?

How long should you wait after a DNS change?

After correcting MX, the new value may take from a few minutes to a few days to appear everywhere; Google states that recognizing new MX records for Workspace can take up to 72 hours. The record’s TTL (time to live) largely determines this: DNS servers cache a record for its TTL period and see the change when it expires.

Incoming emails generally are not lost during the wait. RFC 5321 calls for a sending server receiving a temporary error to retry generally at intervals of at least 30 minutes and wait at least 4–5 days before giving up; a message receiving a temporary error can therefore arrive after a delay. The real risk is some messages still being delivered to the old server during propagation; closing the old mailbox too early can lose them. Lowering TTL several days beforehand shortens a planned transition.

If the mailbox is full, service suspended, or domain expired

When mailbox quota is full, hosting email service is suspended, or the domain expires, incoming external messages are rejected or never arrive; all three situations stop incoming email even if DNS settings are correct.

Mailbox full warning

RFC 3463 defines x.2.2 as “mailbox full”: the allocated quota or physical capacity has been exceeded, and the recipient can free space by deleting old messages. The standard classifies this as a persistent transient failure; if the sender’s retry period expires, the message still bounces back. Quotas commonly fill for these reasons:

• Messages deleted on IMAP-connected devices accumulating in the server’s trash folder
• Large attachments remaining in sent items for years
• One mailbox consuming the total shared quota in a plan

Hosting email service suspended

Service can be suspended when the hosting bill is unpaid, the plan expires, or abuse is detected in the account, and the mail server stops accepting new messages. Warning emails often having been sent to the same business address causes late discovery of the problem.

If the domain has expired

When a domain expires, DNS records may stop working and MX becomes inactive with them; sending servers cannot find the domain’s mail server. Post-expiration stages and renewal are explained in detail in the what happens when a domain expires article.

Could blocking or a blacklist on the sending side be involved?

If emails fail to arrive only from a particular company or person, the issue usually concerns a blocklist, spam filter, or the sending server’s reputation. The receiving mail server may reject a message when the sender’s IP appears on a DNS-based blocklist (blacklist) or the sending domain’s authentication fails. Such rejections usually return a policy code such as 5.7.1 to the sender.

There are three places to check when email from specific senders does not arrive:

1. Blocked senders in webmail: An address blocked by a user years ago can cause that sender’s messages to be deleted unnoticed.
2. Server-side spam filter: Spam settings in the hosting panel can reject high-scoring messages or put them in a separate folder.
3. The sender’s own server: If the sending IP is blacklisted, messages may fail to reach many recipients, not just this address; the solution belongs on the sending side.

The complete bounce shows which server issued the rejection; if it comes from the sender’s own server, investigate on the sender’s side.

If email reaches the server but is missing from the inbox

If a message reaches the server but is absent from the inbox, the cause is usually forwarding, a filter rule, or an email application setting. Search for the message in webmail first; a message visible there but missing from a phone or desktop application is a client problem rather than a server problem.

• Filters and rules: Gmail filters or Outlook rules can move certain senders to archive, another folder, or trash.
• Split inbox: Outlook’s Focused/Other distinction or Gmail tabs can display the message in an unexpected tab.
• Forwarding: If the business address forwards elsewhere and keeping a server copy is disabled, messages arrive only at the destination.
• An old device using POP: If a POP device downloads messages and deletes them from the server, other devices never see them.

A forwarded message may also land in spam under the destination provider’s rules. Adding the business account directly through IMAP on phone and computer makes messages appear consistently on every device.

Where should MX point for Google Workspace and Microsoft 365?

If business email uses Google Workspace or Microsoft 365, MX should point directly to that service’s mail server rather than the hosting server. If MX remains at the hosting default, incoming messages go to an unused mailbox.

Google Workspace

According to Google’s set up MX records for Google Workspace page, the current MX value is smtp.google.com with priority 1; accounts created before 2023 may show older values starting with “aspmx”, which need not be changed if email works. The same page asks that other MX records be removed and states that old or incorrect records can prevent email working properly. After adding the record, Gmail must also be activated in the Google Admin console.

Microsoft 365

According to Microsoft’s external DNS records for Microsoft 365 documentation , the Exchange Online MX points to an address beginning with a tenant-specific token and ending in mail.protection.outlook.com ; its priority is kept at a lower number than other MX records, for example 1. The documentation states that multiple MX records can cause delivery problems and a single record eliminates many potential issues; it recommends removing MX records pointing to the old system after email starts flowing to Exchange Online.

For both services, copy correct values from the domain setup screen in the admin panel. How to create a domain-based business address and which option suits which business are compared in the how to get business email article.

How do you test incoming email problems?

Test incoming email step by step by querying the domain’s MX, sending a message from another provider, and reading any bounce. These tests do not require advanced technical knowledge.

1. MX query: View the domain’s MX through an online DNS lookup tool. For example, Google’s Admin Toolbox Check MX checks a domain’s MX and SPF records; the tool focuses on Google Workspace. In the Windows command prompt, nslookup -type=mx firma.com provides the same information.
2. External test message: Send a short message to the business address from a personal Gmail or Outlook.com account; if it does not arrive, check the test account’s inbox for a non-delivery report.
3. Webmail check: Search in the web interface first; if the message is there, the problem is client-side.
4. Test a second mailbox: Send a message to another address on the same domain too; if only one mailbox is affected, the problem is with that mailbox rather than the domain.

The named tools are examples only; what matters is that the queried MX value matches the service where email is actually hosted.

Business email not arriving checklist

Perform checks in order from the most likely cause to the least likely; the list can also be reused during migration and renewal periods:

1. If a bounce exists, request it from the sender and read the error code.
2. Query the domain’s MX and compare it with the service hosting email.
3. Remove any MX left over from the old provider and check priorities.
4. Note the date of the latest DNS or nameserver change and account for propagation.
5. Check mailbox quota and hosting account status in the panel.
6. Check the domain’s expiration date.
7. Review filters, rules, forwarding, and blocked addresses in webmail.
8. Send a test message from a different provider and record the result.

Common mistakes

The most common mistake is addressing the symptom while leaving the cause. The mistakes encountered most often in practice are:

• Changing nameservers without copying MX to the new DNS zone
• Leaving the old provider’s MX alongside the new one
• Editing DNS in a panel that does not actually manage the domain
• Closing mailboxes on the old server immediately after migration
• Trying to solve incoming email problems with outgoing settings, meaning only SPF and DKIM records

When should you consult a specialist for incoming email problems?

Specialist support saves time if business email is not arriving and DNS panel access is unavailable, if MX appears correct but email still fails, or if the problem began after migration. Where website, email, and form notifications use different services, editing one record incorrectly can affect the other services too.

In Onur Freelance’s hosting proposal, the number of business email addresses to be created is asked upfront; the plan’s email scope and renewal terms are stated in the written quote. The package on the hosting prices page costs 2,000 TL per year and a domain costs 1,000 TL per year; if an existing setup needs correction or migration, the scope is clarified in the initial consultation. Onur Freelance does not promise email will arrive under every circumstance; the aim is to make the incoming email route verifiable and traceable.