-
Notifications
You must be signed in to change notification settings - Fork 103
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
Feature request: domains blacklist #295
Comments
…domain check in subscribe handler
…domain check in subscribe handler
…domain check in subscribe handler
Fix #295 — Add domain blacklist feature
I arrive a bit late but did you know that Sympa can do this already? Remember: most of the time, any problem in Sympa can be solved by a scenario. Consequently, I think that PR #478 is irrelevant and should be removed. I think it is counter-productive to use a different mechanism than the one already existing. It adds only confusion. As it is obviously aimed at being used by listmaster, there is no immediate reason to make it available from the web interface. |
@dverdin, I don't agree to remove PR #478. That is, I think we'd be better to discuss on pros and cons of both solutions (scenario-based blacklist and this domain blacklist) so that we can find better way to improve Sympa. How about opening a new issue? (Thus, I refrain from objecting your arguments by now.) |
I thought it was the right place to do so as this issue is where the problem arose. |
OK, I posted a more elaborated issue here: #523. |
Some people migrating lists from <whatever, I don't know> to our Sympa registers people with some well-known abandoned addresses. In France, we got
voila.fr
that is still registered but without mail server (and it will not change, it's owned by a big ISP that shut down the mail server a few years ago).I suggest a domains blacklist setting that will prevents addresses using those domains to subscribe to list (a message saying "Sorry, that domain is blacklisted" to the subscribing action instigator could be cool)
The text was updated successfully, but these errors were encountered: