Business Email Not Receiving Messages? Check These Four Things First

Suppose you run a bakery in Kumasi and an expected cake enquiry has not appeared in your business inbox. It is tempting to change the email settings immediately. First, find out where the message stopped. A phone that has stopped syncing, a full mailbox and a domain sending mail to the wrong provider need different fixes.

This guide is for a business address on your own domain, such as the sample orders@example.com used for that hypothetical bakery. You can follow the checks whether you read mail in webmail or an app on your phone. If your address uses Google Workspace, Microsoft 365 or another provider, use that provider's mailbox and DNS instructions; do not copy another service's mail records.

1. Check webmail before changing your phone

Open the webmail link provided for the mailbox in your hosting or email service. For a Nakroteck Plesk mailbox, our webmail guide explains how to open it from Mail in Plesk. If your client area shows an Email Manager, use the webmail link shown for your domain. Sign in with the full email address and mailbox password. Never send that password in a support ticket.

Look in Inbox, Spam or Junk, and any folders or rules that could move messages. Then send a short, harmless test from a different email account you control to the business address. Record the time and the sending address. Avoid using a real order or customer details as the test.

If the test appears in webmail but not on your phone, the mailbox received it. Check that the phone is online and that the mail app is showing the right account and folders. Refresh the app and compare its incoming settings with the settings shown for your own service. Our mail-app setup guide covers Plesk accounts; settings can differ for other services. Do not remove the account from your phone until you know how it is configured, especially if it uses POP rather than IMAP.

If the test is absent from webmail too, continue with the next checks. That result narrows the problem, but it does not yet prove that DNS is wrong.

2. Confirm that the address can receive mail

Check that the domain and email service are active, the mailbox exists, and the address was typed correctly. A small spelling difference in a local part such as orders versus order is enough to send a message elsewhere or cause a rejection. In your service's mailbox controls, check storage usage if it is available. A mailbox over its limit can reject new mail; Plesk documents this behaviour for its mail accounts. If the usage display is unavailable or you are unsure what it means, keep the observation for support instead of deleting business messages to make room blindly.

Ask the sender of a missing message whether they received a delivery failure notice. A bounce can contain a useful reason, such as an unknown address or a full mailbox. If only one sender is affected while your own test arrives, give support the sender's domain, approximate sending time and a redacted copy of the failure text. Do not forward private message contents just to diagnose delivery.

3. Check where the domain directs incoming mail

An MX record tells other mail systems where to deliver messages for your domain. If you recently changed nameservers, moved email providers or connected an existing domain to a new service, compare the published MX records with the records assigned to your current email provider. The right values come from your service, not from a generic blog example. Google's MX explanation describes how incoming mail follows these records; its Google-specific values are not instructions for a Nakroteck mailbox.

Nameservers determine which DNS zone is authoritative. Changing them without copying the needed email records can interrupt delivery even while your website appears fine. Our nameserver guide explains what to review, and the DNS propagation guide explains why a recent correction may not appear everywhere at once.

Do not replace MX records as a first guess. If your domain already receives mail at another provider, changing them can redirect new messages before the new mailbox is ready; existing messages do not move automatically. Nakroteck's business email guide recommends planning that switch with support. Write down the current records and ask for help if you cannot tell which service should receive mail.

4. Give support the clues that identify the fault

If messages are still missing, open a ticket from your Nakroteck account for the affected service. Include the domain, the affected mailbox address, when the problem began, whether your controlled test appears in webmail, whether other senders work, and whether the sender received a bounce. Mention any recent nameserver or MX change and paste the relevant error text with personal information removed. You can also say if webmail itself will not open.

That short history helps separate phone syncing, mailbox storage and delivery routing. Keep your password, full customer messages and account recovery codes out of the ticket. Once the cause is fixed, repeat the same harmless test and confirm it appears in both webmail and your usual mail app.