When a business email account stops receiving messages, the problem may be much wider than Outlook, Gmail or the computer being used to check the inbox. Customer enquiries, quote requests, bookings and staff messages can all disappear because the domain is sending incoming mail to the wrong place.
Business email depends on several systems working together. The mailbox may be hosted by Microsoft 365, Google Workspace or another provider, while the domain and DNS are managed somewhere else and the website sits on a completely different server. A change to any one of these can interrupt incoming email even when the website and internet connection appear normal.
If the problem is outgoing mail instead, see PcRiotβs guide to business email not sending.
Business email can fail outside the mailbox
With a personal Gmail or Outlook.com address, most of the infrastructure is controlled by one provider. A business address such as accounts@example.com.au can be more complicated.
A typical business setup may involve:
- π Domain registration: the business must still control an active domain name.
- π§ DNS hosting: the authoritative nameservers must publish the correct records for the domain.
- π¬ MX records: these tell other mail systems which servers should receive email for the domain.
- βοΈ Email hosting: the actual mailbox may be on Microsoft 365, Google Workspace, shared hosting or another mail platform.
- π₯οΈ Website hosting: website contact forms may send mail from a completely separate server.
- π€ Mailboxes and aliases: addresses such as sales@, accounts@ or enquiries@ must still point to a valid destination.
This is why replacing Outlook, resetting a phone or repeatedly entering an email password may achieve nothing. If the incoming route is broken before the message reaches the mailbox, the email application never has an opportunity to receive it.
Wrong MX records can send email to the wrong server
MX records are one of the first things to check when an entire business domain is not receiving email.
An MX record does not store email itself. It tells sending mail servers where email for the domain should be delivered. If the records are missing, outdated or pointing to an old provider, messages may bounce or be delivered somewhere the business no longer checks.
This is one reason a business can send emails but not receive.
Common MX problems include:
- β‘οΈ MX records still pointing to an old web hosting company after email was moved elsewhere.
- β Required MX records being removed during a DNS or hosting change.
- π’ Incorrect MX priorities or incomplete records creating inconsistent mail routing.
- π¦ A new Microsoft 365 or Google Workspace service being configured without completing the domain’s incoming mail records.
- ποΈ Mail continuing to arrive at an old server even though staff have started using a new mailbox.
A useful clue is whether everyone at the domain is affected or only one address. If no business address can receive external email, the domain-level routing deserves particular attention.
Nameserver changes can silently replace working email records
Changing nameservers can affect much more than the website.
When a domain is moved to different DNS hosting, the new DNS zone must contain the records required for the existing email service. If only the website records are recreated, the website may come back online while business email remains broken.
This commonly happens after:
- π Moving a website to a new hosting company.
- π οΈ Changing DNS providers or nameservers.
- π Replacing an old web developer or hosting service.
- βοΈ Moving email to Microsoft 365 or Google Workspace.
- π Creating a new DNS zone without copying all of the previous mail records.
The fact that a website loads correctly does not prove that its email DNS is correct. Web traffic and email traffic use different DNS records.
Domain expiry can interrupt business email
An expired domain can also cause email problems because the domain’s normal DNS records may stop resolving correctly or the registrar may substitute its own expiry configuration.
This can be particularly confusing when nobody in the business normally manages the domain. Renewal notices may be going to a former employee, web developer or old email address, while staff continue using the business domain without realising its registration is approaching expiry.
If both the website and email fail at approximately the same time, checking the domain registration and DNS status is worthwhile before changing individual computers.
Old hosting can still be handling the mail
Businesses frequently move their website and email at different times. This can leave several servers believing they are responsible for the same domain.
For example, a business may now read email through Microsoft 365 while its old shared hosting account still contains mailboxes for the domain. If the MX records still point to that hosting account, customer messages can continue accumulating in the old mailbox instead of appearing in Outlook.
There can also be a more subtle problem when the public MX records are correct but the website server itself is configured to treat the domain as local mail.
On hosting platforms that distinguish between a local and remote mail exchanger, an incorrect local setting can cause messages generated by the website to be delivered into a mailbox on the web server rather than sent to the business’s real external email provider.
This can produce a very specific symptom:
- β Normal external email from customers reaches Microsoft 365 or Google Workspace.
- β The website says a contact form was submitted successfully.
- β The contact form notification never appears in the business inbox.
In that situation, the problem may be the website server’s mail routing rather than the recipient’s Outlook or Gmail settings.
Microsoft 365 or Google Workspace may not be fully configured
Moving business email to Microsoft 365 or Google Workspace involves more than creating a username and password.
The domain must be connected to the service correctly, the required incoming mail records must be published, and each address must have a valid mailbox, alias, group or other destination.
Problems can occur when:
- π€ A staff mailbox has been deleted, disabled or renamed.
- π·οΈ An old alias such as sales@ or enquiries@ was not recreated during migration.
- π₯ A shared mailbox, group or distribution address no longer contains the correct recipients.
- π¬ The domain’s MX records still point to the previous email provider.
- π Part of the business has moved to the new service while another part still depends on the old server.
Testing only one person’s mailbox can therefore give a misleading result. The individual mailbox, shared addresses and domain-level routing may need to be checked separately.
Missing aliases can make only one business address fail
If most email is arriving but messages to one particular business address are missing, the DNS may be completely healthy.
If the problem is mail from one outside person or company rather than one business address, see PcRiotβs guide to not receiving emails from one sender.
The problem may instead be the address itself.
Businesses often use addresses such as:
- πΌ sales@
- π§Ύ accounts@
- π reception@
- π© enquiries@
- π οΈ support@
These may be separate mailboxes, aliases, shared mailboxes, forwarding addresses or distribution groups. If one is removed or pointed at the wrong person, the rest of the business can continue receiving email normally while enquiries sent to that particular address disappear or bounce.
Website contact forms are a separate email system
A website contact form can fail even when ordinary email is working perfectly.
When a customer presses Submit, the website has to generate and deliver a notification to the business. That process may rely on the web server’s local mail system or an authenticated SMTP connection to an external provider.
Contact form notifications may disappear because:
- π― The form is still sending notifications to an old or incorrect email address.
- π Saved SMTP credentials are no longer accepted.
- ποΈ The web server is treating the business domain as local and placing the message into an unused hosting mailbox.
- π« The receiving provider is filtering or rejecting the website-generated message.
- βοΈ The form or mail configuration was changed during a website update or migration.
- π¨ The website reports that the form was submitted even though the notification email was never successfully delivered.
This distinction matters for a business relying on website leads. Seeing a successful confirmation on the website does not necessarily prove that the enquiry reached the inbox.
Test where the email is actually failing
The quickest way to diagnose business email is usually to identify the point where a known test message stops.
Useful checks include:
- 1οΈβ£ Test the mailbox directly. Send an external message to the affected business address and check webmail or the provider’s own interface.
- 2οΈβ£ Compare multiple addresses. Determine whether the whole domain is affected or only one mailbox, alias or shared address.
- 3οΈβ£ Check the current MX records. Confirm that public DNS points to the email provider the business actually uses.
- 4οΈβ£ Confirm the nameservers. Establish which provider currently controls the authoritative DNS zone.
- 5οΈβ£ Check old hosting. Look for mailboxes or routing settings that may still be accepting messages.
- 6οΈβ£ Test the website separately. Submit a known contact form enquiry and trace where its notification is supposed to go.
- 7οΈβ£ Check the actual mailbox configuration. Confirm aliases, shared mailboxes, groups and forwarding destinations.
This approach separates an email application problem from a mailbox problem and a mailbox problem from a domain or website-routing problem.
PcRiot can trace the complete business email path
Business email problems are often difficult to fix by looking at only the computer showing the empty inbox. The fault may be in the mailbox, domain, DNS records, hosting account, Microsoft 365 or Google Workspace configuration, or the website generating customer enquiries.
If your business email is not receiving, PcRiot can check the mailbox, domain, DNS records, hosting, Microsoft 365, Google Workspace, website form and email routing. For broader incoming mail problems, see PcRiot’s email receiving troubleshooting in Perth.
PcRiot provides business email troubleshooting for small businesses across Perth, including problems involving domain email, website enquiries and mail migrations.
If the issue appears limited to one mail app or provider, see the separate guides for Outlook not receiving emails and Gmail not receiving emails.
Get your business email receiving again
If customer emails, quotes, bookings or website enquiries are going missing, the important step is finding where the message is being diverted or rejected rather than repeatedly changing settings on individual computers.