Multiple Proxies
For advanced use cases, Reacher supports a routing mechanism to route email verification requests to different proxies depending on the MX host.
The configuration is divided in 2 steps:
Define a list of proxies. e.g.
"proxy1"
,"proxy2"
etc...Define routing rules, e.g.
route Gmail to "proxy1"
,route Hotmail B2B to "proxy2"
etc...
1. Define a list of Proxies
The simple Reacher configuration allows to define a default proxy via the following environmental variables:
RCH__PROXY__HOST
: The hostname of the proxy.RCH__PROXY__PORT
: The port of the proxy.RCH__PROXY__USERNAME
: (Optional) A username for authentication.RCH__PROXY__PASSWORD
: (Optional) A password for authentication.
On top of the default proxy, Reacher allows you to configure multiple other proxies:
RCH__OVERRIDES__PROXIES__{your-proxy-id-uppercase}__HOST
RCH__OVERRIDES__PROXIES__{your-proxy-id-uppercase}__PORT
RCH__OVERRIDES__PROXIES__{your-proxy-id-uppercase}__USERNAME
RCH__OVERRIDES__PROXIES__{your-proxy-id-uppercase}__PASSWORD
Replace {your-proxy-id-uppercase}
with any unique name of your choosing. We recommend to use PROXY1
, PROXY2
for simplicity.
2. Define routing rules
Reacher allows to configure custom routing rules based on the MX host. To do so, set the following environment variables:
RCH__OVERRIDES__{email-provider}__TYPE=smtp
RCH__OVERRIDES__{email-provider}__PROXY={your-proxy-id-lowercase}
where you replace:
{email-provider}
with one of the followingGMAIL
,HOTMAILB2B
,HOTMAILB2C
,PROOFPOINT
,MIMECAST
,YAHOO
.{your-proxy-id-lowercase}
with one of the proxies you defined in step 1. Make sure to respect the lowercase here.
You can define multiple of these RCH__OVERRIDES__
environment variables for different MX hosts. All the remaining emails which don't match any of the overrides will go through the default proxy.
Example
Below is a Docker Compose file showcasing:
routing Gmail and Proofpoint emails to proxy1
routing Hotmail B2B emails to proxy2
routing everything else to the default proxy
Last updated