WordPress Contact Form Not Sending Emails? Causes and Safe Checks
When a WordPress contact form stops sending emails, the form usually works but the email is not delivered. The common causes are the server sending mail without proper authentication, spam filtering, a changed recipient address, a plugin conflict or a form plugin setting. Testing the whole path from submission to inbox finds the break.
Why this problem costs more than it looks
A form that silently fails is worse than one that visibly breaks. Visitors see a success message, you receive nothing, and enquiries are lost for weeks before anyone notices. If your website exists to generate enquiries, checking form delivery is one of the most valuable routine tests you can run.
Where the email can get lost
| Stage | What can go wrong |
|---|---|
| Form plugin | Wrong recipient, disabled notification, validation or spam setting |
| WordPress | Mail function unavailable or blocked by the host |
| Server | Mail sent without authentication so it is treated as suspicious |
| Receiving mail provider | Message filtered to spam or rejected |
| Your inbox | Rules, full mailbox or an address that has changed |
Not sure what is going on with your website?
Tell us what you are seeing and we will outline the next step before any chargeable work.
How to test properly
- Submit the form yourself from a different device and address
- Check spam and junk folders, and any mail rules
- Confirm the recipient address in the form settings
- Check whether the form plugin records entries so you can see submissions even if email fails
- Test again after any change, including after plugin updates
What a reliable setup looks like
Reliable form delivery generally means sending through an authenticated mail service rather than the web server directly, so receiving providers trust the messages. It also means a copy of each submission is stored in WordPress, so a delivery problem never means a lost enquiry. Ideally you also test the form on a schedule.
Related things to check
- Spam protection plugins that block genuine submissions
- Caching that serves a stale form with an expired security token
- Domain email records such as SPF and DKIM that affect delivery
- Hosting limits on outgoing email
SPF, DKIM and DMARC without the jargon
These are three records in your domain’s DNS that tell the world which servers are allowed to send email on your behalf. SPF lists permitted senders, DKIM adds a cryptographic signature so a message can be verified, and DMARC tells receiving providers what to do when a message fails those checks. When a website sends a form notification from your own domain without these records covering it, providers may treat the message as suspicious and put it in spam or reject it.
A checklist for reliable form delivery
- Send through an authenticated mail service, not the raw web server
- Use an address on your own domain as the sender, with the visitor’s address as reply-to
- Confirm SPF and DKIM records include the sending service
- Store entries inside WordPress so no enquiry is ever lost
- Test on a schedule and after every update or hosting change
Spam protection that blocks real people
CAPTCHA and anti-spam tools protect your inbox, but when misconfigured they can reject genuine enquiries without telling anyone. If the form appears to work but you rarely receive messages, review the spam settings, test with a real person on a different network and look for entries recorded in the form plugin. Our WordPress repair service traces forms end to end, and a maintenance plan keeps updates from quietly breaking them again.
Forms that look fine but lose enquiries
The most worrying form failures are the invisible ones. The visitor sees a “thanks” message, so they assume their enquiry reached you, while nothing arrives. They may not try again, and you never learn that you lost them. Because the failure is silent, it can last for weeks. The defence is to test the form after any change, store submissions inside WordPress so you have a record, and set up a scheduled test that alerts you when a message fails to arrive.
What to include in your request for help
Tell your developer which form is affected, which email address should receive it, when you last received a genuine submission and whether anything changed since, such as a plugin update, a hosting change or a new email provider. Mention any spam-protection tools in use. With that information, tracing the problem from submission to inbox is quick. If you would like us to test your forms and set up a reliable delivery path, ask about WordPress repair or contact WP Mate.
Testing forms as a customer would
Test forms the way a real visitor uses them: from a different device, on a different network, using a plain email address with no special treatment, and without being logged in. Submit realistic content, including a longer message, since some filters treat short or odd messages differently. Check both the notification you receive and any confirmation the visitor sees. Then repeat the test a day later, because some delivery problems only show up as spam filtering catches up. Record the results. A simple monthly test, noted in a log, would catch most silent failures before they cost you an enquiry.
Getting it fixed
WP Mate traces the form from submission to inbox, fixes the break and tests it end to end. See WordPress repair or ask us to check your forms. A maintenance plan keeps updates from quietly breaking them again.
Want this looked after for you?
WP Mate maintenance plans cover managed updates, daily offsite backups, security scanning and 24/7 uptime monitoring.
Not sure what's wrong? Tell us and we'll outline the next step.
Services related to this guide
WordPress repair
Broken website? We investigate the cause and fix it safely.Get a Repair Quote →
WordPress support
Friendly Australian support for your WordPress website.Get WordPress Help →
Talk to WP Mate
Not sure which service fits? Ask us and we will point you the right way.Contact us →
Related guides
Frequently asked questions
Why do form emails go to spam?
Usually because the message is sent by the web server without proper authentication, so receiving providers cannot verify it.
Should I use my own email as the sender?
It is better to send from an address on your own domain through an authenticated service, with the visitor’s address as the reply-to.
How often should I test my contact form?
After any update or hosting change, and on a regular schedule, because failures are usually silent.
Ready to get your website sorted?
Based in Warrnambool, Victoria, helping Australian businesses online. Tell us what is happening.
Tell your mate what's going wrong.
Send us a few details and we’ll work out the next step. Please don’t include passwords or payment details.
- Australian support in plain English
- Clear scope and next steps before chargeable work
- Backup and recovery plan before live changes
