The password reset logic confirms whether en email exists in the user database. This is generally considered bad practice as it enables malicious users to “query” discourse user db. DigitalOcean is a good example of being vague about the provided email, “if the email you specified exists in our system, we’ve sent a password reset link to it”
If you want this, enable it in site settings. Already exists.
By default we tell people since they can never remember which of their 10 email addresses they signed up with, so it is user hostile to force them to walk through all 10 emails to figure out which one they used on your site.
The signup form already gives away if an email address already exists (and turning that off doesn’t make sense) so it doesn’t really matter here, it doesn’t make that attack vector go away and it only makes things harder for users who actually forgot their password (or: forgot their email address)
@codinghorror thanks I didn’t know there’s a setting for it
@michaeld yes, it is true that the sign up form confirms for the existence of an email but one can reduce the email visibility by integrating Discourse with external identity providers or creating a custom sign up form with CAPTCHA.
There are already rate limits on these forms, try it yourself.
これは古い投稿だと思われますが、もし他の人がこの問題に遭遇し、既存のコミュニティメンバーのメールアドレスを検索できることを心配している場合、Discourse は簡単な修正を実装したようです。「hide email address taken」を検索して有効にしてください。これにより、ユーザーが「forgot password」を使用してサーバーのメールアドレスを照会できなくなります。
これを関連付けるために、このコミットでこのトピックの一部として追加されました - Hide 'email account exists' for invites \n\n\nhttps://github.com/discourse/discourse/pull/16703\n\nいいえ、注意していませんでした。 
それは、その設定を招待画面を含めるようにさらに拡張するためでした。それでも、言及してよかった興味深い追加です。
