Axigen Inheritance Schematic

This article describes how settings are inherited between different storage objects held by the mail server.

Solution

"Level 0" or "Server Level" is the most general of them all. Settings applied at this level propagate throughout the whole system. It is very useful to make changes here that need to apply on all domains. Some service settings are unavailable at this level, such as RPOP configuration.

"Level 1" or "Domain Level" is the middle ground. The settings configured here override the settings applied on the server level. However, any changes here, affect only the contents of the particular domain being set up (such as existing and future accounts).

"Level 2" or "Account Level" is the most localized of all three levels. The account level settings override any other settings. There are some settings that cannot be edited at this level, such as the message appender or socket filter configuration.

The general schematic of the inheritance starts from the lowest level (0) to the highest (2).

Settings are overridden in exactly the opposite way, from the highest level (2) to the lowest (0).

 

Below is an example schematic of some of the settings used by Axigen and the way common settings can be configured at different levels:

Settings, in Axigen, are spread within three levels of depth:

The "Level 0" or "Server Level" is the most general of them all. Settings applied at this level propagate throughout the whole system. It is very useful to make changes here that need to apply on all domains. Some service settings are unavailable at this level, such as RPOP configuration.

"Level 1" or "Domain Level" is the middle ground. The settings configured here override the settings applied on the server level. However, any changes here, affect only the contents of the particular domain being set up (such as existing and future accounts).

"Level 2" or "Account Level" is the most localized of all three levels. The account level settings override any other settings. There are some settings that cannot be edited at this level, such as the message appender or socket filter configuration.

NOTE: The general schematic of the inheritance starts from the lowest level (0) to the highest (2).

NOTE: Settings are overridden in exactly the opposite way, from the highest level to the lowest.


Below is an example schematic, covering some of the settings and configuration options:


<pre>

-> Server Level
|                |---> Socket Filters
|                |---> Message Filters
|                |---> Additional Anti-Spam Methods
|                |---> Service Configuration
|
|---> Domain Level
|                       |---> Socket Filters
|                       |---> Message Filters
|                       |---> Domain Message Appenders
|                       |---> Webmail Configuration
|                       |---> RPOP Configuration
|                       |---> Quotas and Restrictions
|
|-----> Account Level
                           |---> Message Filters
                           |---> RPOP Configuration
                           |---> Webmail Configuration
                           |---> Quotas and Restrictions

 

OS: LinuxWindowsFreeBSDNetBSDOpenBSDSolaris
Distros: WindowsDEB based distros amd64