Confused with error “‘From Email’ address does not match your website”

Hi @xolite,

Sorry to hear about the confusion you are facing here!

Please know that by default the From Email is set as {admin_email} that is the administrator email of the site defined under WordPress Dashboard > Settings > General > Administrator email.

If there is a different address you would like to use as the sender’s email, you can simply enter it in this field.

Note: If you’re using an SMTP plugin to ensure email delivery, make sure your From Email follows your mailer’s requirements. Some SMTP mailers require your notifications’ From Email to match the email address you used in your SMTP settings. Others require a domain-specific email address.

Please refer to the From Email in this guide.

Hope this helps!

Thanks so much for the quick reply, this is why I am confused by the error, the email is set in WPAdmin “Settings” as [email protected] yet it gives the error that the email does not match the domain “www.domain.com” and suggests to set an email address that matches such as [email protected] (which literally makes no sense).

It looks like it is grabbing the domain from WordPress URL in settings and not checking the email against the domain without the “www”.

Example:
[email protected] it is comparing it to “www.domain.com” rather than “domain.com” which of course would equal a match and not produce the error. ??

I will look at the code this weekend when I am off work.

I’ve been using WPForms since 2016 (got a paid PRO license as well not just the free version) and this warning in the Notifications settings just started happening within recent versions, I’d guess since around June or July.

It really doesn’t seem to make sense, because…

Let’s say the site is https://www.example.com – regardless of whether we use {admin_email} in the “From Email” field like this:

Or if we use the WordPress > Settings > General > Administration Email Address [email protected] like this:

The warning still appears.

We’ve never had any problems with the forms going through, and still don’t. WPForms come through with the “From Email” as [email protected] , and when we click reply it replies to the address of the submitter of the form, since we have all that set correctly.

And obviously [email protected] is not going to be a valid email address because a valid email address cannot contain www. after the @ and before the domain.

Please don’t get me wrong – I’m not complaining; this is just constructive feedback for the WPForms team.

I was considering submitting a ticket directly to PRO support, but since this thread is already here and the WPForms team are aware of it now, hopefully they can use this feedback here to improve the wording in the warning and possibly get WPForms (both Lite and Pro) to understand that two options in the examples above are valid and work fine, and that recommending users to include www. after the @ is incorrect and will potentially create issues / confusion for some users just starting out.

I understand that WPForms is promoting the WP Mail SMTP plugin and it is a great option for many users, but it’s not going to be for everyone. For some of my clients it will generate ongoing extra steps for me because some of them change their email password frequently and are not comfortable making Plugin modifications (or anything in WP for that matter) to their sites, and they send all such change requests to me.

WPForms is great, and in my opinion the Pro version is the best form plugin around in regard to making it easy for anyone to create and integrate beautiful (even complex) forms of all kinds into their site / pages / posts. It’s a 5-star form plugin IMO, but occasionally there are little issues like this that appear in updates.

It would be great if the WPForms team would take a closer look at this particular issue and at least make some adjustments to when that warning appears and how it is worded.`

Appreciate you chiming in, maybe I did not explain the issue in the best way to explain what the problem is, but you covered it nicely, thank you. Hopefully it is understood now and I am not the crazy guy in the room … LOL.

@xolite – You’re welcome, and you did a fine job at pointing out the issue and how it differs when the www is present in the URL as opposed to just the TLD without the www. I just wanted to add more detail and show that this is not an isolated issue.

@niksebastian – any chance you could get the WPForms team to take a close look at my detailed post above? https://www.ads-software.com/support/topic/confused-with-error-from-email-address-does-not-match-your-website/#post-16006220

And possibly get the team to address the issue? We’d really appreciate it very much, thank you.

Hi @davengmgw and @xolite,

Thank you for your patience here! On checking this likely seems to be a bug and will be fixed in the upcoming releases. I will keep you posted with the updates here.

Sorry for the inconvinience here.

@niksebastian thanks very much for the reply and getting the team’s attention to it. Looking forward to the bug fix in upcoming versions.

Hey @davengmgw – Thanks for your patience, I’m Prashant filling in for Nik.

When you get some time, can you please try updating the WPForms plugin to latest version as we’ve fixed the issue in version 1.7.7? Please update the plugin and let me know how it goes!

Kindly,

@prashantrai Does this apply to me as well or just @davengmgw? I was the OP, should I wait for a different update for myself?

I updated to 1.7.7.2 (I keep all plugins and themes updated daily) and still this issue persists.

@xolite – at this point you and I have become beta testers for an obviously known issue.

@davengmgw Clearly, by the way they tried to dismiss my OP and not includ me in any replies; You said it correct it in your first reply ‘I understand that WPForms is promoting the WP Mail SMTP plugin’ which entirely the reason for the “error”. PHP mail() has issues lol…

• This reply was modified 2 years, 1 month ago by xolite.

Hey @xolite @davengmgw – I sincerely apologize for the issue you’re facing, and it was an accident that I missed tagging @xolite.

I took a closer look into this, and I haven’t been able to replicate the issue. To help you with this, I would request your help. When you have some time, can you please share some additional details about the domain structure you’re on and a screenshot of the error?

Kindly,

@davengmgw Try the most recent update, it is fixed now. @prashantrai thanks for noticing me, appreciate it..

Hey @xolite – Thanks for the confirmation, and I sincerely apologize that I missed tagging you.

@davengmgw when you get a chance, please update the plugin and let me know if the issue is still there.

Kindly,