[Fixed] Gravity Forms Not Sending Email

Quick Fix: Gravity Forms notification failures are usually caused by PHP mail() limitations or "From Address" spoofing. To fix this: 1. Ensure the "From Email" matches your site's domain. 2. Install an SMTP plugin (like WP Mail SMTP) to authenticate your emails. 3. Check for "Routing Logic" conflicts in your notification settings. For zero-risk monitoring, use FormWatch to alert you the second a lead fails to deliver.

Gravity Forms is the "Gold Standard" for WordPress, but even the best plugins are at the mercy of your web server. If your entries are showing up in the WordPress dashboard but not in your inbox, you are experiencing a notification delivery failure.

In this guide, we’ll skip the basics and dive into the high-level technical reasons why Gravity Forms notifications silently disappear.

1. The "Spoofing" Filter (The #1 Killer)

By default, many users set the "From Email" in Gravity Forms to the {admin_email} or, worse, the visitor's email address. If your website is myagency.com but it sends an email claiming to be from customer@gmail.com, your hosting server (and the recipient's inbox) will flag this as "Email Spoofing."

• The Fix: Navigate to Forms > Settings > Notifications. Edit your Admin Notification. Ensure the From Email is a verified address on your actual domain (e.g., notifications@myagency.com).
• Pro Tip: Use the "Reply-To" field for the visitor's email so you can still respond directly.

2. "Could Not Instantiate Mail Function" Error

If you check your Gravity Forms System Report and see this error, it means your host has disabled the PHP mail() function entirely. This is common on "Secure" or "Managed" WordPress hosting (like WP Engine or Kinsta) because PHP mail is unauthenticated and prone to spam.

The Fix: You must use a transactional email service. Connect your site to Postmark, SendGrid, or Amazon SES using an SMTP plugin. This replaces the broken local mail function with a professional-grade delivery API.

3. Conditional Routing Dead-Ends

Gravity Forms allows you to send notifications to different people based on form choices (e.g., "If Department is Sales, send to sales@"). If a user selects an option that you haven't mapped to an email address, the notification simply doesn't trigger. No error is thrown; the lead just vanishes into the database.

The Fix: Always set up a "Fallback" notification with no conditional logic to ensure every lead has a destination, even if the routing fails.

4. Conflict with Caching and "Object Cache"

In 2026, many sites use aggressive Object Caching (Redis/Memcached). Sometimes, the "Nonce" (a security token) used by Gravity Forms is cached too long. When a user submits the form, the token is expired, the submission is rejected, and no notification is ever generated.

FAQ: Troubleshooting Gravity Forms Notifications