How to Troubleshoot Email Delivery Problems
Email problems can quickly become business problems. A customer may not receive a quotation, a supplier may miss an important update, or a password-reset message may never arrive. When email is not being delivered, the cause may be anything from a full mailbox to an incorrect DNS record or a message being filtered as spam.
The most effective approach is to avoid changing several settings at once. Start by identifying exactly what failed, then test the likely cause in a logical order. This guide is designed for small businesses, entrepreneurs and organisations using business email with their own domain.
First, identify the type of delivery problem
“My email is not working” can describe several different situations. The solution depends on which one you are experiencing.
- Sending fails immediately: Your email program may show an error, or the message may remain in the outbox.
- The message bounces: You receive an automated delivery failure notice.
- The message appears sent but never arrives: It may be delayed, rejected later or placed in the recipient’s spam folder.
- You receive email but cannot send: The outgoing mail settings or authentication may be incorrect.
- You can send email but cannot receive it: The domain’s receiving records, mailbox configuration or storage limit may be involved.
- Only one recipient has a problem: The issue may be specific to that recipient’s mailbox or email provider.
Record the sender address, recipient address, approximate time, subject and exact error message. These details are often more useful than a general description of the problem.
Read the bounce message carefully
A bounce message is not just an annoyance; it usually provides a diagnostic clue. Look for phrases such as “mailbox full”, “user unknown”, “message rejected”, “authentication required”, “connection timed out” or “message too large”.
Some bounce messages are temporary. A busy receiving server, a short network interruption or a temporary reputation check may cause delivery to be retried automatically. Others are permanent, such as sending to an address that does not exist.
Do not repeatedly resend the same message without understanding the error. Repeated attempts can create confusion and may make filtering more likely. If the notice contains a technical code, keep it available when contacting your hosting or email support provider.
Check the simple causes before changing technical settings
Many delivery issues have a straightforward explanation. Work through these checks first:
- Confirm that the recipient’s address is spelled correctly.
- Send a short test message without attachments or links.
- Check whether your mailbox is full or has reached its storage limit.
- Review the Sent, Drafts and Outbox folders for messages stuck in a queue.
- Sign in to webmail, if available, to determine whether the problem is limited to your phone or email application.
- Check the recipient’s spam, junk or promotions folders.
- Ask the recipient to add your address to their contacts or approved senders.
- Try sending to a second recipient to see whether the issue affects one address or many.
This test separates an account or domain problem from a device-specific problem. If webmail works but your phone does not, review the phone’s account settings rather than changing your domain records.
Review your outgoing mail settings
Email applications use separate settings for receiving and sending messages. A device can sometimes download incoming mail correctly while failing to connect to the outgoing mail server.
Check that the outgoing server name, connection security and port match the settings supplied by your email hosting provider. The option requiring authentication for outgoing mail should normally be enabled, using the full email address and its password where required.
Avoid copying settings from an unrelated account. The correct configuration for a personal email provider may not be correct for a domain-based business mailbox. If you recently changed your password, update it on every phone, computer or application connected to the account.
If an account has been configured on several devices, temporarily test one device at a time. This can reveal an old device repeatedly attempting to connect with an outdated password.
Check the domain’s DNS records
When a business uses an address such as [email protected], the domain’s DNS records help other mail servers find where messages should be delivered. Incorrect or missing records can prevent incoming email from reaching the right service.
The most important record for receiving mail is the MX record. It identifies the mail server responsible for the domain. If the domain was recently moved, the MX record may still point to an old provider, or it may have been accidentally removed.
Other records help receiving providers verify that messages sent from your domain are legitimate:
- SPF: Identifies the servers allowed to send email for your domain.
- DKIM: Adds a digital signature that helps verify messages have not been altered and came from an authorised system.
- DMARC: Tells receiving providers how to handle messages that fail authentication checks and provides reporting options.
These records must be entered accurately and should not be duplicated without a clear reason. For example, publishing multiple separate SPF records can cause validation problems. DNS changes may also take time to appear across different networks, so avoid repeatedly replacing records while they are propagating.
If you are unsure which records your email service requires, ask your hosting provider to review the domain configuration. This is safer than guessing, particularly when the same domain is used for the website and email.
Investigate spam and reputation issues
A message that leaves your mailbox successfully can still be filtered by the recipient’s provider. Spam filtering may consider the sending domain, server reputation, message content, links, attachments and authentication results.
Start with a controlled test: send a plain-text message with a descriptive subject, a normal signature and no attachment or shortened link. If that arrives but a marketing-style message does not, compare the content and sending method.
Also review whether your account may have been compromised. Unexpected sent messages, unfamiliar login alerts or a sudden increase in bounced messages can indicate that someone else has accessed the mailbox. Change the password to a strong, unique one and contact your email provider for help reviewing the account. Enable additional sign-in protection when it is available.
Do not respond to requests for passwords or payment details merely because they appear to come from an email provider. Use the provider’s known website or support channel instead.
Reduce problems caused by attachments and message size
Large attachments are a common reason for delayed or rejected messages. The sender’s mailbox may allow a file that the recipient’s provider does not. Multiple images, videos and scanned documents can also make a message unexpectedly large.
For important documents, consider sending a secure sharing link through a service you trust, with appropriate access controls. If an attachment is necessary, compress files where practical and send several smaller messages only when that will not create confusion. Never assume that a message was delivered simply because it left the Outbox.
Use a repeatable troubleshooting workflow
A simple workflow helps a small business resolve problems without losing time:
- Capture the exact error or bounce message.
- Confirm the addresses and test with a short message.
- Check webmail, mailbox storage and the Outbox.
- Test another recipient and another device.
- Review outgoing server settings and password status.
- Ask the email host to verify MX, SPF, DKIM and DMARC records.
- Check for spam filtering, account compromise or unusual sending activity.
- Retest and document the final change.
For example, if a Nigerian business can send mail to one customer but not another, the domain may be working correctly. The next step is to examine the bounce notice and ask the recipient to check filtering. If nobody can receive messages sent to the business domain after a website or hosting change, the MX records deserve attention.
When to ask for technical support
Contact your hosting or email provider when the error is unclear, several users are affected, DNS records need changing, messages are being rejected consistently, or you suspect an account has been compromised. Provide the domain, affected addresses, error text, time of the failed attempt and the troubleshooting steps already completed.
Business email should be managed as part of the organisation’s wider online presence. Keep domain ownership and renewal access under the business’s control, maintain accurate account details, use strong passwords and ensure more than one responsible person knows how to reach the provider.
The fastest solution is usually not a random setting change. It is a clear diagnosis: determine whether the failure is caused by the recipient, the mailbox, the device, the email application, the domain’s DNS records or message filtering. Once that distinction is clear, the right fix becomes much easier to apply and verify.
