Knowledge base

An increasing number of anti spam systems looks for information on the IP address which is contacting the SMTP servers they protect; a good habit for every Internet company – in general, at least – is to map the public IP address to something pertaining to them, using a reverse PTR DNS record. If this is the case, you should make sure that EmailVerify.NET is configured correctly to benefit from this scenario:

• Make sure the LocalHostFqdn property matches the one shown in your PTR records
• Make sure your public IP address is not black-listed by the various DNS anti-spam black lists out there

Even if not required, the presence of an SMTP server on the machine where EmailVerify.NET is running may increase validation accuracy too. If this is the case, you should also make sure EmailVerify.NET is configured correctly to benefit from this scenario:

• Make sure the SMTP server is bound to and is available from a public IP address
• Set up the LocalSmtpEndPoint property according to this IP address
• Set up the LocalSenderAddress property to a real email address which has a corresponding mailbox handled by the SMTP server