Understand your mail traffic
Follow mail volumes, filtering decisions and detection changes across your Rspamd installation. Move from a traffic trend to the evidence behind it.
Traffic and filtering outcomes
Review accepted, rejected and otherwise handled mail over time. Compare periods to see whether a change comes from traffic volume, a different sender population or filtering behaviour.
Changes that need attention
Use traffic monitoring and configured alerts to spot unusual changes. Investigate the affected period and traffic before deciding whether the cause is an incident, a campaign or an expected operational change.
Detection impact
Explore which Rspamd signals contribute to filtering decisions. Distinguish a frequently triggered signal from one that actually changes the outcome, so tuning focuses on consequential decisions.
Quality with supporting evidence
Review labelled samples and available replay results alongside traffic statistics. A rejection count alone does not establish accuracy; confirmed false positives and missed threats give a stronger basis for a policy change.
DMARC reports and bounce investigations
Review aggregate domain-authentication reports and bounce evidence to check whether your domain policy is working, investigate spoofing and identify delivery problems with your own mail. Follow up through Cases. Beta deployments require report intake and owned-domain configuration.
Example workflow
Investigating a rise in rejections
- Locate the change in the traffic timeline.
- Inspect the affected messages and contributing signals.
- Compare available labelled examples before proposing a tuning change.
Deployment considerations
Historical views depend on the analytics data you retain. Quality and replay views require their corresponding data and installed capabilities; production traffic is not automatically ground truth.