Back to Changelog
Panel Backend
v1.0.444
Spam filter: per-mailbox score threshold now works, blacklist entries actually block, and an IP can be blocked
Bug Fixes
4- The per-mailbox spam score threshold was never saved. The panel posted it, the server had no field to receive it, and the request still answered "updated" — so the value silently returned to 5 every time. It is stored now, and it is applied: mail is filed by the threshold that mailbox asked for. A mailbox left on the server default is unaffected, and the generated rule for those servers is byte-identical to before.
- Blacklist and whitelist entries of type "domain" and "wildcard" never blocked anything. Postfix looks up a sender access map by exact keys, and the "@example.com" form the panel itself suggested is not one of them — an entry could sit in the list looking active while the mail kept arriving. New entries are now stored in the form Postfix matches. Entries added before this update are deliberately left untouched, so no rule that has been inert starts rejecting mail unannounced.
- A blacklist entry can now be an IP address or a range (203.0.113.10 or 203.0.113.0/24). A forged sender is worthless as a rule; the connecting IP is often the only durable fact in a message. IP rules use a separate Postfix map, wired in only once the first rule exists.
- New option, off by default: reject unauthenticated mail from outside that claims to come from a domain hosted on this server — the trick behind "this mail came from your own address" extortion. It stays off because a website, CRM or newsletter service hosted elsewhere may legitimately send as your domain, and that mail would be rejected too. Locally submitted mail, webmail and authenticated senders are never affected.