.solutions TLD not recognized as valid email address in contact form

[Thumper]

Hey Pablo,

I just found what I believe to be a bug in forms. I have always used the Form Wizard to create a form based on a template. I then always use the Business Contact form. Whenever I have tested it I have had a "normal" email address with a .com, .net, .org TLD and it always worked perfectly.

Recently I changed my business name to ******* Solutions and thus my email address changed to myname@mysite.solutions. When I tested a form I used on a client's new website "Contact Us" page, I used my new email address to test it. I always use validation for certain fields, especially email addresses. I got an error message that said, "Please enter a valid email address". No matter how many times I tested it, using different parameters such as "No Constraints" and "Text", I either got that message in a message box or when the Submit button was pressed it returned the Error page I had specified. Yet when tested it with my personal Gmail email address, it worked perfectly.

It seems that somehow, you are checking for certain TLDs for validation. The .solutions TLD was first approved in 28 December 2013 and was generally available on 26 March 2014. So this TLD has been around for quite a while. I tested some other TLDs (.io [1997] and some others) and they all seemed to work.

I can provide my project if you need it but this doesn't appear to be a project issue since it works with "normal" TLDs.

[Thumper]

I just received a "test" from Jonny. I'm not sure if Jonny is just another member of the forums or if he works with Pablo.

The contact form went through but that's because he used a .com TLD...NOT a .solutions TLD. Note the DOT before the "solutions". (DOT)solutions is a Top Level Domain. Using @solutions.com to test it will obviously go through since the Top Level Domain (TLD) is (DOT)com!

[Pablo]

This is not a bug. This is a configuration issue.
The form script does not matter which email addresses you use. It is most likely server which is blocking the email.
You may be able to solve this by specifying a different 'from' address in the form's properties.

[Thumper]

This is a configuration issue.
The form script does not matter which email addresses you use. It is most likely server which is blocking the email.

Pablo...I don't understand what you are saying here. I am NOT saying that I am not getting the email with the form data sent to me. It is being sent to that address.

I am saying that the validation of the email address, if a (DOT)solutions TLD is be entered in the "Email" field, is generating an error to enter a valid email address. When I enter data into the form by entering information in the fields on my Contact web page using my VALID email address in the "Email" field, I am getting that "Please enter a valid email address" error.

Where does any server even enter the picture at this point in time? The form won't validate the data in the field to even send it out!

You may be able to solve this by specifying a different 'from' address in the form's properties.

Why does this have anything to do with what the person viewing my site and entering data into the form? If they also happen to have a (DOT)solutions TLD, as an example, pablo@wysiwyg.solutions ... it will NOT validate! Yet, if you entered pablo@wysiwyg.com, or .net, or.org, etc., it WILL validate!

Please explain your response further as I believe you are thinking about the form data being sent to me, which is NOT what I wrote about. I felt I was quite clear about what was happening!

[Pablo]

Sorry, then I understood your information incorrectly.
At the moment this is not supported by the built-in validation. I will investigate if it support can be added in a future update.

[Thumper]

I will investigate if it support can be added in a future update.

Thank you Pablo. The (DOT)solutions TLD has been around since 2013 and widely available since March 2014. With more having been authorized since then, this might be a daunting task if you somehow have them coded in.

[Pablo]

This is the first time I have feedback about this. so this is not frequently requested functionality.
But I will investigate if this can be implemented.