Address Maps

Address maps are used to associate one email address with another, either for the purpose of redirecting notifications generated by PureMessage (such as Quarantine Digests), or for the purpose of assigning one user's email preferences to other accounts (for End User Web Interface usage).

The default address maps (the Notifications Address Map and the Recipient Aliases Map) are implemented automatically; they are not explicitly implemented in the policy script. To use these maps, simply populate them with the desired values. Custom address maps must be implemented via a policy rule.

PureMessage processes the contents of address maps from top to bottom. Within a map, if two mappings apply to a single address, the first mapping is used. For example, if the first entry maps sales*@example.com to joe@example.com, and the second entry maps saleslocal@example.com to mary@example.com, all messages with addresses beginning with "sales" are mapped to Joe, not to Mary.

PureMessage is distributed with two address maps:

  • Notifications Address Map: Accessible from the Quarantine or Policy tab in the PureMessage Manager, or by editing the notifications file, located in the etc directory beneath the root PureMessage installation directory.
    Note: The /opt/pmx6/etc/notifications file is a shared resource. If you edit this file, you must sync it to the database with the following command (run as the PureMessage user):
    pmx-profile sync-to-db --resource=notifications --force

    The Notifications Address Map redirects PureMessage notifications (such as quarantine digests and virus notices) from the original message recipient to the recipient specified in the map. For example, the address sales@example.com might be administered by a user called joe@example.com. An entry in the Notifications Address Map that maps sales@example.com to joe@example.com ensures that messages generated by PureMessage to the address sales@example.com are sent to joe@example.com. (Note that the Notifications Address Map does not consolidate digests; see Consolidating Quarantine Digests in the Quarantine Manager chapter for instructions on that feature.)

  • Recipient Aliases Map: Accessible from the Policy tab in the PureMessage Manager, or by editing the recipient-aliases file, located in the etc directory beneath the root PureMessage installation directory.
    Note: The /opt/pmx6/etc/recipient-aliases file is a shared resource. If you edit this file, you must sync it to the database with the following command (run as the PureMessage user):
    pmx-profile sync-to-db --resource=recipient-aliases --force

    The Recipient Aliases Map replaces the original message recipient with another recipient for the purpose of applying user preferences (such as per-user whitelists and blacklists, as well as viewing messages in the End User Web Interface). For example, if the address feedback@example.com is administered by the user karen@example.com, the recipient alias map could be used to assign the preferences associated with karen@example.com to the address feedback@example.com. While this does not alter the actual recipient address (that is, the message is delivered to feedback@example.com), the PureMessage policy uses the preferences set for karen@example.com while processing the message.

    When recipient alias mapping is enabled for a user, per-user whitelist and blacklist entries made via the End User Web Interface (or via the End User Whitelist and End User Blacklist options on the Quarantine tab of the PureMessage Manager), they are only applied for the destination of the recipient alias map, not the source. For example, if feedback@example.com is mapped to karen@example.com. End User Blacklist and Whitelist entries for feedback@example.com are ignored; instead, user preferences for karen@example.com are applied, and karen@example.com will also be able to view the messages for feedback@example.com in the End User Web Interface.

For information about populating map contents, or for information about configuring custom maps, see "Creating Lists or Maps". Also see the "Operators" and "Wildcard Usage" sections for information on matching email addresses, hostnames and IP addresses.