WordPress Not Sending Emails? The SMTP Plugins That Fix It

WordPress Not Sending Emails? The SMTP Plugins That Fix It

Your contact form says “Thank you, your message has been sent.” Nothing reaches your inbox, and customers ask why their order confirmation never came.

With WordPress not sending emails, the form itself may be working fine. WordPress hands each message to your hosting server, and that mail often leaves without the proof Gmail and Outlook look for, so it gets blocked or filed as spam. An SMTP plugin connected to a real mail service, plus a few DNS records on your domain, usually fixes that.

Here’s the setup I’d use to get site mail into your inbox, with a done-for-you path if you get stuck.

Why WordPress isn’t sending your emails

By default, WordPress sends mail through your hosting server with PHP’s mail function. Nothing in that setup proves your domain allowed the server to send for it.

Gmail and Outlook check that proof. Since February 2024, Gmail’s sender guidelines ask every sender to set up SPF or DKIM, two DNS records that tell inboxes which services may send for your domain. Mail without them can be rejected or sent to spam, and your site never hears about it.

Forms add a second problem. Many send the notification “from” the visitor’s own address, say a Gmail account, while the mail actually comes from your server. To an inbox that looks forged. Some hosts also limit or switch off outgoing mail on shared plans, sometimes without telling you.

Check this first (no plugin needed)

Check these before installing a plugin.

  1. Look in the right inbox. Check spam, then the address under Settings → General → Administration Email Address, and the “Send to” address in your form’s notification settings.
  2. Check the notification exists. Open the form’s notification settings and make sure one is turned on. For a store, open WooCommerce → Settings → Emails and check that “New order” is enabled with the right recipient. If your form plugin saves entries, a saved entry tells you the form worked, though not that the email went out.
  3. Test WordPress itself. Log out and request a password reset for your own account. If the reset arrives but form emails don’t, look at the form’s “From” setting. If nothing arrives, the site’s sending is the problem.
  4. Look for an existing setup. You may already have an SMTP plugin installed but still set to the default PHP mailer, which changes nothing. Ask your host whether outgoing mail is limited or switched off on your plan.

If a setting was wrong and fixing it brought the emails back, you may not need a plugin. If nothing arrives anywhere, read on.

The SMTP plugins that fix it

An SMTP plugin sends WordPress emails through a connected mail service, called a “mailer”: Brevo, SendLayer, Google Workspace and others. The plugin is half the fix. The mail service and its DNS records are the other half.

Plugin Best for Free version Paid from Renews at Email log Catch
FluentSMTP Most small sites Everything, no paid tier Free Free Yes, free No step-by-step wizard
WP Mail SMTP Guided setup, paid help Most mailers, test tool $49 first year, 1 site $99 at today’s full price Pro only Logs and Microsoft 365 need Pro
Post SMTP Free log and alerts Log, failure alerts $59.99 a year, 1 site Not shown Yes, free Two serious log bugs in 2025, now fixed

Prices at the time of writing, in USD, before tax.

All three can send through a mail service’s own API (Brevo, SendLayer and others), which works even when a host blocks the usual email ports; a plain SMTP connection still needs those ports open. The real difference is the free version: FluentSMTP and Post SMTP log every email for free, WP Mail SMTP only in Pro.

FluentSMTP: best free option with logs

FluentSMTP routes all site mail through your chosen service and logs every message for free.

What stands out:

  • No paid version: logging, resending, a backup connection and failure alerts are all free.
  • Connects to Gmail, Google Workspace and Microsoft 365 through their own sign-in, plus Brevo, Amazon SES, Mailgun, Postmark and others.

The minus:

  • No step-by-step wizard like WP Mail SMTP’s: you fill in the connection screen yourself, with its documentation open.
  • The Microsoft 365 connection needs an app registered in Microsoft’s Azure portal, a step that trips people up.

Price: free.

On wordpress.org: 700,000+ active installs, updated September 27, rated 4.8 out of 5.

Not for: owners who want a setup wizard and paid support.

This site sends its own mail through FluentSMTP, with the log turned on.

See FluentSMTP on wordpress.org

WP Mail SMTP: best guided setup

WP Mail SMTP is the most installed of the three. Its wizard guides the mail service setup.

What stands out:

  • The free version covers Brevo, SendLayer, Gmail and Google Workspace, Mailgun, Postmark, SendGrid and any other SMTP server.
  • The Email Test tool checks the connection.
  • The Elite plan includes setup by WP Mail SMTP’s own team: DNS records, mailer and a test.

The minus:

  • The email log, failure alerts and backup connection are Pro only.
  • Microsoft 365, Outlook.com, Amazon SES and Zoho Mail mailers are Pro only.

Price: free version, or Pro $49 for the first year (1 site), then $99 a year at today’s full price. Renewals are at full price, and the plan renews automatically unless you cancel. The refund window is 14 days from purchase; renewals aren’t refundable. When Pro expires, Pro features such as email alerts stop.

On wordpress.org: 4+ million active installs, updated October 20, rated 4.8 out of 5.

Not for: owners who want free logs.

See WP Mail SMTP plans

Post SMTP: free log and alerts, keep it updated

Post SMTP is a free plugin with an email log, failure alerts and a built-in check of your domain’s SPF, DKIM and DMARC records.

What stands out:

  • The free log shows every email with its error message.
  • Failure alerts by email, Slack or a browser extension, plus a mobile app.

