The
Safelist Aggregation component of an Edge Transport server allows an
administrator to obtain copies of end users’ Safe Senders lists from
Outlook 2003 and 2007 clients. Safelist Aggregation essentially provides
a mechanism to respect the entries users have made in their Safe
Senders lists, which reduces false positives when filtering for spam. By
moving the user’s safelist to the Edge Transport server, a rule or spam
filtering process set up at the Edge won’t delete email that a user has
deemed desired.
Configuring Safelist Aggregation for Outlook 2003/2007
As with all of the other
Edge Transport rule processes, the Edge Transport server must be
subscribed to the Exchange Server 2010 organization from which you want
to retrieve Safe Senders list entries on Outlook 2003 and 2007 clients.
Safe Senders are replicated to the Edge Transport server using EdgeSync.
Safelist entries created by users and imported using Safelist
Aggregation are recognized when the Content Filtering Agent examines the
message.
Note
You
can only use Safelist Aggregation with the Content Filtering Agent
enabled and on an Edge Transport server that has a subscription with the
organization’s Hub Transport server. Also, entries in the local
Contacts list in Outlook and any external account the user sends email
to is added to their safelist. These entries are replicated to the Edge
Transport server and used with Safelist Aggregation. Outlook’s safelist
collection is composed of the Safe Senders, Recipients, Domains, and
External Contacts. Each user can have a maximum of 1,024 entries in
their safelist collection.
Safelist Aggregation can only be enabled with the Exchange Management Shell by running the Update-SafeList
command against a user’s mailbox on a server running under the Mailbox
server role. That information must then be replicated to the Edge
Transport server using EdgeSync.
To configure Safelist Aggregation, complete the following steps:
1. | Use the Update-Safelist
Exchange shell command on a server running under the Mailbox server
role to aggregate and copy the safelist collection data from the user’s
mailbox to the user object in Active Directory:
Update-Safelist -Identity HeatherL -DomainController dc2.companyabc.com -Type Both
Note
To run the Update-SafeList command against multiple mailboxes residing in a particular organizational unit, you must prepend its use with the Get-MailboxGet-Mailbox command statement, add the update-safelist command: command. This could also be useful when included inside of a script. At the end of the
Get-Mailbox -OrganizationalUnit CompanyABC.com\Sales\Users | update-safelist
|
2. | Schedule the Update-Safelist command to run frequently:
AT 19:00 /every:M,T,W,Th,F,S,Su cmd /c "C:\Temp\Update-SafeList"
Note
You must use the AT
command to schedule Safelist Aggregation. The AT command can call to a
batch file or script that includes the commands to run Safelist
Aggregation.
|
3. | Verify that EdgeSync is properly replicating from the Hub Transport server to the Edge Transport server.
|
4. | Ensure the Content Filtering Agent is enabled on the Edge Transport server on which you want to perform Safelist Aggregation.
|
