Export (0) Print
Expand All

Exchange transport agents evaluation criteria

Exchange

Published: July 16, 2012

Find evaluation criteria for using Exchange transport agents to extend and modify Exchange transport behavior.

Applies to:  Exchange 2013 | Exchange Server 2007 | Exchange Server 2010 

In this article
Functional criteria for using Exchange transport agents
Development criteria for using Exchange transport agents
Security criteria for using Exchange transport agents
Deployment criteria for using Exchange transport agents
Additional resources

Exchange provides a library of classes that support the extension of transport behavior. You can use these classes to extend and modify transport behavior to customize acceptance, rejection, routing, and delivery of messages and to convert between various types of content.

The following table lists and describes the functional criteria for using Exchange transport agents. For descriptions of the functional criteria, see Functional criteria in the Exchange development technology evaluation criteria descriptions article.

Table 1:  Exchange transport agents functional criteria

Criterion

Description

Application function

Transport agents are applications that run on the Exchange server that enable you to intercept email messages to read, write, and modify the message content. These applications can also scan the message for a virus, run the message through a spam filter, and log traffic for inbound and outbound messages.

Availability

Transport agents are available starting with Exchange 2007. Transport agents are not supported in Exchange Online.

Application architectures

Transport agent applications run on the Exchange server and might also include a background service that performs additional tasks.

Remote usage

Transport agents run on the Exchange server and do not support remote usage.

Major objects

The Microsoft.Exchange.Data.Transport namespace contains types that support the extension of transport behavior. You can use the types in this namespace to specify how the Exchange transport handles messages by implementing transport agents that act on SMTP, routing, and delivery events. You can use the classes in the Microsoft.Exchange.Data namespaces to read, write, and modify email message content types such as iCalendar, TNEF, vCard, and MIME formatted content.

Data access model

The message data is accessible as a hierarchical set of data objects.

Threading models

Event processes should not spawn any additional threads.

Transactions

Transport agents do not support transactions.

Management capabilities

Transport agents do not by themselves generate Windows Event Log entries. The code that executes in response to a transport agent can generate Windows Event Log events and information for Windows Performance Counters.

The following table lists and describes the development criteria for using Exchange transport agents. For descriptions of the development criteria, see Development criteria in the Exchange development technology evaluation criteria descriptions article.

Table 2:  Exchange transport agents development criteria

Criterion

Description

Languages and tools

Transport agents are based on the .NET Framework. Any .NET Framework language can be used to develop transport agent applications.

Managed implementation

Transport agent applications can be used with managed code.

Scriptable

Transport agents do not support scripting.

Test/debug tools

No special debugging tools are needed to debug applications that use transport agents.

Expert availability

Few developers who have significant previous experience with transport agents are available. You may be able to find developer support for by visiting the Exchange developer forum.

Available information

Information about the transport agents is available on MSDN and in forums and blogs. For information about developing transport agents, see the Exchange Server 2010 Transport Agents SDK, the Exchange Server Development forum, and the Exchange Server Developer Center.

Developer/deployment licensing

Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your transport agent applications are developed and deployed.

The following table lists and describes the security criteria for using Exchange transport agents. For descriptions of the security criteria, see Security criteria in the Exchange development technology evaluation criteria descriptions article.

Table 3:  Exchange transport agents security criteria

Criterion

Description

Design-time permissions

You must have permissions to access the data in the Exchange store in order to use transport agents.

Setup permissions

A user who has sufficient permission to register the application on the Exchange server must set up applications that use transport agents.

Run-time permissions

You must have permissions to write into the folders on the Exchange server where the events are run in order to run applications that use transport agents.

Built-in security features

Transport agents do not provide any built-in security features.

Security monitoring features

None.

The following table lists and describes the deployment criteria for using Exchange transport agents. For descriptions of the deployment criteria, see Deployment criteria in the Exchange development technology evaluation criteria descriptions article.

Table 4:  Exchange transport agents deployment criteria

Criterion

Description

Server platform requirements

Transport agents are run on Exchange 2013, which must run on the Windows Server 2008 platform. Earlier versions of Exchange have different requirements.

Client platform requirements

Not applicable; transport agents are not a client-side technology.

Deployment methods

You can install transport agent applications by using an Exchange Management Shell script.

Deployment notes

None.

Community Additions

ADD
Show:
© 2014 Microsoft