Mail rules: group and tenant ids in their JMAP form

jcoffey-dev commented

2026-09-29 02:30:34 +00:00

Owner

Stacked on #111. senderGroup, senderTenant and recipientGroup conditions read and write JMAP ids (like legal hold scopes), so the console can use its object pickers; plain numbers still read. Tests: unit (both forms, bad id) and a JMAP round trip.

jcoffey-dev added 2 commits 2026-09-29 02:30:34 +00:00

DLP: how long held mail waits is a setting

ci / fork-checks (pull_request) Successful in 51s

Details

ci / build (pull_request) Successful in 4m32s

Details

de514115dd

inbuxa:DlpSettings (singleton, urn:inbuxa:jmap): keepHeldDays, 1 to 90,
7 by default (settled answer 5 made it a setting). sysDlpPolicyGet reads
it, sysDlpPolicyUpdate changes it, server-level, audited by the request
layer. Each held message keeps the days it was given, and the sender's
notices say that number. Privacy catalog entry; spec §2.6 updated.

mail_rules_tests: 7 by default, 0 refused, 3 set and a message held
afterwards expires 3 days after it was held, the expiry notice says 3.

Mail rules: group and tenant ids in their JMAP form

ci / fork-checks (pull_request) Successful in 2m26s

Details

ci / build (pull_request) Successful in 5m47s

Details

823d42d528

senderGroup, senderTenant and recipientGroup conditions now read and write group and tenant ids as JMAP ids ("b", "c"…), like legal hold scopes and the rest of the API, so the console can use its object pickers; plain numbers are still read. Held as numbers for matching. Unit test for both forms and a bad id; mail_rules_tests round-trips a tenant condition over JMAP.

jcoffey-dev merged commit 94a3a762b0 into main

2026-09-29 02:36:50 +00:00

jcoffey-dev deleted branch feature/rule-ids-as-jmap-ids

2026-09-29 02:36:50 +00:00

jcoffey-dev referenced this pull request

2026-09-29 05:39:08 +00:00

Release 2026.9.29 #121

Mail rules: group and tenant ids in their JMAP form #112