Skip to content

v1.7.3 — Spamhaus Submit hotfix

Choose a tag to compare

View all tags
@jmrGrav jmrGrav released this 21 Jun 05:17
· 68 commits to main since this release
v1.7.3
This tag was signed with the committer’s verified signature.
jmrGrav
GPG key ID: E34BC7955D46431A
Verified
Learn about vigilant mode.
46106d4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

Hotfix: Spamhaus Submit was never wired into the reporting pipeline — the spamhaus.Client interface existed but had no concrete implementation. This release adds SubmitClient (POST /portal/api/v1/submissions/add/ip, Bearer token) and wires it into reporting.Service independently of AbuseIPDB: own 24h per-IP dedup, fail-open on error, independent metrics. AbuseIPDB behaviour is unchanged.

Fixes

  • FIX-SPAMHAUS-SUBMIT — internal/security/enrichment/spamhaus.SubmitClient implements Client.Report() via POST https://submit.spamhaus.org/portal/api/v1/submissions/add/ip with Bearer token auth. HTTP 401/403 → auth error, 429 → rate-limit, 5xx → retryable. All errors fail-open (logged WARN, do not affect AbuseIPDB result).
  • FIX-SPAMHAUS-DEDUP — spamhausIPDedup tracks submitted IPs with a 24h TTL, independent from AbuseIPDB's dedup window.
  • FIX-SPAMHAUS-WIRE — startup wiring reads spamhaus.api_key from credential store and gates on provider-enabled state.

Metrics Added

  • spamhaus_submit_total
  • spamhaus_submit_failures_total
  • spamhaus_submit_dedup_total

Full changelog: see CHANGELOG.md

Assets 4
Loading