Real Form Messages Marked as Spam? How to Get Them Back

Most spam advice is about keeping junk out. This post is about the other failure: a real person filled in your contact form, your spam filter decided they were a bot, and the message went nowhere. No email, no entry, no trace. You only find out weeks later when someone rings up and says “I sent you a message through the website.”

In October 2026 alone there were three Contact Form 7 threads on wordpress.org about spam rules catching real messages, including one owner asking “can I exclude the one form from the disallow list, keep the cake and eat it at the same time?” Older threads say it more bluntly: “reCAPTCHA thinks everything is spam”.
If you came here to block spam, we’ve written that one already: how to stop WordPress form spam. Here we’re doing the reverse. How to tell if real messages are being flagged, where they might still be sitting, and how to loosen things without opening the floodgates.
The short version: spam should be quarantined, not deleted. A filter will always make mistakes. If flagged messages are kept somewhere you can look, a mistake costs you five minutes. If they’re dropped, it costs you the customer.
How to tell it’s happening
The nasty part is that nothing looks broken. The form submits, the page doesn’t crash, and the visitor gets an error they’ll probably blame on themselves. A few ways to catch it:
- Test like a stranger, not like the admin. Submit your own form from your phone on mobile data (wifi off), from a VPN, and from a browser you never use. Logged-in admins on a known office IP are the least likely people to be flagged. Visitors on shared mobile IPs and VPNs are the most likely.
- Look at what the visitor sees. In Contact Form 7, a message flagged as spam gets the response “There was an error trying to send your message. Please try again later.” That is the same default text as a mail sending failure. The only visible difference is the border around the message: orange for spam, red for a failed send. Most visitors won’t notice, and most site owners never see it at all.
- Watch your enquiry count. A sudden drop right after you added reCAPTCHA, turned on Akismet or pasted a keyword list into WordPress settings is a strong hint.
Worth separating two different “spams” here. If your form plugin accepted the message and sent the email, but the email landed in your mailbox’s junk folder, that’s an email delivery problem, not a form filter problem. Check your mail client’s spam folder first, and if emails aren’t arriving at all, see Contact Form 7 not sending email. The rest of this post is about the form refusing the message before any email was sent.
Where flagged messages might still exist
This depends entirely on your setup, and the honest answer is often “nowhere”.
Contact Form 7 on its own: gone
CF7 doesn’t store submissions at all. It sends the email and that’s it (we covered this in does Contact Form 7 store data?). When a submission is flagged as spam, the email isn’t sent either. So with plain CF7 there’s no copy anywhere on your site. You can’t get it back.
CF7 with Flamingo: check the Spam view
Flamingo is the free storage plugin from CF7’s own author. If it was installed before the message was sent, it saves spam-flagged submissions too, with a Spam status, and lists them under a Spam link on its Inbound Messages screen. It also keeps a spam log saying which check flagged the message, which helps a lot (more on that below).
You can mark a message as not spam there. If Akismet was involved, Flamingo reports that correction back to Akismet. What it doesn’t do is send the notification email that never went out. People have asked for a resend button for years. So you read the message in the admin and reply to the customer by hand.
Akismet: not in Comments > Spam
People often go looking in Comments > Spam because that’s where Akismet’s catches usually live. That queue is for comments. When CF7 asks Akismet whether a form message is spam, it sends the message to Akismet for a verdict, and that’s all. It isn’t added to your comment queue. Unless a storage plugin kept it, it’s gone.
Other form builders
Builders that save entries differ on spam. Some keep it in a separate list, some refuse it outright. Submit a test you know will fail (fill the honeypot field with your browser’s dev tools) and see whether it shows up anywhere in the admin.
Common causes of false positives
When you do find a flagged real message, the reason usually falls into one of these.
- reCAPTCHA v3 score too strict. v3 gives each visit a score from 0 (bot) to 1 (human), and the plugin rejects anything under a threshold. VPN users, privacy browsers, people who land straight on the form and type quickly, and some mobile networks get low scores. In CF7 the threshold is 0.50, and a submission has to score above it. CF7 also writes the score and threshold into the spam log, which is why Flamingo is so useful for diagnosing this.
- A keyword or IP list built for comments. CF7 checks submissions against WordPress’s own Disallowed Comment Keys list (Settings > Discussion). Anything you added there to fight comment spam now also blocks form messages. Ban the word “SEO” and a real SEO agency can’t contact you. This is exactly what the “exclude the one form” thread is about.
- Time traps and autofill. A time-trap rejects forms submitted too quickly. A returning visitor whose browser autofills name, email and phone, who then types a two-word message, can beat a strict timer.
- Akismet on very short messages. “Call me back please” with a Gmail address gives a content filter very little to go on. Short, plain messages from new addresses are where content filters guess wrong most.
- Shared and VPN IPs. IP reputation checks punish everyone behind the same address, which includes corporate networks, mobile carriers and VPN exit points.
How to loosen it safely
The goal is not “turn spam protection off”. It’s to keep the checks that never hurt humans, soften the ones that do, and make sure whatever still gets flagged is kept.
1. Keep everything flagged before you change anything
If your form doesn’t store spam, fix that first. With CF7 that means installing Flamingo. Without stored spam you can’t tell which check is wrong, and you can’t tell whether loosening it helped.
2. Adjust the right threshold, in the right direction
For reCAPTCHA v3, a lower threshold lets more through. In CF7 you change it with a filter, for example in a small custom plugin or your theme’s functions.php:
add_filter( 'wpcf7_recaptcha_threshold', function () {
return 0.3;
} );
Don’t go straight to 0.1. Drop it a step, then look at the scores of what still gets flagged over the next week or two. If real people sit at 0.3 to 0.4 and the junk sits at 0.1, you have your number.
3. Clean up keyword lists
Remove broad words real customers might use. Keep exact strings only spammers send, like specific URLs.
4. Keep the honeypot
A properly built honeypot almost never flags a human, so it’s the last thing to remove. If you’re replacing reCAPTCHA v3, Cloudflare Turnstile tends to be gentler on real visitors, but test it the same way: phone, VPN, fresh browser.
5. Review the spam pile on a schedule
Weekly for the first month, then monthly. It’s the only way to know your settings are right.
A form that quarantines spam by default
Full disclosure: Trinity Forms is ours, so here’s what it does, plainly.
In the free core, entries that the spam checks flag are kept in a Spam tab on the entries screen instead of being thrown away. No notification email is sent for them. Each spam entry says why it was flagged: the hidden trap, sent too fast, the bot check, or Akismet. That tells you which setting to loosen.
When you find a real one, open the entry, Restore it, then click “Resend notifications” to send the emails that should have gone out the first time. Bulk actions can restore and resend many at once, if a bad week caught several.
Spam protection in the free version is a honeypot and a time-trap, plus your choice of Cloudflare Turnstile, Google reCAPTCHA (v2 or invisible v3) or hCaptcha, and optional Akismet.
One limit to know about: if a form gets hit by a big burst of spam, there’s a per-minute cap on how much is stored. Spam beyond that cap is dropped, not kept. In normal traffic you won’t hit it, but during a flood some flagged entries won’t be in the Spam tab.
It’s a free download from our site.
Frequently asked questions
Why are real form submissions going to spam?
Usually one check is too strict for some of your visitors. The common ones are a reCAPTCHA v3 score threshold that VPN and mobile users fall under, a keyword list (often the WordPress Disallowed Comment Keys list) that matches normal words, a time-trap beaten by browser autofill, or Akismet guessing wrong on a very short message. Storing flagged submissions shows you which check caught them.
Can I recover form messages marked as spam?
Only if something stored them. If your form plugin or a storage plugin like Flamingo keeps spam-flagged submissions, you can find them in its spam view and contact the person. If the form simply refused the message and kept no copy, it can’t be recovered, so set up spam storage before you need it.
Does Contact Form 7 keep messages it marks as spam?
No. Contact Form 7 doesn’t store submissions, and it doesn’t send the email for a message it flags as spam, so nothing is left. If Flamingo is installed, it saves spam-flagged messages with a Spam status, along with a log of which check flagged them.