[enhancement]: Provide control over DNS blocklists

[udf2457]

Which feature or improvement would you like to request?

Looking at config.sieve there seems to be no control given over which DNS blocklists to use. People may wish to disable certain blocklists.

In addition, please do not hardcode the Spamhaus addresses. Or, at least, allow override. Because people who pay for Spamhaus commercial dqs services need to use their own account specific address that contains a key provided by Spamhaus. See the Spamhaus docs (https://docs.spamhaus.com) and/or git repo (https://github.com/spamhaus/spamassassin-dqs)

Is your feature request related to a problem?

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[sirrkitt]

I was just about to request adding DQS support, but this pretty much spells it out. Spamhaus offers a free DQS version, too, which also outperforms their public blocklists.

[udf2457]

Thanks @sirrkitt !

Also of note, I think they need to generally read the Spamhaus docs more carefully, because there are other commercial lists such as HBL (https://docs.spamhaus.com/datasets/docs/source/10-data-type-documentation/datasets/030-datasets.html#Hash) that are not part of Zen (https://www.spamhaus.org/zen/).

Therefore it is highly likely that at present commercial customers of Spamhaus using Stalwart will not be getting the best out of the service they are paying for (beyond the address hardcoding bit, of course !).

[williamdes]

Or add a private DNS blocklist for example

For example I have a POC that uses https://red.flag.domains/

[mdecimus]

Sure, this feature will be added to the webadmin once it is ready.