Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Fluent Forms Email Notifications Not Working? Step-by-Step Fixes

Fluent Forms Email Notifications Not Working? Step-by-Step Fixes

Short answer

When Fluent Forms email notifications are not working, first check Fluent Forms > Entries to confirm the submission was saved, then open the form's Settings & Integrations > Email Notifications and make sure the notification is enabled, sent to the right address and not blocked by conditional logic. Most remaining cases are fixed by sending WordPress email through an SMTP service.

Key takeaways

  • If the entry is saved, the form works and the problem is email delivery.
  • Check that each notification is enabled, has the right recipient and matching conditions.
  • Use a From address on your own domain and the visitor's email as Reply-To.
  • Route WordPress email through SMTP, for example with the free FluentSMTP plugin.
  • Add SPF, DKIM and DMARC records so receiving servers trust your messages.

How do you know whether the form or the email is failing?

Open Fluent Forms > Entries and look for your test submission; if it is listed, the form works and the email is the problem, but if it is missing, the form itself is failing.

Fluent Forms stores entries by default, which makes this first check quick and reliable. Even when every email fails, the visitor's message is still waiting in the dashboard, so you can reply while you fix the delivery problem.

If the entry is missing, look for error messages on submit, JavaScript errors in the browser console, or a caching or security plugin interfering with the submission.

If the entry is there, move on to the notification settings and then email delivery.

Is the notification enabled and configured correctly?

Open the form, go to Settings & Integrations > Email Notifications, and confirm the notification is switched on, sends to an address you check, and has a sensible subject and message.

Check the Send To field carefully. Typos, an old staff address or the WordPress admin email that nobody monitors are common causes of missing notifications.

If you use a field value as the recipient, make sure that field is required and actually contains an email address.

Save the form after changes and send a new test. Old entries do not trigger new notifications.

Could conditional logic be blocking the email?

Yes. If a notification uses conditional logic, it only sends when the conditions match, so a rule based on an answer nobody chooses means the email never sends.

Review each condition against a real submission. Pay attention to exact values, such as option labels versus option values in dropdowns and radio fields.

Add a catch-all notification without conditions while you test, so you can see whether conditional routing is the cause.

Did something change recently?

If notifications worked before, list recent changes such as a host move, DNS edits, a new SMTP plugin, an expired API key or plugin updates, since these are the most common triggers.

Moving hosts or email providers often removes or replaces SPF and DKIM records. Emails that were fine for years can start failing overnight.

SMTP API keys and app passwords can expire or be revoked. Reconnect the SMTP plugin and send a test from its settings to confirm it still works.

A short change log for hosting, DNS and email settings makes these problems much faster to trace next time.

Is the From address causing problems?

Often yes. Set the From email to a single address on your own domain and put the visitor's email in Reply-To, since sending as the visitor or from a free email service looks forged to receiving servers.

Mailbox providers check whether the sending server is allowed to send for the From domain. A Gmail address sent from your web host fails that check and is often rejected.

An address such as [email protected] works well. If you use an SMTP service, verify that domain with the service.

Why does WordPress fail to send mail by default?

WordPress sends mail through the server's PHP mail function unless told otherwise, and many hosts restrict it while many inboxes distrust it, so messages are dropped or filtered.

This affects every form plugin, password resets and store emails, not just Fluent Forms.

The WordPress wp_mail function reference explains that it relies on the server's mail setup unless an SMTP plugin changes it.

How do you fix delivery with SMTP?

Install an SMTP plugin, such as the free FluentSMTP from the Fluent Forms team, connect it to an email service or your mailbox's SMTP server, and send a test email from the plugin.

The FluentSMTP plugin page lists the email services it connects to, including several transactional email providers.

Use only one SMTP plugin at a time. Two plugins trying to control mail often cause failures that are hard to trace.

Our guide on setting up SMTP in WordPress walks through the process in general terms.

Are your domain's email records in place?

Add SPF, DKIM and DMARC records for your sending domain using the values from your email service, so receiving servers can confirm your messages are genuine.

Large mailbox providers now expect authentication from senders. Google's email sender guidelines describe the requirements.

Our guide on setting up SPF, DKIM and DMARC for WordPress email explains each record.

The DMARC.org overview is a helpful background read if these terms are new.

Are notifications landing in spam?

Check spam and junk folders, mark test messages as not spam, and improve authentication and subject lines if they keep landing there.

Keep subjects plain and descriptive, such as New enquiry from your website, rather than all capitals or sales language.

Company inboxes may quarantine messages before they reach spam. Ask your IT team to check filters if emails go to a work address.

How do you confirm WordPress tried to send the email?

Use the email log in your SMTP plugin to see whether a message was sent after the test submission and whether it shows an error.

No log entry means the notification never fired, so the issue is in Fluent Forms settings or a conflict. An entry with an error points to the sending setup.

FluentSMTP and many other SMTP plugins include logs and a resend option, which helps you recover messages after fixing the problem.

What if only some notifications fail?

When some emails arrive and others do not, compare the failing notifications with the working ones: recipients, conditions, From address, attachments and message length often differ.

Large attachments from file upload fields can exceed mail size limits. Linking to uploaded files instead of attaching them usually solves this.

Notifications sent to external domains may be filtered more strictly than those sent to your own mailbox. Test with addresses at several providers.

Could another plugin or the host be interfering?

Yes. Security plugins, caching, another mail plugin or host-level mail limits can stop or alter outgoing email, so test with conflicting plugins disabled on a staging site and ask your host about mail limits.

Some shared hosts block outgoing SMTP ports. Many email services offer an API connection over HTTPS that avoids blocked ports.

Our guide on setting up a staging site for WordPress shows how to test conflicts safely.

Why does the confirmation email to the visitor fail?

The visitor confirmation fails when its Send To field is not mapped to the form's email field, the email field is optional and empty, or general delivery problems affect it too.

Open that notification and select the email field from the smart codes for the recipient.

Make the email field required and use the Email field type, so addresses are validated before submission.

How do you stop the problem from returning?

Keep SMTP connected and monitored, test each important form monthly and after updates or hosting changes, and rely on stored entries as a backup record.

A monthly test takes a minute and catches silent failures before they cost enquiries. Put a recurring reminder in your calendar so it actually happens.

For business-critical forms, send notifications to a shared inbox as well as one person, so a single filtered mailbox does not mean a lost lead.

Frequently asked questions

Why is Fluent Forms not sending email notifications?

Common causes are a disabled notification, a wrong recipient, conditional logic that never matches, a From address on a free email service, or WordPress sending through the server's basic mail function.

Where are Fluent Forms email notification settings?

Open the form and go to Settings and Integrations, then Email Notifications. There you can enable notifications, set recipients, subjects, messages and conditional logic.

Does Fluent Forms save entries if the email fails?

Yes, by default. Check Fluent Forms then Entries. If the submission is listed, the form worked and the problem is with email delivery.

Which SMTP plugin works with Fluent Forms?

Any reliable SMTP plugin works. The same team makes the free FluentSMTP plugin, which connects to many email services and includes email logs.

Why do Fluent Forms emails go to spam?

Usually because the domain lacks SPF, DKIM or DMARC records, the From address uses a free email service, or emails are sent through the server's basic mail function.

Sources

  1. wp_mail() WordPress Developer Resources
  2. FluentSMTP plugin WordPress.org Plugins
  3. Email sender guidelines Google Workspace Admin Help
  4. Overview DMARC.org
  5. Fluent Forms plugin WordPress.org Plugins

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.