Enable Anti-Spam Functionality on a Hub Transport Server

Enable Anti-Spam Functionality on a Hub Transport Server Exchange 2010 & 2013

The AntiSpam functionalities can also be enabled on HT Server for organizations that may not have enough e-mail volume to justify the cost of installing and maintaining a full perimeter network together with an Edge Transport server.

Exchange 2010 AntiSpam Features:

• Connection filtering
• Content filtering
• Sender ID 
• Sender filtering
• Recipient filtering
• Sender reputation

Exchange 2013 AntiSpam Features:

• Content Filter agent
• Sender ID agent
• Sender Filter agent
• Recipient Filter agent
• Protocol Analysis agent for sender reputation

Note: The attachment filtering is an antivirus feature that isn't enabled or installed. Attachment filtering only runs on the Edge Transport server. However, the file filtering functionality that's provided by Microsoft Forefront Protection for Exchange Server includes advanced features that are unavailable in the default Attachment Filter agent that's included with Microsoft Exchange Server 2010 Standard Edition. 

Procedure:

1. Run the following command from the %system drive%/Program Files\Microsoft\Exchange Server\V14\Scripts folder.
   
   .\install-AntispamAgents.ps1
   
   

2. After the script has run, restart the Microsoft Exchange Transport service by running the following command.
   
   
   

   Restart-Service MSExchangeTransport

   
   

   
   

   
   3. You need to specify the IP addresses of any internal SMTP servers that should be ignored by the Sender ID agent. In fact, you need to specify the IP address of at least one internal SMTP server. If the Mailbox server where you're running the anti-spam agents is the only SMTP server in your organization, specify the IP address of that computer.

   
   

   To add the IP addresses of internal SMTP servers without affecting any existing values, run the following command:

   Set-TransportConfig -InternalSMTPServers @{Add="<ip address1>","<ip address2>"...}
   

   This example adds the internal SMTP server addresses 10.0.1.10 and 10.0.1.11 to the transport configuration of your organization.

   Set-TransportConfig -InternalSMTPServers @{Add="10.0.1.10","10.0.1.11"
   
   }