Some stored data isn't counted toward an account's or its tenant's disk quota, or is checked against less than is stored:
Undelete archive. With archiveDeletedItemsFor set, deleting a message takes it off the account's usage, but its kept copy is stored for the whole retention period without being counted. Filling the account, deleting and filling it again stores the limit's worth once more every cycle, past the account's and the tenant's quota.
Held spam-training samples. A trained message's blob is held for holdSamplesFor (90 days by default) after the message is gone, uncounted. The same fill, delete, fill cycle works through it.
Encrypted mail. The quota is checked against the message before encryption, but the stored message is the encrypted one, plus the headers added on delivery.
iTIP. An invitation is checked against its own size, but both an event and a notification of that size are stored. An update is checked against the event's growth only, not the notification stored with it.
VacationResponse/set has no quota check at all, unlike a Sieve script set.
Expected: what's stored is what's counted and checked. Deleting must still never fail.
Part of the inbuxa/inbuxa-admin#257 remediation (Refs inbuxa/inbuxa-admin#257).
Some stored data isn't counted toward an account's or its tenant's disk quota, or is checked against less than is stored:
- **Undelete archive.** With `archiveDeletedItemsFor` set, deleting a message takes it off the account's usage, but its kept copy is stored for the whole retention period without being counted. Filling the account, deleting and filling it again stores the limit's worth once more every cycle, past the account's and the tenant's quota.
- **Held spam-training samples.** A trained message's blob is held for `holdSamplesFor` (90 days by default) after the message is gone, uncounted. The same fill, delete, fill cycle works through it.
- **Encrypted mail.** The quota is checked against the message before encryption, but the stored message is the encrypted one, plus the headers added on delivery.
- **iTIP.** An invitation is checked against its own size, but both an event and a notification of that size are stored. An update is checked against the event's growth only, not the notification stored with it.
- **VacationResponse/set** has no quota check at all, unlike a Sieve script set.
Expected: what's stored is what's counted and checked. Deleting must still never fail.
jcoffey-dev
added this to the 27.1 milestone 2026-11-20 16:30:18 +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 (Refs inbuxa/inbuxa-admin#257).
Some stored data isn't counted toward an account's or its tenant's disk quota, or is checked against less than is stored:
archiveDeletedItemsForset, deleting a message takes it off the account's usage, but its kept copy is stored for the whole retention period without being counted. Filling the account, deleting and filling it again stores the limit's worth once more every cycle, past the account's and the tenant's quota.holdSamplesFor(90 days by default) after the message is gone, uncounted. The same fill, delete, fill cycle works through it.Expected: what's stored is what's counted and checked. Deleting must still never fail.
Fixed in #502 (
26eaf186). Part of the inbuxa/inbuxa-admin#257 remediation.