← Directory

spamfilter-unbound

Recursive DNS resolver for the IMAP spam filter stack.

  • Network Services
  • Tools & Utilities
Recursive DNS resolver for the IMAP spam filter stack. Lets rspamd run DNSBL queries (Spamhaus, Abusix, SpamCop) without hitting the rate-limits that public/shared resolvers impose. Required for the RBL module to actually contribute signal.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
72last commit 121 days ago
Popular
209 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 13 days ago

GitHub stars
9
Open issues
0
Last commit
2026-06-14
Latest release
v1.0.0
License
MIT
Activity
stale

Checked 6 days ago - source: GitHub (marcelverdult/imap-spamfilter)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 14 days ago - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

Which Docker image does the imap-spamfilter stack use for unbound?

The architecture table lists mvance/unbound:latest for the spamfilter-unbound container.

What resolver issue is the local unbound container intended to address?

It keeps DNSBL lookups out of shared-resolver quotas.

Is unbound run as its own container in the stack?

Yes, the stack architecture lists spamfilter-unbound as a separate container alongside the Redis, rspamd, and main spamfilter containers.

Answers sourced from github.com

Community

Collected 9 days ago - public community threads