Spamhaus DQS key integration

I know this was discussed in a previous post, however, is this true?

"Alternative HestiaCP Method
If using a newer version of HestiaCP, you can use the built-in command to add the DQS key without manually editing templates, as the system automatically prevents key leakage:
v-add-sys-mail-dnsbl yourkey.zen.dq.spamhaus.net"

I am going to try it, but how to verify it? Does it simply update the required exim4 files?

Well. Tests reveal:

Queries lead to spamassassin config. Which yields same results…interesting.

Yes, it is.

That’s true if your installation is relatively new, you should check your current exim conf:

grep spamhaus /etc/exim4/exim4.conf.template

If above command doesn’t show any output, you must edit /etc/exim4/exim4.conf.template and replace this:

deny    message       = Rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text

with this:

deny    message       = Rejected because $sender_host_address is in a black list at ${if match{$dnslist_domain}{^[^.]+[.](.+dq[.]spamhaus.*)}{$1}{$dnslist_domain}}\n$dnslist_text

If you add the dns block list with your key, remember to remove zen.spamhaus.org:

v-delete-sys-mail-dnsbl zen.spamhaus.org
v-add-sys-mail-dnsbl yourkey.zen.dq.spamhaus.net

ok that checks out, however, it still receives the dbl-dqs-ehlo and so forth so it seems incomplete. Spamhaus has always scared me so I am inclined just to remove it altogether as it is obvious they do not care enough to provide a decent solution unless any can comment otherwise?

To block those tests you must also add rules to spamassassin.

Oh, I see, for anyone doing this interested I had to check the reject spam in the edit mail domain THEN do v-add-mail-domain-antivirus user domain from the command line to have this work.