Creating a Custom Group Policy List and Rule

Although the Configuration tab of the Groups Web Interface contains several default lists that can be used to determine how the policy deals with specified email addresses and domains, you can also create custom lists.

Note: Regardless of whether the list is a default list or a custom list, it must be combined with a rule in the PureMessage policy, as described in the second part of this procedure.

In this tutorial step you will create an "offensive" list that the policy will use to quarantine messages that contain keywords specified in this list. Then you will use the PureMessage Manager to configure a group-specific policy rule for messages containing offensive words. These messages will be quarantined with the reason "offensive". Finally, you will add an "offensive" option to the quarantine search criteria that will allow group administrators to search for messages that were quarantined for this reason.

Note: This step and steps 6 and 7 require that you edit the policy script using the policy constructor in the PureMessage Manager. It is recommended that you first create a backup of the existing policy that you can revert to when you have finished this tutorial.

First you must back up the policy. On the Policy tab of the Manager, next to Backups on the sidebar, click Create. A backup entry with the date and time is displayed.

For more information, see "Creating a Group List", "Adding and Deleting Custom Reasons", the pmx-group-list man page, and the pmx-group man page.

For more information about configuring the PureMessage policy, see "Policy Configuration" in the Administrator's Reference and "Policy" in the Manager Reference.

Next, you will use pmx-group command to add a group policy setting, and then associate the setting with a group-specific policy rule.

Related concepts
Policy Configuration
Policy Tab
Related tasks
Creating a Group List
Adding and Deleting Custom Quarantine Search Reasons
Adding and Deleting Custom Log Search Reasons
Related information
pmx-group
pmx-group-list