Blog

Contact Form Not Sending Emails? 9 Causes and Fixes

Published 16 October 2026 · Last updated: 16 October 2026

When notification mail stops, you do not have a “small email problem”—you have a risk of silent lead loss. Work the checklist below, then make sure every submission is stored even if the inbox fails.

Quick Answer

Why is my contact form not sending emails?

Start with spam and the recipient address, then check SMTP/host blocks, SPF/DKIM/DMARC, rate limits, plugin failure, JavaScript errors, and cache. Always confirm the lead was stored—if email is the only copy, a delivery failure means a lost enquiry.

Diagnostic checklist (tick as you go)

Use this interactive list while you troubleshoot. It covers the nine causes below and surfaces the highest-priority unchecked fix so you do not jump to DNS before you have opened spam.

Interactive diagnostic checklist

0 of 9 checked

Tick what you have already verified. We highlight the highest-priority unchecked item to fix next.

Fix this next

Checked spam / junk (and promotions) for the notification sender

Search the inbox for the form tool’s from-address and mark it Not spam / whitelist it.

Nine common causes and how to fix them

  1. Spam or junk folder. Notification emails often come from a noreply or form-tool domain. Filters push them to spam, promotions, or a client quarantine. Search the inbox for “form”, “lead”, or the tool name, then whitelist the sender. Have a teammate check their junk too if alerts go to a shared alias.
  2. Wrong recipient address. A typo in the notification field, an ex-employee’s mailbox, or a form that still points at an old alias will look like “email never sends.” Open settings, confirm the address, and send a test submission after every recipient change.
  3. SMTP or host mail blocked. WordPress plugins and shared hosts often send through the server’s PHP mail. Providers rate-limit or block that path when reputation is poor. If tests never leave the server, move alerts to a transactional email service—or use a form product that sends notifications on its own infrastructure.
  4. SPF, DKIM, or DMARC misalignment. When you send from your domain through a third party, DNS auth must match. Failures can mean spam placement or silent rejection. Align SPF/DKIM with the sending service and keep DMARC in a monitoring mode until reports look clean.
  5. Rate limits or plan caps. Free tiers and SMTP providers sometimes cap messages per hour or month. Auto-replies plus team alerts count as two sends per lead. If notifications stop mid-campaign, check usage before rewriting the form.
  6. Form plugin or integration failure. A deactivated plugin, expired license, or broken webhook means the submit never creates a record—so no email fires. Confirm a new submission appears in the form’s storage. No row means fix capture first, not SMTP.
  7. JavaScript errors on the page. Theme scripts, chat widgets, and tag managers can break the submit handler. The button looks fine; the request never completes. Open the browser console, submit once, and fix any red errors before blaming email delivery.
  8. Caching serving a stale form. Full-page or CDN cache can keep an old embed or an outdated action URL live after you change settings. Purge the page cache, retest in a private window, and confirm the live form ID matches the one you configured.
  9. No backup copy of the submission. If the only path is “email me the fields,” a single delivery failure loses the lead forever. Store every submission in a leads table or database first, then send the alert. Email becomes a notification channel—not the only copy.

How to monitor so a failed email never loses a lead

The durable fix is architectural: store every submission first, then notify. A leads table (or database row) is the source of truth. Email is a signal that something new arrived. If the signal is delayed or filtered, you can still open the dashboard and act.

LeadFormHub is built that way. Every submission is saved to your leads table with search, filters, notes, and follow-up dates. On Pro and Business, turn on email alerts so your team is notified when a lead is created—without relying on WordPress SMTP or a plugin chain. Free plan users should check the dashboard on a fixed cadence until they upgrade. For the “happy path” setup once delivery works, read contact form with instant email notification.

Add a weekly smoke test: one real submission from a private window, confirm the row, confirm the alert (paid plans), and confirm spam is clear. Pair alerts with a fast follow-up process so inbox recovery does not become the bottleneck. Product scope and plan gates are summarised on the lead generation form builder page and pricing.

When to replace a fragile plugin stack

If you repeatedly fight host mail, plugin updates, and cache plugins just to get one alert, consider a dedicated lead capture tool. You still embed or share a form, but notifications and storage are not tied to your theme. That is especially useful for ad landing pages where a silent failure burns spend. See form builders with auto email response if you also want a submitter confirmation on paid plans.

Frequently asked questions

Why is my contact form not sending emails?

Most cases are spam filtering, a wrong notification address, host SMTP blocks, DNS authentication issues, plan rate limits, a broken form plugin, JavaScript errors, or stale cache. Confirm the submission is stored first, then fix delivery.

How do I test if contact form emails are working?

Submit the form yourself, note the exact time, check inbox and spam for the notification, and confirm a new row exists in your form or leads dashboard. If the row exists but mail does not, the problem is delivery—not the form.

Should contact form emails go to spam?

They can, especially from shared noreply domains or misaligned SPF/DKIM. Whitelist the sender and fix DNS if you send from your domain. Do not assume silence means the form failed.

How do I stop missing leads when email fails?

Store every submission in a leads table and treat email as an alert. LeadFormHub keeps every lead in the dashboard; email alerts are available on Pro and Business so a spam filter cannot erase the record.

Does LeadFormHub send email alerts on the Free plan?

No. Free stores leads in the dashboard so you can check on a cadence. Instant email alerts on new leads are available on Pro and Business. Auto-reply to submitters is also a paid-plan capability.

What is the difference between a notification and an auto-reply?

A notification goes to your team with the lead details. An auto-reply goes to the person who submitted to confirm receipt. You usually want both, but they are separate settings—and both count toward email limits if your provider meters sends.

Next step

Run the checklist, confirm every test creates a stored lead, then enable alerts on Pro or Business so the inbox is a backup signal—not the only one. Start free or compare plans on pricing.

Get Started with LeadFormHub Today

Secure sign-up · Your data is protected with SSL encryption.