IceWarp offers easy-to-use configurable limits settings for on-premise and cloud administrators. You can set the limits on the Global (server), Domain or User level to configure the basic settings and behaviour for the selected level. This article will explain how limits on different levels are processed and what level will take precedence in case of conflict.
On-premise
You can set limits via Remote Console in the following nodes:
- User level limits: Domains & Accounts -> Management -> {domain} -> Users -> {user} -> Limits
- Domain level limits: Domains & Accounts -> Management -> {domain} -> Limits
- Global level limit: Mail -> General -> Delivery, Max message size
Limits are always processed in a certain order. The User level limits take precedence over Domain level limits, and the latter take precedence over Global level limits.
However, in order to apply User level or Domain level limits in case of conflict, you need to check Override global limits in Domains & Accounts -> Global Settings -> Domains
There are certain dependencies between limits. For example, if you uncheck Use domain limits in Global Settings, the limit specifying data per day and sending out messages will be disabled. Check Limits Explanation to find out more.
Max message size is the global limit defining the size of the message that will be accepted. The messages larger than the indicated value will be rejected. You can have different scenarios of limits taking precedence. To learn more, check our article about Max Message Size.
Cloud license
You can set limits via WebAdmin.
To set limits for the domain:
- Go to the main menu -> Users & Domains
- Select the domain
- Click Limits
There you can set the Disk Quota, Domain Expiration, Domain Admin Account Limit, etc.
To set limits for the account:
- Go to the main menu -> Users & Domains
- Select the domain, and in the list of users, click the account you want to configure
- Click Limits.
There you can set the Account Disc Quota, Daily Send Limits, Max Message Size, Account Expiration, etc.
Comments
0 comments
Article is closed for comments.