Giters

zytzagoo / smtp-validate-email

A PHP library for performing email addresses validation via SMTP

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

My IP keeps getting temporarily blocked

Nguyen2014 opened this issue · comments

commented

Is there any way to run smtp-validate-email from behind proxys?

commented

Yes, there are ways (multiple), but that will not solve your original problem (and that'd be you talking too much to a server that doesn't want to talk back as much -- I'd suggest you start respecting the server's wishes instead of trying to "outsmart" it).

But, as far as code is concerned, you could probably get something going with some sort of SOCKS5 library/wrapper that'll handle the proxy connection and then rewriting/adapting certain portions of SMTP_Validate_Email to use the aforementioned connection resource to send the required commands (and get the responses).

I currently don't have the time to do it.

commented

Are you available for hire?

commented

Is there any other way to validated 10K+ emails using your class without my IP being blacklisted?
Much appreciate any suggestions.

commented
  1. What have you tried so far?
  2. Do all the addresses belong to the same/single TLD or is it a generic list of more-or-less random 10k addresses? (Or perhaps a large list spread out over relatively "few" distinct TLDs?)
  3. Is it a "one off" thing or is it going to be ran periodically? (if so, how often?)
  4. How quickly do you need to have the results?
  5. Consider how important validation really is with respect to any other parts of the thing you're building... Imagine it costs you, I dunno, USD/EUR 2K to get whatever you need it to do it (somehow) -- is it still equally critical/important or maybe not THAT much? How about if the cost was 10K? 100K?
  6. Completely free + simple + fast (bulk) validation = not gonna happen :)
  7. There are online services offering bulk validation at $0.0075 USD per email (it gets cheaper the more addresses you need and/or if you're a monthly subscriber [or similar standard business models] -- and that's the first thing I found on Google way way back when I looked into it... who knows what's available today). So that'd be 75USD for the 10k. I haven't used them though, so I can't vouch for the results.
commented
  1. I have tried to verify 2K+ addresses and have got blacklisted by CBL and spamhaus zen.
  2. Random emails with different TLDs.
  3. It's one-time run, but I'm afraid there will be another list that may have over 1M addresses.
  4. As quickly as possible.

5, 6, 7. That's what I'm trying to avoid: pay for the job I can do by myself. The only thing I want to leave for some paid third-party service to do is to check them for hygiene.

What I've recently ended up with is to send HELO command instead of EHLO and use TLDs that seem not to reveal my ip in headers. What I'm concerned about for the moment is if this method would give equally accurate results as it did before.
UPD: The method above doesn't do the trick.

BTW, thank you very much for the class, it rocks! Saved me bunch of time.

commented

Glad you found it useful.

Generally speaking, having a properly configured server (ideally more than one) on a "reputable" IP (or at least one with no bad blacklist history) goes a long way in terms of being able to talk to other servers.

I don't see a way of doing "enterprise-scale" bulk validation (without ending up blacklisted) other than distributing your checks over a bunch of different machines/IPs + slowing down to avoid "spikey" traffic pattern filters + maybe some kind of proxy shenanigans (spitballin').

Perhaps others have more ideas and/or different experiences.

commented

Well, it seems reasonable. Anyway, thank you very much for your help, appreciate it.

commented

Here a posible solution. Its work for me:

  1. Sure you ip no banned, prevent the block, verify next indications:
    [http://curlybrac.es/2016/07/27/how-to-configure-a-mail-server/]
  2. Also see: [https://github.com/hbattat/verifyEmail]