Export (0) Print
Expand All

Using the Edge Transport Node

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2007-08-14

Use the Edge Transport configuration node to view and maintain the features of the Edge Transport server role. In Microsoft Exchange Server 2007, the Edge Transport server role is deployed in your organization's perimeter network as a stand-alone server or as a member of a perimeter domain. Designed to minimize the attack surface, the Edge Transport server handles all Internet-facing mail flow. This provides Simple Mail Transfer Protocol (SMTP) relay and smart host services for the Exchange 2007 organization. Additional layers of message protection and security are provided by a series of agents that run on the Edge Transport server and act on messages as they are processed by the message transport components. These agents support the features that provide protection against viruses and spam, apply transport rules to control message flow, and provide message security.

Use the Anti-spam tab to manage anti-spam and antivirus features that can help reduce the volume of spam, viruses, and malicious software, which is also referred to as malware, that enter your organization. By eliminating the bulk of the spam at the computer that has the Edge Transport server role installed, you save processing resources and bandwidth when the messages are scanned for viruses and other malware further along the mail flow path. The Anti-spam tab contains the following items to help configure your system against spam and malware:

  • Content filtering

  • IP Allow list

  • IP Allow List providers

  • IP Block list

  • IP Block List providers

  • Recipient filtering

  • Sender filtering

  • Sender ID

  • Sender reputation

For more information, see Anti-Spam and Antivirus Functionality.

Use the Receive Connectors tab to configure your Receive connectors. Receive connectors are the gateway through which messages are received by an Exchange 2007 transport server. By default, the Receive connectors that are required for mail flow from the Internet and between the Hub Transport server and the Edge Transport server are created when those roles are installed. For more information, see Receive Connectors.

A Send connector controls outgoing connections from the Edge Transport server to the receiving server or destination e-mail system. By default, no explicit Send connectors are created when the Edge Transport server role is installed. You must configure at least one Send connector to establish Internet mail flow. You can manually configure a Send connector on the Edge Transport server or subscribe the Edge Transport server to the Exchange organization. After an Edge Transport server is subscribed to the Exchange organization, all configuration of Send connectors for that Edge Transport server must be performed on a Hub Transport server. The EdgeSync synchronization process then replicates those Send connectors to the Active Directory Application Mode (ADAM) directory service as part of the configuration data.

If you do not subscribe the Edge Transport server to the Exchange organization, you can only designate the local Edge Transport where the Send connector is configured as a source server. If you have subscribed one or more Edge Transport servers to the same Active Directory site, you can designate more than one Edge Subscription as a source server entry. If there is a Send connector that is configured to send mail to an external domain, when any Hub Transport server in the organization routes mail to that domain, the messages are delivered to a source server for that connector for relay to the destination domain. For more information about how to configure Send connectors for the Edge Transport server, see the following topics:

The transport rules that you configure on an Edge Transport server are applied only to e-mail messages that pass through that specific Edge Transport server. For more information, see Overview of Transport Rules.

An accepted domain is any SMTP namespace for which an Exchange organization sends and receives e-mail messages. Accepted domains include those domains for which the Exchange organization is authoritative. An Exchange organization is authoritative when it handles mail delivery for recipients in the accepted domain. Accepted domains also include domains for which the Exchange organization receives mail and then relays to an e-mail server that is outside the Active Directory forest for delivery to the recipient. For more information, see Managing Accepted Domains.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft