infrastructure/mox
1
0
Fork 0
mirror of https://github.com/mjl-/mox.git synced 2025-07-10 08:34:40 +03:00
Code Issues Packages Projects Releases Wiki Activity

quota: fix handling negative max size when configured for an account, and clarify value is in bytes in config file

Browse Source 
for #115 by pmarini-nc
This commit is contained in:
Mechiel Lukkien
2024-01-12 15:02:16 +01:00
parent 7b6cfcd572
commit aea8740e65
5 changed files with 17 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
webadmin/admin.ts
View File

@ -727,7 +727,7 @@ const account = async (name: string) => {
),
dom.label(
style({display: 'block', marginBottom: '.5ex'}),
dom.span('Disk usage quota: Maximum total message size ', attr.title('Default maximum total message size for the account, overriding any globally configured maximum size if non-zero. A negative value can be used to have no limit in case there is a limit by default. Attempting to add new messages beyond the maximum size will result in an error. Useful to prevent a single account from filling storage.')),
dom.span('Disk usage quota: Maximum total message size ', attr.title('Default maximum total message size in bytes for the account, overriding any globally configured default maximum size if non-zero. A negative value can be used to have no limit in case there is a limit by default. Attempting to add new messages to an account beyond its maximum total size will result in an error. Useful to prevent a single account from filling storage.')),
dom.br(),
quotaMessageSize=dom.input(attr.value(formatQuotaSize(config.QuotaMessageSize))),
),