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
Ability to greylist new servers #29266
Comments
Also not bad idea is to implement federated blacklist to cooperate in spam filtering. |
Greylisting is useless nowadays and popular mail services don't use it. Greylisting was invented many years ago to discard messages sent directly from scripts without MTA but that kind of spam is rare today. Also for greylisting to work activitypub needs implementation of responses like "temporary error, please retry later" for s2s interactions, that's unlikely to happen. |
*Happy Roscomnadzor noises* |
Why is this not an option? It's kind of like we're told, oh well, deal with it. |
This will negatively impact single user instances and other small instances. |
I agree with @colinstu12, not only would this put a large burden on moderation teams but that burden slows down potential growth or exposure of small instances. The best method to prevent this ongoing spam issue is to coordinate with other mastoadmins and have the ability to systematically block incoming spam waves.
|
I think spam problem can be facilitated with UI improvement. I'd divide incoming events into categories like |
Pitch
Mastodon administrators should be able to use greylist policy for the servers they see for the first time.
https://en.wikipedia.org/wiki/Greylisting_(email)
Motivation
As the spam attack is getting increasingly worse, we need to learn the lessons of the past federated systems like E-mail. E-mail servers use greylists to discriminate trustable servers from junk servers like spammers.
The text was updated successfully, but these errors were encountered: