{"id":1143,"date":"2026-03-13T15:00:38","date_gmt":"2026-03-13T12:00:38","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1143"},"modified":"2026-09-12T17:14:01","modified_gmt":"2026-09-12T14:14:01","slug":"fix-wordpress-not-sending-emails","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/fix-wordpress-not-sending-emails\/","title":{"rendered":"WordPress Not Sending Emails: Causes and Fixes"},"content":{"rendered":"

The password reset email never comes. The contact form says “sent” and nothing reaches your inbox. The order notification does not get to the customer. WordPress not sending emails<\/strong> looks like one problem, but those three situations have different causes and different fixes.<\/p>\n

This guide helps you identify which one you have, then takes you to the branch that applies.<\/p>\n

\nTable of contents<\/strong><\/p>\n
    \n
  1. Identify the symptom first<\/a><\/li>\n
  2. WordPress not sending emails: where the chain breaks<\/a><\/li>\n
  3. Nothing arrives at all<\/a><\/li>\n
  4. It arrives but lands in spam<\/a><\/li>\n
  5. Some send, some do not<\/a><\/li>\n
  6. The permanent fix for WordPress not sending emails<\/a><\/li>\n
  7. Verification<\/a><\/li>\n
  8. AIOWS SMTP Manager<\/a><\/li>\n
  9. FAQ<\/a><\/li>\n
  10. Sources<\/a><\/li>\n<\/ol>\n<\/div>\n

    Identify the symptom first<\/h2>\n

    Before anything else, run a two-minute test. The result decides which section you read.<\/p>\n

    The test:<\/strong> in the WordPress admin, go to Users \u2192 Profile<\/strong>, put an address you can read into the email field and save. WordPress sends a confirmation email to that new address.<\/p>\n

    \n\n\n\n\n\n\n\n
    Result<\/th>\nWhere to go<\/th>\n<\/tr>\n<\/thead>\n
    Nothing arrived, not even in spam<\/td>\nNothing arrives at all<\/a><\/td>\n<\/tr>\n
    It landed in the spam folder<\/td>\nIt arrives but lands in spam<\/a><\/td>\n<\/tr>\n
    It reached the inbox<\/td>\nSome send, some do not<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    The third result tells you something important: WordPress can send. The problem is in a specific plugin, a specific recipient, or a specific event.<\/p>\n

    This test is safe: the change only takes effect when you click the link in the email. If you do not click it, your profile stays exactly as it was and there is nothing to undo. Ignoring the email is enough.<\/p>\n

    WordPress not sending emails: where the chain breaks<\/h2>\n

    To find the problem you need to know the chain.<\/p>\n

    When WordPress sends email it calls wp_mail()<\/code>. That function uses the PHPMailer library. PHPMailer hands the message to PHP’s mail()<\/code> function by default, which passes it to the local delivery agent on the server. That agent tries to reach the recipient’s mail server.<\/p>\n

    Four links: WordPress \u2192 PHPMailer \u2192 PHP mail() \u2192 server \u2192 recipient.<\/strong><\/p>\n

    \n\"WordPress
    With SMTP configured, an authenticated server replaces the third link.<\/figcaption><\/figure>\n

    The breaks usually happen at the third and fourth links. Most shared hosting providers disable mail()<\/code> or block outbound traffic, to stop spam. Even where it works, the message goes out without authentication and the receiving server does not trust it.<\/p>\n

    That is why the permanent fix is to change the chain: connect PHPMailer to a real mail server instead of the local agent. That is SMTP.<\/p>\n

    Nothing arrives at all<\/h2>\n

    WordPress is not sending emails and the test message is not in spam either. Work through these in order.<\/p>\n

    Is mail()<\/code> disabled?<\/strong> Ask your hosting provider’s support, or if your control panel has a PHP info page, look at the disable_functions<\/code> list. If mail<\/code> is there the function is off and no plugin can change that.<\/p>\n

    Is the outbound port blocked?<\/strong> Providers almost always block port 25, and some close 587 and 465 as well. When that is why WordPress is not sending emails, configuring SMTP will not help either; you need the provider to open it.<\/p>\n

    Has a plugin intervened?<\/strong> Security plugins, maintenance-mode plugins and some caching plugins can block sending. Disable them temporarily and repeat the test.<\/p>\n

    Is a filter cancelling the send?<\/strong> Theme or plugin code can hook wp_mail<\/code> and stop delivery. Switch to a default theme and test; if it works, the problem is in the theme.<\/p>\n

    If all four are clean, the cause is almost certainly missing authentication and the fix is SMTP.<\/p>\n

    It arrives but lands in spam<\/h2>\n

    Here WordPress not sending emails is the wrong description: the message is being sent. This is a reputation problem, not a delivery one. The message reaches the recipient but is not trusted.<\/p>\n

    Is the sender address on your domain?<\/strong> Sending from something like noreply@gmail.com<\/code> looks like forgery to a receiving server. The sender address has to be on your site’s domain.<\/p>\n

    Is an SPF record defined?<\/strong> SPF declares, through DNS, which servers may send on behalf of your domain. Without it the receiving server cannot verify anything.<\/p>\n

    Is there a DKIM signature?<\/strong> DKIM proves the message was not altered in transit, and works alongside SPF.<\/p>\n

    Is the content triggering filters?<\/strong> Heavy capitalisation, many exclamation marks, shortened links and messages that are a single large image all trip filters.<\/p>\n

    Configuring SMTP solves part of this \u2014 the message now leaves an authenticated server. But you will not get the full result without adding SPF and DKIM records to DNS.<\/p>\n

    Some send, some do not<\/h2>\n

    The most confusing shape of WordPress not sending emails, and usually the easiest to fix.<\/p>\n

    The test works, the form does not.<\/strong> The most common variant. The form plugin puts the visitor’s address in the sender field. You authenticate as info@yoursite.com<\/code> but the message is sent as visitor@gmail.com<\/code>, and it is rejected.<\/p>\n

    The fix: in the form settings, fix the sender to an address on your own domain and put the visitor’s address in Reply-To<\/strong>. Replying still reaches the visitor, but the sending identity stays correct. Contact Form 7<\/a> has a guide of its own.<\/p>\n

    The admin gets it, the customer does not.<\/strong> The recipient’s mail provider may be rejecting the message. Sending to your own domain looks fine because the message never leaves the server. This is where missing SPF and DKIM show themselves.<\/p>\n

    Some events never fire.<\/strong> Order emails are sent on specific status changes. The email you are waiting for may never have been triggered \u2014 that is a configuration problem, not a delivery one.<\/p>\n

    Scheduled emails do not go.<\/strong> WordPress runs some jobs on its own scheduler, and that scheduler runs when someone visits the site. On low-traffic sites the jobs wait in a queue.<\/p>\n

    The permanent fix for WordPress not sending emails<\/h2>\n

    Most of the branches above lead to the same place: WordPress’s default delivery path is not reliable.<\/p>\n

    Configuring SMTP connects PHPMailer to a real mail server instead of the local delivery agent. The message now leaves an authenticated source, the receiving server trusts it, and deliverability improves markedly.<\/p>\n

    You need four values: host, port, encryption type and credentials. For real values by provider and a step-by-step setup, see the WordPress SMTP settings guide<\/a>.<\/p>\n

    Verification<\/h2>\n

    If you think you have fixed WordPress not sending emails, run all four checks before you trust it.<\/p>\n

    \n\n\n\n\n\n\n\n\n
    Check<\/th>\nExpected<\/th>\n<\/tr>\n<\/thead>\n
    Profile email change confirmation<\/td>\nReaches the inbox<\/td>\n<\/tr>\n
    Contact form submission<\/td>\nReaches the inbox<\/td>\n<\/tr>\n
    Received:<\/code> lines in the message source<\/td>\nShow the mail server you configured<\/td>\n<\/tr>\n
    Test with wrong credentials<\/strong><\/td>\nMust fail<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Do not skip the last one. Put a deliberately wrong password into the SMTP settings and test. If the test still reports success your message is not going through SMTP \u2014 the plugin has fallen back to the old path and nothing has been fixed. Restore the correct password afterwards.<\/p>\n

    Send to an address at a different provider as well. Sending to your own domain can look fine because the message never leaves the server.<\/p>\n

    \n

    How AIOWS helps:<\/p>\n

    AIOWS SMTP Manager<\/h2>\n

    The hard part of SMTP setup is not entering the values, it is arranging the authentication. Gmail and Microsoft 365 no longer accept an account password; you have to create an app password or complete an OAuth authorisation.<\/p>\n

    The OAuth route means creating a project in the Google Cloud Console, configuring the consent screen, generating credentials, defining a redirect URI, copying the keys into the plugin and completing the authorisation flow. Fifteen steps, twenty minutes, and again from scratch on every site.<\/p>\n

    EasyConnect in AIOWS SMTP Manager reduces that to one link: it picks your account, you grant permission, and the connection is made. The module also ships host and port values for thirteen providers \u2014 shared hosting and Yandex included \u2014 and keeps a send log showing which message went when.<\/p>\n

    When a test fails it names the stage it failed at: DNS resolution, connection, TLS handshake or authentication. That distinction points directly at which branch of this article you are in \u2014 and it is usually the fastest way to find out why WordPress not sending emails has become your problem today rather than last week.<\/p>\n

    \n\"The
    The stage, the server’s own reply and what to do \u2014 credentials are never shown.<\/figcaption><\/figure>\n

    Its limits, stated plainly:<\/strong> the module cannot re-enable a mail()<\/code> function your hosting provider has disabled, it cannot open a blocked port, and it cannot write your domain’s SPF or DKIM records into DNS for you. Those three need you or your provider.<\/p>\n

    Explore AIOWS SMTP Manager<\/a>Compare AIOWS plans<\/a><\/p>\n<\/section>\n

    FAQ<\/h2>\n

    WordPress says “email sent” but nothing arrives. Why?<\/strong><\/p>\n

    WordPress only knows that it handed the message to the server, not that it was delivered. The server may have dropped it silently, or the recipient rejected it.<\/p>\n

    WordPress is not sending emails \u2014 do I have to install an SMTP plugin?<\/strong><\/p>\n

    Not strictly, but in practice yes. WordPress’s default delivery path does not authenticate, so your messages either do not arrive or land in spam.<\/p>\n

    Can I use my Gmail address as the sender?<\/strong><\/p>\n

    Don’t. The sender address should be on your site’s domain. Sending from a Gmail address is treated as forgery by receiving servers.<\/p>\n

    My host blocks the SMTP ports. What can I do?<\/strong><\/p>\n

    Try 465 instead of 587. If both are closed, ask your provider to open them; if they will not, use a transactional email service that sends over an API.<\/p>\n

    The test email works but form emails do not.<\/strong><\/p>\n

    The form plugin is putting the visitor’s address in the sender field. Fix the sender to an address on your own domain and put the visitor’s in Reply-To.<\/p>\n

    Emails only fail to reach some recipients.<\/strong><\/p>\n

    The recipient’s provider is rejecting them. Check your SPF and DKIM records; without both, some providers will not accept the message.<\/p>\n

    Sources<\/h2>\n