How to Fix WordPress Not Sending Email: Step-by-Step Checklist

Confirm the website is actually generating the message

Start by checking the plugin or feature that should create the email. Contact-form plugins often keep submission logs, and WooCommerce has order notes and email settings that show whether a notification was triggered.

If the application never creates the message, changing SMTP or DNS will not solve the problem. Fix the WordPress event or plugin configuration first.

Identify the current sending method

Find out whether WordPress is using PHP mail, local sendmail, an SMTP plugin, Microsoft 365, Google Workspace or a transactional provider. The correct troubleshooting steps depend on the real sender.

A common failure occurs after a hosting migration: WordPress still points to an old hostname or uses a local mail route that no longer matches the domain configuration.

Verify SMTP login and encryption

If you use SMTP, confirm the hostname, port, encryption and username. Port 465 is commonly used with implicit TLS, while 587 is commonly used with STARTTLS, but always follow your provider's documentation.

Use a full mailbox address as the username when required and avoid storing passwords in publicly accessible files. If the provider supports application passwords or OAuth, use the recommended authentication method.

Check the From address and Reply-To

Use a From address that belongs to the authenticated domain. For contact forms, put the visitor address in Reply-To rather than pretending the message was sent by the visitor.

Misaligned From addresses can trigger provider restrictions and DMARC failures, particularly when visitors use Gmail, Yahoo or other domains with strong policies.

Verify DNS authentication

Check SPF, DKIM and DMARC for the domain. SPF should authorize the real sending infrastructure, DKIM should sign the message, and DMARC should see aligned authentication.

If you recently changed providers, stale or duplicate DNS records can create intermittent results until the configuration is cleaned up.

Read the logs and bounce message

The fastest path to a fix is often the exact error. SMTP authentication failures, relay denied messages, blocked ports and recipient rejections each point to different causes.

Capture the full SMTP response or mail-server log entry before changing settings. That evidence prevents random configuration changes and makes support escalation much easier.