Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IP-based method #48

Open
phillipp opened this issue May 23, 2017 · 2 comments
Open

IP-based method #48

phillipp opened this issue May 23, 2017 · 2 comments

Comments

@phillipp
Copy link
Owner

Hey @korny

just an idea, because it might be easier to scale: we once had the idea to perform a lookup of the ip addreses of the MX records of the domains in the list and generate a list of the mailserver IPs.

Then the e-mail validation cloud check the MX record of the email domain against that list. It's much harder to get more IP addresses than domains, so that might be a more effective list to manage.

Just an idea, maybe you find it worth looking into.

Phillipp

@korny
Copy link
Collaborator

korny commented May 25, 2017

Great idea, but I'm not sure it actually works for the most problematic providers.

You can do the lookup in Ruby using resolv. But the latest example from 10minutemail.net (tipsb.com) resolves to four different IPs:

["li991-34.members.linode.com", 10], ["li1175-43.members.linode.com", 10], ["li984-13.members.linode.com", 10], ["li335-83.members.linode.com", 10]

which is not really helpful if these are throw-away instances.

Also, the blacklist check needs to be fast - a DNS lookup can take a while. If we could rely on some public blacklist service, and update the list behind the scenes every hour or so, that would be awesome...

@motionless
Copy link

I know this issue is old.
My PR - #97 might address that issue in a different way but also looking up the MX record. I'd appreciate your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants