Key facts
- Most website forms send their notification email through PHP mail or a basic SMTP connection, both of which major inbox providers increasingly filter or reject without proper sender authentication.
- A CMS, form plugin, or hosting platform update is one of the single most common triggers for a form that worked fine for months and then silently stops emailing.
- SPF, DKIM, and DMARC records tell receiving mail servers whether an email claiming to be from your domain is legitimate; a change to your domain's DNS records can break form email delivery without touching the form itself.
- Many third-party form and email delivery services enforce a monthly sending quota; once a free or low tier plan hits that limit, notifications stop silently until the next billing cycle.
- A form can submit successfully and store the lead's data while still failing to send the notification email, since submission and notification are two separate steps that can fail independently.
The Form Probably Still Works, The Email Doesn't
When a lead form stops emailing you, the instinct is to assume the form itself broke. In practice the form usually still submits and stores the entry fine; it is the notification email, a separate step, that failed to arrive. Confirm this first by checking whether submissions are actually landing somewhere, such as a plugin's entry list, a spreadsheet integration, or your CRM, even though no email showed up.
If the data is there but the email is not, you have already ruled out a broken form and narrowed the problem to email delivery specifically, which is a much smaller and more findable list of causes.
Check the obvious first: your spam or junk folder, any email filtering rule that might route the notification elsewhere, and whether the inbox receiving the notification is even still active and not full.
Something Changed, Even If You Did Not Touch It
Forms that worked for months rarely break on their own. Something changed: a CMS core update, a form plugin update, a hosting provider migration, or a change to your domain's DNS records. Check your site's update history and your hosting provider's change log around the date the emails stopped.
If your form uses a plugin, check whether it has a setting for how it sends mail, since many switched their default sending method in recent versions to require a dedicated SMTP connection instead of the server's basic mail function, and an update can silently reset that setting.
If you or your developer recently changed anything in your domain's DNS, including adding a new tool that touches SPF records, that is worth checking specifically, since a broken SPF or DKIM record can cause receiving mail servers to reject the message outright without ever showing up as an error on your end.
Quiet Limits On Third-Party Email Services
If your form sends notifications through a separate email delivery service rather than your own hosting, check that service's dashboard directly for a sending quota, a suspended account, or a flagged domain reputation issue. Many of these services enforce a monthly sending limit on lower tiers, and once you cross it, notifications stop with no warning to you.
It is also worth checking whether the service flagged your account for a high bounce rate or spam complaint rate elsewhere, which can pause all outgoing mail from your account, not just the lead form's notifications.
If a developer or agency set this up originally, ask them directly which service handles the sending and whether it is on a plan with a limit, since this is the kind of detail that is easy to lose track of once the form has been running quietly for a long time.
Testing The Fix Properly
Submit a real test entry yourself and watch each step: does the confirmation message appear, does the entry save wherever it is supposed to save, and does any email arrive within a few minutes, checking spam as well as your inbox. This tells you exactly which step in the chain is broken.
If you or your developer has access to the hosting control panel, check the server's mail error log or the form plugin's own log for a specific failure message; most sending failures leave a clear reason, such as an authentication failure or a rejected connection, rather than failing silently at that level.
Once fixed, send several test submissions over a couple of days rather than one, since some delivery problems are intermittent and only show up when the receiving mail server is under load or a spam filter changes its rules.
Related questions
Check whether the submitted entry actually saved somewhere, such as a plugin's entries list, a connected spreadsheet, or your CRM. If the data is there but no email arrived, the form itself is working and the problem is specifically with the email notification step, which narrows down what you need to check next.
Yes. Some hosting providers restrict or disable the basic PHP mail function to fight spam, especially after a security incident on their servers, and a plan or policy change can affect your site without any change on your end. Ask your host directly whether outgoing mail is restricted and whether they recommend a dedicated SMTP connection instead.
This usually points to an authentication problem rather than a broken form: a missing or incorrect SPF, DKIM, or DMARC record for your sending domain. Receiving mail servers use those records to decide whether to trust the message, and a recent DNS change, even one unrelated to email, can accidentally affect them.
If your form currently relies on your server's basic mail function, switching to a dedicated SMTP connection or a reputable transactional email service usually improves reliability, since those are built specifically for consistent delivery and give you visibility into failures. This is a reasonable fix even if you eventually find and resolve the original cause.
A quick real test submission once a month is enough to catch a silent failure before it costs you weeks of lost leads. Set a reminder, since most owners only discover a broken form when a customer mentions they submitted it and never heard back, which can mean the problem was live for a while unnoticed.
Want a second opinion on your situation?
Get a free, no-obligation proposal. We’ll look at your site and your market and tell you honestly what we’d do — and what we wouldn’t.
Get your free proposal