Parameters for email classification
Available parameters
Available parameters
Those rule parameters can be adjusted per verdict and confidence. For example, the following configuration activates quarantining for high-confidence phishing, but delivers medium-confidence phishing with a subject rewrite:
local.properties
Parameters for reported emails
Available parameters
Available parameters
The following example shows how to auto-handle high-confidence phishing, but keep medium-confidence phishing cases open:
local.properties
REPORTED_BENIGN_early_decision_action=DROP). This should ensure that no malicious email is accidentally auto-handled as benign. Therefore, reported emails may be marked as benign, but not auto-handled.
The most important requirements for auto-handling benign emails are:
- All links must have a local reputation above 0.
- Email must be internal or the sender must have at least medium trust.
- No suspicious files attached (e.g., no HTML files).
- No high spam or risk score.
- No cloud storage links.
Disable acknowledgment emails
Normally, acknowledgment emails are disabled via the Actions configuration screen. In special cases, you can configure the following inactiveguard/core/rule_sets/90_local/params/local.properties:
ACKNOWLEDGE_RECEIPT is the default):
Multi-Tenancy
Thelocal.properties file used throughout this page lives in 90_local and therefore applies to all tenants.
To set a parameter for a single tenant only, use a tenant.properties file in that tenant’s rule set instead of local.properties. See Manage Tenant Rules for the setup.
To switch a tenant to a completely different set of parameters, reference a different rule profile for that tenant.