Manage filtering policy
Create targeted rules, maintain filtering maps and tune scoring from Console. Connect a policy change to the investigation that justified it.
Rule maps and custom rules
Maintain filtering maps and author SpamAssassin-style rules through the operator interface. Combine existing detection signals with composite rules when a policy needs several conditions to be considered together.
Targeted conditions and exceptions
Use Selector Grid to build conditions around message properties and focus policy on the traffic you intend to affect. Narrow exceptions help address a particular delivery problem without broadly weakening filtering.
Scoring and policy tuning
Review symbol scores and adjust scoring controls from a shared interface. Use the message's complete filtering evidence to understand whether a proposed adjustment would change the final outcome.
Preview scores and verify corrections
Use What-If to compare symbol weights and action thresholds against retained traffic. After applying a correction, rescan selected Case samples with the current scanner configuration. Case verification records the result; it does not simulate an unapplied rule.
Example workflow
From false positive to a reviewed correction
- Identify the signal and traffic scope responsible for the delivery problem.
- Prepare a targeted rule, exception or scoring adjustment.
- For scoring changes, compare the proposed weights or thresholds against retained traffic.
- Apply the reviewed correction, rescan selected samples and keep the results with the case.
Deployment considerations
Available editors and previews depend on the installed integration and retained data. Console complements Rspamd configuration expertise; it does not make every configuration setting editable or every change reversible.