We all know that we can classify a sender as Safe or Blocked in Outlook 2003/Exchange 2003 environment, this is just local SPAM control solution in Exchange 2003.
Exchange 2007 takes is a little further with the cmdlet Upadte-Safelist.
This cmdlet synchronizes the JUNK mail settings of the user to the Exchange Transport servers and allows for the JUNK mail handling at the server level itself.
This classification becomes important as EDGE server role which is not part of the Corporate network, handles the mails to the users based on the data in the ADAM, avoiding false positives.
You can choose to Sync either the Safe sender list or the Safe recipient list or Both, the default being Safe sender list.
Ex:-
Update-Safelist -Identity <UserAlias> -Type "Safesenders"
Update-Safelist -Identity user1 -Type "Saferecipient"
Update-Safelist -Identity user2 -Type "Both"
You can apply it on the Server/Storage group/Store level or to a particular filter setting.
No comments:
Post a Comment