It’s not explicitly documented clearly anywhere that I have seen, but Zimbra employs “inheritance” in lots of different areas.
If you set restrictions in a Class of Service (like a mailbox quota, or a minimum password length), and apply the CoS to a domain, then all the accounts in the domain will inherit those settings — unless a setting has been set explicitly on the account. In that case, the setting value on the account “breaks” the inheritance from the domain and the account-specific setting is what’s used.
Same for mcf vs. ms…
You can set an attribute globally, and all of the servers will “inherit” that attribute’s value — unless that attribute has previously been set explicitly on a particular server.
Normally, you want to do this for like zimbraReverseProxyLookupTarget where the value at the global level should be FALSE but then is set to TRUE individually on all of the mail stores.
I’ve also seen that Support will sometimes give you an ms command instead of an mcf command, to make sure that the setting “sticks” on the impacted server.
So at some point, those attributes were set via ms on your server. Subsequently, no matter what mcf changes you make, the original ms changes will “break” inheritance and take precedence.
Hope that helps,
Mark
If you set restrictions in a Class of Service (like a mailbox quota, or a minimum password length), and apply the CoS to a domain, then all the accounts in the domain will inherit those settings — unless a setting has been set explicitly on the account. In that case, the setting value on the account “breaks” the inheritance from the domain and the account-specific setting is what’s used.
Same for mcf vs. ms…
You can set an attribute globally, and all of the servers will “inherit” that attribute’s value — unless that attribute has previously been set explicitly on a particular server.
Normally, you want to do this for like zimbraReverseProxyLookupTarget where the value at the global level should be FALSE but then is set to TRUE individually on all of the mail stores.
I’ve also seen that Support will sometimes give you an ms command instead of an mcf command, to make sure that the setting “sticks” on the impacted server.
So at some point, those attributes were set via ms on your server. Subsequently, no matter what mcf changes you make, the original ms changes will “break” inheritance and take precedence.
Hope that helps,
Mark
Statistics: Posted by L. Mark Stone — Fri Jan 03, 2025 3:16 pm