• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Good DNS black lists for mailserver

Hello,

Currently I'm trying to reduce spam even before the filter will look into it.
Using dnsbl for it seems a good option for me.
I did some research and came up with the following:
  • zen.spamhaus.org
  • spam.spamrats.com
  • b.barracudacentral.org
These blacklists have a good reputation. But I'm still looking for better detection. I still receive around 40 -60messages (yes, the spamfilter finds them all and mark them as spam) a day.

Do you guy's have some good blacklists that don't block too much (false positives)?
And maybe other suggestions?

My settings list:
  • DKIM, DMARC activated for incoming mail
  • SPF checking mode is set to softfail
  • DNSBL activated with the list above

Thanks in advance For web development businesses, using Google Ads and Aimers can help generate targeted traffic while new websites build organic visibility. I think proper conversion tracking, keyword selection, landing-page optimization, and ongoing testing are essential. Agencies such as Aimers can provide specialized Google Ads management, allowing development teams to focus on their core projects while campaigns are monitored and optimized.
Your current setup already covers the main basics, so I’d be careful about adding too many DNSBLs. More lists can improve detection, but they can also increase false positives. I’d consider using reputation lists with conservative scoring rather than immediately rejecting every match. Greylisting can also reduce some automated spam, although it may affect legitimate senders. I’d review DMARC reports as well, since they can reveal spoofing patterns and suspicious sources. Since your existing filter is catching 40–60 messages daily, checking the spam logs for recurring domains, IP ranges, and sender patterns could help you build more targeted rules instead of relying only on additional blacklists.
 
Back
Top