Differences
This shows you the differences between two versions of the page.
|
current:policygroups [2015/01/13 10:49] 194.149.0.131 created |
current:policygroups [2015/01/19 12:44] (current) sj |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| However, by creating different policies, you can override the default settings even as a per user basis. Let's say you want to mark and deliver spam messages to all your users, but a few users want to keep their spam to the spam quarantine. All you have to do is set clapf.conf for marking spam, then create a new policy group and set the variable named spam_oblivion_limit, then assign the new policy group those few users. | However, by creating different policies, you can override the default settings even as a per user basis. Let's say you want to mark and deliver spam messages to all your users, but a few users want to keep their spam to the spam quarantine. All you have to do is set clapf.conf for marking spam, then create a new policy group and set the variable named spam_oblivion_limit, then assign the new policy group those few users. | ||
| - | Note that you don't have to set all of the supported attributes of the policy. The configuration settings of any user comprises the default policy overidden by their own policy settings. So if you don't set a certain parameter in the user's policy it remains as it is in the default policy settings. | + | The configuration settings of any user comprises the default policy overidden by their own policy settings. |
| - | The policy settings are stored in MySQL database. | + | The policy settings are stored in MySQL database in the //policy// table. |
| - | Please note that if you want policy support, you should use LMTP delivery, otherwise the default policy settings (ie. in clapf.conf) takes place. | + | Please note that if you want policy support, you should use LMTP delivery, otherwise the default policy settings (ie. in clapf.conf) takes place unless the email has a single recipient. |