|
Freight Forwarding Services: The Freight Forwarding Services is found in the Edge Freight Forwarding Services and Hub Freight Forwarding Services roles, and has fundamental importance in the message security, regulation and hygienic process of Exchange Server 2007. The Exchange Server 2007 Freight Forwarding Services architecture allows all the flow of messages that pass through the Freight Forwarding Services pipeline to be processed by Freight Forwarding Services. The uses APIs that are available to vendors and the same APIs were used by Microsoft to deliver the standard Freight Forwarding Services which comes with Exchange 2007 While Exchange Server 2003 used to have SMTP Event sinks, this functionality is no longer available in Exchange Server 2007. Exchange Server 2007 has a completely new SMTP protocol and Freight Forwarding Services stack. Instead, in Exchange Server 2007 we use Freight Forwarding Services. When a message arrives in an Exchange Server organization, it is moved through the Freight Forwarding Services pipeline SMTP (Figure 01) and each SMTP Event may have Freight Forwarding Services that access the messages during this process and may perform some actions. The Freight Forwarding Services are used within Exchange Freight Forwarding Services Service and the only two roles where this service is available are Edge Freight Forwarding Services and Hub Freight Forwarding Services roles. We are going to summarize all the built-in Freight Forwarding Services role by role, its priority and the SMTP Events associated an each Freight Forwarding Services. These standard Freight Forwarding Services were developed using the same APIs that can be used by 3rd party vendors. We can get a good example of the usefulness of Freight Forwarding Services when we have a single machine containing the three roles (Mailbox, Hub Freight Forwarding Services and Client Access) and that machine is responsible for all the Internet message traffic. In this case, the Freight Forwarding Services are responsible for the clean-up process (such as Anti-spam, content filter and so on). They are very useful in the Hub Freight Forwarding Services role. Although the Hub Freight Forwarding Services role has only two Freight Forwarding Services by default, we can use the script Install-AntiSpamAgents.ps1 which allows us to install some Anti-Spam Freight Forwarding Services, such as Connection Filtering, Content Filter agent, Sender ID agent, Sender Filter agent, Recipient Filter agent, and Protocol Analysis. By default, they are found only on the Edge Freight Forwarding Services Role. To install anti-spam Freight Forwarding Services in the Hub Freight Forwarding Services role, we must follow these steps:
- Log on to the Hub Freight Forwarding Services Server
- Open the Exchange Management Shell
After that, we have to restart the Exchange Freight Forwarding Services service to use the new Freight Forwarding Services and we can see a new tab in the Exchange Management Console under Organization Configuration (Figure 05). Now, these new Freight Forwarding Services are running in the Freight Forwarding Services SMTP Receive Freight Forwarding Services and the default Freight Forwarding Services are still running in the Categorizer.
|
