|
Cargo Customs Services: The Cargo Customs Services is found in the Edge Cargo Customs Services and Hub Cargo Customs Services roles, and has fundamental importance in the message security, regulation and hygienic process of Exchange Server 2007. The Exchange Server 2007 Cargo Customs Services architecture allows all the flow of messages that pass through the Cargo Customs Services pipeline to be processed by Cargo Customs Services. The uses APIs that are available to vendors and the same APIs were used by Microsoft to deliver the standard Cargo Customs 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 Cargo Customs Services stack. Instead, in Exchange Server 2007 we use Cargo Customs Services. When a message arrives in an Exchange Server organization, it is moved through the Cargo Customs Services pipeline SMTP (Figure 01) and each SMTP Event may have Cargo Customs Services that access the messages during this process and may perform some actions. The Cargo Customs Services are used within Exchange Cargo Customs Services Service and the only two roles where this service is available are Edge Cargo Customs Services and Hub Cargo Customs Services roles. We are going to summarize all the built-in Cargo Customs Services role by role, its priority and the SMTP Events associated an each Cargo Customs Services. These standard Cargo Customs 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 Cargo Customs Services when we have a single machine containing the three roles (Mailbox, Hub Cargo Customs Services and Client Access) and that machine is responsible for all the Internet message traffic. In this case, the Cargo Customs Services are responsible for the clean-up process (such as Anti-spam, content filter and so on). They are very useful in the Hub Cargo Customs Services role. Although the Hub Cargo Customs Services role has only two Cargo Customs Services by default, we can use the script Install-AntiSpamAgents.ps1 which allows us to install some Anti-Spam Cargo Customs 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 Cargo Customs Services Role. To install anti-spam Cargo Customs Services in the Hub Cargo Customs Services role, we must follow these steps:
- Log on to the Hub Cargo Customs Services Server
- Open the Exchange Management Shell
After that, we have to restart the Exchange Cargo Customs Services service to use the new Cargo Customs Services and we can see a new tab in the Exchange Management Console under Organization Configuration (Figure 05). Now, these new Cargo Customs Services are running in the Cargo Customs Services SMTP Receive Cargo Customs Services and the default Cargo Customs Services are still running in the Categorizer.
|
