Prices and service limits checked 19 November 2026.
When WordPress is not sending emails, password resets never arrive, order confirmations vanish, and form notifications go nowhere — while WordPress insists everything was sent. WordPress reports success when a message leaves the server, not when it reaches an inbox.
The fix has three parts. First, diagnose where the email breaks: WordPress itself, your host, or the spam filters at the other end. Second, route mail through an authenticated SMTP service instead of your server’s default mail function. Third, publish the SPF, DKIM and DMARC records that prove your domain may send.
In this guide
- The short answer: diagnose first, then fix it properly
- Why WordPress is not sending emails: wp_mail and PHP mail
- Diagnose WordPress not sending emails in 10 minutes
- The three SMTP plugins compared
- Pick your sending service: the free tiers compared
- Step by step: set up SMTP with Brevo and WP Mail SMTP
- Add SPF, DKIM and DMARC records
- Troubleshooting: the three failure modes
- When only the contact form fails
- What it costs at real volumes
- Frequently asked questions
- The verdict
The short answer: diagnose first, then fix it properly
When WordPress is not sending emails, do not start by installing a plugin. Find out which of the three layers is broken first. Check whether WordPress is even trying to send: an email log shows every message attempted. If nothing appears in the log, the problem is inside WordPress — a form, a notification setting, or a plugin conflict.
Then check whether mail leaves your server: the default path uses PHP’s mail() function, and many hosts block it — a common cause of WordPress not sending emails. Finally, check authentication: since February 2024, Gmail and Yahoo require SPF or DKIM. The reliable fix for WordPress not sending emails is a free SMTP plugin plus a transactional email service with a genuine free tier, plus three DNS records — $0 in total for most small sites.
Why WordPress is not sending emails: wp_mail and PHP mail
Every email your site sends goes through one WordPress function, wp_mail(), which hands the message to PHPMailer and then to your server’s PHP mail() function. That design is the root of most cases of WordPress not sending emails. First, no authentication is attached: PHP’s mail() knows nothing about SPF, DKIM or DMARC, and no web server signs your messages with DKIM. Second, the From address usually does not exist: WordPress defaults to [email protected], and no mailbox exists there.
Third, your host may block the route entirely: many shared hosts disable or throttle PHP mail(), and Google Cloud, AWS and DigitalOcean all block outbound port 25 by default. Worst of all, wp_mail() returns true on handoff — not on arrival.
Diagnose WordPress not sending emails in 10 minutes
Work through these checks in order. Each one narrows the problem to a single layer.

Step 1: Send a test email from WordPress itself. Use your SMTP plugin’s test tool, or Tools → Site Health, and send a test to an address you control at a different provider. If it arrives, the problem is specific to one form or notification.
Step 2: Check the email log. Install a plugin that logs mail — FluentSMTP and Post SMTP include logging free — and trigger the failing email again. If the log shows no attempt at all, that is the cause of WordPress not sending emails: it never tried.
Step 3: Read the error, not the success message. If the log shows a failed send, the error names the layer: timeouts mean blocked ports, “Authentication failed” means wrong credentials, and SPF or DKIM rejections mean authentication.
Step 4: Look up your domain’s DNS records. Free tools such as MXToolbox show whether SPF, DKIM and DMARC records exist. Missing records are the most common cause of WordPress not sending emails that reach the inbox.
The three SMTP plugins compared
An SMTP plugin does not send mail itself: it reconfigures wp_mail() so every message goes through the email service you choose. These are the three plugins worth shortlisting, with install counts and ratings from WordPress.org checked in November 2026.
| Plugin | Active installs | Rating | Email log | Paid price |
|---|---|---|---|---|
| WP Mail SMTP | 4+ million | 4.8/5 (5,200+ reviews) | Pro only | Pro $49 first year, then $99/year (1 site) |
| FluentSMTP | 700,000+ | 4.8/5 | Free | $0 — no paid tier exists |
| Post SMTP | 300,000+ | 4.7/5 | Free | Pro from $59.99/year |
WP Mail SMTP is the default choice: the most installed, the easiest setup wizard, and the widest mailer list. Its free version covers the core job for WordPress not sending emails — routing mail through Brevo, Gmail, Mailgun, SendGrid and any SMTP server. The catch: logging, failure alerts, backup connections and smart routing are Pro features, and Microsoft 365, Amazon SES and Zoho Mail need Pro too. Pro costs $49 the first year, then $99 a year. Get it from the WP Mail SMTP page on WordPress.org.
FluentSMTP is the best free option and our recommendation for most sites: completely free, it includes email logs, resending failed mail, multiple connections with automatic fallback, and routing by sender address. It covers Amazon SES and Microsoft 365 free.
Post SMTP is the diagnostic specialist. Its free version includes email logs, a fallback mailer, a weekly summary, and failure alerts by email, Slack or webhook — plus a mobile app that notifies your phone when WordPress is not sending emails. Microsoft 365 and Amazon SES need Pro.
Pick your sending service: the free tiers compared
The plugin is only half the fix for WordPress not sending emails — it needs a service to send through. These are the realistic options, with free tiers and first paid prices checked 19 November 2026.
| Service | Free offer | Limit | First paid plan |
|---|---|---|---|
| Brevo | Free forever, no card | 300 emails/day | $9/month (Starter, 5,000/month) |
| Mailgun | Free, no expiry | 100 emails/day | $15/month (Basic, 10,000/month) |
| Gmail SMTP | Free | 500/day (free Gmail); 2,000/day (Workspace) | $0 |
| SendGrid | 60-day trial only — no permanent free plan | 100/day during the trial | $19.95/month (Essentials, 50,000/month) |
| Amazon SES | No free tier for new accounts; $0.10 per 1,000 emails (see note) | Pay as you go | $0.10 per 1,000 emails |
Brevo is the recommendation for most sites. Its free plan is genuinely free forever: 300 emails a day once approved. Starter is $9 a month for 5,000 emails — see Brevo’s pricing page.
Mailgun’s free plan gives 100 emails a day with no expiry; Basic is $15 a month for 10,000 emails. Note: without a card on file, a free account can only send to authorised recipients, and the old Flex plan no longer appears on its pricing page.
SendGrid is the trap to avoid. Older guides still describe a permanent free plan at 100 emails a day; it was retired in 2025. New accounts get a 60-day trial; when it ends, sending stops until you pay — Essentials starts at $19.95 a month.
Amazon SES is the cheapest at volume and the most fiddly to set up. The headline rate is $0.10 per 1,000 emails, but since July 2026 new accounts start on Essentials at $0.16 per 1,000. Treat SES as a $0.16-per-1,000 service with no free tier unless the AWS pricing page says otherwise.
Step by step: set up SMTP with Brevo and WP Mail SMTP
This walkthrough fixes WordPress not sending emails with WP Mail SMTP and Brevo. It takes about twenty minutes.

