Skip to content
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

False positives: _protected/app/configs/banned/email.txt #1132

Open
ip6li opened this issue Aug 6, 2023 · 0 comments
Open

False positives: _protected/app/configs/banned/email.txt #1132

ip6li opened this issue Aug 6, 2023 · 0 comments

Comments

@ip6li
Copy link

ip6li commented Aug 6, 2023

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:

  1. New Account
  2. Use e.g. [email protected]
  3. See error

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.:

$ host spamwc.cf.dbl.spamhaus.org
Host spamwc.cf.dbl.spamhaus.org not found: 3(NXDOMAIN)

On a "bad" domain following happens:

$ host dbltest.com.dbl.spamhaus.org
dbltest.com.dbl.spamhaus.org has address 127.0.1.2

To check bad ip addresses, zen.spamhaus.org is a good choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant