Using distribution lists as part of Symantec Messaging Gateway policy groups has unanticipated results when applying filtering policies and taking actions on email traffic.

When binding a distribution list to a policy group through its LDAP Distinguished Name and distribution list expansion is diabled:

• mail sent to the distribution list primary address will not trigger policies assigned to the policy group
• mail sent to a distribution list alias address will not trigger policies assigned to the policy group

When binding a distribution list to a policy group via an alias address and distribution list expansion is disabled:

• mail sent to the distribution list member's primary address will not trigger policies assigned to the policy group
• mail sent to the distribution list member's email alias addresses will not trigger policies assigned to the policy group

When binding a distribution list to a policy group via an alias address and distribution list expansion is enabled:

• mail sent to the distribution list primary address will not trigger policies assigned to the policy group
• mail sent to the distribution list's alias address will not trigger policies assigned to the policy group
•  mail sent to the distribution list member's primary address will not trigger policies assigned to the policy group
• mail sent to the distribution list member's email alias addresses will not trigger policies assigned to the policy group

Many of these behaviors will be addressed in a future release. Currently, binding distribution lists to policy groups to distribution lists through their primary mail address will provide the most predictable results.