Getting configuration error with a protected form

Hi!

After a recent Contact Form 7 update, we’ve started getting a configuration error warning us that we use user-inputted email from the form as an input parameter for “To:” in “mail (2)”. Based on your website, we should use recaptcha to avoid this error.

But we already use a different form of protection – CleanTalk. It works great, so we don’t want to add another unnecessary layer, like recaptcha.

Would you be willing to detect this and don’t show the error when the form is actually protected?

Or is this something that CleanTalk should be implementing?

Thanks!