• Resolved flamenco

    (@flamenco)


    Hi!
    Not urgent, but possibly useful information for a CF7 update…

    I also noticed the new validation error. My emails have not had any problem working, but I decided to try to try eliminating the error anyway to keep things as legitimate as possible.

    I set up new headers for “Sender” and “Reply-to”. Most importantly, I changed the “From” to use an address on the site’s domain. My test email worked just fine, reply-to works, and so on.

    However, I still get the same configuration error above! I finally tracked it down – my site is on an add-on domain, which is connected to a subdomain. I was able to eliminate the error by using an email address with the subdomain instead of the add-on domain. Wild, eh?

    So I gather that CF7’s validation test can find a subdomain, but is not aware of the add-on domain “on top of it”, at least on my host. ??

    This could possibly cause concern in some users. I hope that helps!

    Great job in any case!
    Dave

    https://www.ads-software.com/plugins/contact-form-7/

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

    (@takayukister)

    There is no way of distinguishing a subdomain and “add-on domain”, so the false warning isn’t avoidable at least for now. Future releases may provide a filter that allows you to hide specific errors.

    Configuration errors don’t affect front end form submission, so you can safely ignore the error if you know it’s not important.

    BTW, you don’t need to set “Sender” here.

    I set up new headers for “Sender” and “Reply-to”.

    Thread Starter flamenco

    (@flamenco)

    Mr. Miyoshi,
    I thought that might be the case – the add-on part. ??

    I appreciate your reply and advice! The error message doesn’t bother me – I hope this helps you with others who might ask this question when they don’t realize an add-on domain is being used.

    As always, it’s sending well for me, and this is still my favorite form plugin, even though I’ve used a lot of them!

    Thanks as always, arigato,
    Dave

    Thanks for clarification!

    I haven’t got a clue what you are talking about. How on earth it does make sense using the FROM field when it suppose to be where is it coming FROM .

    My website contact form is not working, I am getting the “Failed to connect to mailserver!”

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    In the “From” field I have put My Site <no-reply@mysite> to conform.

    Is it possible to have it so that when I hit “reply” it goes to the sender (rather than back to me). If so how?

    Thank you Mr. Miyoshi for a great form and for answering. Just to clarify:

    1. is it best to have the “From” field populated with “[email protected]” or such rather than the form-sender’s info?

    2. then the additional header would have “Reply-to [your-name] <[your-email]>” and if I want to reply to the sender it will grab this header info?

    Thread Starter flamenco

    (@flamenco)

    Just FYI for anyone interested.. the latest update (4.4.1) does “relax” the error checking for the form.

    To have it fully take effect, I updated the plugin and then re-saved my forms, tada, no error message.

    I knew he’d see it my way! ??

    Dave

    I can no longer have a user’s email in the “from” field now due to it not having the same domain as my own site, which is something that would never happen.

    This is a bug. I had to make up a fake email address so it would pass validation and actually send the email. I am using Version 4.4.1.

    I look forward to it being fixed.

    This error is very easy to fix.

    The reason for this headache is in the misunderstanding of this field. We all understood The “From” field as a user email address, however the ones who built the form, want it to be a field that will indicate to the email’s receiver where the email originated. The answer to the problem is in the documentation https://kb.cf7skins.com/contact-form-7-email-issues/#spam where the developers explained that this field is suppose to have the same domain name as the website to avoid spamming.

    For example if your website is: https://www.mywebsite.com, all you need to do is put the following data in the email field
    From : [email protected]

    This email doesn’t need to be valid. so when the user submit the form, you will receive an email with from: wordpress <[email protected]>
    if you want to replace that default “wordpress” in the from field, for example type in the From field: Contact Us Form <[email protected]> again [email protected] doesn’t need to be valid. most important to remember is mywebsite.com should match the domain name of your website.

    You may think where to put the user’s email address, you could add it in the additional header or the message body. That is the way the contact form 7 developer came up with this preventing spams idea, I would have done it different way ??

    Hope this will help.

    • This reply was modified 8 years, 1 month ago by epsilon0.
    • This reply was modified 8 years, 1 month ago by epsilon0.
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘"email address does not belong to the same domain as the site" – subdomain’ is closed to new replies.