Banned emails list #587

Closed
opened 5 years ago by elegaanz · 5 comments
elegaanz commented 5 years ago (Migrated from github.com)

Is your feature request related to a problem? Please describe.

Someone can quite easily create hundreds of fake email addresses and register as much accounts on Plume, to spam people. Someone who gets banned can also recreate an account with the same email.

Describe the solution you'd like

Being able to have a list of forbidden emails patterns would be useful. It should accept regex, wildcard patterns or something like that, so that if someone tries to generate emails on the fly following a pattern it can easily be stopped.

Describe alternatives you've considered

Additional context

Discussion on Loomio

**Is your feature request related to a problem? Please describe.** Someone can quite easily create hundreds of fake email addresses and register as much accounts on Plume, to spam people. Someone who gets banned can also recreate an account with the same email. **Describe the solution you'd like** Being able to have a list of forbidden emails patterns would be useful. It should accept regex, wildcard patterns or something like that, so that if someone tries to generate emails on the fly following a pattern it can easily be stopped. **~~Describe alternatives you've considered~~** **Additional context** [Discussion on Loomio](https://framavox.org/d/LUb3JMeX/moderation-tools)
elegaanz commented 5 years ago (Migrated from github.com)

Also, I'm thinking about it: we don't currently check if the email that we ask for during registration is valid, we probably should (but this would need its own issue).

Also, I'm thinking about it: we don't currently check if the email that we ask for during registration is valid, we probably should (but this would need its own issue).
epsilon-phase commented 4 years ago (Migrated from github.com)

Would it suffice, for now, to provide some formatting checking?

It seems like an expedient thing to add while fiddling with the blocklist

Would it suffice, for now, to provide some formatting checking? It seems like an expedient thing to add while fiddling with the blocklist
igalic commented 4 years ago (Migrated from github.com)

the easiest way to check for validity of an email address is to send a confirmation link to it

do we currently do that?

the easiest way to check for validity of an email address is to send a confirmation link to it do we currently do that?
Owner

The email is currently used only for password reset. It's (laxly) checked to be valid on signup, but no mail is sent to it

The email is currently used _only_ for password reset. It's (laxly) checked to be valid on signup, but no mail is sent to it
igalic commented 4 years ago (Migrated from github.com)

we should probably change that. some time in the future

we should probably change that. some time in the future
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#587
Loading…
There is no content yet.