syntax error: "This email address does not belong to the same domain as the sit

@andreas Beer – The author gives this solution, I understand your problem but I do not see that the solution or to the fictitious email [email protected]
that’s it, sorry, but you see the message of the author at the top of the forum, for him, there is no bug, but a bad configuration of the plug-in users.

Good courage, for me this is my last post here

I have my To, From, and Subject fields correct BUT it shows under each field “This field has syntax errors.”. Why is that? I am suing the latest version of Contact Form 7 and the latest version of wordpress. I don’t see why it shows that. Please help.

Hold on a second,

I always thought that from field refers to the senders email address. Why on earth would this field be required to be the same as the site’s domain name?

Is this user flow not correct?

———————– The Flow ———————
Site visitor fills out the sendmail form. One of the fields is “your-email”.

When the sendmail message is sent to the site owner (form recipient) they read the message and reply. It goes to the email defined in [your-name] <[your-email]>.
——————————————————–

Is thinking not correct? If it is not correct how do you define incoming email’s from address?

Why should this be a validation issue?

My question remains: I get this error IN RED:

galapesca_contactPage
3 configuration errors found
Edit | Duplicate

and inside this contact page, under MAIL tab, I get these messages IN RED:

[your-email]
“This field has syntax errors.”

[your-name]<[your-email]>
“This field has syntax errors.”

[your-subject]
“This field has syntax errors.”

I always thought that from field refers to the senders email address. Why on earth would this field be required to be the same as the site’s domain name?

No, the From field should be “where the email came from”. If you send the email, then it came from you. If your website sends the email, then it should be marked as from the website. Even if that “from” is a fake address, it needs to have the domain name of the website in order to not get flagged as potentially faked.

Think about it. If it can send with any old email address you type in there, then it’s kind of trivial for you to fake emails from anybody to anybody else. This is why email receiving services do additional checks, to detect and recognize “faked” From addresses. If you put in a From address that isn’t on the domain, then it’s likely to get picked up as “fake” by the receiving ends.

On the other hand, if you own that domain, then there’s no checks that will reliably detect it as false, because those checks rely on checking with the domain that the email claims to be from. If you sent email claiming to be from my domain, for example, then my domain has rules that would tell any receiver “nope, that’s fake”. But you control your domain, and those checks thus roll back to you.

That’s why you use your own domain in From lines. If you need replies to those emails to come back to a different location, then that is what the Reply-To: header is for.

I get this

To: myemail
from: [your-name] <[your-email]> This email address does not belong to the same domain as the site.

But if I put something else it says syntax error and if I put my email (which is wrong, I cant reply to customers as it wants to send it to my email)
I need to solve this asap as I cant work with not working emails ??

Is there a way to disable this new configuration validation feature? My company uses CF7 heavily, but this new validation feature is very disruptive to our flow. We work in complex environments, often applying custom layers within CF7, and this feature does not like it. It was never previously a problem. We have dozens of WordPress sites that use this plugin, and really do not want to switch. It is possible to have a setting in the config to disable this, even if it is disabled by default?

This feature really cramps the flexibility your plugin provides.

I am getting these error messages under the following 3 FIELDS from the backend of my contact form:

[your-email]<[your-email]>
“This field has syntax errors.”

[your-name]<[your-email]>
“This field has syntax errors.”

[your-subject]<[your-subject]>
“This field has syntax errors.”

Am I setting these fields right? So when I see the list of all my forms I get a warning that there are configuration errors. I need to solve this but I do not know whether the above 3 fields are configured correctly. Please help.

====================================
ERROR BEFORE IN MY CONTACT FORMS LIST:
galapesca_contactPage
3 configuration errors found
Edit | Duplicate

Sigh, took me a while to figure this out. Short practicable examples how to solve this might help more than the Docs I guess. Yes, I read them…. And those syntax errors bugged me to, while I used the tags provided in “In the following fields, you can use these mail-tags:”

@sewansome
So I put an address I just invented in the “From” field: [email protected]

In “Additional Headers” this:
Sender: [email protected]
Reply-To: [full-name] <[your-email]>

The Reply-To always makes it possible to send your reply to the sender′s email-address by just clicking on “Reply” as usual while the fantasy-email just makes sure it validates and you know where it′s coming from. Errors gone.

Just test it.

@vcoronel

If an email is being sent from your website domain, it should now have a FROM address from that domain. This is because emails are being spoofed by spammers and are being sent from a different domain (e.g. I send you a message from my domain but claim to be sending it from paypal.com). Such messages are being routed into the Spam folder, and so best practice is now to include a FROM email address that is from the website domain. Look at the following setup:

== MAIL ==
To: [email protected]
From: [your-name] <[email protected]>
Subject: Re: [your-subject]
Additional Headers: Reply-To: [your-email]

What happens and why:

1. The mail is sent from the contact form to the email address specified in the TO field.
2. When you receive the message, it will have the sender’s name and be from the noreply email address specified in FROM (Depending in your hosts, this may need to be a real email address (test to see if it processes), and it does need to be @your-domain.com).
3. By including Re: in the SUBJECT, you will ensure that the field always has some text in it, even if the sender does not complete this field (Best practice is to ensure that there is at least some text in the subject field). Or, you can make the SUBJECT a required field in the *Form* by adding an asterisk: [text* your-subject]
4. Adding the Reply-To: [your-email] in ADDITIONAL HEADERS means that you can reply to the sender by hitting the Reply button in your email client.
5. If you want to actually see the sender’s email address in the message you receive you can include it in the MESSAGE section. For example:

MESSAGE BODY:

From: [your-name] <[your-email]>
Subject: [your-subject]

[your-message]

If your website sends the email, then it should be marked as from the website. Even if that “from” is a fake address, it needs to have the domain name of the website in order to not get flagged as potentially faked. – @samuel Wood (Otto)

If an email is being sent from your website domain, it should now have a FROM address from that domain. This is because emails are being spoofed by spammers and are being sent from a different domain (e.g. I send you a message from my domain but claim to be sending it from paypal.com). Such messages are being routed into the Spam folder, and so best practice is now to include a FROM email address that is from the website domain. – barnez

Put <[your-email]> in the message body to see who it is from.

Thank you @samuel Wood (Otto) and @barnez for answering the original post.

This now makes perfect sense.

Have 2 contact forms, almost identical and one is OK, second has 3 configuration errors.
First one is made of standard named fields.

Almost as it gives errors if you make custom named fields: [text-305], [text-349], [textarea-621], [tel-277]….etc…

I have no visible red errors, nothing to start from.
Sorry, maybe not right topic, will try to find better one.

Difference is also forms are in different languages.

if you use “Reply-To: [your-email]” as additional header, make sure “your-email” is required (using asterisk) on Form, “[email* your-email]”

Hello:
I solved the problem with this configuration:
See the image

Regards.