Update SQLBlackWhiteList.pm #1
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
*.spammer.com it's great, but with this little modification it also allows to set a less broader rule like this one foo@*.spammer.com Why it's useful? For example info@random1.domain.com is OK info@random2.domain.com is OK info@random3.domain.com is OK ads@random1.domain.com is bad ads@random2.domain.com is bad Can be BL as: ads@*.domain.com
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Be able to blacklist like *.domain.ext is great, but with this little change it also allows to set less broader rules like this one foo@*.spammer.com
Why it's useful? Example:
info@random1.domain.com is OK
info@random2.domain.com is OK
info@random3.domain.com is OK
ads@random1.domain.com is bad
ads@random2.domain.com is bad
Can be solve blacklisting only ads@*.domain.com instead of *.domain.com that would be too much.