Email List Cleaner
Email List Cleaner is a Ruby program that verifies large lists of email addresses stored in a CSV file.
It was used to clean and sort a list of 400k emails that were collected over the years by a friend of mine. Spread out across 50 proxies, the entire process took a few hours.
A tool like this comes in handy when you need to send massive email campaigns — as many services such as SendGrid, MailChimp, and CampaignMonitor will penalize you for sending to addresses that bounce. Running Email List Cleaner will ensure you don't pay for sending to invalid addresses, or risk possible termination of your account with those email delivery providers.
There are many commercial services that perform this function, but they're extremely expensive. Why pay for something you can do yourself with a little bit of automation?
- Ruby 2.3.x
- Redis Server
- A publicly reachable IP (a shell account at co-location facility) — OR — SOCKS5 proxy servers (see below)
- A CSV list of email addresses (_list.csv)
How It Works
- Email List Cleaner loads all addresses into a Redis Set, which removes duplicates.
- It then utilizes the email_verifier gem, which does a number of things, but ultimately connects to each SMTP server to verify using SMTP commands.
- Finally, it will dump CSV files of "good", "bad", and "todo" (if any remain)
How To Install
git cloneto your computer
How To Use
- Copy config-example.yml to config.yml, read the comments & edit appropriately
- Provide a _list.csv of email addresses
- My list was in the format "name", "email" ...so the program expects your
_list.csvto follow suit.
- Check the
scriptfolder for easy to run examples.
- This script is meant for consumption by Ruby devs that know what they're doing. "It worked on my machine", but you might run into issues. I encourage you to download it, give it a try, and send me a pull request to make it work in a broader range of situations.
- Starts a run of Email List Cleaner. You can savely cancel out of it (CTRL-C), and it will continue to run in the background.
- If the run of Email List Cleaner got interrupted for any reason, this will continue with the data available inside Redis.
- Dumps statistics of current run to the console.
- Saves CSV files to after a run has been completed. Will dump tmp/_list_bad.csv and tmp/_list_good.csv
Using Proxy Servers
I strongly suggest you use this with multiple proxy servers — as the program is written to thread requests across proxies so completion happens faster. There are lists of freely available proxies online if you Google, but I've also written another Ruby program that will spin up as many proxies as DigitalOcean will allow you to have droplets...
!!! VERY IMPORTANT - Read so you don't get your IPs blacklisted
Due to the nature of the check, some MX (mail) servers will ban or "blacklist" you from automating this process too quickly from one IP address. The Microsoft family of email addresses in particular (Hotmail.com, MSN.com, Live.com, Outlook.com, etc) are very sensitive to this tactic.
Here's the error message that mx.hotmail.com will return in the above scenario:
550 SC-002 Mail rejected by Outlook.com for policy reasons. The mail server IP connecting to Outlook.com has exhibited namespace mining behavior. If you are not an email/network admin please contact your Email/Internet Service Provider for help.
...And an explanation from the Outlook.com website:
Namespace mining is a method commonly used by malicious senders to generate lists of email addresses. This approach uses automation to sift through possible email names seeking to identify valid email addresses, e.g., Joe@domain.com, John@domain.com, and Josy@domain.com.
I'm unsure of the EXACT sleep_time parameter that's necessary - but if you trip their alarms you will need to ditch your current IP. I recommend a cloud provider like Digital Ocean or Linode in this scenario so you can spin down/up instances quickly if you get banned. Keep your Redis instance separate so you don't lose your work each time.
My advice? Increase the "sleep_time" parameter in the config.yml file (if you can wait), or add "proxy_servers" if you're checking a very large list.
Due to the Hotmail mail server issue noted above, I've been thinking of other ways to verify those Microsoft accounts. One solution in particular involves using PhantomJs to make web requests to Microsoft login properties, who give the helpful message "there's no account that fits that description…". Maybe in the future.