Hi,
I have a webform setup and have used the contact-email SuperOffice element field to be the e-mailadres field of my form.
To test the the form I have setup some temporary e-mail addresses like e.g.: test1@mydomain.com , test2@mydomain.com etc.
The question is , how is this validated and why are my "valid" and existing e-mailaddresses marked as "not valid" and non-exising made-up e-mailaddreses are markt as "valid".
Hope someone can clearify this behaviour and how we can fix this.
br/
Mehmet
PS: 8.5 R17 on-prem.
All Replies (4)
Hi,
To validate the email address, we are looking up the domain which was typed into the form, and we look for the mail exchanger record (MX record) which specifies the mail server responsible for accepting email messages on behalf of that domain name.
mydomain.com is a registered and valid domain with an MX record, which means it is expected to pass the validation test.
gisbs.nl is also a registered and valid domain with an MX record, and should pass the validation test too.
During the years with different versions of SuperOffice, there has been made adjustments to this validation procedure. Which means there might be a bug in a former version.
1) Please make sure you did not type in a space at the end of the domain before validation. Could be an issue there.
2) Can you please send us a link to your published form? Then we might be able to see what is going wrong in your scenario.
Best regards,
Trude
Hi Mehmet,
in onsite installations we use the local DNS Service to check for MX Records.
If the local DNS Service is not able to get the MX Record for an domain it will fail.
Sometimes made up domains really exist. like mydomain.com has a valid MX record :)
You can test it like this from the Server:
1. Open the command prompt.
2. Type "nslookup", then press Enter. You will see the following: Default Server: <FQDN of your server> ...
3. Type "set type=mx", then press Enter.
4. Type the domain’s name that you want to look up, then press Enter. The MX records of that domain will appear.
Hi Alexander,
Thank you for the insight , this is/was verry helpful.
Did a check with NSLookup and turns out that NSlookup for our own domains fails to get the mx records internally.
We have to look if we want to correct this.
Thank you!