Skip to content
Hosting Operations6 min read

Email Not Sending: causes and solutions

Stop email not sending issues fast. Check logs, queue limits, DNS, and delivery settings. Follow this evergreen troubleshooting guide for hosting environments.

Written by Abdul AbrorTechnical Hosting Support Engineer
closeup of mail app icon on phone
On this page

TL;DR — Key takeaways

  • Check the mail queue and application logs first when email not sending; most issues trace to a blocked port, full disk, or misconfigured relay.
  • Verify DNS MX and SPF records, then confirm the outbound SMTP port is reachable from the server before changing any application code.
  • Set queue size limits, monitor disk usage, and alert on delivery failures to prevent a small glitch from becoming a full outage.
  • Test with a single message before rolling out changes, and keep a rollback plan for relay or queue configuration edits.
  • Track delivery status, bounce rates, and queue depth over time so recurring email not sending patterns are caught early.

Email not sending is one of the most common support tickets in hosting environments. The message may sit in a queue, fail at the SMTP handshake, or never leave the server. This guide covers the operational steps that fix most cases, with clear verification points and safe testing boundaries.

Treat every change as a hypothesis. Check the queue, review logs, verify network access, then test with a single message before scaling the fix.

Start with the mail queue and logs

The first step is to locate where the message stopped. Most mail systems keep a queue that holds messages until the delivery attempt succeeds. If the queue is full or the delivery worker is down, messages pile up and appear as email not sending.

Check the queue status with the mail system command or admin panel. Look for messages in deferred, failed, or held states. Read the recent logs for the mail transfer agent and the application that triggered the send. The log usually names the recipient, the error code, and the exact point where delivery stopped.

  • Run the queue status command and note the number of deferred messages.
  • Search logs for delivery errors, timeout messages, or connection refused entries.
  • Identify whether the failure happens at the application layer or the MTA layer.

Verify network access and SMTP ports

Outbound email depends on open ports. Port 25 is the standard for SMTP, while 587 and 465 handle submission and TLS. Many hosting providers block port 25 for shared accounts, and some networks filter it entirely. If the port is closed, the mail server cannot connect to the recipient or the relay.

Test the port with a simple connection check. Use a command line tool to attempt a TCP handshake to the relay host on the expected port. If the handshake fails, the issue is network or policy, not the application. Confirm with the hosting provider if the port is blocked at the edge.

Do not assume the application is at fault. A blocked port produces the same symptom as a broken relay, and changing application code will not fix it.

  • Test TCP connectivity to the SMTP host on ports 25, 587, and 465.
  • Check firewall rules and network policy for outbound mail traffic.
  • Confirm the relay host and port match the application configuration.

Check DNS records and authentication

Even with a clear path, the receiving server may reject the message. DNS records define how the sender is identified and whether the recipient trusts the domain. The MX record points mail to the right server. SPF and DKIM prove the message came from your domain. Missing or conflicting records cause hard bounces or silent drops.

Query the MX record for the sending domain. Verify the SPF record includes the mail server IP or a trusted relay. Check the DKIM selector and public key if signing is enabled. Compare the records against the actual sending configuration. A mismatch here explains why email not sending persists after the queue is cleared.

Keep the records aligned with the current infrastructure. If the relay changed, update the SPF include or DKIM keys before testing again.

  • Confirm the MX record points to the correct mail server.
  • Validate the SPF record covers the outbound relay.
  • Verify DKIM keys match the signing configuration.

Monitor queue depth, disk usage, and delivery status

A healthy mail system stays within limits. The queue grows when delivery stalls, and the disk fills when messages accumulate. A full disk stops the mail worker from writing new messages, which makes email not sending look like a total outage. Set thresholds for queue size and disk usage, then alert before the limit is reached.

Track delivery status, bounce rate, and latency. A sudden spike in bounces often points to a bad recipient list or a changed DNS record. A slow queue suggests network throttling or a heavy relay load. Use the monitoring dashboard to compare today against the previous week, and investigate only when the trend breaks.

Set up alerts for queue depth, disk usage, and delivery failures. These metrics catch the issue before customers notice it.

  • Alert when the queue exceeds a safe threshold or disk usage passes 80 percent.
  • Track bounce rate and delivery latency as leading indicators.
  • Review queue depth before and after any configuration change.

Test safely and roll back if needed

Change one variable at a time. After adjusting the relay, clearing the queue, or updating DNS, send a single test message to a known working address. Confirm the message leaves the server, reaches the recipient, and does not bounce. This boundary keeps a small experiment from turning into a full outage.

If the change causes new failures, revert it immediately. Keep a backup of the previous configuration file and the previous DNS records. Document the change, the reason, and the result. This practice turns a troubleshooting session into a repeatable process for the next incident.

Never assume the fix is permanent. Re-check the queue and logs after a few hours. Delivery issues can return when the network, relay, or DNS changes again.

  • Send one test message after each change and confirm delivery.
  • Keep a rollback copy of the previous relay and DNS settings.
  • Re-check the queue and logs after a few hours to confirm stability.

Quick troubleshooting checklist

  • Check mail queue status and recent log entries for delivery errors.
  • Confirm outbound SMTP ports 25, 587, and 465 are not blocked by firewall or network policy.
  • Validate MX, SPF, and DKIM records for the sending domain.
  • Review disk usage and mail queue size limits on the server.
  • Test a single test message after each configuration change.
  • Monitor queue depth, bounce rate, and delivery latency in the dashboard.

FAQ

Why is email not sending from my hosting account?

Email not sending is usually caused by a blocked outbound port, a full disk, a misconfigured relay, or DNS records that block delivery. Check the mail queue, application logs, and network access first.

What is the fastest way to fix email not sending?

Verify the mail queue, confirm the SMTP port is reachable, and review recent logs. Most cases resolve after clearing a full disk, unblocking a port, or fixing a relay setting.

How do I know if my DNS is blocking email delivery?

Check the MX record for the sending domain and confirm SPF and DKIM are present. Missing or conflicting records can cause the receiving server to reject the message.