Email Not Sending: 7 Fixes That Actually Work
Stop email not sending with this security-hardened guide. Audit your server, verify authentication, and test delivery safely.

On this page
TL;DR — Key takeaways
- Check the mail queue, authentication records, and firewall rules before changing any configuration.
- Verify SPF, DKIM, and DMARC records match your sending domain and IP addresses.
- Restrict outbound SMTP to trusted clients and disable open relays to reduce abuse risk.
- Test with a single external recipient before restoring full delivery after a change.
- Keep backups of configuration files and roll back if a hardening step breaks delivery.
Email delivery problems are among the most common support tickets. The message may sit in a queue, bounce back instantly, or never leave the server. The cause is usually a configuration mismatch, a blocked port, or a missing authentication record.
This guide covers the threat model, an audit checklist, hardening steps, and safe verification methods. Work through the sections in order, and keep a backup of your mail server configuration before making any changes.
Why Email Stops Sending
Most delivery failures trace back to three layers: the mail server, the DNS records, and the network path. A full disk, a misconfigured relay, or an expired certificate can stop the queue. A missing SPF record or a wrong MX entry can make the receiving server reject the message. A firewall rule can block outbound port 25 or 587.
Start with the mail log. It shows the exact point of failure. Look for lines that mention rejected, deferred, or refused. Those words tell you whether the problem is local, remote, or DNS related.
- Check the mail queue size and the last error entries in the log.
- Verify the mail server process is running and listening on the correct ports.
- Confirm the hostname resolves to the same IP used for outbound mail.
Threat Model for Mail Servers
An open relay is the most common abuse vector. Attackers send spam through your server, and the receiving provider blocks your domain. Spoofing happens when authentication records do not match the sender address. Phishing campaigns use your domain to trick recipients, and a weak firewall invites port scans.
Hardening is not optional. Restrict relay access, enable authentication checks, and publish strict DNS records. These steps reduce abuse and protect your sending reputation.
- Disable open relays and require authentication for outbound SMTP.
- Publish SPF, DKIM, and DMARC records that match your sending infrastructure.
- Block inbound and outbound traffic to unused ports with a firewall.
Audit Checklist
Run these checks before changing anything. They are quick and reversible. Record the current values so you can compare after each step.
Start with the mail queue, then move to DNS, then to network and authentication.
- Check the mail queue for stuck messages and read the last error lines.
- Verify the MX record points to the correct mail exchanger.
- Confirm SPF, DKIM, and DMARC records exist and match your sending domain.
- Test that outbound SMTP is allowed only from trusted clients.
- Review firewall rules for open ports 25, 587, and 465.
Hardening Steps
Apply one change at a time. Back up the configuration files first, then test with a single external recipient. If delivery breaks, roll back to the backup and try the next step.
Restrict relay access to authenticated users. Disable open relays. Enable DKIM signing for outgoing mail. Add a DMARC policy that reports and rejects unauthorized senders. Keep the firewall tight, but allow only the ports your mail server needs.
- Back up /etc/postfix/main.cf and /etc/dkim.conf before editing.
- Set smtpd_relay_restrictions to require authenticated clients.
- Enable DKIM signing and verify the selector and key path.
- Add a DMARC policy that reports failures to your monitoring address.
- Close unused ports and allow only 25, 587, and 465 from trusted networks.
How to Verify the Configuration
Use a third-party mailbox to test delivery. Send one message from a non-production account and watch the full delivery path. Check the mail log for the final result. If the message bounces, read the error code and match it to the checklist.
Test the DNS records with a command-line lookup. Compare the values with what your mail server expects. Do not change multiple settings at once, because that makes it impossible to know which step caused the problem.
- Send a test message to an external address and check the mail log.
- Run a DNS lookup for SPF, DKIM, and DMARC records.
- Verify the MX record and the hostname used in the envelope sender.
- Confirm the mail server listens on the expected ports and accepts authenticated connections.
Safe Testing Boundaries
Never test with a production account until the configuration is stable. Use a temporary mailbox or a dedicated test domain. Keep the test message small and avoid sending to large distribution lists. If you change a firewall rule, test from a second machine before opening the rule to the public.
Roll back immediately if the mail queue grows or the log shows repeated rejections. A broken mail server can damage your domain reputation and block legitimate mail for hours.
- Use a temporary account for all pre-production tests.
- Back up configuration files before every change.
- Roll back to the last known good state if delivery fails.
- Monitor the mail queue for 30 minutes after a change.
Quick troubleshooting checklist
- Run a mail queue status command and review the full error log for the last failed delivery.
- Confirm SPF, DKIM, and DMARC DNS records resolve to the correct values for the sending domain.
- Test outbound SMTP from a non-production machine using a temporary account.
- Back up /etc/postfix/main.cf and /etc/dkim.conf before editing any mail server settings.
- Verify the MX record points to the correct mail exchanger and that the hostname matches the envelope sender.
FAQ
Why does my email stop sending without an obvious error?
Email delivery usually fails at one of three points: the mail queue rejects the message, the receiving server blocks the connection, or authentication records do not match. Check the mail log first, then verify DNS records and firewall rules before assuming the application is broken.
How do I harden my mail server without breaking delivery?
Restrict outbound SMTP to known clients, disable open relays, and enable authentication checks. Keep a backup of the configuration files, apply changes one step at a time, and test with a single external recipient before restoring normal traffic.
What is the fastest way to verify email security settings?
Run a DNS lookup for SPF, DKIM, and DMARC records, then send a test message to a third-party mailbox. Compare the results with your mail server configuration and adjust the records or the server settings until the test passes.
Related articles
- Hosting OperationsHow 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.
- 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 Actually WorkFix email not sending issues fast. Check MX records, SPF, and logs. This guide covers 7 practical steps to restore outbound 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 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.