From 2cbecac415aaf70d7df3f087d54737c4d376d3d3 Mon Sep 17 00:00:00 2001 From: John Coffey Date: Fri, 18 Sep 2026 15:28:24 -0700 Subject: [PATCH] Multi-tenancy decision before implementation: generated DKIM keys count against maxDkimKeys (MT-17) --- docs/spec/features/multi-tenancy.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/spec/features/multi-tenancy.md b/docs/spec/features/multi-tenancy.md index c9b8cfb..d863e45 100644 --- a/docs/spec/features/multi-tenancy.md +++ b/docs/spec/features/multi-tenancy.md @@ -223,6 +223,10 @@ Each requirement has an ID, and tests name the IDs they check. emits `limit.tenant-quota`. Moving a domain into a tenant counts its principals and keys against the tenant's limits first, and is refused the same way if any limit would be crossed. + **Decision** (2026-09-18): creating a domain with automatic DKIM in a + tenant counts the keys the server will generate for it (MT-9) against + `maxDkimKeys`, and the domain is refused with `overQuota` if they wouldn't + fit. Nothing is ever generated past the limit. - **MT-18.** Existing objects over a lowered limit stay. Only new ones are refused. - **MT-19.** Disk quota. `maxDiskQuota` bounds the total storage of every