The console half of the DLP and mail flow rules spec (§3):
Compliance › Data loss prevention and Settings › Mail flow › Rules: rules of one kind in order, each in words; on/off, change, delete (click twice), per-kind permissions.
Rule editor: conditions and exceptions (sender, recipients, outside, words, patterns, headers, attachments, can't be inspected, size; detectors by region with least counts, or by template), actions (warn/hold/block + notice for DLP; disclaimer, subject prefix, headers, copy, redirect, route, refuse for mail flow), live preview in words, optional audit reason.
Compliance › Held mail: held messages with rules and counts; Read (audited), Release, Reject with a note; reasons required.
Detector and template lists generated from the server tables, with a test.
Checked on a local preview built from inbuxa-server main + #108 + #109: rules created through the editor (preview sentence matched), a held message listed with counts, Read showed the text. Typecheck, lint, 518 unit tests. Ships with the server release that has #108 and #109.
The console half of the DLP and mail flow rules spec (§3):
- **Compliance › Data loss prevention** and **Settings › Mail flow › Rules**: rules of one kind in order, each in words; on/off, change, delete (click twice), per-kind permissions.
- **Rule editor**: conditions and exceptions (sender, recipients, outside, words, patterns, headers, attachments, can't be inspected, size; detectors by region with least counts, or by template), actions (warn/hold/block + notice for DLP; disclaimer, subject prefix, headers, copy, redirect, route, refuse for mail flow), live preview in words, optional audit reason.
- **Compliance › Held mail**: held messages with rules and counts; Read (audited), Release, Reject with a note; reasons required.
- Detector and template lists generated from the server tables, with a test.
Checked on a local preview built from inbuxa-server main + #108 + #109: rules created through the editor (preview sentence matched), a held message listed with counts, Read showed the text. Typecheck, lint, 518 unit tests. Ships with the server release that has #108 and #109.
The console half of the DLP and mail flow rules spec (§3), over
inbuxa:MailRule and inbuxa:HeldMessage:
- Management > Compliance > Data loss prevention and Settings > Mail
flow > Rules: one page per kind, rules in the order they run, each
described in words, switch on or off, change, delete (a second click
to confirm), with each kind's own permissions.
- The rule editor: name, order, on/off, which mail (mail flow rules),
conditions and exceptions (sender, recipients, outside recipients,
words, patterns, headers, attachments by type, extension, name, size
and count, can't be inspected, message size; detectors for DLP, picked
by region with a least count, or added by template), actions (warn,
hold or block with a notice for DLP; disclaimers, subject prefix,
headers, copies, redirects, routes and refusals for mail flow), and
the rule in words as it's built. An optional reason for the audit log.
- Management > Compliance > Held mail: each held message with sender,
recipients, size, when it goes back, the rules and each detector's
count; Read (recorded in the audit log), Release and Reject (with a
note for the sender), each with a required reason.
- The detector and template lists are generated from the server's
tables; a test checks the count and that templates name real ones.
Visibility: sysDlpPolicyGet, sysDlpReviewGet, sysMailRuleGet. Needs
inbuxa-server #108 and #109; ships with that server release.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The console half of the DLP and mail flow rules spec (§3):
Checked on a local preview built from inbuxa-server main + #108 + #109: rules created through the editor (preview sentence matched), a held message listed with counts, Read showed the text. Typecheck, lint, 518 unit tests. Ships with the server release that has #108 and #109.