jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
The journaling spec, for approval; nothing built. A copy of each queued message taken at the queue (after DLP and transport rules, so every path and the final envelope are covered), wrapped in a journal report with the envelope (Bcc, list members from ORCPT, rule-added recipients), kept in a built-in journal with a per-node hash chain and retention, and/or sent to an outside archive. Scope by accounts, groups, domains, tenants and direction, plus a Journal it rule action. Seven questions for John at the end, each with a recommendation.
The journaling spec, for approval; nothing built. A copy of each queued message taken at the queue (after DLP and transport rules, so every path and the final envelope are covered), wrapped in a journal report with the envelope (Bcc, list members from ORCPT, rule-added recipients), kept in a built-in journal with a per-node hash chain and retention, and/or sent to an outside archive. Scope by accounts, groups, domains, tenants and direction, plus a Journal it rule action. Seven questions for John at the end, each with a recommendation.
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 journaling spec, for approval; nothing built. A copy of each queued message taken at the queue (after DLP and transport rules, so every path and the final envelope are covered), wrapped in a journal report with the envelope (Bcc, list members from ORCPT, rule-added recipients), kept in a built-in journal with a per-node hash chain and retention, and/or sent to an outside archive. Scope by accounts, groups, domains, tenants and direction, plus a Journal it rule action. Seven questions for John at the end, each with a recommendation.