How to Fix Email Not Sending (2026)
Fix email not sending with a security-hardening checklist. Audit your server, tighten authentication, and verify delivery step by step.

On this page
TL;DR — Key takeaways
- Start with the most common causes first: full disk, misconfigured DNS, wrong authentication, and blocked ports.
- Verify SMTP authentication, SPF, DKIM, and DMARC before assuming the mail transfer agent is broken.
- Run a security audit that checks open relays, weak credentials, and outdated TLS settings.
- Test with a single external recipient and monitor logs before changing production settings.
- Keep backups and document rollback steps before applying any mail server configuration changes.
Email not sending is one of the most common support tickets, and it usually points to a delivery, authentication, or security control issue. The mail queue may be empty, but the message still never arrives. That gap between a clean queue and a failed delivery is where most troubleshooting starts.
This guide covers a practical, security-focused path to finding the cause. You will audit the server, verify DNS and authentication, harden the mail transfer agent, and test the configuration without breaking production delivery.
Start with the mail queue and server logs
Open the mail queue and check for stuck messages. A full disk or exhausted disk quota is a frequent cause of email not sending. Run df -h on the mail partition and check the queue directory for files that cannot be written.
Next, read the mail logs. Look for rejected recipients, TLS handshake failures, authentication errors, and DNS resolution failures. The log line usually names the exact rule or check that blocked the message. Do not guess from the queue size alone.
- Check disk space on the mail partition and the queue directory.
- Review the mail log for rejected recipients and TLS failures.
- Identify whether the failure happens at connection, authentication, or delivery.
Verify DNS, MX, SPF, DKIM, and DMARC
Email delivery depends on DNS records that tell other servers where to send mail and how to verify it. Check the MX record first. It must point to the correct mail server and resolve to an IP address that matches your server.
Publish SPF, DKIM, and DMARC records if they are missing. SPF lists the servers allowed to send mail for your domain. DKIM signs messages with a private key and publishes a public key in DNS. DMARC tells receiving servers what to do with messages that fail the checks. Missing or malformed records cause bounces and spam folder placement.
- Confirm the MX record points to the correct mail server hostname.
- Verify SPF, DKIM, and DMARC records are published and valid.
- Check that the DKIM selector and public key match the signing configuration.
Audit SMTP authentication and relay settings
SMTP authentication prevents unauthorized servers from using your mail transfer agent to send spam. If authentication is disabled or too permissive, the server may be an open relay. Test with a dedicated application password and confirm that only authenticated sessions can send mail.
Check the relay configuration. Restrict relay to known IPs or require authentication for all outbound mail. Disable anonymous relay and review the configuration for default credentials. Change passwords immediately if any shared or default credentials are in use.
- Require SMTP authentication for outbound mail.
- Disable open relay and restrict relay to trusted networks.
- Use a dedicated application password instead of a shared account password.
Harden TLS and connection settings
Mail servers should use TLS for both incoming and outgoing connections. Check that the server presents a valid certificate and that clients are not forced to fall back to plain text. Weak cipher suites and outdated TLS versions weaken the connection and can cause delivery failures.
Review the allowed cipher list and disable deprecated protocols. Enable modern TLS versions and strong ciphers. Test the connection with a mail client and verify that the STARTTLS or SMTPS handshake completes without errors.
- Enable TLS for incoming and outgoing mail.
- Disable deprecated TLS versions and weak ciphers.
- Verify the certificate is valid and matches the mail server hostname.
Test the configuration safely
After making changes, test with a single external recipient. Do not send bulk mail until the configuration is verified. Watch the mail queue and logs for successful delivery and for any new rejection messages.
If the test fails, roll back the last change and re-check the logs. Keep a backup of the previous configuration so you can restore it quickly. Document the rollback steps before applying risky changes.
- Send one external test message after each configuration change.
- Monitor the queue and logs for successful delivery or new errors.
- Keep a backup of the previous configuration and document rollback steps.
Quick troubleshooting checklist
- Check disk space and mail queue size before changing any mail server settings.
- Confirm the MX record points to the correct mail server and that the hostname resolves.
- Verify SPF, DKIM, and DMARC records are published and syntactically valid.
- Test SMTP authentication with a dedicated application password, not a shared account password.
- Scan for open relay configuration and disable it if port 25 accepts mail from unauthorized senders.
- Review mail logs for rejected recipients, TLS failures, and authentication errors.
- Back up the mail server configuration and document the rollback procedure before changes.
- Test with one external recipient and confirm delivery before enabling broader sending.
FAQ
Why is my email not sending?
Email not sending usually means a delivery, authentication, or security control is blocking the message. Common causes include a full disk, misconfigured DNS, wrong SMTP credentials, blocked ports, or missing SPF, DKIM, and DMARC records. Check the mail queue and logs first, then verify the mail server configuration and security settings.
How do I harden my mail server against abuse?
Harden the mail server by disabling open relay, enforcing SMTP authentication, using strong credentials, enabling TLS, and publishing SPF, DKIM, and DMARC records. Restrict outbound ports, monitor logs, and test with a single recipient before changing production settings.
What should I check first when email delivery fails?
Check the mail queue and server logs first. Look for full disk space, rejected recipients, TLS errors, authentication failures, and DNS resolution problems. Then verify MX records, SPF, DKIM, and DMARC before assuming the mail transfer agent is broken.
Related articles
- Hosting OperationsEmail Not Sending: 7 Fixes That Actually WorkStop email not sending with this security-hardened guide. Audit your server, verify authentication, and test delivery safely.
- Hosting OperationsHow 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.
- Hosting OperationsHow 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.
- Hosting OperationsEmail Not Sending: 7 Fixes That WorkStop email not sending issues fast. Compare SMTP, relay, and local delivery, then follow clear steps to restore mail flow.
- Hosting OperationsEmail Not Sending? 7 Fixes That Work in 2026Stop email not sending errors now. Fix SMTP timeouts, DNS misconfigurations, and blocked ports with these 7 practical server-side solutions.
- Hosting OperationsFix Website Down Not Working (2026)Website down not working? Follow this security-hardening checklist to audit logs, lock down access, and verify your server is safe and reachable.