-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
spamhaus put our domains onto DBL #490
Comments
https://check.spamhaus.org/ticketing/?a=ST1507615&b=3c0274d263845a97b34e9d6b2b69bd4a ticket for nerdpol.ovh, same issue. |
ThomasWaldmann
changed the title
spamhaus put nsupdate.info onto DBL
spamhaus put our domains onto DBL
Feb 21, 2022
Quoting spamhaus: "The public suffix list does not count, being entirely self-serving." So, they are aware of it and they do not use it and rather prefer to harm unrelated parties. |
More from spamhaus:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
spamhaus.org put nsupdate.info onto its domainname black list.
i contacted them after being notified of that, but my issue was just closed without considering my arguments and without removing nsupdate.info from the DBL (as another query on their site showed).
https://check.spamhaus.org/ticketing/?a=ST1503684&b=d632a81406a1d5d1dc1a12cd3be173b0
i filed another ticket there, pointing out that not considering the public suffix list is a bug on their side (and unacceptable behaviour in case they are aware of it and not fixing it):
https://check.spamhaus.org/ticketing/?a=ST1507591&b=9b9540a58077bab645d839a69d6c91d5
i also requested that they confirm they will in future consider the public suffix list before blacklisting domains.
The text was updated successfully, but these errors were encountered: