Distribution List Handling

If the distribution list has a Home-MTA, messages containing a distribution list recipient are first routed to the designated distribution list expansion point or to the local expansion point, if no distribution list expansion point is defined. When all recipients have been routed, either locally or to a remote connector, the original message is fanned out ¾ that is, multiple copies are created, one for each destination. Each message has its responsibility attribute set for all recipients who have been routed to that destination.

If the message is routed locally, a distribution list-expansion message copy whose recipients are the distribution list members is first fanned out. Then the distribution list expansion copy is passed back through the routing process. The process is repeated recursively for each nested level of the distribution list. The MTA verifies that an infinite loop is not generated by distribution list expansion.

An MTA can be configured to not expand replicated remote-site distribution lists.

    To configure an MTA to not expand replicated remote site distribution lists

1. In the Administrator program, double-click the server's MTA object, and then select the General tab.
2. Clear the Expand Remote Distribution Lists Locally check box.
3. Choose OK.