Tuesday, February 23, 2010

How to and when to enable Anti Spam feature on Hub Transport Servers

In this article, we have given a piece of the information about enabling and disabling the Anti-Spam Features on Hub Transport Servers. Usually, the Anti Spam feature will be disabled in the Hub Transport Servers and the Anti Spam feature is enabled in the Edge Transport Servers. This is the desired configuration, if you want the Edge Transport Servers to run Anti-Spam filters on messages before they are routed into the Exchange Organization. Once the messages are filtered by the Edge Transport Servers, you don’t have to filter them again, as the Hub Transport Servers have Anti-Spam features disabled. Consider, if an organization has Hun Transport Servers and doesn’t have the Edge Transport Servers, you can enable the Anti-Spam features on Hub Transport servers that receive messages from the Internet. If you want to enable or disable the Anti-Spam features on Hub Transport servers, you can do it by using Set-TransportServer cmdlet.


All you have to do is just enable set the Anti-SpamAgentEnabled parameter $true. At the same time if you want to disable, just make the AntispamAgentsEnabled parameter to $false.

The example given below let you understand how to enable Anti-Spam feature on a Hub Transport server named CorpSvr127.
Set-TransportServer –Identity 'CorpSvr127' –AntispamAgentsEnabled $true

Once you enable the Anti-Spam Feature on a Hub Transport Server, you have to restart the Microsoft Exchange Transport service on the Server but, if you exit and restart the Exchange Management Console, you’ll then see the Anti-Spam tab in the details pane.
By