# New user auto-silenced with no option to approve?
**URL:** https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708
**Category:** Support
**Created:** [10.Январь.2018 22:53:02 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708 "2018-01-10T22:53:02Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@bts](https://meta.discourse.org/u/bts)
#### Post date: [10.Январь.2018 22:53:02 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/1 "2018-01-10T22:53:02Z")
Just had a user get blocked (“silenced”) by system while trying to make their first post, for reason = typing too fast. The user mentioned he was copying something written in another document so that makes sense. But a bit confusing trying to resolve this as an admin:
1. I went in and manually un-silenced the user and told him to try posting again. But when he did, same thing happened. Maybe it would make sense to turn off the auto-block measures in the case an admin has manually overruled it?
2. In [this post](https://meta.discourse.org/t/users-automatically-blocked-by-system/41579/8) from 2016 @codinghorror mentions that “blocked posts by new users always come into the approval queue” — but we didn’t get an admin notification here, it seems this user went straight to “silenced” with no way to approve or not. Only saw it happened at all b/c the user emailed us. If it _were_ the case that this was flagged w/ option to approve, that would be 👍 too!
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [10.Январь.2018 22:53:47 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/2 "2018-01-10T22:53:47Z")
Is this new user pasting in the content of their first post? That’s highly consistent with spam behavior.
---
### Author:  [@bts](https://meta.discourse.org/u/bts)
#### Post date: [10.Январь.2018 23:00:21 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/3 "2018-01-10T23:00:21Z")
Yes they said they have a large topic prepared and saved elsewhere…I can see how it makes sense to flag as suspicious, just would like to have a way to manually verify in that case.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [10.Январь.2018 23:01:44 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/4 "2018-01-10T23:01:44Z")
I believe there is a site setting for this, did you look there? Check under `notify mods when user silenced`. That’s all you need.
---
### Author:  [@bts](https://meta.discourse.org/u/bts)
#### Post date: [10.Январь.2018 23:08:48 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/5 "2018-01-10T23:08:48Z")
Ah thanks, didn’t see that, just turned it on (maybe that setting should be enabled by default…)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [10.Январь.2018 23:12:46 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/6 "2018-01-10T23:12:46Z")
We usually don’t want that, because the spammers are very persistent.
---
### Author:  [@bts](https://meta.discourse.org/u/bts)
#### Post date: [10.Январь.2018 23:44:19 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/7 "2018-01-10T23:44:19Z")
Gotcha. Then we’ll consider ourselves lucky; I believe this is the first possible-spammer-auto-silence we’ve seen, in several months of active forum! Possibly b/c Wordpress SSO is an extra barrier, or we’re just not a big enough target yet 🙂
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [08.Июнь.2024 12:43:37 UTC](https://meta.discourse.org/t/new-user-auto-silenced-with-no-option-to-approve/77708/8 "2024-06-08T12:43:37Z")
Эта тема была автоматически закрыта через 2340 дней. Новые ответы больше не принимаются.