From MS Exchange 2013 Edge Transport Server Security Technical Implementation Guide
Part of SRG-APP-000247
Associated with: CCI-001095
Email system availability depends in part on best practice strategies for setting tuning configurations. This setting controls the maximum number of hops (email servers traversed) a message may take as it travels to its destination. Part of the original Internet protocol implementation, the hop count limit prevents a message from being passed in a routing loop indefinitely. Messages exceeding the maximum hop count are discarded undelivered.
Review the Email Domain Security Plan (EDSP). Determine the value for Receive connectors. Open the Exchange Management Shell and enter the following command: Get-ReceiveConnector | Select Name, Identity, MaxHopCount For each Receive connector, if the value of MaxHopCount is not set to 60, this is a finding. or If the value of MaxHopCount is set to a value other than 60 and has signoff and risk acceptance, this is not a finding.
Update the EDSP.
Open the Exchange Management Shell and enter the following command:
Set-ReceiveConnector -Identity <'IdentityName'> -MaxHopCount 60
Note: The
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer