Reacher
  • Welcome to Reacher
  • Getting Started
    • Verify your 1st email
    • Understanding "is_reachable"
  • Self-Hosting
    • SaaS vs Self-Host
    • Install Reacher in 20min
    • Scaling for Production
      • Manage scaling yourself
      • Option 1: RabbitMQ-based Queue Architecture
    • Licensing
      • Commercial License Trial
    • Proxies
      • Multiple Proxies
    • Reacher Configuration
    • Debugging Reacher
  • Advanced
    • OpenAPI
      • /v0/check_email
      • /v1/check_email
      • /v1/bulk
    • Run your own Proxy
    • Migrations
      • Reacher Configuration (v0.10)
      • Migrating from 0.7 to 0.10
      • Bulk Verification (v0.7)
      • Docker Environment Variables (v0.7)
Powered by GitBook
On this page
  • What is a SOCKS5 Proxy?
  • Setting up a Proxy
  • Which 3rd-party proxies does Reacher recommend?
  1. Self-Hosting

Proxies

Maintaining a good IP reputation is hard. Reacher integrates seamlessly with SOCKS5 proxies.

What is a SOCKS5 Proxy?

A SOCKS5 proxy is a flexible proxy protocol that supports various types of traffic, including SMTP. When using it for email verifications, the reputation of the proxy’s IP is what matters, not your own IP. This is crucial for maintaining deliverability and avoiding issues like blacklisting.

Choosing a reputable 3rd-party proxy will greatly improve the quality of your email verification results. For a list of recommended proxies, see Which 3rd-party proxies does Reacher recommend?

SMTP email verifications are not possible via a traditional HTTP proxy.

Setting up a Proxy

Once you've purchased a proxy, run the Docker command (see how in Install Reacher in 20min) and pass the following flags:

  • -e RCH__PROXY__HOST=<host>: The IP or hostname of the proxy server.

  • -e RCH__PROXY__PORT=<port>: The corresponding port.

  • -e RCH__PROXY__USERNAME=<username>: Optional. A username to authenticate the proxy.

  • -e RCH__PROXY__PASSWORD=<password>: Optional. The corresponding password.

  • -e RCH__HELLO_NAME=<domain>: The identifier to use during the "HELO/EHLO" step. It should match a domain name owned by the proxy. Ask your proxy provider about this setting.

  • -e RCH__FROM_EMAIL=<email>: The email to use during the "MAIL FROM" step. It should be an email from the same domain as the HELLO_NAME. Ask your proxy provider about this setting.

If you're using the Commercial License Trial, these fields are already populated with the built-in proxy. However, you can overwrite them by passing these flags again, pointing to a proxy of your own choosing.

For advanced usage, you can configure Multiple Proxies.

Which 3rd-party proxies does Reacher recommend?

PreviousCommercial License TrialNextMultiple Proxies

Last updated 12 days ago

Reacher has been working closely with since early 2024. The service is run by Jon, an email verification expert who has had over 10 years experience in the industry. He understands the complications and challenges that arise from large scale SMTP connections. His proxies integrate seamlessly with Reacher, and are tailored for B2B emails.

Ask for an introduction to Jon.

Proxy4Smtp
amaury@reacher.email