Doesn't matter how small your server is, or isn't. Spamhaus blocks public queries, but does it a bit imperfectly, so it's the kind of thing where you can get away with it for a while, then something changes, and they find a new way to lock it down a bit better. Look at the response code.
Sign up for Spamhaus DQS and implement the proper DNS zone query with your DQS key embedded, as one does. That'll fix this. Full stop. That's the problem, that's the solution. Learn: https://www.spamresource.com/2021/11/howto-query-spamhaus-safely.html "Spamhaus is even blocking Gmail" is a dead giveaway: https://www.spamresource.com/2022/11/spamhaus-is-not-blocking-gmail.html Spamhaus closing loopholes for public/unfettered DNS querying: https://www.spamresource.com/2022/10/spamhaus-to-block-queries-from-aws.html https://www.spamresource.com/2024/02/spamhaus-blocking-queries-from-digital.html https://www.spamresource.com/2022/01/querying-spamhaus-via-cloudflare-dns.html Bad news: https://www.spamresource.com/2021/10/be-careful-using-spamhaus-with-open.html They've been warning us for three years now: https://www.spamresource.com/2021/02/spamhaus-warns-watch-for-new-error.html No, almost five years! https://www.spamresource.com/2019/10/spamhaus-blacklist-changes.html Cheers, Al Iverson -- Al Iverson / Deliverability blogging at https://www.spamresource.com Subscribe to the weekly newsletter at https://ml.spamresource.com DNS Tools: https://xnnd.com / (312) 725-0130 / Chicago (Central Time) _______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
