• Is there a way to hide this warning? I’m happy the domain endings are different. The site forms work just fine, the emails are delivered. Really the entry in the FAQ’s is misleading, it’s all down to SPF records. As long as the SPF records are correct for then sending email address, and it includes the server hosting the site then all is good.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Thread Starter rollstore

    (@rollstore)

    Thanks for the reply. Is there a way to turn off just the sender validation? Validating the form fields and other configuration is a good thing and it’d be a shame to lose that aspect.

    For what it’s worth your FAQ over simplifies things. It should really discuss SPF records and incorporate these checks in the validation. I think it’s quite common for larger companies to have different hosts for their websites as their email. SPF records are essentially a list of servers that are allowed to send email for a particular domain. As long as the host the contact form is running on is included in the SPF records then any mail it generates will not be viewed as spoofed. Also, when used with other plugins such as WP SMTP, the host the site is running on becomes irrelevant.

    Happy to have a go at writing a section about SPF records for the FAQ if you would like?

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    See also: Best practice to set up mail

    If you are interested in how the From header domain impacts SPF and other email authentication methods, learn about SPF Alignment.

    The prior comments on reasons for checking email domains are important and valid, yet I manage a site for a small nonprofit that has a website on one domain, and all the email accounts and data that people use on another domain – for historical reasons. The suggestion above on Disabling only specific error types of config validator is plausable, but fragile in our context, as there is no place to reliably document that kind of custom change — and importantly, it is likely that future people may not have sysadmin skills necessary to update it.

    Would you consider adding a simple toggle button to the plugin so it can be switched off and on from the WordPress Admin panel for the plugin? That would really fit with the spirit of WordPress. Thanks in advance for considering the idea.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.