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

Forminator Email Notifications Not Working? How to Fix Them

Forminator Email Notifications Not Working? How to Fix Them

Short answer

When Forminator email notifications are not working, first confirm the submission was saved under Forminator > Submissions and that the notification is enabled with the right recipient. Then set the From address to one on your own domain and send WordPress email through an SMTP service, since the server's basic mail function is the most common cause of missing emails.

Key takeaways

  • Check Submissions first: if the entry exists, the form works and the problem is email delivery.
  • Make sure notifications are enabled and sent to an address you actually check.
  • Use a From email on your own domain and put the visitor's email in Reply-To.
  • An SMTP service plus SPF, DKIM and DMARC records fixes most delivery problems.
  • Test with an email log so you can see whether WordPress tried to send the message.

How do you tell whether the form or the email is the problem?

Open Forminator > Submissions and look for the test entry; if it is there, the form worked and the problem is email delivery, but if it is missing, the form itself is failing.

This single check saves a lot of time. Most people assume the form is broken when the entry was saved perfectly and only the email went missing.

If the entry is missing, look for error messages when submitting, JavaScript errors in the browser console, or a caching or security plugin blocking the submission.

If you are setting up a new form, our guide on adding a Forminator form to WordPress covers each setting from the start.

Are the notifications set up correctly?

Open the form, go to its Email Notifications settings, and check that the admin notification exists, is enabled, and sends to the right address with a sensible subject and message.

Typos in the recipient address are surprisingly common. So is a recipient set to the WordPress admin email, which may be an old or unmonitored inbox.

If you use conditional routing, check that the conditions match real submissions. A rule based on a field value that never appears means the email never sends.

Save the form after any change, then submit a new test entry using an address you can check right away. Old entries will not trigger new notifications.

Is the From address causing the problem?

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

Mailbox providers check whether the server sending an email is allowed to send for the domain in the From address. A Gmail or Yahoo address sent from your web host fails that check.

An address like [email protected] is ideal. It does not need to be a full mailbox if your SMTP service handles sending.

Why does WordPress fail to send emails?

By default WordPress sends mail through the server's PHP mail function, which many hosts limit or block and many inboxes distrust, so messages are dropped or filtered as spam.

This affects every form plugin, not just Forminator, as well as password resets and WooCommerce emails.

The reliable fix is to route all WordPress email through an authenticated SMTP service or email API. Our guide on setting up SMTP in WordPress shows how to do it with a plugin.

Our broader guide on fixing WordPress not sending emails covers other causes that affect the whole site.

Are your domain's email records set up?

Add SPF, DKIM and DMARC records for the domain you send from, using the values your SMTP or email provider gives you, so receiving servers can verify your messages.

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

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

The DMARC.org overview is a good background read if the terms are new to you.

Are the emails going to spam?

Check the spam and junk folders, then mark a test message as not spam; if emails keep landing there, improve authentication, avoid spammy subject lines and keep the message short and clear.

Subjects in all capitals, lots of links or only an image can trigger filters. A plain subject such as New contact form message from your site works better.

If emails go to a company inbox, ask the IT team whether a filter or quarantine is catching them. Corporate filters can be stricter than personal ones.

How do you confirm WordPress tried to send the email?

Install an email logging plugin, or use the log in your SMTP plugin, then submit the form and check whether a message was recorded and whether it shows an error.

If no message appears in the log, the notification never fired, so the problem is in the form settings or a conflict. If it appears with an error, the problem is the sending setup.

Logs turn guesswork into a clear answer. Many SMTP plugins also offer a test email button that shows the exact error from the mail server.

Could another plugin be interfering?

Yes. Another SMTP or mail plugin, a security plugin or a caching rule can stop or change outgoing mail, so test with conflicting plugins disabled on a staging site.

Running two SMTP plugins at once is a common mistake. Keep only one plugin in charge of sending mail.

Our guide on setting up a staging site for WordPress shows how to test plugin conflicts without risking the live site.

Why does the auto-reply to the visitor fail?

The visitor's confirmation usually fails because the To field is not mapped to the form's email field, the email field is empty or mistyped, or the same delivery problems affect the auto-reply.

Open the auto-reply notification and make sure the recipient uses the form's email field rather than a fixed address.

Make the email field required, so every submission includes an address to reply to, and use the Email field type so obvious typos are caught before the form is sent.

Does your host block outgoing email?

Some hosts block or limit outgoing mail on shared plans, or block the ports SMTP uses, so ask your host whether PHP mail and outbound SMTP ports are allowed.

If the host blocks standard SMTP ports, many email services offer an API connection over HTTPS instead. SMTP plugins usually support these APIs directly.

Hosts sometimes suspend mail after a spike in sending, such as a spam attack on an unprotected form. Check your hosting dashboard for mail limits or notices.

Protecting the form with a CAPTCHA and honeypot reduces junk submissions, which keeps your sending volume and reputation healthy. Our guide on stopping contact form spam explains the options.

Did a recent change break the emails?

If notifications worked before, look at what changed recently, such as a new host, DNS changes, a new SMTP plugin, an expired API key or an update to Forminator or WordPress.

DNS changes are a frequent cause after moving hosts or email providers. If SPF or DKIM records were removed or replaced, previously reliable emails can start failing overnight.

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

Keeping a note of changes to hosting, DNS and email settings makes this kind of problem far quicker to trace.

How do you prevent the problem from coming back?

Keep an SMTP service connected, monitor its sending log, test the form after major updates or hosting changes, and keep stored entries as a backup record of every submission.

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

If the form is business-critical, also send notifications to a second address, such as a shared team inbox, so one filtered mailbox does not mean a lost lead.

Frequently asked questions

Why is Forminator not sending emails?

Usually because WordPress sends mail through the server's basic PHP mail function, which hosts often block and inboxes distrust. Set up SMTP and use a From address on your own domain to fix it.

Where are Forminator email notification settings?

Open the form in Forminator and go to its Email Notifications settings. There you can edit the admin notification, add auto-replies, set recipients and change the subject and message.

How do I know if Forminator saved the submission?

Go to Forminator then Submissions and select the form. If the entry is there, the form worked and the problem lies with email delivery rather than the form itself.

Why do Forminator emails go to spam?

Missing SPF, DKIM or DMARC records, a free email address as the sender, or spammy subject lines can cause it. Authenticate your domain and send through an SMTP service.

Should I use the visitor's email as the From address?

No. Use an address on your own domain as the From email and put the visitor's email in the Reply-To field. Sending as the visitor looks forged and is often blocked.

Sources

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

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.