Troubleshooting · Troubleshooting
How to Fix WordPress Not Sending Emails
Short answer
WordPress is not sending emails because its default PHP mail route is unauthenticated and often blocked or filtered as spam. Fix it by routing wp_mail through an authenticated SMTP provider, using a real From address on your own domain, and publishing SPF, DKIM and DMARC records. Then send a test email and check that it arrives in the inbox, not spam.
Key takeaways
- A true result from wp_mail means WordPress handed the message on, not that it reached the inbox.
- The default From address is wordpress@ plus your site domain, with www removed.
- Authenticated SMTP on port 587 with TLS is the fix for most sites with missing WordPress email.
- Since 1 February 2024, Google requires SPF or DKIM for all senders to personal Gmail accounts.
- Senders of more than 5,000 messages a day to Gmail need SPF, DKIM and DMARC with an aligned From domain.
- Google recommends always setting up SPF, DKIM and DMARC for every sending domain.
Why is WordPress not sending emails?
WordPress usually fails to send email because its default route uses unauthenticated PHP mail, so receiving servers reject the message or place it in spam.
WordPress sends mail through wp_mail(), a wrapper around PHPMailer. By default, PHPMailer uses PHP mail(), which needs a sendmail-compatible binary on the server. Mail – Advanced Administration Handbook WordPress has never provided its own mail server, so the host setup decides if that route works at all.
The most likely causes, in order, are:
- Your host blocks or limits PHP
mail(). - The From address does not match your domain.
- SPF, DKIM or DMARC is missing or wrong.
- Your SMTP login, host, port or encryption is wrong.
- Another plugin has changed the
wp_mail()settings.
What does “sent” mean in WordPress?
In WordPress, sent means the message was handed to the next mail system without an error, not that it reached the inbox.
The wp_mail() reference states that a true return value does not mean the user received the email. It only means the method used was able to process the request without errors. A message can still be rejected later, filtered as spam, or dropped after that handoff.
That gap explains the most confusing symptom: WordPress reports success, a form shows a thank-you message, and nobody receives anything. You need a test that checks the inbox, not only the WordPress screen.
How do you find where the email stops?
Send a test to an address you control on another provider, check inbox and spam, then read the error or log to see if WordPress or the receiver stopped it.
Start with a controlled test, not a live form submission. A form adds its own notification settings, spam checks and recipient list, so it cannot tell you if the mail route itself works.
- Open your SMTP plugin and use its email test screen. In WP Mail SMTP, that screen is under WP Mail SMTP → Tools → Email Test.
- Send the test to a mailbox you can open at once, on a different domain from your site.
- Check the inbox, then the spam folder. Note the exact result and any error text.
- Open the email log if your plugin keeps one. WP Mail SMTP Pro adds email logging, reporting, backup connections and alerts, while the free plugin covers the connection itself.
What if there is no error message?
WordPress fires the wp_mail_failed hook after a PHPMailer exception is caught. wp_mail_failed hook That hook passes a WP_Error object with the PHPMailer message and the mail data.
A short-term logger on that hook can record the real error while you reproduce the failure. Remove the logger when you are done, so mail data does not stay in a log file.
If the log says the message was sent but it never arrives, the fault is after the handoff. That points to authentication, spam filtering, or the receiving server, not to the WordPress send step.
How do you fix the From address?
Use a real mailbox on your own domain, such as [email protected], and force that address for all WordPress mail.
If you do not set a From address, WordPress builds one from your site domain. The wp_mail() reference shows the default as wordpress@ plus the site host, with a leading www. removed. Some hosts block mail from that address if the mailbox does not exist.
WordPress 6.9 changed how the sender address is set. More-reliable email in WordPress 6.9 If a From header is present, WordPress 6.9 uses that address. Otherwise it defaults to wordpress@ plus your home URL host, and plugins can change it with the wp_mail_from filter.
Do not put a visitor address in the From field. A visitor Gmail address fails authentication for your domain, because your server is not allowed to send as Gmail. Put the visitor address in Reply-To instead, and keep From on your own domain.
How do you set up SMTP in WordPress?
Install an SMTP plugin, choose your mailer, enter the host, port, encryption and login from your mail provider, then save and send a test.
An SMTP plugin reroutes wp_mail() through an authenticated mail server instead of local PHP mail. WP Mail SMTP by WPForms
The plugin page says it fixes deliverability by reconfiguring WordPress to use a proper SMTP provider. More than 4 million websites use it, as of November 2026. Its own site is at WP Mail SMTP.
- Go to Plugins → Add New, search for “WP Mail SMTP”, then click Install Now and Activate.
- Follow the Setup Wizard, or open WP Mail SMTP → Settings to set it up by hand.
- Choose your provider mailer when it is listed. Otherwise choose Other SMTP.
- Enter the From Email and From Name, then the SMTP Host, Encryption, SMTP Port, SMTP Username and SMTP Password from your mail provider.
- Turn on Force From Email if the plugin offers it, so no plugin can send from another address.
- Click Save Settings, then send a test email from the plugin test screen.
Use only one SMTP plugin at a time. Two plugins can fight over wp_mail() settings, and the second one can undo the first fix without a clear error.
Which SMTP port and encryption should you use?
Use port 587 with TLS for most SMTP servers, or port 465 with SSL when your provider lists that pair.
| Encryption | Port | When to use it |
|---|---|---|
| TLS | 587 | Most providers, including the DreamHost SMTP setup below |
| SSL | 465 | Your provider lists 465 with SSL or SSL/TLS |
| None | 25 | Do not use it for normal mail; it is the PHP default in php.ini |
DreamHost lists TLS and port 587 for its WP Mail SMTP setup, with the host smtp.dreamhost.com. Configuring the WP Mail SMTP plugin Your own provider values will differ, so copy the host, port and encryption from your mail provider, not from a guide.
The wp_mail() reference notes that the PHP settings SMTP and smtp_port use port 25 by default. That default is the local mail route, not an authenticated SMTP login, so changing it alone does not fix authentication.
Why do SPF, DKIM and DMARC matter for WordPress email?
SPF, DKIM and DMARC prove your domain allowed the message, so add all three records for the domain in your From address.
SPF is a TXT record that lists the servers allowed to send mail for your domain. DKIM adds a signature that the receiver checks against a public key in your DNS.
DMARC is a TXT record that tells receivers what to do when SPF or DKIM checks fail. The Mail handbook calls setting up SPF, DKIM and DMARC a critical step for deliverability.
| Record | What it does | Key fact as of November 2026 |
|---|---|---|
| SPF | Lists allowed senders for your domain | Your SPF record should include all email senders for your domain |
| DKIM | Signs each message so receivers can check it | Google needs a key of at least 1024 bits and recommends 2048 bits |
| DMARC | Sets the policy for mail that fails SPF or DKIM | Bulk senders to Gmail need DMARC; a policy of p=none is allowed |
Google requires SPF or DKIM for all senders to personal Gmail accounts since 1 February 2024. Email sender guidelines
Senders of more than 5,000 messages a day to Gmail accounts need SPF and DKIM, plus DMARC, and the From domain must align with the SPF or DKIM domain. Google also asks senders to keep spam rates in Postmaster Tools below 0.3%.
If you send through more than one service, list every sender in SPF. The Mail handbook warns that you need to add all the addresses to the SPF record when you send through different servers, including your WordPress install. For the full record setup, see the SPF, DKIM and DMARC setup guide.
How do you check SPF, DKIM and DMARC after setup?
Send a test to Gmail, check the message headers in the receiving mailbox, and confirm SPF, DKIM and DMARC all pass for your domain.
DNS changes take time to spread, so wait before you judge a new record. Google recommends that you always set up SPF, DKIM and DMARC for your domains. Email sender guidelines Do not change the same record again while you wait.
Check one record at a time. If SPF passes and DKIM fails, the DKIM key or selector is wrong, not the whole setup. Copy every DNS value from your own mail provider or admin console, never from a sample in a guide, because keys and selectors differ by account.
If all three pass but mail still lands in spam, the cause is often reputation or content. A shared IP can carry the reputation of other senders on it, and Google notes that activity from other senders on a shared IP affects all senders on that IP. Email sender guidelines
What if the SMTP test works but a form still sends nothing?
If the SMTP test works but a form still sends nothing, check that form notification settings, not the mail route.
A working SMTP test proves WordPress can hand mail to your provider. A form can still fail if its notification is off, its recipient address is wrong, or its spam check blocks the submission before mail is sent.
- Check the form notification recipient and From address first, then resubmit the form.
- If only one form fails, the fault is in that form, not in SMTP.
- If every form fails but the SMTP test works, check for a plugin conflict by testing with other plugins off on a staging copy.
Related fixes for single-form faults:
- Fix a contact form that does not send email
- Fix WPForms not sending email
- Fix Gravity Forms notifications not sending
- Fix Contact Form 7 not sending messages
Password reset mail uses the same wp_mail() route, so a fix that makes the SMTP test arrive should also fix reset mail, unless the reset message itself is blocked as spam. Check the spam folder for that message before you change SMTP settings again.
When should you contact your host about WordPress email?
Contact your host when the SMTP test fails with a connection error, when a port is blocked, or when PHP mail is disabled on your server.
The Mail handbook says that on managed hosting, mail questions should go to your web host. Check if the host provides an SMTP relay through its admin panel.
On a self-managed server, you are responsible for the mail server setup. The host can only tell you if a port or mail function is blocked.
Send your host this short list:
- The exact error text from the SMTP test or the
wp_mail_failedlog. - The time of the failed test, with your timezone.
- The From address, the test recipient, and the SMTP host and port you used.
- Whether PHP
mail()works at all on your plan, and whether ports 25, 465 and 587 are open for outbound mail.
Ask the host to confirm the SMTP relay it offers, if any. If the host has no relay and blocks outbound SMTP, you need a third-party mail provider, not another WordPress plugin setting.
What mistakes should you avoid?
Avoid using a free personal address as From, running two SMTP plugins at once, and changing DNS records without copying the exact values from your provider.
- Keep the default
wordpress@address only if that mailbox exists and your domain allows it. - Never use a visitor Gmail or Outlook address as the From address.
- Never run two SMTP plugins at the same time.
- Never treat a WordPress “sent” result as proof of inbox delivery.
- Never copy a DKIM key or SPF value from a guide; use the value from your own provider.
- Never change SPF, DKIM and DMARC at once and then guess which change fixed the fault.
Frequently asked questions
Why do WordPress emails go to spam even when the test says sent?
The test only proves WordPress handed the message to your mail provider. Spam placement happens after that handoff, when the receiver checks SPF, DKIM and DMARC, the sender reputation, and the message content. Fix the From address and the three DNS records first, then check the spam rate and the message headers for the failing check.
Can I use a Gmail address as the From address for WordPress mail?
No, not as the From address for mail sent from your own domain. Your server is not allowed to send as Gmail, so that mail fails SPF and DKIM alignment and is likely to be rejected or marked as spam. Use a real mailbox on your own domain for From, and put a Gmail address in Reply-To only if you want replies to go there.
Do I need SMTP if my host says PHP mail works?
You may still need it. PHP mail can hand a message on without any login or signature, and many receivers now reject or filter that mail. Authenticated SMTP adds a login, a clear sender, and a route that your mail provider can sign and track. If mail still lands in spam on PHP mail, switch to SMTP and add SPF, DKIM and DMARC.
Do I need SPF, DKIM and DMARC for a small site with low mail volume?
Yes, the same records help a small site. Google requires SPF or DKIM for all senders to personal Gmail accounts, and it recommends all three records for every sending domain. A small site sends password resets, order mail and form mail, and each of those can be filtered as spam without authentication. Set the records up once, then test with a real message to a Gmail address.
Why did WordPress email change after the WordPress 6.9 update?
WordPress 6.9 changed how the sender address is set, so it now uses the From header when present and otherwise defaults to wordpress@ plus your home URL host. Sites with custom mail setups that relied on the old behaviour may need to set the sender with the wp_mail_from filter. Check the From address in a test message before you change SMTP settings.
Can WordPress send email without any plugin?
Yes, if the server mail setup is correct. WordPress uses wp_mail and PHPMailer, and by default that route needs a working sendmail-compatible mail server on the host. Many hosts do not provide a reliable setup for that route, so an SMTP plugin that connects WordPress to an authenticated mail provider is the usual fix.
Sources
- wp_mail() WordPress Developer Resources
- Mail – Advanced Administration Handbook WordPress Developer Resources
- More-reliable email in WordPress 6.9 Make WordPress Core
- wp_mail_failed WordPress Developer Resources
- Email sender guidelines Google Gmail Help
- WP Mail SMTP by WPForms WordPress.org
- Configuring the WP Mail SMTP plugin DreamHost
- WP Mail SMTP WP Mail SMTP
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