The minus:

  • Its email log had two serious security holes in 2025 that let attackers read logged emails, password reset links included. Both are fixed in later versions, so keep it updated.
  • One recent update broke the log page and sending on some sites until owners rolled back. Check the log after each update.

Price: free, or Pro from $59.99 a year for 1 site, which adds Microsoft 365, Amazon SES and Zoho Mail. The renewal price isn’t shown and the plan renews yearly. The pricing page promises a 14-day refund, but the refund policy adds conditions, so read it before you buy.

On wordpress.org: 300,000+ active installs, updated September 24, rated 4.7 out of 5.

Not for: owners who’d rather not watch updates closely.

See Post SMTP on wordpress.org

Pick a mail service to send through

Pair the plugin with a sending service:

Service Free Paid from Fits
Brevo 300 emails a day, after account approval $9 a month, 5,000 emails Most small sites and stores
SendLayer Trial, up to 200 emails $60 a year upfront (shown as $5 a month), 1,000 emails a month You want a small paid plan from the start
Your own mailbox Included with Google Workspace or Microsoft 365 Your current plan A low-volume contact form

The daily limit counts every email the site sends: form notifications, order emails and password resets together. A plugin plus Brevo’s free plan costs $0 while you stay under that limit. FluentSMTP with SendLayer costs $60 a year at today’s price.

See Brevo’s free plan

Which SMTP plugin to use

  • If you want it free with a log, use FluentSMTP.
  • If you’d like a wizard and a support team, or someone else to do the setup, use WP Mail SMTP (Elite includes their setup).
  • If you send through Microsoft 365 and don’t want to pay, use FluentSMTP.
  • If Post SMTP already works for you, keep it, keep it updated and check its log after each update.

For a typical small business site, I’d pair FluentSMTP with Brevo’s free plan. It costs nothing, and the log shows you every email the site tried to send.

The free version covers everything: log, resend and a backup connection. Run one SMTP plugin at a time.

Get FluentSMTP

How to set it up with FluentSMTP and Brevo

The clicks take a few minutes. The DNS records can take up to 48 hours to work everywhere, so start with them.

  1. Pick the sending address. Use an address on your own domain, such as hello@yourdomain.com. Every email from the site will come “from” it.
  2. Add your domain in Brevo. Create a free account (Brevo approves it before you can send), add your domain and copy the records Brevo shows: a Brevo code, DKIM and DMARC. Add them where your domain’s DNS is managed, which is not always your host. If you already have a DMARC record, choose the manual setup and keep yours. Then add your sending address as a sender in Brevo.
  3. Create a Brevo API key in your Brevo account and treat it like a password.
  4. Connect FluentSMTP. Install the plugin, open Settings → FluentSMTP, add a Brevo connection, paste the key, enter your sending address as the “From” email and turn on Force From Email, so mail from other plugins uses it too.
  5. Fix the form’s “From”. In your form’s notification settings, set “From” to your sending address and put the visitor’s email in “Reply-To”, so you can still answer with one click.
  6. Send a test. Use FluentSMTP’s test email and send it to a Gmail address you can open.
  7. Check where it landed. It should be in the inbox, not spam. In Gmail, open the message, choose “Show original” and look for SPF, DKIM and DMARC. DKIM should say PASS for your domain. Then send the real form, request a password reset, and for a store open a recent order and use its order actions to resend the new order notification. To test the customer email, send the order details from an order placed with your own email address. Each should arrive and appear in the FluentSMTP log.

If the test fails, read the error in the log first. “Sender not valid” usually means the “From” address isn’t a verified sender in Brevo yet.

Still not working? Have it fixed

Get help if you can’t reach your domain’s DNS settings, run a store with live orders and don’t want to experiment, or completed the setup but mail still lands in spam.

On Fiverr, an SMTP setup with one mail service and a test email usually costs $20-40. With SPF, DKIM and DMARC records written and checked for your domain, expect $40-80, plus Fiverr’s service fee.

Before ordering, read how to hire someone to fix WordPress email and contact forms for access, the brief and checks before accepting the work.

Summary

When WordPress is not sending emails, look at the route the mail takes before you blame the form. An SMTP plugin, a mail service and the DNS records it asks for move your mail off your hosting server, and checking the real inbox shows whether it worked. If DNS is the part you’d rather not touch, a small Fiverr order covers it.

FAQ

Is a free SMTP plugin enough?

Yes, for most small sites. FluentSMTP is free with no paid tier, and the free WP Mail SMTP covers the common mail services. You pay for extras like WP Mail SMTP's email log, alerts or Microsoft 365 connection, not for sending itself.

Why do my emails still go to spam after setting up SMTP?

Common reasons: the domain isn't verified at the mail service yet, or the DNS records haven't spread, which can take up to 48 hours. Check that the "From" address is on your verified domain and that DKIM shows PASS in Gmail's "Show original".

The test says "sent", but nothing arrives. Why?

"Sent" means WordPress handed the message on without an error, not that an inbox accepted it. Check the plugin's log and your mail service's own log: the service may have rejected an unverified sender, not approved a new account yet, or hit a daily limit such as Brevo's 300 free emails.

Can I send through my Gmail or Outlook account?

Yes, for a small contact form. FluentSMTP connects to Gmail, Google Workspace and Microsoft 365 for free; WP Mail SMTP connects Gmail free and Microsoft 365 in Pro. For order emails, a dedicated mail service such as Brevo fits better.

Can I get back the messages I missed?

Only if your form plugin saved the entries, or an email log was already running when they were sent. A log you install today records mail from now on; it can't recover emails WordPress tried to send before.