Email delivery problems can happen even when your website, hosting account, and mail client seem to be configured correctly. In a hosting environment, message failures are often caused by authentication issues, incorrect SMTP settings, DNS problems, mailbox limits, spam filtering, or temporary server-side blocks. Understanding where the failure occurs is the fastest way to fix the issue and restore reliable email flow.
This article explains the most common reasons emails fail to send or be received, how to troubleshoot them in a hosting control panel such as Plesk, and what settings to verify in your email client. It is especially useful for business email users who rely on hosted mailboxes for daily communication.
How Email Delivery Works
To understand email problems, it helps to know the basic path a message takes.
Sending an email
When you click Send in Outlook, Thunderbird, Apple Mail, or another client, the message is usually submitted to an SMTP server. The SMTP server then attempts to relay the email to the recipient’s mail server.
Receiving an email
Incoming mail is delivered to the recipient’s mail server first. Your email client then retrieves it using IMAP or POP3, depending on the configuration. If the message never reaches the mailbox, the issue is usually on the sending, routing, or filtering side.
Where problems can occur
- Local email client misconfiguration
- Incorrect SMTP, IMAP, or POP3 settings
- Authentication failures
- DNS or domain misconfiguration
- Mailbox quota limits
- Spam or security filtering
- Temporary server-side restrictions
- Recipient-side rejection or filtering
Common Reasons Emails Fail to Send
1. Incorrect SMTP settings
One of the most common causes of outgoing email failure is an incorrect SMTP server configuration. If the server name, port, or encryption setting is wrong, the mail client may be unable to connect to the outgoing mail server.
Typical settings to verify in a hosting environment include:
- SMTP server hostname
- SMTP port number
- Encryption type: SSL/TLS or STARTTLS
- Username and password
- Authentication enabled
In many hosting platforms, the SMTP server is the same as the mail server hostname for the domain or subscription. If you are using Plesk, confirm the mail settings in the control panel or the email account details provided by your hosting provider.
2. Authentication is disabled or incorrect
Most modern mail servers require SMTP authentication. If authentication is turned off, or if the username and password are incorrect, the server may reject the outgoing message.
Check whether:
- The full email address is used as the username
- The password matches the mailbox password
- SMTP authentication is enabled in the client
- The email account was not recently changed or reset in the control panel
If you changed the password in Plesk or another control panel, remember to update the saved password in all connected devices.
3. Port or encryption mismatch
Email clients often fail when the selected port does not match the encryption mode. For example, using port 465 without SSL/TLS or port 587 without STARTTLS can prevent successful submission.
Common outgoing mail combinations are:
- Port 587 with STARTTLS
- Port 465 with SSL/TLS
- Port 25 with no encryption or STARTTLS, depending on server policy
For most business email setups, port 587 is the safest and most widely supported option for authenticated sending.
4. Outbound mail restrictions on the server
Hosting servers may temporarily restrict outgoing mail when they detect suspicious activity, a compromised mailbox, or excessive sending. This is a protection measure to reduce spam and abuse.
Possible triggers include:
- Sending too many messages in a short time
- Repeated login failures
- Spam-like content in messages
- Compromised account activity
- Unusual sending behavior from a new IP address
If you manage the mailbox in Plesk, review the mail logs and security alerts. In some cases, your hosting provider may have rate limits or abuse protections that require a support review.
5. Mailbox quota exceeded
If the mailbox has reached its storage limit, new outgoing or incoming messages may fail. Some email clients show an error immediately, while others continue to send partially and then fail later.
To check quota issues:
- Open the mailbox settings in the control panel
- Verify available storage space
- Delete old messages or large attachments
- Empty trash and sent items if they consume space
In hosted email environments, quota limits can also affect message processing if the mailbox is full during delivery.
Common Reasons Emails Are Not Received
1. DNS records are missing or incorrect
For a domain to receive mail properly, its DNS must be configured correctly. The most important records for email delivery are MX records, and often SPF, DKIM, and DMARC as well.
If MX records point to the wrong mail server, incoming messages may be delivered elsewhere or bounce back to the sender. If SPF, DKIM, or DMARC are misconfigured, receiving systems may mark messages as spam or reject them entirely.
Check the following:
- MX records point to the correct mail host
- SPF includes the correct sending servers
- DKIM is enabled and publishes a valid public key
- DMARC policy is not overly strict during setup
In Plesk, these settings are commonly managed in the domain DNS zone and mail settings.
2. The message was filtered as spam
Sometimes mail is delivered to the recipient’s spam or junk folder instead of the inbox. This is especially common when the sender domain has weak authentication, poor reputation, or unusual content patterns.
Reasons a message may be filtered include:
- No SPF or DKIM authentication
- Mismatch between the From address and authenticated sender
- Suspicious attachments or links
- Mass-mailing behavior from a shared hosting account
- Recipient-side filtering rules
If an email is marked as spam by a receiving mailbox provider, delivery may appear successful even though the user never sees the message in the inbox.
3. The recipient mailbox is full
If the recipient’s mailbox has no free space, new messages may bounce or be silently rejected depending on the destination server’s policy.
This issue is outside your hosting account, but it can still cause delivery failures. Bounce messages often mention storage limits or mailbox unavailable errors.
4. Recipient address is invalid
An incorrect address, typo, or deleted mailbox will prevent delivery. This is one of the simplest causes of failure, but it is often overlooked when users expect a message to arrive quickly.
Verify the address carefully, especially the domain name and any periods, hyphens, or aliases.
5. Temporary delivery delays
Not every missing email is actually lost. SMTP is designed to retry delivery when a destination server is temporarily unavailable. This can create delays ranging from minutes to hours.
Temporary delays can happen because of:
- Remote server maintenance
- Greylisting
- Network issues
- Anti-spam deferrals
- Transient DNS problems
If the message is time-sensitive, check mail logs and bounce status before resending multiple copies.
How to Troubleshoot Email Sending Problems
Step 1: Check the exact error message
The error message in your email client is often the fastest clue. Common SMTP errors may mention authentication failure, connection timeout, relay denied, or mailbox unavailable.
Write down the full error text and any numeric code. This information helps identify whether the issue is local, server-side, or recipient-related.
Step 2: Verify account details
Confirm that the email address and password are correct. If you recently changed the mailbox password in the control panel, re-enter it on all devices.
Also confirm:
- SMTP username is the full email address
- Outgoing server name is correct
- IMAP or POP3 settings match the hosting provider’s instructions
Step 3: Test from webmail
If your hosting platform provides webmail, try sending a message from the browser-based interface. If webmail works but your email client does not, the issue is likely with local settings on the device.
If webmail also fails, the problem may be related to the mailbox, server policy, or domain configuration.
Step 4: Check server logs in the hosting control panel
In a managed hosting environment, mail logs are one of the most useful diagnostic tools. In Plesk, you can review mail activity and server logs to see whether the message was accepted, delayed, rejected, or delivered.
Look for:
- Authentication failures
- Rejected recipients
- Spam filtering entries
- Delivery deferrals
- Quota-related errors
Step 5: Review DNS and mail authentication
Check that your domain has properly configured MX, SPF, DKIM, and DMARC records. If messages are not being received, DNS problems may be the underlying cause even when the mailbox itself is healthy.
For best deliverability:
- Use one clear MX destination per domain setup
- Keep SPF record syntax valid and concise
- Enable DKIM signing for outgoing mail
- Start DMARC in monitoring mode if possible
Step 6: Confirm there are no local software issues
Email clients can fail because of cached credentials, outdated account profiles, firewall restrictions, or security software blocking mail ports. Try:
- Removing and re-adding the account
- Testing with another device or app
- Disabling VPN or firewall temporarily for testing
- Updating the email client
How to Troubleshoot Email Receiving Problems
Verify the mailbox exists
Make sure the receiving mailbox is created in your hosting control panel and not disabled. If the mailbox was deleted or renamed, incoming messages may bounce.
Check forwarding rules and filters
Emails can appear missing if they are forwarded elsewhere or filtered into a folder you are not checking. Review:
- Forwarding rules
- Server-side filters
- Autoresponder settings
- Vacation messages or routing rules
In some cases, a filter may move important messages away from the inbox automatically.
Inspect spam protection settings
Overly strict spam filtering can block legitimate mail. If your hosting platform includes anti-spam tools, review quarantined messages and allowlisting options.
Be cautious when relaxing filtering. A balance between usability and security is usually best.
Check whether the domain is using the correct mail server
If your domain recently migrated to a new hosting provider or mail service, DNS changes may still be propagating. During that time, some senders may deliver mail to the old server while others use the new one.
Verify that the MX records are fully updated and that no conflicting records remain in DNS.
Correct Email Client Settings to Verify
While the exact values depend on your hosting account, the following settings are commonly required for email protocols in a hosted environment.
Incoming mail settings
- IMAP: for syncing mail across devices
- POP3: for downloading mail to a single device
- Username: full email address
- Password: mailbox password
- Encryption: SSL/TLS recommended
Outgoing mail settings
- SMTP server: the correct mail server for your domain or hosting account
- Port: 587 or 465, depending on the setup
- Encryption: STARTTLS or SSL/TLS
- Authentication: enabled
Best practice for business email
For most business users, IMAP is the preferred protocol because it keeps messages synchronized across desktop, mobile, and webmail. POP3 may be suitable for older workflows, but it can create confusion if multiple devices are used.
How Plesk Can Help Diagnose Email Issues
If your hosting platform uses Plesk, several built-in tools can help identify the problem quickly:
- Mail Accounts: confirm mailbox creation, password, and quota
- DNS Settings: review MX, SPF, DKIM, and related records
- Mail Settings: check whether mail service is enabled for the domain
- Logs: inspect delivery attempts and rejection messages
- Webmail: test sending and receiving without a local client
If email works in webmail but not in Outlook or another client, the issue is usually limited to client configuration. If mail fails everywhere, check the server and DNS first.
Preventing Future Email Delivery Problems
Once the immediate issue is fixed, a few best practices can reduce the chance of recurrence.
- Use strong passwords and update them regularly
- Enable SMTP authentication on all devices
- Keep SPF, DKIM, and DMARC properly configured
- Monitor mailbox quotas
- Review mail logs after migration or DNS changes
- Avoid sending bulk mail from a standard mailbox
- Keep email client settings documented for support use
Good email hygiene is especially important on shared or managed hosting platforms, where reputation and security controls can affect delivery for multiple users.
FAQ
Why can I send email but not receive it?
This often points to an MX record problem, spam filtering, a full mailbox, or a misconfigured forwarding rule. Check your DNS zone and mailbox settings in the hosting control panel first.
Why do my emails go to spam?
Messages may go to spam if your domain lacks SPF, DKIM, or DMARC, if the content looks suspicious, or if your server or domain has a poor sending reputation. Authentication and consistent sending practices improve deliverability.
Why does my email client keep asking for my password?
This usually means the saved password is incorrect, the mailbox password was changed in the control panel, or authentication is misconfigured. Re-enter the full email address and current password, then verify SMTP/IMAP settings.
What is the difference between IMAP and POP3?
IMAP keeps messages synchronized on the server across multiple devices, while POP3 downloads messages to one device and may remove them from the server. For most hosted business email accounts, IMAP is recommended.
What should I do if webmail works but Outlook does not?
This usually indicates a local client issue. Check server names, ports, encryption, saved credentials, and firewall or antivirus interference. Recreating the mail profile often resolves the issue.
Can a full mailbox stop new emails from arriving?
Yes. If the mailbox exceeds its quota, incoming messages may bounce or fail. Clear old messages or increase the mailbox size if your plan allows it.
How do I know if the problem is on my side or the recipient’s side?
If your message leaves your server but is rejected later, a bounce message or mail log will usually show the recipient-side reason. If the message fails before leaving your server, the issue is likely local or related to your hosting configuration.
Conclusion
Email delivery issues are usually caused by a small number of predictable problems: incorrect SMTP settings, missing authentication, DNS misconfiguration, mailbox quotas, spam filtering, or temporary server restrictions. In a hosting environment, the fastest route to resolution is to check the exact error message, verify protocol settings, test with webmail, and review mail logs in the control panel.
For stable business email operation, keep your domain authentication records in order, use the correct IMAP and SMTP settings, monitor mailbox space, and confirm that your hosting provider’s mail service is enabled and properly configured. With these steps, most send and receive problems can be identified and fixed quickly.