Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - Add proxies for email verification #53

Open
ashleykleynhans opened this issue Jun 13, 2017 · 2 comments
Open

Feature Request - Add proxies for email verification #53

ashleykleynhans opened this issue Jun 13, 2017 · 2 comments

Comments

@ashleykleynhans
Copy link

Now that email verification is rate limited, it would be great if you could add a feature where the mail server can read an optional config of proxies to get around the rate limit issue.

@drallieiv
Copy link
Owner

Until mail and core are united in a single service, implemeting proxies on both modules will still cause issues if the 2 modules share the same IPs. The 503 errors thrown by PTC fronts are shared for both creation and activation.

Currently, the creation with core has a server side limit of 5 accounts per 16 minutes, which makes around 20/h.
While the validation server has a limit of 6 per minute, which is around 360/hour

So unless you are using more then 18 IPs, the mail server is faster then the account are produced.

@ashleykleynhans
Copy link
Author

Yeah, I'm using lots of IPs which is why I encountered this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants