Contact Form 7 Mail (2) Not Sending? A Fix Checklist

You get the form notification in your own inbox. The visitor who filled in the form gets nothing. No “thanks, we got your message”, no copy of what they sent. In Contact Form 7 that second email is Mail (2), and when it stays silent while the first one works, the cause is almost always in a short list of places.
A thread on the CF7 support forum from this month sums it up: “Mail 2 not sending”. Note the “-4” in that URL. It’s the fourth thread with that exact title. That one got fixed after seven replies, and the cause was a single mail-tag in the wrong field. We’ll get to it.
If neither email arrives, that’s a different problem (usually the server, not the form), and our post on Contact Form 7 not sending email covers it. This one assumes the admin copy works and only the visitor copy doesn’t.
First, how Mail (2) actually works
Two details from the CF7 source explain a lot of the confusion.
- Mail (2) only goes out if Mail went out first. CF7’s own help text says it: Mail (2) “is sent only when Mail has been sent successfully.” If the main notification fails, the autoresponder is never even attempted.
- The result of Mail (2) is ignored. Once Mail succeeds, CF7 sends Mail (2) and shows the visitor the green success message no matter what happened to Mail (2). So a broken autoresponder looks exactly like a working one from the front end. Nobody sees an error.
That second point is why people only find out when a customer asks “did you get my message?”
The checklist
Work through these in order. Most sites are fixed by step 2 or 3.
1. Is “Use Mail (2)” ticked?
Open the form, go to the Mail tab and scroll down. Below the main Mail section there’s a checkbox labelled Use Mail (2). CF7 describes it as “an additional mail template often used as an autoresponder.” If the box is unticked, the Mail (2) fields are hidden and nothing is sent. Sounds obvious. It’s also the box that gets lost when someone duplicates or imports a form.
2. Is the “To” field the email field’s mail-tag?
This is the big one, and it’s what broke the forum thread above. The “To” field of Mail (2) has to hold the mail-tag of the email field in your form. On the default CF7 form that’s:
[your-email]
Not [your-name], not [your-subject], not your own address. If you renamed the field in the form (say, [email* contact-email]), the tag in “To” has to match: [contact-email]. A typo here means the “address” CF7 hands to WordPress is someone’s name or an empty string, and the send fails quietly.
CF7 does try to warn you. When you save, its configuration validator swaps each mail-tag for a sample value and checks the result. A text field becomes the word “example”, which isn’t an email address, so you get a notice on the Mail tab: “Invalid mailbox syntax is used.” If you see that next to Mail (2), fix the “To” field first.
3. Is “From” an address on your own domain?
Lots of people set Mail (2)’s “From” to their Gmail address, or worse, to [your-email] (the visitor’s own address). Mail servers don’t like either. A message claiming to be from [email protected] but sent by your web server fails SPF and DMARC checks, and many receiving servers drop it or bin it.
CF7 checks this too. If the “From” address isn’t on your site’s domain, the validator shows “Sender email address does not belong to the site domain.” This is a warning, not a block: CF7 still tries to send. But treat it as a real problem. Use something like [email protected] or [email protected] as “From”, and if you want replies to reach a different inbox, put that in Additional headers as Reply-To:.
(One quirk from the source: on localhost or a site addressed by IP, CF7 skips this check, so you won’t see the warning on a local test site even if the setting is wrong.)
4. Did you get the “Unsafe email config” warning?
Recent CF7 versions show “Unsafe email config is used without sufficient protection.” when the “To” field (or a header) is filled from a visitor’s email input and the form has no reCAPTCHA or Turnstile active. That’s exactly the Mail (2) setup, so a lot of people meet this warning for the first time on their autoresponder.
The reason: a form that emails whatever address is typed into it can be used by bots to send mail to strangers through your server. Your host or mail provider may throttle or block you if that happens. The warning on its own doesn’t stop CF7 from sending, but it’s worth taking seriously. Turning on Turnstile or reCAPTCHA clears it. Our guide to stopping WordPress form spam covers the options.
5. Is mail going through an SMTP service with SPF and DKIM set up?
By default WordPress hands mail to PHP’s mail() on your web server. Plenty of hosts deliver that badly or not at all to outside addresses. Which is a neat explanation for “admin copy arrives, visitor copy doesn’t”: your admin inbox might be on the same server or the same provider, while the visitor’s Gmail or Outlook rejects it.
Install an SMTP plugin and send through a real mail service (your host’s SMTP, Amazon SES, Brevo, Mailgun and so on). Then set up SPF and DKIM for your domain at your DNS host, following the provider’s instructions. This one step fixes more autoresponder problems than everything else here combined.
6. Does it fail, or does it arrive in spam?
These are different problems and you need to know which one you have.
| What you see | Likely meaning | Where to look |
|---|---|---|
| Mail log in your SMTP plugin shows an error | The send failed | The error text: auth, blocked sender, bad “To” address |
| Log shows sent, nothing in inbox, something in spam | Delivered, but not trusted | “From” domain, SPF/DKIM, message content |
| Log shows sent, nothing anywhere | Accepted, then dropped or bounced | Your mail provider’s bounce/activity log |
| No log entry for Mail (2) at all | Never attempted | Steps 1 and 2, and whether Mail itself succeeded |
An SMTP plugin with a mail log is the easiest way to tell these apart. If messages land in spam, our post on form messages marked as spam goes deeper on that side.
7. Test with a mailbox you control
Don’t test by typing your admin address into the form. You’ll get both emails in one inbox and won’t be able to tell them apart, and some servers treat “from me, to me” differently. Use a separate Gmail or Outlook account you can log into, submit the form as a visitor, then check inbox and spam. Try two providers if you can. Gmail accepting it while Outlook doesn’t tells you a lot.
8. Don’t use Flamingo as proof
Flamingo is handy for keeping a copy of every submission. Open a message and you’ll see a “Submission result” line, such as mail_sent or mail_failed. That result is about the main Mail only. Contact Form 7 ignores whether Mail (2) went out, so a mail_sent row tells you nothing about the visitor’s copy, and it certainly doesn’t mean anything was delivered.
What the checklist can’t fix
Being honest about the limits: even with everything above in place, a visitor can mistype their own address. CF7’s email field checks the format, so [email protected] passes and the autoresponder goes into the void. There’s no setting for that. And once a mail server accepts a message, WordPress has no idea what happens next. A later bounce or a quiet drop at the receiving end won’t show up anywhere in your dashboard, only in your mail provider’s logs.
Another option, if you’re rebuilding the form anyway
Full disclosure: Trinity Forms is ours. Switching form plugins is a big step for a mail bug, and the checklist above fixes most cases. But if you’re already planning a new form, a few things in the free version are aimed squarely at this problem:
- In each notification, Send to has two choices: “These addresses” or “An email field on the form”. Pick the second and you choose the field from a dropdown, so the autoresponder address is picked from a list, not typed as a merge tag. That removes the
[your-name]mistake from step 2. - When WordPress reports a send failure, the reason is written onto that entry’s activity log, and recent failures show up as a warning on the dashboard. Settings has a Send a test email button.
- If a send failed, you can re-send it: Resend notifications on the entry screen, or as a bulk action in the entries list.
Same limit as above, in Trinity’s own words: WordPress only knows the mail server accepted the message, and a bounce after that is invisible, so nothing claims an email was delivered. It needs PHP 8.2 or newer. It’s a free download from our site.
Frequently asked questions
Why does Contact Form 7 send the admin email but not Mail (2)?
Usually the Mail (2) “To” field doesn’t hold the email field’s mail-tag (for example it says [your-name] instead of [your-email]), the “Use Mail (2)” box is unticked, or the visitor’s mail provider rejects the message because the “From” address isn’t on your domain or SPF and DKIM aren’t set up.
Does Contact Form 7 show an error if Mail (2) fails?
No. Mail (2) is only attempted after the main Mail succeeds, and its result doesn’t change the message the visitor sees. The form shows the normal success message even if the autoresponder failed, so you need an SMTP plugin’s mail log to see what happened.
What should the From address be for a Contact Form 7 autoresponder?
An address on your own site’s domain, such as [email protected]. Contact Form 7 warns “Sender email address does not belong to the site domain” otherwise. If you want replies to go to another inbox, add a Reply-To line in Additional headers.