Troubleshooting
Contact Form 7 Reply to Not Working: Causes and How to Fix It

Short answer
Contact Form 7 reply-to fails when the Reply-To line is missing from Additional Headers, the mail-tag does not match your email field name, or an SMTP plugin overrides the header. Add Reply-To followed by your email field tag in the Mail tab, keep From on your own domain, and test again.
Key takeaways
- Add Reply-To: [your-email] in the Mail tab's Additional Headers.
- The tag must match your email field's exact name.
- Use an email-type field and make it required.
- Keep the From field on your own domain, never the visitor's address.
- SMTP plugins with forced reply-to settings can override the header.
- Check the original message source to confirm the header is present.
Why is Contact Form 7 reply-to not working?
Contact Form 7 reply-to usually fails because the Reply-To line is missing from Additional Headers, the mail-tag name does not match your email field, or an SMTP plugin or mail service overrides the header.
When reply-to works, you open a form notification, click Reply, and your email app addresses the reply to the visitor. When it fails, the reply goes to your own site address or to nobody useful.
Contact Form 7 sets this with a mail header, not a checkbox. The official guide to setting up mail explains the Mail tab, and this article covers each reason the header can go wrong.
How should the Reply-To header look in Contact Form 7?
In the form's Mail tab, the Additional Headers box should contain a line like Reply-To: [your-email], where the tag in brackets matches the name of your form's email field exactly.
- Go to Contact > Contact Forms and edit your form.
- Click the Mail tab.
- Scroll to Additional Headers.
- Add this line:
Reply-To: [your-email]
- Click Save.
The default Contact Form 7 form uses a field named your-email, so this line works out of the box for that form. Custom forms often use other names.
Our guide to Contact Form 7 mail settings explains the other fields on this tab.
Does the mail-tag match your email field name?
If your email field is named something else, such as email-123 or user_email, the Reply-To tag must use that exact name, or Contact Form 7 leaves the header empty.
Open the Form tab and look at your email field. It will look something like this:
[email* your-email placeholder "Your email"]
The word after email* is the field name. In this example it is your-email. If yours says [email* email-482], your header must be:
Reply-To: [email-482]
Below the Mail tab fields, Contact Form 7 lists the mail-tags you can use for this form. Copy the name from there to avoid typos. Tag names are case sensitive.
Is the Reply-To tag pointing to an email field?
The Reply-To tag must come from an email-type field, because using a text field or name field puts something that is not a valid address in the header, and mail apps ignore it.
A common mistake is writing Reply-To: [your-name]. The header then contains a name, not an address, and email clients cannot reply to it.
Use an email field type in your form, not a plain text field. The email type validates the address before the form can be sent. You can include a display name too:
Reply-To: [your-name] <[your-email]>
The email message format standard defines how name and address pairs should look. Keep the angle brackets around the address.
Make the email field required, with an asterisk, as in [email* your-email]. An optional empty field creates an empty Reply-To header.
Is the header written with the correct syntax?
Each header must sit on its own line in the form Header-Name: value, with a colon after the name, and no extra words, commas or quotes around the line.
Check for these slips:
- Missing colon:
Reply-To [your-email]will not work. - Wrong spelling:
Reply To:orReplyTo:instead ofReply-To:. - Two headers on one line: put
Cc:orBcc:lines on separate lines. - Stray characters: smart quotes pasted from a document can break the line.
Contact Form 7's configuration validator flags many of these problems. If you see a warning at the top of the form editor, read it. Our guide to Contact Form 7 configuration errors explains the common messages.
Did you put the visitor's address in the From field instead?
Putting the visitor's email in the From field is a common mistake that breaks delivery, so keep From on your own domain and use Reply-To for the visitor's address.
Many people try to make replies work by setting the From field to [your-email]. That makes it look as if the visitor sent the email from your server. Mail providers reject or spam-filter these messages because your domain is not allowed to send for their address.
The correct setup is:
| Field | Value |
|---|---|
| To | Your inbox, for example [email protected] |
| From | [_site_title] <[email protected]> |
| Additional Headers | Reply-To: [your-email] |
This keeps sender checks happy and still lets you reply straight to the visitor. Contact Form 7 lists special tags such as [_site_title] on its special mail-tags page.
Is an SMTP plugin overriding the Reply-To?
Some SMTP plugins and mail services have options that set or force a Reply-To address, which can replace the header Contact Form 7 adds.
Contact Form 7 passes its headers to WordPress through the wp_mail() function. An SMTP plugin then takes over sending. If that plugin has a reply-to setting turned on, it may win.
Check your SMTP or mailer plugin's settings for fields such as:
- Reply-To or Force Reply-To.
- Override headers or similar options.
- Mailer-specific settings in a transactional service's dashboard.
Turn off any forced reply-to, save, and send a new test. Some email services also have account-level settings that rewrite headers. If the plugin looks clean, check your provider's dashboard.
Is your email app ignoring the header?
Most email apps respect Reply-To, but some behave oddly when the Reply-To matches your own account or when you view a message in a sent or forwarded folder.
To be sure the header is present, open the original message source:
- In Gmail, open the message, click the three-dot menu and choose Show original.
- In Outlook, open the message properties or view source.
Search for Reply-To:. If the visitor's address is there, Contact Form 7 did its job. If your reply still goes elsewhere, the app or a mail rule is the cause.
Testing with your own email address as the visitor can confuse things. Use a separate test address, like a second mailbox, when you submit the form.
How does Reply-To work in Mail (2)?
Mail (2) has its own Additional Headers box, so if you send an autoresponder to the visitor, set its Reply-To to your own address rather than the visitor's.
Mail (2) is the optional second email, often used to send a confirmation to the person who filled in the form. Its headers are separate from the main Mail tab.
For an autoresponder, a sensible setup is:
Reply-To: [email protected]
That way, if the visitor replies to the confirmation, the reply reaches you.
How do you test the fix?
Save the form, submit it from a private browser window with a test email address, then reply to the notification and confirm the reply goes to the test address.
- Save the form after editing the Mail tab.
- Clear any page cache so the form uses the latest version.
- Submit the form from a private window, using an address you can check.
- Open the notification and click Reply.
- Confirm the To line shows the test address.
If the notification itself does not arrive, that is a delivery issue, not a reply-to issue. See how to fix Contact Form 7 not sending.
If notifications arrive but land in spam, read our guide to setting up SPF, DKIM and DMARC.
The plugin's own page on WordPress.org links to its support forum if you need more help.
Frequently asked questions
Where do I add Reply-To in Contact Form 7?
Edit the form, open the Mail tab, and scroll to the Additional Headers box. Add a line that starts with Reply-To followed by a colon and your email field's mail-tag, then save the form.
Why does my reply go to my own website address?
The notification has no valid Reply-To header, so your email app replies to the From address. Add the Reply-To line in Additional Headers and check that its mail-tag matches the email field in your form.
Can I set the From field to the visitor's email instead?
You should not. Sending as the visitor's address fails sender checks such as SPF and DMARC, so the email may be rejected or sent to spam. Keep From on your own domain and use Reply-To for the visitor.
Does WP Mail SMTP break Contact Form 7 Reply-To?
Not usually. Most SMTP plugins pass the Reply-To header through untouched. Problems appear when a plugin or mail service has a forced reply-to option turned on. Check your mailer settings and turn off any override.
How do I check if the Reply-To header was sent?
Open the notification email and view its original source. In Gmail, use Show original from the message menu. Search the source for Reply-To. If the visitor's address appears there, Contact Form 7 sent the header correctly.
Sources
- Setting up mail Contact Form 7
- Special mail-tags Contact Form 7
- Contact Form 7 plugin WordPress.org
- wp_mail() function WordPress Developer Resources
- RFC 5322: Internet Message Format IETF
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


