-
-
Notifications
You must be signed in to change notification settings - Fork 2k
[FR] Spamhaus Data Query Service support #2955
Copy link
Copy link
Closed as not planned
Labels
meta/closed due to age or inactivityThis issue / PR has been closed due to inactivityThis issue / PR has been closed due to inactivitymeta/needs triageThis issue / PR needs checks and verification from maintainersThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activityThis issue / PR has become stale and will be closed if there is no further activitypriority/low
Metadata
Metadata
Assignees
Labels
meta/closed due to age or inactivityThis issue / PR has been closed due to inactivityThis issue / PR has been closed due to inactivitymeta/needs triageThis issue / PR needs checks and verification from maintainersThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activityThis issue / PR has become stale and will be closed if there is no further activitypriority/low
Feature Request
It would be nice to be able to add support for Spamhaus Data Query Service to avoid queries being blocked when using a public DNS provider. Accounts are free for small usage and the feature would make configuration much easier. Another problem DQS resolves is that it works around the many ISP's that are now hijacking DNS queries and forcing you to use their servers.
Context
Right now to avoid Spamhaus from blocking queries you need to either stand up your own recursive DNS server or register for a key which becomes part of the spamhaus URL in the postfix main.cf file. For example references to:
zen.spamhaus.org=127.0.0.[2..11]
become:
.zen.dq.spamhaus.net=127.0.0.[2..255]
While it is possible to replace the usage in main.cf directly it is possible that the user will lose a future addition made by docker-mailserver since there are likely other *restrictions that are provided out of box. A safer/cleaner work around is presently to run a sed command from user-patches.sh.
This feature just makes it easier to do without doing hack-ish like changes which could break something down the road.
Is your Feature Request related to a Problem?
Not really. Sed seems to be a good workaround for now. Sed can change the URL's if DNSBL is enabled.
Describe the Solution you'd like
Adding my key as an optional environment variable would be really nice. If the key is present then fix up the URL's in main.cf as appropriate.
Are you going to implement it?
No, and I understand that it is highly likely no one will implement it. Furthermore, I understand that this issue will likely become stale and will be closed.
What are you going to contribute??
I could test and verify functionality.
Additional context
Alternatives you've considered
Who will that Feature be useful to?
What have you done already?