Spam Filters
Panelica filters spam in two layers. Content scanning (SpamAssassin scoring every message) is server-wide and lives in Email Settings → Protection. This page manages the other layer: sender lists that accept or reject mail by who sent it, before content scanning even runs, plus a per-account overview of your mailboxes.
Email → Spam Filtershttps://YOUR-SERVER-IP:8443/email/spam| Pattern | Type | Reason | Scope | Action |
|---|---|---|---|---|
[email protected] | phishing attempts | Global | delete | |
@spam-network.ru | domain | bulk spam source | Global | delete |
Blacklist and whitelist
Add an entry as a full email address ([email protected]) or a domain (@spam-network.ru), with an optional reason for your future self. Blacklisted senders are rejected at the SMTP door with your reason in the rejection message; whitelisted senders are explicitly accepted. Deleting an entry asks for confirmation.
OK, blacklist entries as REJECT <reason>), hashed with postmap and regenerated automatically after every change. Rejection happens during the SMTP conversation, so blacklisted mail never consumes disk, never reaches a mailbox and never generates a bounce from your side; the sender's server gets the rejection directly.*@*.ru are accepted by the form but do not match in Postfix's hash table, so prefer explicit domain entries. Second, only global entries (created by ROOT/ADMIN) are compiled into the mail server; entries scoped to a regular user are stored but not enforced at delivery. Treat sender lists as a server-wide administration tool.Account overview
The Account Settings tab lists every mailbox with its quota and scanning flags, and the guide cards at the bottom explain score thresholds. Note that the effective SpamAssassin threshold is the server-wide one from Email Settings; per-mailbox threshold tuning is not applied to the delivery path in this version.
Access
Requires the email and spam_filter license features and local mail, and defaults to a ROOT/ADMIN page. Where the model matters: ROOT and ADMIN manage global entries (the ones actually compiled into Postfix); if a reseller or user is granted access, they see global entries but can create and delete only their own, and cannot remove a global rule. List changes regenerate the Postfix map automatically in the background. See roles and permissions.