Skip to content
Hosting Operations7 min read

How to Fix Email Not Sending (2026)

Stop email not sending issues with a structured checklist. Verify DNS, ports, firewall, and queue settings, then monitor delivery to keep mail flowing.

Written by Abdul AbrorTechnical Hosting Support Engineer
black laptop computer
On this page

TL;DR — Key takeaways

  • Start with the simplest checks first: verify the MX record, open SMTP ports, and confirm the mail queue is not blocked.
  • Use port 587 with STARTTLS for client submissions and port 25 for server-to-server delivery, then test each path separately.
  • Monitor the mail queue and delivery logs daily to catch stalled messages before they affect deliverability.
  • Back up configuration files before changing firewall, DNS, or mail server settings, and keep a rollback plan ready.
  • If email still does not send, isolate the problem by testing from a different network, checking authentication, and reviewing provider status pages.

Email not sending is one of the most common support tickets, and it usually comes from a small configuration gap rather than a broken server. I have seen this happen on shared hosting, managed mailboxes, and custom SMTP setups. The pattern stays the same: a wrong MX record, a blocked port, a full queue, or a failed authentication check. This guide walks through the practical steps to find the cause, tune the delivery path, and verify the result. Work through the checklist in order, test each change, and keep backups before touching DNS or firewall rules.

Start with the DNS and MX Record

The first place to look is the domain's MX record. This record tells receiving servers where to send mail for your domain. If it points to the wrong host, or if the priority value is missing, delivery fails before the message even leaves your server. Use a DNS lookup tool or run dig MX yourdomain.com from the command line. Confirm the record matches your mail provider and that the TTL is low enough for quick changes.

Also check the SPF record. This record lists the servers allowed to send mail on your behalf. A missing or too-strict SPF policy can cause receiving servers to reject the message. Add a TXT record with v=spf1 include:yourprovider.com ~all if your provider recommends it. Keep the record short and avoid multiple conflicting SPF entries.

  • Run dig MX yourdomain.com to verify the mail exchanger.
  • Confirm the MX priority is a valid number, usually 10 or 20.
  • Check the SPF TXT record for syntax errors and missing includes.

Verify SMTP Ports and Firewall Rules

Once DNS is correct, test the actual delivery path. Client submissions usually use port 587 with STARTTLS, while server-to-server delivery uses port 25. Some providers also offer port 465 for implicit TLS. Open a terminal and run telnet or nc to test each port. A connection that hangs or refuses means the port is blocked or not listening.

Next, check the firewall. Outbound traffic on ports 25, 587, and 465 must be allowed. If you are on a managed host, verify the security group or network ACL. A common mistake is blocking port 25 for outbound traffic while allowing inbound. Test from the server itself, not just from your local machine, because local firewalls behave differently.

  • Test port 587 with STARTTLS using a mail client or telnet.
  • Test port 25 for server-to-server delivery.
  • Confirm the firewall allows outbound traffic on the required ports.

Check the Mail Queue and Logs

A full or stuck mail queue is a frequent cause of email not sending. When the queue grows too large, the mail server may pause delivery to protect the system. Look at the queue directory or use the mail server's management tool. Identify messages that have been waiting for hours or days. Review the logs for error codes like 421, 450, 451, or 550. These codes point to connection limits, policy rejections, or bad recipients.

If the queue is backed up, clear it carefully. Do not delete messages without checking the logs first. A single bad recipient can poison the queue. After clearing, restart the mail service and watch the queue drain. If messages keep failing, the issue is likely authentication, DNS, or a provider-side block.

  • List the queue and identify messages stuck for more than an hour.
  • Read the delivery logs for the exact error code.
  • Restart the mail service only after clearing the queue.

Validate Authentication and Sending Domains

Authentication failures are another common cause. The sending domain must have valid SPF, DKIM, and DMARC records. SPF authorizes the sending server, DKIM adds a cryptographic signature, and DMARC tells receiving servers what to do with failed messages. Check each record with a DNS lookup tool. Missing or misaligned records cause receiving servers to reject or quarantine the mail.

Also verify the account credentials. A wrong password, expired token, or revoked API key will block sending. If you use an SMTP username and password, test the login manually. For API-based sending, confirm the API key has the correct permissions. Never share credentials or store them in plain text.

  • Verify SPF, DKIM, and DMARC records for the sending domain.
  • Test SMTP authentication with the correct username and password.
  • Check API keys and tokens for expired or revoked permissions.

Performance Tuning and Monitoring

Once delivery works, tune the system for steady performance. Set the mail queue to retry failed messages every 15 to 30 minutes. Configure alerts when the queue exceeds a small threshold, such as 50 messages. Monitor delivery latency and bounce rates over a 24-hour period. A healthy setup drains the queue quickly and keeps bounce rates below 2 percent.

Use a monitoring tool to track SMTP connection success, queue size, and log error rates. Set up alerts for sudden spikes in failures. Keep a rollback plan for DNS and firewall changes. Test changes on a staging environment first, then apply them to production. Document the steps so the next engineer can follow the same path.

  • Retry failed messages every 15 to 30 minutes.
  • Alert when the queue exceeds 50 messages.
  • Track delivery latency and bounce rates daily.

When to Escalate and Next Steps

If email still does not send after checking DNS, ports, the queue, and authentication, escalate to the hosting provider or mail service support. Prepare a summary with the domain, mail provider, error codes, and the steps you already tried. Providers can check for IP reputation issues, blacklisting, or account-level blocks. Do not keep retrying the same fix without new evidence.

Keep a troubleshooting log with the date, the change made, and the result. This record helps you spot patterns and speeds up future support requests. If you manage multiple domains, check each one separately. A single misconfigured subdomain can block mail for the entire account.

  • Collect the domain, provider, error codes, and steps tried before escalating.
  • Keep a log of changes and results for future reference.
  • Check each domain separately when managing multiple accounts.

Quick troubleshooting checklist

  • Confirm the MX record points to the correct mail server and has a valid priority value.
  • Test SMTP submission on port 587 with STARTTLS and verify the connection succeeds.
  • Check the mail queue for stuck messages and review delivery logs for error codes.
  • Verify firewall rules allow outbound traffic on ports 25, 587, and 465.
  • Validate authentication credentials and ensure the sending domain has valid SPF, DKIM, and DMARC records.
  • Monitor queue size and delivery latency over a 24-hour period to confirm the fix holds.

FAQ

Why is my email not sending?

Email not sending usually happens when the MX record is wrong, the SMTP port is blocked, the mail queue is full, or authentication fails. Check DNS first, then verify ports and logs.

Which SMTP port should I use for sending email?

Use port 587 with STARTTLS for client submissions and port 25 for server-to-server delivery. Port 465 is also common for implicit TLS, but confirm your provider supports it.

How do I check if my email is actually being delivered?

Open the mail queue, review delivery logs, and watch for bounce messages. A healthy queue stays small and messages move through within minutes.