Email Verification Proxy System Setup
Budget: $30 – $250 USD
I run a high-volume email verification platform and our current proxy pool is hitting a wall—Gmail and Outlook/Hotmail addresses trigger frequent IP blocking long before throughput targets are met. I need someone who has actually built rotating proxy infrastructure for SMTP-based verification (not just scraping) to design and deploy a replacement that can keep pace with millions of checks per day.
What I expect you to tackle
• Architect a rotating proxy layer that automatically shifts IPs, maintains sessions, and fails over cleanly when an endpoint greylists or rate-limits us.
• Tune rotation logic so Gmail and Outlook/Hotmail see natural-looking traffic patterns, dramatically lowering block rates.
• Address SMTP-specific quirks such as greylisting delays and transient soft bounces without sacrificing speed or accuracy.
• Deliver concise monitoring and alerting so I can spot anomalies in real time and add capacity before problems surface.
Acceptance criteria
1. Verification success rate must remain ≥ 99 % over a 48-hour load test at full traffic.
2. Block incidence from Gmail and Outlook/Hotmail should drop by at least 80 % compared to my current baseline.
3. All infrastructure and code must be reproducible via a single command (Docker / Terraform, etc.) and documented for hand-off.
If this is the kind of deep, protocol-aware proxy engineering you specialise in, let’s talk.
What I expect you to tackle
• Architect a rotating proxy layer that automatically shifts IPs, maintains sessions, and fails over cleanly when an endpoint greylists or rate-limits us.
• Tune rotation logic so Gmail and Outlook/Hotmail see natural-looking traffic patterns, dramatically lowering block rates.
• Address SMTP-specific quirks such as greylisting delays and transient soft bounces without sacrificing speed or accuracy.
• Deliver concise monitoring and alerting so I can spot anomalies in real time and add capacity before problems surface.
Acceptance criteria
1. Verification success rate must remain ≥ 99 % over a 48-hour load test at full traffic.
2. Block incidence from Gmail and Outlook/Hotmail should drop by at least 80 % compared to my current baseline.
3. All infrastructure and code must be reproducible via a single command (Docker / Terraform, etc.) and documented for hand-off.
If this is the kind of deep, protocol-aware proxy engineering you specialise in, let’s talk.