Exchange 2016 Event ID 2030

Question

_{Wednesday, March 29, 2017 12:51 PM}

Hi all,

I have this repeating ID in the logs on the server:

The EHLO options for the client proxy target <IP Address> did not match while setting up proxy for user  on inbound session 08D47334A097AA0D. 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.

The Exchange has 2 IP addresses and both are presented in the events. I've checked some articles and it seems that this is a configuration issue with the receive connectors. I've checked also this link: https://social.technet.microsoft.com/Forums/en-US/42fe1dd1-e8e8-4fb9-9c4c-56685acb8584/exchange-2013-msexchangefrontendtransport-error-2030?forum=exchangesvrgeneral but we have 7 connectors and I want to find out where is the problem and hopefully who is the user/computer/server causing this event. On the server I can see Connectivity, MessageTracking and SmtpReceive/Send logs but I was not able to find something about such sessions. Can you give some information about checking the logs - maybe I'm looking in the wrong logs.

Thanks in advance

All replies (2)

_{Thursday, March 30, 2017 5:50 AM}

Hi,

The issue may be related to your receive Connectors message size limit. If you have changed the size on a specific connector and not all of them, then you could be getting NDRs once you hit the lower of the two settings.We can run the following command to check the detailed message size limit:

Get-transportconfig | ft maxsendsize, maxreceivesize 

Get-SendConnector | ft name, MaxMessageSize

Get-receiveConnector | ft name, MaxMessageSize

https://technet.microsoft.com/en-us/library/bb124345(v=exchg.160).aspx

Best Regards,
David Wang
TechNet Community Support

Please remember to mark the replies as answers if they helped.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, March 30, 2017 6:02 AM}

Hi David,

thank you for your answer but this is not what I'm looking for. In my post I wrote that I've checked what is the problem but I what to find which one connector is the problem and which user/computer actually "hit" this connector and caused the event. That's why I have to look deeper in the logs but my knowledge there is not so good.