Let's imagine you have a list of e-mail addresses containing 72'000 entries and you need to test every single address with eMail Verifier. So, you load the list and click on the 'Verify' button.
How much time are you willing to wait to get the process complete? 10 minutes, one hour, a day? Well, there is no way to get an exact answer until you actually process the list, so we did it. Result, it took us around 14 hours to clean a list the size of 72'000 emails. You may think, wow, I cannot afford to lose that kind of time!... well, eMail Verifier can run unattended, no need to wait in front of it. If you need to test lists this size, just do it overnight!
Why did it take that much? Let's see,
72'000 DNS requests + 72'000 SMTP connections in 14 hours? This is actually quite fast! Well, maybe there are less requests, perhaps 60'000 because of possible duplicates... but usually a DNS request + a SMTP connection takes at least one second and a half. eMail Verifier spends most of its time waiting for responses from servers. DNS query response time may vary. SMTP connections may time-out. A low quality list can cause lots of timeouts and lots of useless wait time.
How are addresses getting tested? DNS requests are to resolve addresses. Usually a Domain Naming Server (DNS), or Domain Name System, is what turns an internet name like www.yahoo.com into an internet address such as 126.96.36.199. It may also tells us the address of the relaying mail server of an e-mail address. So eMail Verifier asks the server, waits, and gets a response. From this response it extracts the SMTP server address, tries to connect to it and simulates the sending of a message. You can see the whole process in the eMail Verifier 'Console' panel. It looks like this:
The first line is the DNS lookup followed by the SMTP connection and finally the message delivery simulation. In this case it takes 6 seconds to complete the verification. This is because we are testing one single address, one single thread and no grouping of addresses by domain. Indeed, in order to spend as few time as possible, eMail Verifier only performs a DNS lookup once per domain and takes advantage of every opened connection to a server to verify as many addresses belonging to that server as possible.
Can I go faster? Well, if you have a good internet connection you can try to set the Threads number from the eMail Verifier preferences to a higher number. Default is 10, 10 DNS requests/SMTP simultaneous connection threads. You can also enter faster DNS servers or decrease Retries and Timeouts settings, by default eMail Verifier will retry 3 times and wait 15 seconds between each attempt.
As said before, a low quality list can cause lots of timeouts and lots of useless wait time. There are perhaps some more adjustments but leaving an e-mail Verifier or a bulk emailer software working overnight is actually quite usual. Just remember to deactivate the operating system sleep mode feature.
If you want to make the most of the software that you have acquired at Maxprog, do not miss the Stan's Blog. It is a library of Tutorials and Tips covering specific features and tipical problems you may have when using our tools. This page is updated regularly depending on the topics discussed in our public forums and issues reported thru our HelpDesk. If you are interested on what we are currently working on (or want to participate in beta testings) don't miss the Stan's Logbook.
For years, MAX Programming has provided companies around the globe with sophisticated and innovative solutions. Our commitment to quality is not only evident in our products, but also in our people. It is our mission in Professional Support Services to ensure that our products perform to the fullest of their ability in order to meet the business objectives of our customers. We provide the tools and information required for improved productivity. To accomplish this, we offer an array of services including: Technical Support, Education Services and Consulting Services.
WAIT! In order to add a comment below just use your Facebook, Google+, Twitter or Disqus login data.