used sophos dns protection as dns server in sophos firewall with mail security with rbl servers.
all mails are rejected because dns protection cannot handle rbl request.
well done sophos ... sorry ... that is ***.
Thats an odd statement. Do you mean, the DKIM break?
Rejected by what?
__________________________________________________________________________________________________________________
An RBL (remote block list or realtime blackhole list), also called a DNS-based blacklist or block list, is a spam-fighting tool.
Ok: What RBL did you add to the product and failed with SFOS?
__________________________________________________________________________________________________________________
Can you send me your Account ID via PN?
__________________________________________________________________________________________________________________
We are looking into this.
From an external view:
Your DNSBL blocks the whole Internet!
There can be several reasons why a DNSBL can appear to list all IPv4 addresses (when it really doesn’t):
MOST COMMON: Using Amazon, Quad9, Google, Cloudflare or some other public/open DNS resolver – OR your network is querying our data using an IP that has generic, unattributable rDNS. READ THIS FIRST.
Additionally, as you use zen, it would be a "workaround"/"solution" to create a DNS request route to directly resolve Spamhaus and not query it via our service.
https://www.spamhaus.org/blocklists/zen-blocklist/
We had the same discussion a while ago via Sophos UTM: zen.spamhaus.org not working for me? RESULT: MAKE SURE NOT TO USE GOOGLE DNS!
__________________________________________________________________________________________________________________
Yes, situation is not clearly a problem of Sophos DNS Protection.
As you see it can be a risky thing just replace public dns resolver.
So - We have some kind of feeling, something went wrong here:
Could you PN me your Support - Access ID of the Firewall?
Because we have the feeling, the site (firewall WAN IP) was not maintained in Sophos Central DNS Protection.
__________________________________________________________________________________________________________________