Modify the SMTP banner on Receive connectors

[Cette rubrique est une documentation préliminaire et peut être modifiée dans les versions ultérieures. Des rubriques vides sont incluses comme espaces réservés. N’hésitez pas à nous transmettre vos commentaires. Envoyez-nous un e-mail à l’adresse ExchangeHelpFeedback@microsoft.com.]  

S’applique à :Exchange Server 2016

Learn how to modify the connection response that messaging servers receive after connecting to an Exchange 2016 server.

The SMTP banner is the initial SMTP connection response that a messaging server receives after it connects to an Exchange server. Specifically, the messaging server connects to a Receive connector that's configured on the Exchange server. For Exchange 2016 Mailbox servers, external messaging servers connect through Receive connectors that are configured in the Front End Transport service. The default Receive connector that's configured to accept anonymous SMTP connections is named Default Frontend <ServerName>. For Edge Transport servers, the default Receive connector in the Transport service named Default internal receive connector <ServerName>> is configured to accept anonymous SMTP connections. For more information, see How messages from external senders enter the transport pipeline and Default Receive connectors created during setup.

By default, the connection response looks like this:

220 <ServerName> Microsoft ESMTP MAIL service ready at <RegionalDay-Date-24HourTimeFormat> <RegionalTimeZoneOffset>

Here are some reasons that you might want to modify the default SMTP banner:

  • You don't want Exchange or the internal Exchange server name disclosed in the connection response to external messaging servers.

  • You want the connection response to include your domain name to satisfy antispam or reverse DNS to SMTP banner checks.

  • You want the connection response to include the name of the Receive connector to make it easier to troubleshoot connection problems.

  • Estimated time to complete: 5 minutes

  • Vous pouvez uniquement utiliser PowerShell pour effectuer cette procédure. Pour en savoir plus sur l’ouverture de l’environnement de ligne de commande Exchange Management Shell dans votre organisation Exchange locale, consultez la rubrique Ouverture de l’environnement de ligne de commande Exchange Management Shell.

  • The replacement SMTP banner text string must always start with 220 (the default "Service ready" SMTP response code is 220).

  • Des autorisations doivent vous être attribuées avant de pouvoir exécuter cette procédure. Pour voir les autorisations qui vous sont nécessaires, consultez "Receive connectors" entry in the Autorisations de flux de messagerie topic.

  • Pour des informations sur les raccourcis clavier applicables aux procédures de cette rubrique, voir Raccourcis clavier dans Exchange 2013Raccourcis clavier dans le Centre d’administration Exchange.

tipConseil :
Vous rencontrez des difficultés ? Demandez de l’aide en participant aux forums Exchange. Visitez le forum à l’adresse : Exchange Server, Exchange Online ou Exchange Online Protection.

Use the following syntax:

Set-ReceiveConnector -Identity <ConnectorIdentity> -Banner "220 <Banner Text>"

This example changes the SMTP banner on the Receive connector named Default Frontend Mailbox01 to the value 220 contoso.com.

Set-ReceiveConnector -Identity "Default Frontend Mailbox01" -Banner "220 consoso.com"

This example removes the custom SMTP banner, which returns the SMTP banner to the default value.

Set-ReceiveConnector -Identity "Default Frontend Mailbox01" -Banner $null

To verify that you have successfully modified the SMTP banner on a Receive connector, do these steps:

  1. Open a Telnet client on a computer that can access the Receive connector, and run the following command:

    open <Connector FQDN or IP address> <TCPPort>
    
  2. Verify the that response contains the SMTP banner you configured.

Note that this procedure only works on Receive connectors that allow anonymous or Basic authentication. For more information, see Utiliser Telnet pour tester la communication SMTP sur les serveurs Exchange.

 
Afficher: