SecureSMTP
Free trial

Fluent Forms not sending email? Here’s why, and how to fix it

Fluent Forms submissions arrive in the dashboard but the notification email never lands? It’s a wp_mail() problem, not a Fluent Forms bug. Here’s the fix.

5-minute readLast updated · June 2026Fluent Forms setup guide →

You built a beautiful contact form with Fluent Forms. You added an email notification under Settings → Email Notifications. You set up conditional logic to route different inquiry types to different teams. You tested once — perfect. The email arrived.

Six weeks later, a customer messages you on social media asking why you never responded to their contact form submission. You check Fluent Forms: the entry is there, dated last week. Your inbox: nothing. Spam folder: nothing.

Fluent Forms isn’t broken — but WordPress is. Here’s why and how to fix it permanently.

Why Fluent Forms email fails

When someone submits a Fluent Forms form, the plugin does two things:

  1. Stores the submission in WordPress’s database (you see it under Fluent Forms → Entries)
  2. Calls WordPress’s wp_mail() function to send the notification email

Step 2 is where everything breaks. wp_mail() is a thin wrapper around PHP’s mail() function, which by default sends from [email protected] — an address that fails SPF, DKIM, and DMARC checks at Gmail, Outlook, and Apple Mail. The message either:

  • Lands silently in the recipient’s spam folder
  • Gets dropped entirely by aggressive corporate filters
  • Gets delayed by hours when shared hosting mail queues back up

Fluent Forms’ entry log shows the submission as “Successful” because, from the plugin’s perspective, it successfully passed the data to wp_mail(). What happens after that is invisible to Fluent Forms.

Every WordPress form plugin has this problem

Contact Form 7, WPForms, Gravity Forms, Forminator, Elementor Forms, Ninja Forms — every form plugin built on wp_mail() hits the same underlying deliverability problem. The fix is the same too: replace the unauthenticated wp_mail() handler with one that signs and routes through reputation-clean infrastructure.

Diagnose your Fluent Forms delivery problem

Four-step check:

  1. Submit your own form with a Gmail address you control. Wait 5 minutes. Check inbox AND spam.
  2. Check Fluent Forms entries. Fluent Forms → Entries. Your test should be there. If yes, the form is working — only the email step is broken.
  3. Check the notification settings. Open the form → Settings & Integrations → Email Notifications. Make sure the notification is on and the Send To address is right.
  4. Run mail-tester.com. Submit a form to the mail-tester.com address they provide. Score below 7/10 = delivery problem.

The fix: install the SecureSMTP WordPress plugin

  1. Sign up at securessmtp.com/signup — free tier covers 5,000 emails/month.
  2. Dashboard → Forms → Sites → + Add Site. Copy the site’s API key from the last step. It is shown only once.
  3. WordPress Admin → Plugins → Add New Plugin → Upload Plugin → upload the SecureSMTP plugin .zip → Install Now → Activate.
  4. In wp-admin open SecureSMTP → Settings, paste the key into API Key and click Save and test connection.
  5. Under Email Delivery, tick Route outgoing email through SecureSMTP and save. Until you tick it, WordPress keeps sending with its own mailer.
  6. Submit your Fluent Forms form. Once your sending domain is verified, the email should arrive within a minute.

What changes for Fluent Forms

Fluent Forms continues to use wp_mail() exactly like before. The SecureSMTP plugin takes each call and sends it through SecureSMTP, signed with DKIM and logged. You don’t change any Fluent Forms settings. New accounts send from their own verified sending domain. Older accounts can keep using [email protected] for a limited time, with your sender name, and the original From address becomes the Reply-To.

Verify Fluent Forms email is working

  1. Submit your form again. It should arrive in the inbox within a minute.
  2. Check SecureSMTP → Mail Log in wp-admin. The email is listed with its source plugin and status Sent.
  3. Check the Email log in your SecureSMTP dashboard for the delivery result.
  4. Run mail-tester.com again. Score should be 9+/10.
  5. Check Gmail headers. “Show original” on the test email. DKIM should pass. DMARC passes for your own domain once you send from a verified sending domain (any plan, including Free).

Frequently asked questions

Will this affect my other WordPress plugins' emails?+

Yes — and that's a good thing. The SecureSMTP plugin intercepts every wp_mail() call across WordPress, so every plugin's emails now use authenticated delivery. Fluent Forms, WPForms, WooCommerce, comment notifications, password resets — all routed through SecureSMTP. One install fixes deliverability for the entire site.

Do I need Fluent Forms Pro for this to work?+

No. The fix is at the wp_mail() layer, which is below Fluent Forms. The free version of Fluent Forms uses wp_mail() exactly the same way Pro does, so any fix that addresses wp_mail() addresses Fluent Forms regardless of which version you have. No need to upgrade anything on the Fluent Forms side.

My log says the email was sent. Why didn’t I get it?+

"Sent" only means the email was handed to wp_mail() and then to your server’s mail handler. After that it can still bounce, go to spam or be dropped by the receiving server. With SecureSMTP, the Email log in your SecureSMTP dashboard shows what happened to each email (delivered, bounced and so on). The plugin’s Mail Log in wp-admin shows which plugin sent it and whether it went through SecureSMTP.

Does Fluent Forms have its own SMTP settings?+

No. Fluent Forms sends with wp_mail() and has no SMTP fields. The same team makes a separate plugin, FluentSMTP, which you could point at our SMTP settings (host smtp.securessmtp.com, port 587, username securessmtp, your site API key as the password). With the SecureSMTP plugin you do not need FluentSMTP: it handles wp_mail() for every plugin. Use one of the two, not both.

Can I keep using Fluent Forms' Slack / Discord / Telegram integrations?+

Yes. Those run on Fluent Forms' webhook layer, not the email layer. SecureSMTP only changes how email is sent. Your Slack notifications, Discord webhooks, and other downstream integrations continue working exactly as before.

Will the form submitter see anything different?+

No visible change. They still fill out the Fluent Forms form, click submit, and see your custom success message. The only thing that changes is that any auto-reply email you send to the submitter is sent through SecureSMTP, signed with DKIM, instead of from [email protected]. It comes from your own address once you verify a sending domain, which any plan can add. Older accounts can keep using [email protected] with your sender name for a limited time.

Ready to fix it?

Try SecureSMTP free. Set up SecureSMTP for WordPress →

Related guides

Stop guessing whether your email is landing.

SecureSMTP sends your website and app email with SPF, DKIM and DMARC passing, from your own domain once you verify it, and logs every email. 5,000 free emails a month, no card required.

Start freeSee Fluent Forms setup

More delivery guides

WordPress · 8-min read

Fix WordPress wp_mail() going to spam: the complete diagnostic + fix guide

WordPress sends mail from [email protected] by default — an address that fails SPF, DKIM, and DMARC. Here's why your wp_mail() emails land in spam and how to fix it.

Shopify · 7-min read

Shopify SMTP: why there is no SMTP setting, and how to send from your own domain

Shopify sends store emails itself and has no custom SMTP setting. Here’s how to authenticate your domain in Shopify, and when to send through the SecureSMTP API instead.

Squarespace · 6-min read

Squarespace email troubleshooting: why your form submissions aren't arriving

Form submitted. No email. Here’s how to check Squarespace’s notification settings and forward submissions through Zapier to SecureSMTP.

Webflow · 6-min read

Webflow form delivery: why form notifications go missing, and how to fix it

Webflow forms collect submissions reliably; the notification emails are the weak spot. Here’s how to send them through an automation tool and SecureSMTP instead.

Wix · 6-min read

Wix contact form email not working: how to fix it

Wix contact form submitted but no email arrived? Wix has no SMTP setting, so here’s how to send notifications through Zapier, Make or Velo code instead.

Ghost · 6-min read

Ghost email troubleshooting: when magic links and welcome emails miss

Ghost members not getting magic-link logins or welcome emails? Here’s how to send a self-hosted Ghost’s transactional email through SecureSMTP. Newsletters still need Mailgun.

Mailchimp Transactional · 7-min read

Mailchimp Transactional (Mandrill) email problems: how to diagnose and fix them

Mailchimp Transactional rebrand of Mandrill is confusing, expensive, and shares IPs across customers. Here's why delivery fails and the simpler alternative.

Forminator · 6-min read

Forminator email setup: configure notifications that actually arrive

Forminator notification emails going to spam — or missing entirely? It's WordPress's wp_mail() problem, not Forminator. Here's the fix that works on any host.

WP Mail SMTP · 6-min read

WP Mail SMTP setup with SecureSMTP: the Other SMTP settings, step by step

Use the WP Mail SMTP plugin with SecureSMTP as your SMTP server. The exact Other SMTP settings, how to keep your key out of the database, how to test, and what to do when it fails.