feat: Add disposable email blocking system to prevent user registration noise #75
Conversation
…on noise - Add comprehensive list of 700+ disposable email domains - Implement smart email validation with subdomain detection - Add configurable blocking via BLOCK_DISPOSABLE_EMAILS env var - Add strict mode for business-only domains via EMAIL_STRICT_MODE env var - Integrate validation into manual signup and social auth flows - Provide user-friendly error messages with helpful suggestions - Include comprehensive test suite with benchmarks - Add detailed documentation and configuration examples This feature helps maintain user quality by blocking temporary/throwaway email addresses while providing clear guidance to users on alternatives.
|
|
✅ Deploy Preview for hoppdocs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Thanks for the PR @shree-xvi 🙏 Some points to make this PR mergable.
-
The domain list is quite arbitrarily generated, so it will be hard to maintain without any fetching/syncing step with a remote source in the long run. I would simplify the implementation a lot by going with a library like this one lindell/go-burner-email-providers as they have a maintained list, and currently contain 27.280 domains. The libs' API is also super easy to use.
-
Readme for this feature is not needed.
-
You can also add the
BLOCK_DISPOSABLE_EMAILSin our env file here hopp/backend/env-files/.env.local at main · gethopp/hopp with what the default value should be.
|
Closing in favour of #116 |
3 participants
This feature helps maintain user quality by blocking temporary/throwaway email addresses while providing clear guidance to users on alternatives.