On 3/8/22 7:49 pm, Claudio Kuenzler wrote:
After some experimentation I got this setup to work with spamrats on my mail gateway. spamcop, sorbs, abuseat, and spamhaus caused problems so were removed from the configI just ran into this problem as well -> https://twitter.com/ClaudioKuenzler/status/1554559303507492865 <https://twitter.com/ClaudioKuenzler/status/1554559303507492865> Starting yesterday (August 2nd 2022) afternoon, all incoming mails are being rejected due to a "blocked using...". This concerns all DNSBL managed by Spamhaus. The reason is that Spamhaus stopped serving their DNSBL via public DNS resolvers, such as Cloudflare's 1.1.1.1 or Google's 8.8.8.8 and 8.8.4.4 resolvers. See: https://www.spamhaus.com/resource-center/if-you-query-spamhaus-projects-dnsbls-via-cloudflares-dns-move-to-the-free-data-query-service/ <https://www.spamhaus.com/resource-center/if-you-query-spamhaus-projects-dnsbls-via-cloudflares-dns-move-to-the-free-data-query-service/>The solution, according to Spamhaus support, is to register for a free account and use their DQS (Data Query Service). I just did that this morning and although I was assured this would be a free of charge account, I now received a quote of USD 450 per year.I guess that was it then with Spamhaus.
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination reject_invalid_hostname reject_non_fqdn_hostname reject_non_fqdn_sender reject_non_fqdn_recipient reject_unknown_sender_domain reject_rbl_client noptr.spamrats.com reject_rbl_client spam.spamrats.com reject_rbl_client dyna.spamrats.com # reject_rbl_client bl.spamcop.net # reject_rbl_client dnsbl.sorbs.net # reject_rbl_client sbl.spamhaus.org # reject_rhsbl_helo dbl.spamhaus.org # reject_rhsbl_reverse_client dbl.spamhaus.org # reject_rhsbl_sender dbl.spamhaus.org # reject_rbl_client cbl.abuseat.org -- Jeremy
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature