Replies: 1 comment
-
|
This is the list of DNSBLs that Stalwart is currently using: https://github.com/stalwartlabs/spam-filter/blob/main/rules/dnsbl.toml Before adding a new DNSBL to your lists make sure it is actively maintained. This is to avoid delays in message intake by sending requests to DNSBL servers that are not being updated. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Stalwart-mail uses IP blocklists to reduce spam. Great!
So do others, and thus the opposite task is to make sure one doesn’t accidentally end up on these lists.
It seems however, these lists are constantly in flux: old, well established ones (e.g. sorbs) go away, new ones show up.
Does anyone have a strategy to keep up with these?
I wrote a script that cron runs, and alerts me, if my server shows up on any of the lists, but that script is only as useful as my list of blocklist servers is up to date…
Best I could find so far is this list but it’s rather short, and a lot of the lists I found elsewhere, and it’s not clear if they just aren’t tracked there, or if they are defunct.
This is the list of blocklists I have compiled, commented out lines are known to be defunct hosts, left in there to prevent accidental re-adding:
Beta Was this translation helpful? Give feedback.
All reactions