Skip to content

I can set limit for send requestPassowrd reset in parse server? #4595

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

Closed
joaoarmando opened this issue Feb 28, 2018 · 3 comments
Closed

I can set limit for send requestPassowrd reset in parse server? #4595

joaoarmando opened this issue Feb 28, 2018 · 3 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@joaoarmando
Copy link

Hello, I have not found anything in the documentation on, so, if this is there somewhere, forgive me for letting it go unnoticed. I'm using mailgun to send emails, like verification, and reset password. But let's say a "human profiteer", keep clicking on send the password reset email, there will be 2 things.
1- Flood of messages from my app in the user's email.
2- Email limit has exceeded, causing me to have more costs.
I would like to know if there is any method to set a time limit, for example, the user sent 1 e-mail, and it did not arrive (okay, there may have been some problem, or email has not yet been sent yet), then the user sends again an email to reset password. I would like to prevent this user from sending you another email for the next 1 hour. Do I have to do this manually? Thank you!

@flovilmart
Copy link
Contributor

such feature isn’t implemented yet. But that would be an interesting enhancement

@willsmillie
Copy link

I implemented a similar feature by adding a bool called "resetSent" to the User column which is set to true if a reset link has been sent, and false when it has been successfully reset by the user. If a password reset is requested and the "resetSent" is true, it wont send it the email.

@stale
Copy link

stale bot commented Sep 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

4 participants