# Pre-seeding banned/suspended member list

**URL:** https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204
**Category:** Support
**Created:** [10 februari 2020 om 17:45 UTC](https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204 "2020-02-10T17:45:29Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![RubyRhod](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rubyrhod/32/40260_2.png) [@RubyRhod](https://meta.discourse.org/u/RubyRhod)
#### Post date: [10 februari 2020 om 17:45 UTC](https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204/1 "2020-02-10T17:45:29Z")

</div>

I have started to invite members over from our old board. So far, so good!

But I have 500 or so ‘bad actors’ from over the years who I’d love to pre-ban if possible. Is it possible?

The evil way would be to invite them into a group with no permissions, but I’ll bet 90% of them have mostly forgotten about us, and an email to remind them would not be cool.

What do you suggest? So far I have a list posted in our staff section of the banned member list from the old software. This is not ideal, obviously.

Thanks

---

<div class="post-metadata">

### Author: ![maiki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maiki/32/233950_2.png) [@maiki](https://meta.discourse.org/u/maiki)
#### Post date: [10 februari 2020 om 23:58 UTC](https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204/2 "2020-02-10T23:58:51Z")

</div>

You can tweak the trust levels to your community’s needs. Making it harder to bring noise with new accounts might just solve your problem.

---

<div class="post-metadata">

### Author: ![RubyRhod](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rubyrhod/32/40260_2.png) [@RubyRhod](https://meta.discourse.org/u/RubyRhod)
#### Post date: [11 februari 2020 om 13:44 UTC](https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204/3 "2020-02-11T13:44:37Z")

</div>

The ideal solution would be a batch of invites that don’t get emailed, creating the accounts and then immediately giving them the proverbial finger.

The admin in me wants to spin up a smarthost mailserver temporarily, reject all the mail, then turn it off.

> There’s got to be a better way

---

<div class="post-metadata">

### Author: ![RubyRhod](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rubyrhod/32/40260_2.png) [@RubyRhod](https://meta.discourse.org/u/RubyRhod)
#### Post date: [11 februari 2020 om 15:45 UTC](https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204/4 "2020-02-11T15:45:50Z")

</div>

OK… searching around, I found an empty list under Logs called ‘Screened Emails’ under logs. This seems to be the right place to drop in my list of baddies.

Feature request to allow manual insertion here?

---

<div class="post-metadata">

### Author: ![dachary](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dachary/32/119731_2.png) [@dachary](https://meta.discourse.org/u/dachary)
#### Post date: [11 september 2021 om 15:05 UTC](https://meta.discourse.org/t/pre-seeding-banned-suspended-member-list/141204/5 "2021-09-11T15:05:39Z")

</div>

> [@RubyRhod](#):
>
> Feature request to allow manual insertion here?

For cross reference purposes, the following post explains how to do it:

> [@Manually add an email to the screened email list](https://meta.discourse.org/t/manually-add-an-email-to-the-screened-email-list/142277):
>
> I’m wondering if there is a way to add an addresses to the screened email address list without that person having an account? We have a request to remove a persons account from multiple systems to stop him from receiving email. To prevent any further work for our team, we want to prevent him from signing up and making more requests. I’m able to prevent him from signing back up on my other systems, but it would be nice to prevent him from signing up on the community as well. The screened email …
