Skip to content
WordPress November 17, 2026 4 min read

WordPress Form Not Sending Email? How to Fix It

When a WordPress form is not sending email, start with the sender address, SPF and DKIM, and SMTP setup. Here is the order we check things in.

Parameter
Parameter
Author

A contact form that stops delivering email almost never tells anyone. The visitor sees a friendly thank-you message, your inbox stays empty, and the problem comes to light weeks later when a customer calls to ask why nobody replied. If your WordPress form is not sending email, the fix is usually quick once you find where the message dies. This is the order we check things in.

Confirm the Form Is Actually Failing

Submit a test yourself and read the response closely. In Contact Form 7, the Contact Form 7 FAQ explains the colors:

  • Red border: the plugin tried to send with wp_mail() and it failed. The cause could be a bad mail setup or a mail server that is down. Your host can check the error logs.
  • Orange border: a spam module (Akismet, reCAPTCHA or the disallowed list) flagged the submission. Turn on spam logging to see which one.
  • Green "sent" message: PHP handed the mail off fine. If it never arrives, it was lost or filtered after that, often by a spam filter.

The red and orange cases show the same error text on purpose, so visitors can’t tell which one happened. A spinner that never stops is a different problem, usually a plugin or theme conflict.

One more thing: Contact Form 7 does not save submissions. Install Flamingo now so you don’t lose leads while you troubleshoot. Other form plugins word things differently, but the questions stay the same. Did WordPress hand the message off, and did it arrive?

Why a WordPress Form Stops Sending Email

The same few causes show up again and again when a WordPress form is not sending email:

  • The host blocks or limits PHP mail, which often starts right after a host move.
  • The domain has no SPF, DKIM or DMARC records, or they point at the wrong servers.
  • The From address uses the visitor’s Gmail or Yahoo address instead of your own domain.
  • The default wordpress@yourdomain mailbox doesn’t exist, and the host refuses to send from it.
  • The mail arrives fine but lands in spam.
  • A shared IP has a bad reputation. With Gmail, a 550 5.7.1 error can mean that IP is on a suspended list.

Fix the Sender: From Address, SPF, DKIM and DMARC

Contact Form 7’s mail setup guidance gives the basics. Use a From address on your own domain. Put the visitor’s address in Reply-To using the "Additional headers" field. Create a real wordpress@yourdomain mailbox, since WordPress also sends comment and new-user notices from it. Set a sender name, or mail goes out as "WordPress." Don’t leave the message body empty, and make sure your headers still work when optional fields are blank.

Then check authentication. Under Google’s sender guidelines, all senders to Gmail have needed SPF or DKIM since February 1, 2024. Unauthenticated mail can go to spam or be rejected with a 5.7.26 error. Your SPF record should list every third-party sender. DKIM keys need to be at least 1024 bits, and Google recommends 2048. Set up both. Only one of them has to align with your From domain. Gmail has also been enforcing these rules more strictly since November 2025.

Switch to Authenticated SMTP and Turn On Logging

PHP mail is the weak link. Send wp_mail() through authenticated SMTP with an SMTP plugin connected to your mailbox or a transactional email provider. Confirm that the provider signs mail for your domain with SPF and DKIM. Then turn on the plugin’s email log, if it has one. A log shows whether the message left WordPress and what the receiving server said back. That cuts most of the guesswork.

Rule Out Plugin Conflicts and Host Changes

On a staging copy, turn off your other plugins and switch to a default theme, then test again. Contact Form 7 4.8 and later submit through the REST API, so a security plugin that disables the REST API will break the form. If emails show raw codes like [foobar], a mail-tag doesn’t match any field in the form. This is the routine work Parameter’s WordPress maintenance plans are built around.

After a migration, look at DNS first. SPF often still points at the old host, and the DKIM keys may not have moved with the site. Our post-migration recovery example walks through that cleanup. If the move also broke the site itself, see our guide to fixing database connection errors.

Keep It From Failing Silently Again

Send a test submission on a schedule and confirm it arrives. Review the delivery log every so often. If you send to Gmail users, set up Postmaster Tools.

Then decide who owns this. After a host move or a custom build, form email tends to fall between the developer, the host and whoever manages DNS. Each assumes someone else is watching. Write down who owns the SMTP account, the DNS records and the monitoring. At Parameter, we treat form delivery as part of ongoing site operations, not a launch checklist item that never gets looked at again. That way a WordPress form not sending email gets caught by a check, not by a customer. Our frequently asked questions cover how that handoff works.

Want WordPress to feel handled?

Self-serve onboarding takes minutes. Parameter takes care of the rest, hosting, ops, and improvements when you need them.