Creating Lists or Maps

The procedure for creating either a new list or a new map is mostly the same, and both procedures use the same page and form in the PureMessage Manager.

Lists are used in the policy to exclude or include the listed groups or addresses from tests or actions. For example, in the default policy, messages originating from addresses contained in the Whitelisted hosts list are not scanned for spam.

Maps are used to associate one email address with another for the purpose of redirection (as with the Notifications Address Map). For example, the policy could be configured to redirect messages from an alias email address to a personal email address via the use of an address map. Maps can also be used to apply user preferences (as with the Recipient Aliases Map), or, in the case of custom maps, for a user-defined purpose.

Note Although PureMessage supports the creation of LDAP-based lists and maps, these lists and maps are read-only; you can only edit them using LDAP tools and not with PureMessage.

To create a new list or address map:

  1. On the sidebar of the Policy tab, click New beside Lists to create a new list, or click New beside Address Maps to create a new address map.

    The Add List/Map page is displayed, with either List or Map displayed in the Type drop-down list, depending on which New button you clicked.

  2. In the Create New List/Map table, specify the following:
    1. Type: Ensure that the correct type is selected, either List or Map.
    2. ID: Enter the identity that will be used for the list’s or map’s filename.
      Lists and maps are stored in individual configuration files. The name that you enter in this text box becomes the filename. The name that you enter should therefore describe the purpose of the list or map, and it should be in a format that is usable as a filename. For example, the Anti-spam opt-outs list has an identity of anti-spam-optouts.
    3. Name: Enter the name of the list or map.
      This is the name that will be displayed on the Policy tab sidebar.
    4. Description: Enter a meaningful description for the list or address map.
      This information will be displayed in the Description column of the Configured Lists or Configured Maps table that is displayed when you click manage at the bottom of either the Lists or Address Maps sections of the Policy tab sidebar.
    5. Match Type: Enter the matching method that you want the message filtering to use when the policy service compares a message to the contents of the list.

      See “Match Types” for detailed information on the significance of each of these choices.

  3. In the Source section, select either Flat file or LDAP. If you select LDAP, you must also enter the following information:
    1. LDAP Server: Specify the 'host:port' of the server(s) to connect to when authenticating users via LDAP.
      To specify more than one LDAP host for failover, enter a list of hosts separated by semicolons. If no ':port' is specified, port 389 is used by default. To use an encrypted LDAPS connection, simply prefix the host:port with 'ldaps://'. For LDAPS connections, port 636 is used if no port is specified. For example:
      localhost:636 ldaps://
      As a failover, it is strongly advised that you specify two or more LDAP servers in the LDAP Server text box. This is done by separating the URLs with semicolons. For example:
    2. DN for binding to LDAP server: Specify the Distinguished Name(DN) used to connect to the LDAP server in order to query the Distinguished Name of the user the system is attempting to authenticate. This text box supports variable substitution.
    3. Password for binding to LDAP server: Specify the password used to connect to the LDAP server in order to query the Distinguished Name (DN) of the user that the system is attempting to authenticate. This DN and password should be granted minimal rights but must be able to perform a query to retrieve the DN for a user based on their provided username/id.
      Note Any password entered when adding an LDAP-based list or map appears in a plain text file, either etc/maps.conf or etc/lists.conf. It is therefore suggested that you use the password for an LDAP account with privileges limited to user and password authentication.
    4. Base DN for matching: Specify the top LDAP directory node underneath which the search is performed to retrieve the DN of the user. This text box supports variable substitution.
    5. Filter to match list/map: Specify the LDAP or Active Directory search string. This text box supports variable substitution. To match on an email address, use the %s variable. You can also use %u to match only on the portion of the address to the left of the @ symbol, or %d to match everything to the right of the @ symbol.
    6. Map attribute: When creating a new map, enter the 'map to' value here. For example, if converting user IDs to email addresses, the map attribute could be 'mail'.
  4. Once all the required information is set, click Save to add the list or map.