Email Validator FAQ-2

I've tried your Email Validator component and I want to buy it. But the validation process is taking a very long time. Is it possible to shorten the processing time?

Yes, it is possible to set SMTP time out.

Some email address using Email Validator component take a long time, especially if it is a bad email address. How to stop the process and notify us if the process does not complete within 30 seconds? How can we set the 30 seconds to get the failure notice?

If it is known bad email address, you can add into bad email address list forever. Please note that SMTP timeout property accepts time in sec not in millisecond. Hence assign value 3 for 3 Second time out not 3000.

We bought the Email Validator; we are trying to use the DLL. We are getting the error saying that, "SocketException: error message " An existing connection was forcibly closed by the remote host"while executing 'Validate()'. What could be the reason?

There are the things that you should make sure
1) Your firewall is not blocking MX query
2) Antivirus software is not blocking MX query or connection to mail server outside your network.

What could be the parameters for DnsServer, SmtpFromEmail, SmtpFromDomain ? I am running on my local machine.

You should get DnsServer IP address from your network administrator. This varies from organization to other. SmtpFromEmail is email address which will be used to communicate while doing MX query to destination server. E.g. yourname@xyz.com. SmtpFromDomain is email server address which is used as base to communicate while Doing MX query. E.g. mail.xyz.com or smtp.xyz.com.

Using your Email Validator some email addresses on the validation check is failing when checking the emails. The error that is returned is: Recipient address rejected: Grey listed for 5 minutes, Is there any around this?

For this error could be security configured on destination mail server. Such email server is checking From Email address and SMTP server from where you are querying. If this found to be fake or incorrect it returns this error. You might be using email server and email used in demo. These are smtp.neevsoftware.com and info@neevsoftware.com. You should use your email server in EmailValidator properties.

Do you have a sample code in ASP.NET visual basic?

You can find the examples in documentation. Please have a look at documentation for code samples. In Documentation, there is a topic named Examples, in that topic you can find code samples for both C# and VB.NET.

I purchased the single developer license, but it always fails when connecting to the domain server. It always works when I use demo@neevsoftware.com

Demo version uses Neev Software's mail server and DNS server. Please change mail server and DNS properties as per you network settings.

I have been having a fair bit of trouble trying to get your Email Validator into the toolbox in VS2008. I am new to VS. What is the correct process for installing your control into VS?

Email Validator is Component not a Control so you can’t get it into Toolbox. Add reference to Email Validator assembly and namespace to code file where you want to use. This will allow you use Email Validator object.

I purchased Email Validator and managed to get the control to work on my web site fine no problems, I transferred the working page onto the live site but it keeps telling me the email address is invalid all the time, any suggestions please.

Please have a look at Validation Log. This will help you identify where it not working. Possible reason could be
1) New environment is blocking MX query other mail servers
2) DNS and mail server properties need to be changed.

I purchased the Email Validator component. It has been working for a long time until just recently; I put your demo version in my domain. The property values are hard coded rather than entering in text boxes.

Email Validator works with help of values set in its properties. If u set server names, such as from email, DNS, etc, which does not allow MX Query through external program you may get security problem.

more FAQ