none
FQDN receive connectors

    Question

  • Dear All,

    we are trying to change the FQDN of the Default Exchange recieve connectors.

    when we telnet external it does use the server.domain.local which cause a smtp banner check error and could cause us being on the black list.

    can someone please advise how to get this fixed?

    our receive connectors are as following

    Name           : Default EX
    AuthMechanism   : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole   : HubTransport
    PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers
    MaxMessageSize : 35 MB (36,700,160 bytes)

    Name           : Client Proxy EX
    AuthMechanism   : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole   : HubTransport
    PermissionGroups : ExchangeUsers, ExchangeServers
    MaxMessageSize : 35 MB (36,700,160 bytes)

    Name           : Default Frontend EX
    AuthMechanism   : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole   : FrontendTransport
    PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
    MaxMessageSize : 36 MB (37,748,736 bytes)

    Name           : Outbound Proxy Frontend EX
    AuthMechanism   : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole   : FrontendTransport
    PermissionGroups : AnonymousUsers, ExchangeServers
    MaxMessageSize : 36 MB (37,748,736 bytes)

    Name           : Client Frontend EX
    AuthMechanism   : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
    RemoteIPRanges : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    TransportRole   : FrontendTransport
    PermissionGroups : ExchangeUsers
    MaxMessageSize : 35 MB (36,700,160 bytes)

    Name           : veeam
    AuthMechanism   : Tls, ExternalAuthoritative
    RemoteIPRanges : {192.168.4.4}
    TransportRole   : FrontendTransport
    PermissionGroups : AnonymousUsers, ExchangeServers
    MaxMessageSize : 35 MB (36,700,160 bytes

    the error I get from the mxtoolbox is 

    Connecting to IP address 

    220 EX.domain.lan Microsoft ESMTP MAIL Service ready at Wed, 21 Jun 2017 05:26:39 +0200 [675 ms]
    EHLO PWS3.mxtoolbox.com
    250-EX.domain.lan Hello [64.20.227.134]
    250-SIZE 37748736
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-STARTTLS
    250-X-ANONYMOUSTLS
    250-AUTH NTLM
    250-X-EXPS GSSAPI NTLM
    250-8BITMIME
    250-BINARYMIME
    250-CHUNKING
    250 XRDST [713 ms]
    MAIL FROM:<supertool@mxtoolbox.com>
    250 2.1.0 Sender OK [714 ms]
    RCPT TO:<test@example.com>
    550 5.7.1 Unable to relay [5720 ms]

    • Edited by Julien.AG Wednesday, June 21, 2017 3:32 AM
    Wednesday, June 21, 2017 3:25 AM

All replies

  • if you wish to change the helo banner you should make a new dedicated receive connector and change the url to match your external FQDN
    • Proposed as answer by Andy DavidMVP Wednesday, June 21, 2017 9:54 PM
    Wednesday, June 21, 2017 8:39 PM