Step 1: Create a Brevo account. Sign up at Brevo with your domain email address; approval usually takes a few hours.
Step 2: Verify your sending domain in Brevo. In Brevo, go to Senders & IP, add your domain, then publish the DKIM key.
Step 3: Install WP Mail SMTP. In your WordPress dashboard, go to Plugins → Add New, search for “WP Mail SMTP”, install and activate it — the setup wizard opens automatically. Do this during a quiet hour: saving switches all mail to the new route.
Step 4: Choose Brevo as the mailer. In the wizard, select Brevo and use the one-click connection — API connections work even when your host blocks ports.
Step 5: Set the From name and address. Set the From email to an address on your own domain and tick “Force From Email” so no plugin overrides it.
Step 6: Send the test email. In WP Mail SMTP → Tools → Email Test, send a test to an address at a different provider. Confirm it arrives in the inbox, not spam. Then request a password reset for your own admin account. If both arrive, the transport layer is fixed.
Step 7: Turn on logging if you have it. FluentSMTP and Post SMTP include the email log — the record that proves whether WordPress is not sending emails or the receiver is filtering them.
Add SPF, DKIM and DMARC records
SMTP alone does not prove your mail is legitimate. Three DNS records do that, and without them WordPress not sending emails often becomes WordPress emails going to spam instead.
SPF is a TXT record listing which servers may send mail for your domain; Brevo gives you the entry to include. A domain must have exactly one SPF record, so merge Brevo’s entry into your existing record.
DKIM is a cryptographic signature: Brevo generates a key for your domain, and you publish it as a TXT record. Once DKIM passes, your mail is provably from your domain.
DMARC is a TXT record at _dmarc.yourdomain.com telling receivers what to do when SPF or DKIM fail. Start with a monitoring policy — v=DMARC1; p=none; rua=mailto:[email protected] — and move to p=quarantine after a week of clean reports.
Add these records at your DNS provider and wait up to 48 hours. Verify with MXToolbox, then send a test email and check its headers in Gmail: SPF, DKIM and DMARC should all show “PASS”.
Troubleshooting: the three failure modes
Most cases of WordPress not sending emails fall into three patterns — match yours before changing anything.
Test email works but real emails do not
This is the most common form of WordPress not sending emails, and it almost never means SMTP is broken. The test email uses the From address you configured; real emails use the sending plugin’s. Check the From address on the failing email type first, then the notification address itself.
Emails arrive in spam
When WordPress is not sending emails to the inbox and they land in spam instead, this is an authentication or reputation problem, not a transport problem. Confirm SPF, DKIM and DMARC all pass in the message headers and your From address is on your own domain. Then look at content: image-heavy mail, URL shorteners and spam-trigger words score badly. A new domain starts with no reputation; consistent, authenticated sending over a few weeks builds it.
Nothing arrives anywhere, not even in spam
When WordPress is not sending emails anywhere, not even to spam, the message is being blocked or never left your server. Check the email log for the error. A timeout usually means a blocked port: switch to an API-based mailer connection. An authentication error means wrong credentials — regenerate the API key. A quota error means you hit a daily limit: Brevo stops at 300 a day. If there is no log entry at all, WordPress never attempted the send.
When only the contact form fails
A contact form that shows a success message but never delivers is the purest example of WordPress not sending emails — and it has its own checklist.
First, check the form’s notification settings: confirm the “Send To” address is correct and “From Email” is your domain address. Many forms default From to the visitor’s submitted email, which fails SPF and DMARC immediately. Set From to your domain and put the visitor’s address in Reply-To instead.
Second, check for a plugin conflict: deactivate other form and email plugins one at a time and resubmit the form after each change. Two SMTP plugins active at once will fight over wp_mail(). Our WordPress security checklist covers the plugin hygiene that prevents this, and our guide to how to speed up WordPress explains why piling on plugins hurts.
Third, check spam filtering on the receiving mailbox — a common reason for WordPress not sending emails that seem to vanish. Form notifications are the emails most likely to be filtered, because they contain user-submitted text and links. If the notification reaches Gmail but not your business mailbox, that mailbox’s filter is the suspect, not your site.
What it costs at real volumes
Count a month of real volume before choosing a service.
| Monthly volume | Cheapest honest option | Monthly cost |
|---|---|---|
| 10,000 emails | Brevo Starter | $9 |
| 50,000 emails | SendGrid Essentials | $19.95 |
| 50,000 emails | Amazon SES (Essentials rate) | About $8 |
For most WordPress sites, Brevo’s free tier is the whole answer: 300 emails a day is roughly 9,000 a month. Starter at $9 a month is needed only when daily volume passes 300. For high-volume sites where WordPress is not sending emails cheaply enough, Amazon SES wins on price — 50,000 emails cost about $8, against $19.95 for SendGrid Essentials — but it costs more of your time. FluentSMTP and Post SMTP are free, so Brevo-plus-FluentSMTP costs $0 indefinitely; a WP Mail SMTP log costs $49 for the first year and $99 a year after.
Frequently asked questions
Why is WordPress not sending emails all of a sudden?
WordPress not sending emails all of a sudden usually means the site changed something: a host migrated the site, a plugin updated, or a DNS record expired. Check the email log first — a new error message points at the change. The most common cause is a host blocking PHP mail after a migration, or a DMARC policy moving to reject.
Do I need to pay for an SMTP plugin?
No. FluentSMTP and Post SMTP are free and include email logs, and free WP Mail SMTP handles the core job. WP Mail SMTP Pro costs $49 for the first year, renewing at $99 a year.
Is Gmail SMTP good enough for WordPress?
For a personal blog, yes: Gmail SMTP is free and handles up to 500 emails a day. For a business site, no: it sends from a Gmail address and offers no delivery logs. Brevo gives you a domain From address for the same $0.
Why do my WordPress emails go to spam but the test email does not?
WordPress not sending emails while the test works means the test and real emails differ in From address, content or both. Check the headers of a real message that landed in spam: if SPF, DKIM or DMARC fail, the From address or service is misconfigured. If authentication passes, the content is the problem.
The verdict
WordPress not sending emails is a diagnosis problem before it is a setup problem. The default mail path — wp_mail() through unauthenticated PHP mail — was already fragile, and Gmail and Yahoo’s sender rules since February 2024 made it unreliable. Installing a plugin without diagnosing first moves the failure, not the fix.
The fix for WordPress not sending emails is unglamorous and cheap: find the broken layer with a test email and a log, route mail through an authenticated service, and publish SPF, DKIM and DMARC. For most sites that means FluentSMTP or free WP Mail SMTP, Brevo’s free tier at 300 emails a day, and $0 a month. The whole job takes under an hour; the proof is in a delivered message’s headers.
Do it once, test each email type, and check the log monthly. Email is infrastructure: WordPress not sending emails breaks every password reset and order confirmation.
For hosting, security and monetisation, see our best WordPress hosting guide, our WordPress security checklist, and our guide to how to add AdSense to WordPress.
Prices and service limits checked 19 November 2026. Prices change often; confirm the current offer on the provider’s official pricing page before signing up. Amazon SES’s free-tier terms changed during 2025–2026 and sources disagree on what new accounts receive — check the AWS SES pricing page before counting on any free allowance.