Skip to content
Hosting Operations7 min read

How to Fix Email Not Sending (2026)

Compare the main ways to fix email not sending. Follow clear steps for SMTP, DNS, and mail server checks. Pick the right fix for your hosting setup.

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

TL;DR — Key takeaways

  • Check SMTP authentication, port settings, and firewall rules first when email stops sending.
  • Verify MX, SPF, and DKIM records before assuming the mail server is broken.
  • Use a test script or local SMTP client to isolate whether the issue is client, server, or network related.
  • Keep backups of configuration files and test changes on a staging environment before applying them to production.
  • Escalate to hosting support only after confirming the issue is not a local client or DNS problem.

Email stops sending when the path from your application to the recipient's inbox breaks. The failure can sit on the client side, the network, the DNS records, or the mail server itself. This guide compares the main troubleshooting paths and gives you a clear way to pick the right fix.

You will check SMTP settings, DNS records, firewall rules, and server logs. Each section answers a specific question and gives you a concrete next step. Test changes in a safe order so you do not make the problem worse.

What Does It Mean When Email Is Not Sending

Email not sending means your application or mail client cannot deliver messages to the recipient's server. The failure usually happens before the message leaves your network, inside the mail server, or during DNS resolution. The symptom is the same: no email arrives, and the sending tool returns an error or simply drops the message.

The most common causes are wrong SMTP credentials, blocked outbound ports, missing or incorrect DNS records, or a mail server that rejects the connection. The fix depends on where the break occurs. You need to isolate the failure point before changing anything.

  • Client-side issues: wrong SMTP port, missing authentication, or a blocked outbound connection.
  • DNS issues: missing MX, SPF, or DKIM records that cause the receiving server to reject mail.
  • Server-side issues: mail queue problems, authentication failures, or rate limits on the mail server.
  • Network issues: firewall rules or security groups that block ports 25, 465, or 587.

Compare the Main Troubleshooting Paths

Three paths cover most email delivery failures. The first path checks the mail client and SMTP settings. The second path verifies DNS records and domain authentication. The third path inspects the mail server and network rules. Each path has different trade-offs in speed, accuracy, and risk.

Checking SMTP settings is fast but only tells you if the client is configured correctly. DNS checks are quick and prevent receiving servers from rejecting your mail. Server and network checks are more invasive but reveal the root cause when the first two paths pass. You need all three to be sure.

  • SMTP check: verify port, authentication, and encryption settings. Fast but limited to client configuration.
  • DNS check: confirm MX, SPF, and DKIM records. Prevents receiving servers from rejecting mail.
  • Server check: review logs, queues, and connection limits. Reveals root cause but requires access.
  • Network check: test outbound ports with a local SMTP client. Isolates firewall or routing problems.

Step 1: Verify SMTP Settings and Authentication

Start with the sending client. Open the mail server settings and confirm the SMTP hostname, port, and encryption method. Common ports are 25 for unencrypted relay, 465 for implicit TLS, and 587 for explicit TLS. Many applications default to port 25, which modern mail servers often block.

Next, verify the username and password. Some services use the full email address as the username, while others use the account ID. Authentication failures usually return an error like 535 or 534. Test with a dedicated test account instead of a production account to avoid locking the real user out.

  • Confirm the SMTP hostname matches the mail service you are using.
  • Use port 587 with STARTTLS or port 465 with implicit TLS for secure sending.
  • Check that the username matches the service account, not the display name.
  • Test with a test account to avoid locking out a real user during troubleshooting.

Step 2: Check DNS Records and Domain Authentication

If the SMTP settings are correct, the receiving server may still reject your mail. The receiving server looks at DNS records to decide whether to accept the message. The MX record tells it where to deliver mail. The SPF record lists the servers allowed to send mail for your domain. The DKIM record adds a cryptographic signature that proves the mail was not altered.

Missing or incorrect records cause bounces, spam folder placement, or outright rejection. Check the MX record first. It must point to the mail server that handles your domain. Then verify SPF and DKIM. If you use a third-party sending service, the SPF record must include that service's IP range or domain.

  • Confirm the MX record points to the correct mail server for your domain.
  • Verify SPF includes all authorized sending servers and IP ranges.
  • Check DKIM keys are published and match the signing service.
  • Use a DNS lookup tool to verify records before changing anything.

Step 3: Test the Network and Mail Server

When client settings and DNS look correct, test the network path. Use a local SMTP client or a simple script to connect to the mail server on port 25, 465, or 587. The server should respond with a greeting code. If the connection is refused, the firewall or security group is likely blocking the port. If the connection succeeds but the server rejects authentication, the mail server configuration is the issue.

Check the mail server logs for connection refused, authentication failures, or rate limit messages. Review the queue status to see if messages are stuck. If you changed the mail server configuration, back up the original files first. Apply changes in a staging environment and test before touching production.

  • Connect to the mail server with a local SMTP client to test the network path.
  • Check firewall and security group rules for outbound ports 25, 465, and 587.
  • Review mail server logs for authentication failures, queue buildup, or rate limits.
  • Back up configuration files before changing mail server or DNS settings.

When to Escalate to Hosting Support

Escalate to hosting support when the issue is server-side and you cannot fix it locally. This includes stuck mail queues, server-side authentication failures, or provider-side routing problems. Provide the mail server logs, the exact error message, and the steps you already tested. Support can check server-side queues, IP reputation, and provider-side routing.

Do not escalate too early. Most email delivery issues are client or DNS problems. Test the client, verify DNS, and check the network first. If the problem persists after those checks, escalate with clear evidence. This reduces ticket time and helps support resolve the issue faster.

  • Confirm the issue is not a local client, firewall, or DNS problem before escalating.
  • Provide mail server logs, exact error messages, and the steps you already tested.
  • Ask support to check server-side queues, IP reputation, and provider-side routing.
  • Keep a backup of configuration files before making any risky changes.

Quick troubleshooting checklist

  • Confirm the sending domain has a valid MX record pointing to the correct mail server.
  • Verify SPF and DKIM records are published and aligned with the sending service.
  • Test SMTP authentication with the correct username, password, and port.
  • Check firewall and security group rules for outbound ports 25, 465, and 587.
  • Review mail server logs for connection refused, authentication failures, or rate limits.
  • Run a test email through a local SMTP client to isolate the failure point.
  • Back up configuration files before changing mail server or DNS settings.

FAQ

Why is my email not sending from a website or app?

Email usually stops sending because of SMTP authentication failure, wrong port, firewall blocking outbound mail traffic, or DNS records that reject the sending domain. Check the mail client settings first, then verify the domain's MX, SPF, and DKIM records before assuming the mail server is broken.

What is the fastest way to test if SMTP is working?

Use a local SMTP client or a test script to connect to the mail server on port 25, 465, or 587. Authenticate with the correct credentials, send a test message, and read the server response. This isolates whether the problem is on the client, the network, or the mail server.

When should I contact hosting support about email not sending?

Contact hosting support after confirming the issue is not a local client, firewall, or DNS problem. Provide the mail server logs, the exact error message, and the steps you already tested. Support can then check server-side queues, IP reputation, and provider-side routing.