Key takeaways
- A true return from wp_mail(), a green Contact Form 7 notice or a passing SMTP test only means the message was handed off. None of them proves it reached an inbox.
- Contact Form 7 shows the same error text for spam blocks and mail failures. The border colour tells them apart: orange is a spam module, red is a failed mail call.
- Installing WP Mail SMTP changes nothing until you pick a real mailer. Its default PHP Mailer option leaves delivery exactly as it was.
- Put an address on your own domain in From and the visitor’s address in Reply-To. A visitor’s Gmail address in From looks like spoofing to the receiving server.
- In one review of 150 confirmed public cases, the missing email was sitting in spam only 8 times. Check spam, but don’t stop there.
The visitor sees a success message, but the email never reaches your inbox. Often nobody notices for weeks, until enquiries slow down or a customer phones to ask why nobody replied. The form plugin is rarely broken. The message stopped somewhere between the form and the inbox, and the fix depends on where.
WordPress doesn’t run a mail server. WordPress’s mail handbook says wp_mail() hands messages to PHP’s mail() by default, which depends on a mail transfer agent on the server. Hosts often block, limit or misconfigure that agent. The receiving provider, such as Gmail or Microsoft 365, then decides whether to accept the message. If the form itself was set up recently, check it against our guide to adding a contact form in WordPress before going further.
Why “message sent” doesn’t mean the email arrived
A success message means the form handed the email off. It doesn’t mean anyone received it. The wp_mail() reference says a true return only means WordPress processed the request without error. A passing test in an SMTP plugin or a “Sent” line in a log has the same limit.
Every case of “no email arrived” fails at one of four stages:
| Stage | What you see | Where to look |
|---|---|---|
| Submission blocked | Spinner, error, or orange notice in Contact Form 7 | Browser Network tab, spam protection settings |
| Form never requested mail | Success, but nothing in any mail log | The form’s notification or Mail settings |
| Handoff failed | Red notice, or an error in the SMTP log | SMTP plugin log, host mail settings |
| Lost after handoff | Log says sent, inbox is empty | Spam folder, mail routing, SPF/DKIM/DMARC |
How to find the failing stage in five minutes
Run these checks before you change any settings. Each one rules out a stage.
- Submit the form yourself in a private window and note the time. If you test while logged in, caching and security token problems that hit real visitors stay hidden.
- Read the response. Contact Form 7’s FAQ explains what the border colour around its message means. Orange means a spam module (Akismet, reCAPTCHA or the disallowed list) flagged the submission. Red means the
wp_mail()call failed. Green means the handoff finished, so look further down the path. The text alone tells you nothing, because Contact Form 7 deliberately shows “There was an error trying to send your message” for both spam and mail failure. - Check whether the entry was saved. Contact Form 7 doesn’t store submissions on its own. Its FAQ points to the Flamingo plugin for that. If your form plugin stores entries and this one is missing, the problem is in the form.
- Test the whole site’s mail. Use “Lost your password?” on the login screen. If WordPress says “The email could not be sent. Your site may not be correctly configured to send emails,” the problem affects every email the site sends, not just this form. Our password reset guide covers what that screen tells you.
- Open the mail log, if an SMTP or mail logging plugin keeps one. If there’s no entry for your test, the form never asked for an email. An entry with an error means the handoff failed. An entry marked sent means the message was lost later.
When the form never asked for an email
Many missing emails were never sent at all, and SMTP settings can’t fix those. In one developer’s review of 150 confirmed public cases, the form never triggered an email in 24 of them. Spam protection was involved in 10 of those 24.
Spam protection rejecting real visitors
reCAPTCHA keys have to match the current domain. Keys left over from an old domain after a migration will fail quietly. Contact Form 7 says a missing reCAPTCHA token can also come from the script not loading or the theme misbehaving. Running reCAPTCHA v2 and v3 together causes conflicts too. Don’t just switch spam protection off. Find the module that’s responsible, or the inbox fills with spam instead.
Requests blocked before WordPress sees them
Open the browser’s developer tools, go to the Network tab, and submit again. A 403 response with the body -1 means the submission was stopped by a security plugin, a firewall or a cached page carrying an expired security token. Exclude the form page from caching, or allow that request in the security plugin.
Mail settings inside the form
Check the form’s own notification settings:
- The notification is turned on.
- The To field is a valid address.
- No conditional rule sends mail for only one dropdown choice.
- In Contact Form 7’s Additional Settings, there is no
skip_mail: online. It turns off mail completely.
A new field also needs its own mail-tag in the email body. A field written as [text your-new-field] only shows up in the email if the body contains [your-new-field].
If you suspect a conflict, turn on WP_DEBUG_LOG, which writes errors to wp-content/debug.log. Look for a fatal error at the time of your test. Then disable plugins one at a time on a staging copy of the site, using the method in fixing plugins that stop working.
When WordPress can’t hand the message off
A red notice or an SMTP error means WordPress tried to send and failed. The error text usually tells you which part failed.
| Error | What it means |
|---|---|
| Could not instantiate mail function | PHP mail can’t run on this host. Switch to authenticated sending. |
| SMTP Error: Could not connect to SMTP host | Wrong host, port or encryption, or the host or a firewall blocks the port |
| 535 Incorrect authentication data | The mail server rejected the login. You may need an app password. |
| Invalid address: (From) | The sender address was rejected before sending |
The fix people report most often is to stop relying on the host’s PHP mail. Send through an authenticated SMTP or API mailer instead, using a plugin such as WP Mail SMTP, FluentSMTP or Post SMTP. Installing one isn’t enough. WP Mail SMTP’s troubleshooting docs say its default “PHP Mailer” option doesn’t improve delivery. You have to choose a real mailer and enter that provider’s settings.
WP Mail SMTP’s connection guide recommends TLS on port 587, or SSL on port 465 if your provider requires it. It says not to use port 25. If your host blocks SMTP ports, use an API mailer, which sends over HTTPS. For Gmail or Google Workspace through “Other SMTP”, the settings are:
- Host
smtp.gmail.com, TLS on port 587, with authentication on. - Your full address as the username.
- An app password, not your normal password. Google only lets you create app passwords after 2-Step Verification is turned on.
Regular passwords fail with Gmail, Yahoo, Zoho and iCloud.
When the email left but never reached the inbox
If the log says sent and the inbox is empty, check four things in this order: the From address, the plugin settings, mail routing, then DNS records.
The visitor’s address is in From
This is the classic mistake. If From shows the visitor’s Gmail address, your server is claiming to send on behalf of gmail.com, and receiving servers treat that as spoofing. Contact Form 7’s mail setup best practice is to use an address on your site’s domain in From and put the visitor in Reply-To:
From: Your Company <wordpress@yourdomain.com>
Additional headers: Reply-To: [your-email]
Replies still go to the visitor. If the owner would rather read mail in Gmail, forward the domain mailbox there.
The SMTP test passes but the form still fails
The SMTP plugin’s test email uses that plugin’s own From address. The form uses its own, which may not match. WP Mail SMTP’s docs warn that another plugin’s settings can stop that plugin’s emails. Its Force From Email option makes every email use one sender. Turn it on, or set the form’s From address to match the mailer account.
Mail reaches Gmail but not your company address
That pattern usually means your host thinks it handles your domain’s mail when Google Workspace or Microsoft 365 actually does. The server delivers the email to a local mailbox nobody reads. In cPanel, go to Email, then Email Routing, and choose Remote Mail Exchanger if your mailbox lives somewhere else. Only change this once you know where your mailbox actually is. The wrong setting causes the same problem in reverse.
SPF, DKIM and DMARC don’t match the sender
WordPress’s mail handbook names SPF and DKIM, and whether the sender is authorised for the domain, as deliverability factors. The records have to cover the service that actually sends. If WP Mail SMTP sends through Brevo, SPF and DKIM need Brevo’s values, and DMARC has to align with the From domain. Before you edit DNS, list every legitimate sender: the website, your mailbox provider and any newsletter tool. Publishing a new SPF record that leaves one out breaks that sender.
Check the spam folder, but don’t stop there. In the same 150-case review, the email was in spam only 8 times.
Do WooCommerce order emails fail the same way?
Yes, because WooCommerce sends through wp_mail(). WooCommerce’s email troubleshooting docs add store-specific checks. The transactional-emails log under WooCommerce, then Status, then Logs, shows each email as Sent, Failed, Disabled or Skipped. A Pending Payment order doesn’t send the email you might expect, so check the order status before you blame delivery.
How to catch the next failure sooner
Mail often breaks quietly after a plugin update, a mailbox password change or a host move. After any of these, submit the form yourself, check the inbox and the spam folder, and run a password reset. Keep stored entries, through Flamingo or your form plugin, so a lost email doesn’t mean a lost lead. Stored entries hold personal data, so limit who can see them and delete old ones.
When to stop and get help
Stop when the next step means work you can’t see or undo:
- reading server mail logs
- changing mail routing
- editing DNS records that other services rely on
- a red error that the settings above don’t explain
Contact Form 7’s own guidance for red errors is to have the host check its logs. Ask your host whether PHP mail works, which outbound ports are open, and whether they offer a transactional mail service. If your logs show the message was accepted and the recipient’s provider filtered it, keep the log as proof. The rest is that provider’s filtering, not your site. If you want someone else to trace this, SiteSelf’s agent can diagnose and fix the broken form on your site and report what it changed and checked. The connector plugin covers form and mail settings. Reading logs needs hosting access.
Frequently asked questions
Do I need an SMTP plugin at all?
Only if the host’s mail is blocked, limited or unauthenticated, which is common on shared hosting. Some managed hosts provide their own transactional mail service. Ask your host before adding a plugin.
Contact Form 7 warns “Sender email address does not belong to the site domain.” Is sending broken?
No, it’s a configuration warning, not a failure. It tells you From uses an address outside your domain. Fix it with a domain address in From and the visitor in Reply-To.
Should I add the site’s address to my safe senders list?
It can hide the symptom, but spoofed mail using that address then gets through too. Fix the From address and authentication instead.
Why did the form stop working when nothing changed on the site?
Something outside the site often changed: a mailbox password, the host’s mail settings, or how the receiving provider filters mail. In one WordPress.org thread, the cause was Gmail no longer delivering copies of mail the owner had sent to themselves.
Can I see a message whose email never arrived?
Only if the form stored it. Contact Form 7 needs Flamingo for that. Many other form plugins keep entries by default. Without storage, the message is gone.
Leave a Reply