{"id":379,"date":"2026-09-10T12:30:19","date_gmt":"2026-09-10T18:00:19","guid":{"rendered":"https:\/\/photonconsole.com\/blog\/?p=379"},"modified":"2026-09-10T18:01:19","modified_gmt":"2026-09-10T23:31:19","slug":"fixing-wordpress-not-sending-email-permanently","status":"publish","type":"post","link":"https:\/\/photonconsole.com\/blog\/fixing-wordpress-not-sending-email-permanently\/","title":{"rendered":"Fixing “WordPress Not Sending Email” Permanently"},"content":{"rendered":"\n

Contact form submissions never arrive. Password reset links never reach users. WooCommerce order confirmations vanish, and customers email asking whether their purchase went through.<\/p>\n\n\n\n

WordPress reports no error. The form shows a success message. Nothing in the dashboard suggests a problem. This is one of the most common failures on self-hosted WordPress sites, and it is almost never caused by the plugin you are blaming.<\/p>\n\n\n\n

The cause is how WordPress sends mail by default. This guide explains what actually happens when wp_mail()<\/code> runs, why hosting providers block it, and how to configure authenticated SMTP so email delivery stops being something you have to keep fixing.<\/p>\n\n\n\n

Quick Answer: Why Is WordPress Not Sending Email?<\/h2>\n\n\n\n

WordPress uses the PHP mail()<\/code> function by default. That function sends mail directly from your web server with no authentication, which most hosting providers block and most mailbox providers reject or filter as spam.<\/p>\n\n\n\n

The fix is to route WordPress mail through an authenticated SMTP service instead:<\/p>\n\n\n\n

\/\/ wp-config.php\ndefine( 'SMTP_HOST', 'smtp.photonrelay.com' );\ndefine( 'SMTP_PORT', 587 );\ndefine( 'SMTP_USER', 'your_project_api_user' );\ndefine( 'SMTP_PASS', 'your_secret_api_key' );\ndefine( 'SMTP_FROM', 'noreply@yourdomain.com' );\ndefine( 'SMTP_NAME', 'Your Site Name' );<\/code><\/pre>\n\n\n\n
You can apply this with a plugin or with a small amount of code, both covered below. Either way, the change that matters is the same: WordPress stops sending mail itself and starts handing it to a service that is authorised to send on your domain’s behalf. An authenticated relay such as PhotonConsole<\/a> handles that authorisation.<\/p>\n\n\n\n
What wp_mail() Actually Does<\/h2>\n\n\n\n
\"Diagram
Default WordPress mail leaves unauthenticated. An SMTP relay sends with SPF and DKIM in place.<\/figcaption><\/figure>\n\n\n\n
Every email WordPress sends \u2014 registration notices, password resets, comment notifications, plugin alerts, WooCommerce receipts \u2014 passes through a single function called wp_mail()<\/code>.<\/p>\n\n\n\n
Internally, wp_mail()<\/code> uses PHPMailer<\/a>. By default PHPMailer is configured to use PHP’s built-in mail()<\/code> function, which hands the message to whatever mail transfer agent exists on the web server. On most shared hosting and cloud servers there either is no properly configured agent, or the one that exists sends from an IP address with no sending reputation.<\/p>\n\n\n\n
The message leaves. It just never arrives. If you want the underlying protocol explained first, see our guide to what SMTP is<\/a>.<\/p>\n\n\n\n
Why WordPress Email Fails<\/h2>\n\n\n\n
Most email delivery failures on WordPress come down to authentication and server configuration rather than faults in WordPress itself. These are the causes worth checking, in order.<\/p>\n\n\n\n
1. No Authentication on the Sending Domain<\/h3>\n\n\n\n
Without SPF and DKIM records, receiving mail servers cannot verify that your web server is allowed to send as your domain. Gmail, Outlook and Yahoo respond by filtering the message into spam or rejecting it outright, in line with Google’s sender guidelines<\/a>. This is the single most common cause. Our guide to SPF, DKIM and DMARC<\/a> covers the records in detail, and you can check what your domain currently publishes with the free email deliverability checker<\/a>.<\/p>\n\n\n\n
2. The Default From Address Does Not Exist<\/h3>\n\n\n\n
WordPress sends from wordpress@yourdomain.com<\/code> unless a filter<\/a> tells it otherwise. That mailbox usually does not exist, which means bounces go nowhere and DMARC alignment fails. Mailbox providers treat mail from a non-existent sender with suspicion.<\/p>\n\n\n\n
3. Your Host Has Disabled the mail() Function<\/h3>\n\n\n\n
Many hosts disable PHP mail()<\/code> entirely to prevent spam originating from compromised sites. When this happens wp_mail()<\/code> returns false, but most plugins do not surface that failure to the user.<\/p>\n\n\n\n
4. Hourly Sending Limits on Shared Hosting<\/h3>\n\n\n\n
Shared hosting plans commonly cap outbound mail per hour. A store processing orders, or a site with an active membership area, hits that ceiling and the remaining mail is silently discarded for the rest of the hour.<\/p>\n\n\n\n
5. Outbound SMTP Ports Are Blocked<\/h3>\n\n\n\n
Cloud providers including AWS, Google Cloud and DigitalOcean block outbound port 25 by default, and some block 587 as well. AWS documents its port 25 throttle removal process<\/a>, though removal does not solve the reputation problem underneath.<\/p>\n\n\n\n
Quick Fix<\/p>\n\n\n\n
WordPress Sends No Email At All<\/p>\n\n\n\n