This email address does not belong to the same domain as the site.

That clearly was an update I did not need.
I am using that forms on MY website for customers to contact me.
Hence From-Email has to be the senders email address, making it easy for me in my mail program just to hit reply to reply.
That used to work until I updated.
I am going back to the last version until this unwanted feature is fixed

How do you want to reverse the database update, @juergen Schulze?

I’ve just had to remove this plugin from my sites because clients were trying to email me and nothing was being received. They all show an error since the update so as is always, people tinkering with things that worked perfectly fine but can’t keep their hands to themselves.
The plugin is totally useless now and whoever the author is has just destroyed his credibility in on stroke.
Found an alternative anyway so good luck to all of you still hanging on.:)

@davidfb: Thankyou! Your post cleared up all my questions!

Using this plugin on a huge multisite install, with staging server set up on a different subdomain (think staging.example.com).

Configuration validation not very helpful in this case (of course it’s a different subdomain). Is there any way to turn it off via a filter or something?

Would be great to have a workaround here. Before I go ahead and update dozens of contact forms (not even sure how to fix this with staging subdomain), I’d rather ditch the plugin or the forms entirely…

Jeez – it’s just a warning people. You can ignore it (or you can google “DMARC” and understand why this change is so important).

Sure, it’s just a warning. However, I can’t permanently hide it, and I have no shortage of (mostly useless) plugin warnings in wp-admin. Ignoring simply doesn’t scale beyond 3-5 warnings.

I’d suggest to:
– let at least subdomains pass the configuration test
– add an option to disable configuration validation
– make it easy to permanently disable the warning

I would bet that having parts of the site on different subdomains (e.g. https://support.example.com) and the email address on the main domain (e.g. [email protected]) is a very common setup. I mean, who sets up [email protected]?

let at least subdomains pass the configuration test

The plugin author has discussed this use case at https://www.ads-software.com/support/topic/email-address-does-not-belong-to-the-same-domain-as-the-site-subdomain?

@buzztone: Thanks for the pointer, very helpful!

Does anyone have a screenshot of how this should be configured now? I don’t have a valid email address that is the same domain as my website. Do I just make one up? I currently have my settings as such:

To: my valid email address
From: [email protected] (not a valid email address..don’t have one)
Additional Headers: Sender: [email protected]
Reply-To: [your-email]

Is this correct? It’s not working…says it sent, but never receive an email.

Yes, a screenshot of what the fields should look like would be very helpful… Can someone please provide? Much appreciated!

I have the same problem and tried to restore database to before update but the form still doesn’t work. Seriously, is someone working on this?
something is messed up with email validation, I’m no expert but seems that this needs to be fixed in the last update.

Here is a solution to these issues WITH screenshots of the correct configuration:

https://www.wiyre.com/solution-contact-form-7-issues-your-contact-form-has-a-configuration-issue/

yes this worked!!
so the bottom line is: change the [[email protected]] or <[[email protected]]> whatever the case may be to just <[email protected]>

In other words, get rid of the square brackets around your email address in the From field and it’s done.
perfect! thanks

Well done, Wiyre

You just need to add:
Additional Headers:
Reply-To: [your-email]

So the resulting emails respond properly. Then all is hunky dory again.

If you’re going to use a fake domain address, I’d use something well-known not to be valid like [email protected]