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

Spamhaus false positives with public DNS #2

Closed
analogic opened this issue Aug 26, 2022 · 1 comment · Fixed by #4
Closed

Spamhaus false positives with public DNS #2

analogic opened this issue Aug 26, 2022 · 1 comment · Fixed by #4

Comments

@analogic
Copy link

We've recently hit issue with
https://www.spamhaus.org/news/article/807/using-our-public-mirrors-check-your-return-codes-now

Log:
2022-08-26T11:34:46.185Z [DEBUG] [data.uribl] (envfrom) found 1 items for lookup
2022-08-26T11:34:46.185Z [DEBUG] [data.uribl] (envfrom) checking: domainexample.cz
2022-08-26T11:34:46.191Z [DEBUG] [data.uribl] domainexample.cz.dbl.spamhaus.org. => (127.255.255.254)
2022-08-26T11:34:46.191Z [INFO] [data.uribl] found domainexample.cz in zone dbl.spamhaus.org (127.255.255.254)
2022-08-26T11:34:46.191Z [INFO] [core] hook=mail plugin=data.uribl function=hook_mail params=scan@domainexample.cz retval=DENY msg="domainexample.cz listed in dbl.spamhaus.org; see http://www.spamhaus.org/query/dbl?domain=domainexample.cz"

We can fix it either by noticing it in documentation or/and matching 127.0... only (I expect 127.0.* in valid cases only...)

@analogic
Copy link
Author

@msimerson msimerson mentioned this issue Sep 4, 2022
msimerson added a commit that referenced this issue Nov 29, 2022
- fix #2 change Spamhaus defaults to not assume errors as positives
- warn instead of debug when result do not validate
- test: increase timeout for DNSBL test
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

Successfully merging a pull request may close this issue.

1 participant