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 10 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)
  • Any server (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.

55/100 Fair

Maintained
69last commit 160 days ago
Popular
2110 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
89no serious findings, 1 minor, CI, tests

Based on 4 of 5 factors.

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

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

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

Resources & Compatibility

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

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

First-install notes

  • Install the basic Python package Run `pip install spamfilter` in a terminal so your Python setup can import it. If you skip this, code that says `import spamfilter` will not work. source
  • Add extras only if you need them If you plan to use OpenAI, API calls, or Transformers, install the matching extra, such as `pip install spamfilter[openai]`. Plain `pip install spamfilter` does not include those add-ons, so features that rely on them may fail. source
  • Check the version after installing Open a Python prompt and run `import spamfilter`, then check `spamfilter.__version__`. This confirms the install finished before you build filters on top of it. source
  • Deploy via Unraid or Docker Run as a container on the shared spamnet Docker network alongside rspamd and redis. Deploy via the included Unraid Community Apps template, or on any Linux host with Docker as part of the imap-spamfilter stack. source

Fetched 37 days ago - each note links to its source

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 48 days ago - public community threads