[GH-ISSUE #30] [BUG] Domainadmin can adjust domain quotas and restrictions set by superadmin #27

Closed
opened 2026-02-26 09:35:16 +03:00 by kerem · 3 comments
Owner

Originally created by @click on GitHub (Dec 25, 2012).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/30

When a superadmin creates/edits a domain, he/she can set up specific quotas and account-limits that should be applied further downstream onto that particular domain.

Example:
The superadmin creates a domain called example.net, with 10 mailboxes, 10 aliases, 10G domainquota and 1G userquota.
Now, adding a domainadmin user allows this domain to be managed by that user, as intended.

The issue is however that the new domainadmin can change all of these when he/she wants to, effectively avoiding the intended restriction-system set by the superadmin. I doubt this is how it is intended?
My thought would be that the domainadmin should handle accounts and their limits, and not the restrictions set for the domain itself?

Originally created by @click on GitHub (Dec 25, 2012). Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/30 When a superadmin creates/edits a domain, he/she can set up specific quotas and account-limits that should be applied further downstream onto that particular domain. Example: The superadmin creates a domain called example.net, with 10 mailboxes, 10 aliases, 10G domainquota and 1G userquota. Now, adding a domainadmin user allows this domain to be managed by that user, as intended. The issue is however that the new domainadmin can change all of these when he/she wants to, effectively avoiding the intended restriction-system set by the superadmin. I doubt this is how it is intended? My thought would be that the domainadmin should handle accounts and their limits, and not the restrictions set for the domain itself?
kerem closed this issue 2026-02-26 09:35:16 +03:00
Author
Owner

@barryo commented on GitHub (Feb 15, 2014):

Should be fine in version 3.

<!-- gh-comment-id:35151402 --> @barryo commented on GitHub (Feb 15, 2014): Should be fine in version 3.
Author
Owner

@florianbeer commented on GitHub (Nov 14, 2014):

I have just set up version 3.0.10 and the described issue is still present.
I created a domain with 10 Mailboxes and 20 Aliases, but the designated Domain Admin can still set this number higher if he wants to.

<!-- gh-comment-id:63066350 --> @florianbeer commented on GitHub (Nov 14, 2014): I have just set up version 3.0.10 and the described issue is still present. I created a domain with 10 Mailboxes and 20 Aliases, but the designated Domain Admin can still set this number higher if he wants to.
Author
Owner

@click commented on GitHub (Aug 2, 2016):

@barryo - this issue is still present in 3.0.15 / master - it's also re-mentioned in #181 (actually a full on duplicate of this report).

<!-- gh-comment-id:237083900 --> @click commented on GitHub (Aug 2, 2016): @barryo - this issue is still present in 3.0.15 / master - it's also re-mentioned in #181 (actually a full on duplicate of this report).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ViMbAdmin-opensolutions#27
No description provided.