none
SmtpProxyEhloOptionsDoNotMatchContinueProxyingMonitor Exchange 2016 RRS feed

  • Question

  • Hi, 

    I have compare setting in different environment that I setup and have no this errors. And show same size/limits when im running :

    get-transportconfig | ft maxsendsize, maxreceivesize 
    get-receiveconnector | ft name, maxmessagesize 

    Log Name:      Application
    Source:        MSExchangeFrontEndTransport
    Date:          28.02.2017 11:12:45
    Event ID:      2030
    Task Category: SmtpSend
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      *****************
    Description:
    The EHLO options for the client proxy target **************** did not match while setting up proxy for user HealthMailboxa********************* on inbound session 08D45EBF9CD88457. The potentially mailflow-impacting mismatched options were SIZE (value). The non-impacting mismatched options were NONE. Client proxying will continue, but the mismatched options might cause some messages to be rejected by the target server.

    PSComputerName          : *********************
    RunspaceId              : 41f0b1b1-ac55-4486-9bff-0cc478119a2b
    PSShowComputerName      : False
    Server                  : **********************
    CurrentHealthSetState   : Online
    Name                    : SmtpProxyEhloOptionsDoNotMatchContinueProxyingMonitor
    TargetResource          : HubTransport
    HealthSetName           : HubTransport
    HealthGroupName         : ServiceComponents
    AlertValue              : Unhealthy

    IsHaImpacting           : False
    ServerComponentName     : HubTransport
    LastExecutionResult     : Succeeded
    IsStale                 : False
    Error                   : 
    Exception               : 
    IsNotified              : False
    LastFailedProbeId       : -229450476
    LastFailedProbeResultId : 2988
    ServicePriority         : 2
    Identity                : HubTransport\SmtpProxyEhloOptionsDoNotMatchContinueProxyingMonitor\HubTransport

    Tuesday, February 28, 2017 3:38 PM

Answers

  • Hi ,

    This error may happen if you have multiple Exchange 2013 or 2016 servers where the max receive and transport size are mismatched across your servers on your receive connectors.

    First to get the limits on each server:

    Get-transportconfig | ft maxsendsize, maxreceivesize

    Get-receiveconnector | ft name, maxmessagesize

    We can change the limits with the following powershell:

    Set-TransportConfig -MaxSendSize 50MB -MaxReceiveSize 50MB

    Get-receiveconnector | set-receiveconnector -maxmessagesize 50MB

    Restart the transport service after you’ve changed the values of the maxmessagesize.

    If it still doesn’t work, please check the protocol log, specifically the receive connector Client Proxy <servername>, we need to enable the log firstly with the following command:

    Get-receiveconnector | Set-receiveconnector -protocollogginglevel verbose

    Hope it helps.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by MaliStane Friday, March 3, 2017 9:27 AM
    Wednesday, March 1, 2017 3:11 AM
    Moderator

All replies

  • Hi ,

    This error may happen if you have multiple Exchange 2013 or 2016 servers where the max receive and transport size are mismatched across your servers on your receive connectors.

    First to get the limits on each server:

    Get-transportconfig | ft maxsendsize, maxreceivesize

    Get-receiveconnector | ft name, maxmessagesize

    We can change the limits with the following powershell:

    Set-TransportConfig -MaxSendSize 50MB -MaxReceiveSize 50MB

    Get-receiveconnector | set-receiveconnector -maxmessagesize 50MB

    Restart the transport service after you’ve changed the values of the maxmessagesize.

    If it still doesn’t work, please check the protocol log, specifically the receive connector Client Proxy <servername>, we need to enable the log firstly with the following command:

    Get-receiveconnector | Set-receiveconnector -protocollogginglevel verbose

    Hope it helps.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by MaliStane Friday, March 3, 2017 9:27 AM
    Wednesday, March 1, 2017 3:11 AM
    Moderator
  • Hallo Jason,
    I am aware of this. Problem is that I have development environment that mirror Production environment with same mix. The only difference is that anonymous relay connectors, are  same size as global limits, all other connectors are  at same limits as  in production environment.
    I will change the limit in DEV environment and update the information.

    To we know how to verify to which connector is  connecting, when it does itch cheeks ?

    BR,

    Borut Puhar

    Wednesday, March 1, 2017 7:58 AM
  • Hallo Jason,
    I asset settings on one Exchange 2016 server  in Mix 2013/2016  organization. Server is set  the same as it set 
    Set-TransportConfig -MaxSendSize 20MB -MaxReceiveSize 20MB

    Get-receiveconnector –Server “Servername” | set-receiveconnector -maxmessagesize 20MB

    I have restart  all transport services on the server, and  status for the server  is the same.
    But problem that I have is  that I don’t know how to trigger it (look  timframe
    Name                    : SmtpProxyEhloOptionsDoNotMatchContinueProxyingMonitor
    TargetResource          : HubTransport
    HealthSetName           : HubTransport
    HealthGroupName         : ServiceComponents
    AlertValue              : Unhealthy
    FirstAlertObservedTime  : 2/17/2017 7:54:09 AM
    Description             :
    IsHaImpacting           : False
    RecurranceInterval      : 0
    DefinitionCreatedTime   : 2/9/2017 3:19:14 AM
    HealthSetDescription    :
    ServerComponentName     : HubTransport
    LastTransitionTime      : 2/17/2017 7:54:09 AM
    LastExecutionTime       : 2/17/2017 7:54:09 AM
    Friday, March 3, 2017 8:56 AM
  • Ok,

    I restarted _

    Microsoft Exchange Health

    Microsoft Exchange Health Manager Recovery

    Looks good

    Friday, March 3, 2017 9:27 AM
  • Hi,

    Still looking for solution.

    What shout i loom in protocol log. What type of error, warring, or similar?

    In DEV works  with no problem, in prod with same setting, same error.

    Monday, April 10, 2017 12:45 PM
  • Only difference that I see is overwrites :

    In DEV environment :

    FrontendTransport\OnPremisesSmtpClientSubmissionMonitor

    In PROD this overwrite does not exist

    Monday, April 10, 2017 1:27 PM