If your business email suddenly stops working, the cause is often simple: a mailbox quota is full, a DNS record changed, the password was updated, a mail client is misconfigured, or the server is blocking messages because of spam, authentication, or routing issues. In a hosting environment, especially when using a control panel such as Plesk, email delivery can be affected by both server-side settings and local device configuration.
This guide explains what to check when business email is not working, how to identify whether the problem is with sending, receiving, or syncing, and which hosting and control panel settings commonly cause email failures. It is designed for users who manage email through a hosting platform, business email hosting, or a managed server setup.
Identify the type of email problem
Before changing settings, determine exactly what is failing. Business email problems usually fall into one of these categories:
- You cannot send email from your mailbox.
- You cannot receive email from external senders.
- Email is delayed or not appearing in your inbox.
- Email works in webmail but not in Outlook, Apple Mail, or a phone.
- Messages are landing in spam or being rejected by recipients.
Knowing whether the issue is sending, receiving, or syncing helps narrow the cause quickly. If webmail works but your mail app does not, the issue is usually on the device or client side. If nothing works anywhere, the problem is more likely related to the hosting account, DNS, mailbox status, or server-level email service.
Check whether the mailbox is active and not full
A common reason business email stops working is that the mailbox has reached its storage limit. When a mailbox is full, new messages may bounce, fail to arrive, or remain queued. In a hosting control panel, mailbox usage is often visible in the email management section.
What to verify
- Confirm the mailbox still exists and has not been disabled.
- Check the mailbox quota or storage usage.
- Delete old messages, especially large attachments, if the mailbox is near capacity.
- Empty the Trash, Junk, and Sent folders if they are taking up space.
If you are using Plesk, open the email account settings and review mailbox usage. Some hosting platforms allow you to increase quota or switch to unlimited storage depending on the plan. If the mailbox is over quota, increasing the limit or archiving emails may resolve the issue immediately.
Test email in webmail first
Webmail is one of the best ways to isolate whether the problem is with the server or the email client. If you can send and receive in webmail, the mailbox and mail server are likely functioning. That means the issue is probably related to your email app, device, or sync settings.
How to test
- Log in to webmail from the hosting control panel or the provider’s webmail URL.
- Send a test message to an external address such as Gmail or Outlook.com.
- Reply from that external account and check whether the message arrives.
- Look in the Sent folder to confirm the message actually left the mailbox.
If webmail works but your desktop or mobile app does not, the hosting service is probably not the root cause. You should then focus on account settings, authentication, and device connectivity.
Confirm the correct incoming and outgoing server settings
Incorrect mail server settings are one of the most common causes of business email not working, especially after a migration, password reset, or device change. A mailbox may be set up with outdated IMAP, POP3, SMTP, or port information.
Typical settings to verify
- Incoming server: IMAP or POP3 host name
- Outgoing server: SMTP host name
- Encryption: SSL/TLS or STARTTLS
- Username: full email address in many hosting environments
- Password: current mailbox password
- Ports: correct ports for secure mail access
In a hosting platform, the recommended mail settings are usually documented in the control panel or account welcome email. If your provider supports Plesk, the control panel often displays the exact configuration for your domain. Make sure the settings in Outlook, Thunderbird, Apple Mail, or your phone match the values provided by the hosting company.
Common configuration issues
- Using the wrong mail server hostname
- Using an outdated password
- Leaving SMTP authentication disabled
- Using the wrong port for secure connection
- Configuring POP3 when you intended to use IMAP
If you recently changed passwords in the control panel, update the password in every device and mail app. One outdated device can repeatedly fail authentication and make it seem like the mailbox is down.
Check SMTP authentication and outgoing mail restrictions
When business email can receive messages but cannot send, the issue is often related to SMTP authentication or outbound restrictions. Hosting platforms commonly require authenticated SMTP to prevent abuse and spam.
What to check
- Make sure SMTP authentication is enabled in the mail client.
- Verify the outgoing server uses the same username and password as the mailbox.
- Confirm the connection uses the secure SMTP port recommended by your host.
- Check whether the server has reached an outgoing message limit or temporary block.
Some hosting environments limit the number of emails sent per hour or per day to protect deliverability and prevent spam outbreaks. If your business account suddenly stopped sending after a bulk mailing, a script error, or too many repeated attempts, the server may have placed a temporary restriction on outbound mail.
If you use Plesk, review the mail service settings and any restrictions on outgoing messages. Also check whether the mailbox or domain has been flagged for suspicious activity.
Review DNS records for the domain
If your business email is hosted with a domain on a hosting platform, DNS records play a major role in whether mail is delivered correctly. Incorrect MX, SPF, DKIM, or DMARC records can cause receiving failures, spam placement, or rejected messages.
Important DNS records to check
- MX records: point incoming mail to the correct mail server.
- SPF record: authorizes servers allowed to send mail for the domain.
- DKIM record: signs outgoing mail to improve trust and authentication.
- DMARC record: sets policy for handling unauthenticated mail.
If the domain was recently moved to a new hosting provider, these records may still point to the old server. That can cause mail to disappear, bounce, or arrive very late. Make sure the MX records match the current email hosting setup. If the mail service is hosted in Plesk or another panel, verify that the domain’s DNS zone includes the correct mail-related entries.
When DNS changes may cause email to fail
- After a domain migration to a different hosting company
- After switching from one email platform to another
- After modifying DNS manually
- When using third-party mail filtering or external email services
DNS changes can take time to propagate. If records were corrected recently, some senders may still use cached information for several hours. However, if the problem persists for longer, verify the actual DNS zone and not only the expected settings.
Check spam, junk, and mail filtering rules
Sometimes email is working correctly, but messages are not visible where users expect them. They may be filtered into Junk, Spam, Archive, or a custom folder by a rule or anti-spam system.
What to inspect
- Spam or Junk folders in webmail and mail clients
- Custom mail rules or filters
- Forwarding rules that may redirect messages elsewhere
- Server-side anti-spam settings in the control panel
In managed hosting or Plesk-based environments, the server may apply spam filtering before messages reach the mailbox. If the filter is too aggressive, legitimate business messages can be blocked. Review the spam score, blacklists, or anti-spam configuration if available.
Also check whether your inbox rules move emails from specific senders or with certain subject lines. A rule created long ago can silently send important mail to another folder or delete it after arrival.
Verify domain and mailbox authentication for deliverability
Deliverability issues are often mistaken for email outages. Your message may send successfully, but the recipient never sees it, or it arrives in spam. This is often caused by missing or incorrect authentication records such as SPF, DKIM, and DMARC.
Why authentication matters
- It proves that your hosting server is allowed to send mail for your domain.
- It reduces the chance that outgoing mail is rejected as spoofed.
- It improves trust with major providers such as Gmail, Microsoft, and Yahoo.
If your hosting platform provides DKIM signing, ensure it is enabled for the domain. If you send mail through a third-party system, such as a CRM or newsletter platform, SPF must include that service too. Otherwise, recipients may classify your messages as suspicious.
For businesses using a dedicated email hosting or managed hosting environment, it is good practice to confirm that authentication is aligned after any DNS, server, or platform change.
Look for account lockouts or security blocks
Mail services may temporarily block access when they detect suspicious login attempts, password failures, or unusual sending behavior. This is common if a mailbox password is saved incorrectly in multiple apps or if malware is trying to send mail through the account.
Signs of a security-related issue
- Repeated password prompts in your mail client
- Messages about blocked login or authentication failure
- Unable to send after a series of failed login attempts
- Sudden increase in outgoing mail volume from one mailbox
Change the mailbox password if you suspect unauthorized access or if the password may have been shared too widely. Then update all connected devices. Review recent login activity if your hosting panel or mail system provides it. If you manage email through a control panel like Plesk, check whether the account has any security notices or restrictions.
Check whether the mail service is running on the server
On hosted servers, email depends on the mail service being active and reachable. If the mail daemon is stopped, restarted incorrectly, or affected by a server resource issue, mail may stop working temporarily.
Server-side items to inspect
- Mail service status in the control panel
- Server resource usage such as CPU, memory, and disk space
- System-level mail queue for stuck or deferred messages
- Firewall or security rules blocking mail ports
In a managed hosting setup, your provider may need to check the mail queue or service logs. If many messages are delayed, the queue may be full or a remote mail server may be rejecting them. If the server disk is full, email services can behave unpredictably, so verify available storage not only for the mailbox but also at the server level.
Confirm your device and app can reach the server
When business email only fails on one device, the problem is usually local. Network restrictions, cached credentials, old profiles, or app sync bugs can all interfere with email access.
Steps to try
- Restart the mail app or device.
- Check internet connectivity on the device.
- Remove and re-add the mail account if settings are correct.
- Update the mail client to the latest version.
- Test from another network, such as mobile data instead of office Wi-Fi.
Corporate firewalls and some antivirus tools can block IMAP, POP3, or SMTP ports. If email works on a mobile network but not on office Wi-Fi, the network may be filtering mail traffic. In that case, your IT team or hosting provider may need to review firewall settings.
Check for forwarding, aliases, and catch-all behavior
Business email hosting often uses forwarding addresses, aliases, or catch-all mailboxes. If these are configured incorrectly, messages can seem lost or may end up in the wrong inbox.
Verify the following
- Whether the mailbox has a forwarder enabled
- Whether the forwarder points to a valid destination
- Whether an alias is associated with the correct mailbox
- Whether catch-all email is enabled and how it handles unknown addresses
Forwarding loops can cause delivery failures. For example, if address A forwards to address B and B forwards back to A, mail may bounce or disappear. Review forwarding carefully if your business uses shared inboxes or multiple address aliases.
Review message headers and bounce errors
If you receive a bounce message or delivery failure notice, it often contains valuable information. Even a short error code can point to authentication, DNS, reputation, or mailbox issues.
What to look for in bounce messages
- “Mailbox full” or “quota exceeded”
- “Authentication failed”
- “Relay denied”
- “Message rejected”
- “SPF fail” or “DKIM fail”
- “Recipient address rejected”
If you can view the full message headers in webmail, they may show the route the message took and where it was rejected. This can help determine whether the issue happened on your hosting server, on the recipient’s mail system, or at an external spam filter.
Check recent changes in the hosting account
Email problems often start after a change. If business email stopped working recently, review anything that may have changed in the hosting control panel or account settings.
Recent changes to review
- Password resets
- Domain DNS changes
- Migration to a new server or hosting plan
- Mailbox quota changes
- Anti-spam or antivirus configuration changes
- New device setup or email client reconfiguration
Many email issues are caused by a small configuration mismatch introduced during routine maintenance. Even a simple change such as switching DNS providers or renewing a certificate can affect how email clients connect.
When to contact your hosting provider
If you have checked the mailbox, webmail, client settings, DNS, and spam filtering, and email still does not work, contact your hosting provider or support team. They can inspect server logs, mail queues, authentication failures, and mail service health.
Provide the following details
- The affected email address
- The domain name
- Whether the issue affects sending, receiving, or both
- Any bounce error messages
- The time the issue started
- Whether webmail works
- Whether the issue affects all devices or only one
If you are using managed hosting, the support team may also verify server logs, firewall rules, blacklist status, or mail service configuration. The more detail you provide, the faster the issue can be isolated.
Recommended troubleshooting order
If you are not sure where to start, use this sequence:
- Check whether the mailbox is active and not full.
- Test email in webmail.
- Verify incoming and outgoing server settings.
- Confirm SMTP authentication and secure ports.
- Review spam, junk, and filtering rules.
- Check MX, SPF, DKIM, and DMARC DNS records.
- Look for account lockouts or sending restrictions.
- Test on another device or network.
- Inspect bounce messages and mail headers.
- Contact hosting support if the issue continues.
This approach helps separate user-side problems from hosting-side issues and saves time during troubleshooting.
FAQ
Why does business email work in webmail but not in Outlook?
This usually means the mailbox and server are working, but the email client has incorrect settings, an old password, or a sync problem. Recheck IMAP or POP3 settings, SMTP authentication, port numbers, and encryption.
Why can I send email but not receive it?
Possible causes include incorrect MX records, a full mailbox, a forwarding issue, spam filtering, or an inactive mailbox. Check DNS and verify that messages are not being routed to another folder or address.
Why are my emails going to spam?
Common reasons include missing SPF or DKIM records, poor sender reputation, spam-like message content, or a domain that is not properly authenticated. Confirm DNS authentication and review the content and sending pattern of your messages.
What should I check after moving email to a new hosting provider?
Verify MX records, SPF, DKIM, mailbox passwords, and mail client settings. Also confirm that the old mail service is no longer being used and that DNS propagation has completed.
How do I know if the issue is server-side?
If webmail does not work, multiple users are affected, messages bounce with server errors, or the hosting control panel shows mail service problems, the issue is likely server-side. Support can check service status, queues, and logs.
Can antivirus or firewall software block email?
Yes. Security software and firewalls can block SMTP, IMAP, or POP3 connections, especially on office networks. If email works on mobile data but not on a local network, security rules may be involved.
Conclusion
When business email is not working, the cause is often one of a few common issues: full mailbox storage, incorrect mail client settings, missing authentication, DNS misconfiguration, spam filtering, or a hosting-side service problem. In a hosting environment or control panel like Plesk, checking webmail, DNS records, mailbox status, and server restrictions will usually reveal the source of the problem.
By testing in a structured order, you can quickly determine whether the issue is with the mailbox, the device, the DNS zone, or the mail server. If the problem continues after these checks, your hosting provider can review mail logs and server settings to complete the diagnosis.