Hermes Mail Suite v0.1.9

Version 0.1.9
🔧 Fixed DNSBL false positives
If your DNS resolver is a public/shared one (or you're over Spamhaus's free query limit), Spamhaus answers real lookups with an error code in the 127.255.255.x range (e.g. 127.255.255.254 = "blocked resolver"). Hermes was mistaking those for a listing - so rbl=/uribl= could fire on everything, even clean domains like github.com, quietly inflating spam scores.
Now those error codes are correctly treated as "not listed," and umail logs a one-time warning so a blocked resolver is obvious instead of silently poisoning your scores.
💡 If you see that warning: point the server at a local recursive resolver (e.g. unbound) or use a free Spamhaus DQS key (
rbl-zone <key>.zen.dq.spamhaus.net/uribl-zone <key>.dbl.dq.spamhaus.net). The free public zones refuse queries via large shared resolvers.
✨ Added - see exactly what matched
The scan log line now shows which blocklist zones flagged the IP and which domains in the body were listed:
scan <...> ip=198.51.100.7 score=6.5 action=tag clamav=clean \
rbl=1 [zen.spamhaus.org] uribl=1 [bad.example] fcrdns=ok score=6.5Empty brackets [] when the count is 0. No more guessing whether a hit was genuine - it's right there in the log.
Replies (0)
No replies yet.
Log in to reply.