Four places where a tenant's storage usage isn't counted the way its limit expects:
CalDAV/CardDAV item COPY and MOVE into another account skip the quota check. Only copying a whole calendar or address book checks the destination's quota. A member can copy events or cards one at a time into a group account or a shared calendar, and its usage (and its tenant's) grows past the limit without ever being refused.
Tenant usage is charged to the writer's tenant, not the owner's. Calendar, contact, file and sieve writes, and deletes, move the tenant counter of whoever makes the change. When the writer is in another tenant, or is a server administrator with no tenant, the owner's tenant counter doesn't move with its account's, so its limit stops matching what it stores.
Destroying an account never takes its usage off its tenant. Every destroyed member leaves its bytes in the tenant's counter until a recount.
A tenant recount leaves out deleted members still kept (undelete). Their data stays until they're destroyed, but a recount drops it from the tenant's usage, so the tenant can fill that space again while the kept data is still there.
Part of the inbuxa/inbuxa-admin#257 remediation.
Four places where a tenant's storage usage isn't counted the way its limit expects:
1. **CalDAV/CardDAV item COPY and MOVE into another account skip the quota check.** Only copying a whole calendar or address book checks the destination's quota. A member can copy events or cards one at a time into a group account or a shared calendar, and its usage (and its tenant's) grows past the limit without ever being refused.
2. **Tenant usage is charged to the writer's tenant, not the owner's.** Calendar, contact, file and sieve writes, and deletes, move the tenant counter of whoever makes the change. When the writer is in another tenant, or is a server administrator with no tenant, the owner's tenant counter doesn't move with its account's, so its limit stops matching what it stores.
3. **Destroying an account never takes its usage off its tenant.** Every destroyed member leaves its bytes in the tenant's counter until a recount.
4. **A tenant recount leaves out deleted members still kept (undelete).** Their data stays until they're destroyed, but a recount drops it from the tenant's usage, so the tenant can fill that space again while the kept data is still there.
jcoffey-dev
added this to the 27.1 milestone 2026-11-20 16:25:14 +00:00
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.
Part of the inbuxa/inbuxa-admin#257 remediation.
Four places where a tenant's storage usage isn't counted the way its limit expects: