You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ban file _protected/app/configs/banned/email.txt contains many false positives and not existing domains, so this file is unusable for banning domains. For identifying throwaway e-mail addresses it is also unusable, because some throwaway mail services changes their domains daily and operating such domains for 2 or 3 days only. Same is true for ip addresses, a local ban list is simply useless.
Describe the bug
Ban file _protected/app/configs/banned/email.txt contains many false positives and not existing domains, so this file is unusable for banning domains. For identifying throwaway e-mail addresses it is also unusable, because some throwaway mail services changes their domains daily and operating such domains for 2 or 3 days only. Same is true for ip addresses, a local ban list is simply useless.
To Reproduce
Steps to reproduce the behavior:
Domain spamwc.cf is not registered, at least not known to root nameservers.
Expected Behavior
Ban list should be sourced by e.g. Spamhaus DBL. This list is quite reliable and regularly updated. DBL implementation is based on DNS queries, e.g.:
On a "bad" domain following happens:
To check bad ip addresses, zen.spamhaus.org is a good choice.
The text was updated successfully, but these errors were encountered: