|
|
|
|
|
by bedatadriven
1189 days ago
|
|
Removing user-controlled input indeed removes the incentive, but for reasons beyond my comprehension, our sign up form _still_ gets periodically blasted. Without additional countermeasures, our sending reputation would be at risk. We apply a few strategies... 1. Require oauth-based sign up for gmail.com, hotmail.com, and live.com addresses. No emails sent until after authentication. 2. Drop obvious spam. If your name contains "http://" or "Whatsapp" or your User-Agent is "python-requests" than you get a 400. 3. Manual approval for suspicious sign ups. High Abuse IP DB scores, statistically unusual names, etc generate a help desk ticket that someone from our staff approves before an email is sent. Persistent bad actors are blocked by IP for 2 weeks. 4. Rate limiting by IP. This prevents bad actors from spamming our help desk. All together this seems to have largely solved the problem... for now. |
|
When I did this, the spammers got more creative trying other ways to get through.
Now I return a 200, and the response looks identical to a successful signup.
The only difference is nothing actually happened on the backend.