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

can the script itself be open sourced? #1

Open
gammons opened this issue Jun 5, 2024 · 2 comments
Open

can the script itself be open sourced? #1

gammons opened this issue Jun 5, 2024 · 2 comments

Comments

@gammons
Copy link

gammons commented Jun 5, 2024

Hi, this README is excellent. I am the solopreneur of truelist.io and I wanted to see how Truelist's results stack up against the services you've measured in the README. Wondering if you could open source the script and test list so I could add Truelist's results as well!

@centminmod
Copy link
Owner

Hi Grant thanks for the kind words and for taking the time in reaching out here.

I wrote the script for my private use in assisting me with my clients - mainly Xenforo forum owners in cleaning their email lists. As such, I have no intention of open-sourcing the script. And the test list of working emails segment at least are my own email addresses so not something I'd want to be sharing :)

All my clients would be cost-conscious, so they would look at PAYG pricing rather than monthly - hence the list of email verification providers I ended up selecting to test.

@gammons
Copy link
Author

gammons commented Jun 9, 2024

No problem, I understand.

Anyways, I read your reddit post. Yahoo's mail servers are configured for accept-all, so mail verification services have to find alternate methods of determining if an email exist (e.g. they can't do it just via SMTP validation). Depending on how MillionVerify is doing that, you may indeed have run into a bug.

One other thing I'll mention is that depending on the size of the list and how many emails appear on the same domain, rate limiting can occur on the host. If you're verifying using an api in real time (e.g, you're waiting for the results during the request), that not usually enough time to retry transient temporary connection errors, and thus you might get an incorrect 'invalid' result sometimes. This is especially true if the host is using a weird our outdated mail server - especially one that does greylisting.

Truelist competes on price with a lot of the services you tried (although some are significantly cheaper, but you get what you pay for IMO), so it might make sense to add it to the pile.

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

2 participants