2 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	e0060c9e6e	DLP at DATA: block, warn and override over SMTP and JMAP ... Phase 2f of the DLP and mail flow rules spec: the rules now run on mail an authenticated sender submits, after the DATA system script and before headers and DKIM signing (§2.1). - smtp/inbound/mailflow.rs: builds what the rules look at from the message (subject, the text version of each body, one level of attached messages, attachment text via the extractor, 10 MB of text at most) and the envelope (sender's groups and tenant; each recipient local or not, and its groups). Skipped entirely when no enabled rule applies to outgoing mail. Rules that can't be loaded refuse with a 451: nothing unchecked leaves. - Block: 550 5.7.1 with the rule's notice. Warn: 550 5.7.1 with the notice and how to override: "[override: reason]" at the start of the subject, taken out before the message goes on (settled answer 1). Until phase 3, a hold rule blocks rather than let mail through. - JMAP: EmailSubmission takes inbuxa:dlpOverride {reason}; a refusal comes back as inbuxa:dlpWarning or inbuxa:dlpBlocked with each rule's name and notice (description too, for older clients). - Audit: one record per DLP match, the sender as actor, action create, target a message: the recipient domains, each rule with its detectors' counts, the outcome, an override's reason. Never the matched text. No new audit action: an older node that meets one fails its daily clean-up, which would make rolling back unsafe (spec §2.7 updated). Tests: mail_rules_tests gains the DLP flow over JMAP (no rules, warning with rule and notice, local recipient not warned, override with a reason, block that no reason passes, the subject tag stripped from the delivered message, audit records with no card or key text). smtp inbound tests pass; system_tests passed twice after one timeout in the email delivery tests that didn't recur.	2026-09-28 17:52:37 -07:00
jcoffey-dev	c8280de9c3	DLP and mail flow rules: the rule model, the engine and the node cache ... Phase 2e of the DLP and mail flow rules spec, in the features crate. - rules.rs: a rule (§2.2) with its conditions (§2.3) and actions (§2.4), as JSON under R/r in the fork's subspace. validate() enforces the spec's shape: DLP rules check outgoing mail and have exactly one of block, warn or hold; transport rules have neither those nor detectors; lists, header names, header values (one line), addresses, texts, word lists, patterns and detector ids are checked. - engine.rs: rules compiled once (word lists to automata, patterns to size-limited regexes) and run in priority order with exceptions and stop processing. Each detector runs at most once per message and only when a rule asks for it. The outcome lists what matched with each detector's count, and decides DLP strictest first: block, hold, warn; an override answers warnings only (§2.5). - cache.rs: each node's compiled copy, refreshed after 30 seconds or at once when this node changes a rule. Nothing calls this yet: the JMAP object and the check at DATA follow. 55 unit tests in mailflow.	2026-09-28 17:29:35 -07:00