Contact Form 7 Not Sending Email? Fix It, Save Leads

You submit your own contact form to test it and get a red box: “There was an error trying to send your message. Please try again later.” Or worse, the form says “Thank you for your message. It has been sent.” and nothing ever reaches your inbox.
Most people who search for this want two things. They want the form to send again, and they want to know whether the messages that failed in the meantime are gone. One site owner put it like this on the WordPress.org forum: “There was a problem with my form this morning and I missed some people’s messages.” Where did they go?
Were the failed messages lost?
Probably, yes. Contact Form 7 keeps no copy of what people send. It builds an email from the form fields, hands it to WordPress to send, and that’s the end of it. If the send fails, the content of that submission isn’t sitting in a table somewhere waiting for you. We’ve covered the why in more detail in does Contact Form 7 store data?
There are three places worth checking before you give up:
- A storage plugin. If Flamingo or any other entries plugin was active when the messages came in, they’re there. Look for Flamingo > Inbound Messages in your sidebar, or an entries screen from another plugin. Flamingo saves failed sends too, not only the ones that went out.
- Your SMTP plugin’s email log. If you already had an SMTP plugin with logging switched on, the log may hold the full message body of each attempt, including the failed ones.
- Your host’s mail log. Ask support. Mail logs usually show that a message was attempted and why it bounced, but rarely the message itself. Still useful: it tells you how many people you missed and roughly when.
If none of those exist, the content is gone. Nothing can rebuild a message that was never written down. What you can do is fix the sending, then make sure the next failure costs you nothing.
First, is it really a mail failure?
Here’s something that trips people up. CF7 shows exactly the same default text, “There was an error trying to send your message. Please try again later.”, in two different situations: when the email failed to send, and when the submission was flagged as spam. Same words, different problem.
The border colour of the message box tells them apart. In CF7’s own stylesheet a failed send gets a red border and a spam verdict gets an orange one. If you’re seeing orange, your mail is probably fine and something (reCAPTCHA, Akismet, a disallowed word list) decided the message was spam. That’s a separate fix, and we’ve written up how to stop form spam without blocking real people.
Want to be sure? Open your browser’s developer tools, go to the Network tab, submit the form, and click the request ending in /feedback. The JSON response has a status field. It reads mail_failed when the email didn’t go, spam when it was blocked as spam, and mail_sent when CF7 thinks everything worked.
Why Contact Form 7 fails to send, most common first
1. Your host blocks or doesn’t authenticate PHP mail()
Out of the box, WordPress sends email through PHP’s mail() function on your web server. Plenty of hosts turn that off, rate-limit it, or let it through unauthenticated so Gmail and Outlook throw it away. This is the cause most of the time.
How to check: trigger any other WordPress email, like a password reset for a test user. If that doesn’t arrive either, it isn’t a CF7 problem. Your site can’t send mail at all.
2. The From address is on a different domain
Open the form, go to the Mail tab and look at the From field. If it’s set to the visitor’s address (something like [your-email]) or to a Gmail address while your site lives on example.com, receiving servers check SPF and DMARC, see a server that isn’t allowed to send for that domain, and reject or junk the message.
CF7 actually warns you about this. Its configuration validator flags “Sender email address does not belong to the site domain.” on the Mail tab. Set From to an address on your own domain, such as [email protected], and put the visitor’s address in Additional headers as Reply-To: [your-email] so hitting reply still reaches them.
3. No SMTP at all
Even when mail() works, unauthenticated mail from a shared server is a coin toss. It might arrive, it might land in spam, it might vanish. If the form says “sent” but nothing arrives, this is the usual reason. CF7 really did hand the email off. It just never got anywhere useful.
4. A typo in the To field
Boring, but it happens. Check the To field on the Mail tab for a misspelled domain, a stray space, or an old address nobody reads anymore. If Use Mail (2) is ticked for an autoresponder, remember Mail (2) only goes out after the main Mail has been sent successfully, so a broken Mail takes the autoresponder down with it.
5. A caching or security plugin blocks the request (the form spins forever)
CF7 submits through the WordPress REST API, to a URL that looks like /wp-json/contact-form-7/v1/contact-forms/123/feedback. If a security plugin, firewall rule or Cloudflare setting blocks the REST API for logged-out visitors, the spinner just spins and no message ever appears. Page caching can also serve an old copy of the form with stale data.
How to check: same Network tab trick. If the /feedback request returns a 403, 401 or never completes, it’s being blocked before CF7 even tries to send. Exclude the contact page from caching and allow the /wp-json/contact-form-7/ route in your security plugin.
The fix that works for most sites: an SMTP plugin
For causes 1 and 3, and often 2, the answer is the same. Stop sending through the web server and send through a real, authenticated mailbox instead.
- Install an SMTP plugin. WP Mail SMTP, FluentSMTP and Post SMTP are the common picks. They all do the core job: route every WordPress email, CF7 included, through the mail service you choose.
- Connect a mailbox or a sending service. Either the SMTP login for an email account on your own domain (your host’s email, Google Workspace, Microsoft 365), or a transactional provider like Amazon SES, Brevo, Postmark or Mailgun. For anything more than a handful of messages a day, a transactional provider tends to be more reliable.
- Set up SPF and DKIM for that service on your domain’s DNS. The provider gives you the records. Skip this and you’re back to the spam folder.
- Send a test email from the SMTP plugin’s test screen. Then submit your actual CF7 form and check that it arrives.
- Turn on the email log if your SMTP plugin has one (in some it’s a paid feature). This is the part people skip. With a log, the next failure shows up as a red row you can see, instead of a silence you only notice weeks later when a customer asks why you never replied.
Once the From address matches the domain you’re sending through, the CF7 side needs no other changes.
Stop losing messages next time
Fixing delivery solves today’s problem. It doesn’t help the day your mail provider has an outage, your API key expires, or someone changes a DNS record. Email will fail again at some point. The question is whether a failed email also means a lost lead.
It doesn’t have to. Store every submission inside WordPress as well, and the email becomes a notification rather than the only copy. The free way to do that is Flamingo, written by CF7’s own author. It needs no setup, and it saves submissions even when the email fails. We’ve written the full walkthrough in how to save Contact Form 7 submissions to the database, so we won’t repeat it here.
The one rule: install storage before you need it. No plugin can capture a submission that came in before it was active.
Another option for keeping a copy
Full disclosure: EntryVault is ours. Its free core captures Contact Form 7 submissions on CF7’s wpcf7_before_send_mail hook, which fires before CF7 tries to send the email. So the entry is already saved by the time the email goes wrong, and it stays saved. It captures valid, non-spam submissions and puts them on a board where you can tag them, add notes and reply. It also captures 18 other form plugins, which matters if the site runs more than CF7.
To be plain about the limit: EntryVault is not a mailer. It won’t fix email delivery, and you still need the SMTP setup above for the notification itself. What it does is make sure a failed email doesn’t take the message with it. It’s a free download from our site. If you only run CF7 and only need a safety net, Flamingo does that job just fine.
Frequently asked questions
Why does Contact Form 7 say there was an error trying to send your message?
CF7 shows that text in two cases: the email failed to send, or the submission was flagged as spam. A red border around the message means the send failed, usually because the host blocks PHP mail(), the From address is on another domain, or there’s no SMTP. An orange border means a spam check blocked it.
Can I recover Contact Form 7 messages that failed to send?
Only if something else saved them. Contact Form 7 keeps no copy, so check for Flamingo or another storage plugin, your SMTP plugin’s email log, and your host’s mail log. If none of those were in place when the messages arrived, the content of the failed messages is gone.
Do I need an SMTP plugin for Contact Form 7?
On most sites, yes. Without one, WordPress sends through your web server’s PHP mail(), which many hosts block or send unauthenticated, so messages get rejected or land in spam. An SMTP plugin connected to a real mailbox or a transactional provider fixes delivery for CF7 and every other WordPress email.