FrontEnd protocol logs

Question

Hello!

Would you please help me clarify the following two questions regarding Exchange logs:

1) While configuring the Send connector I did NOT enable the outbound proxy through the FrontEnd service:

Nevertheless I can see the Outbound Proxy FrontEnd connector in the FrontEnd\SmtpReceive logs - why?

2) Protocol Logging

Is the "Inbound Proxy Internal Send Connector" from my FrontEnd\SmtpSend log the "The implicit and invisible intra-organization Send connector in the Front End Transport service on Mailbox servers." mentioned in the Protocol Logging article above?

Thank you in advance,
Michael

Answer 1

Hi
Here are the answers to your two questions:

1. I made a test , it also occurred that the logs of Outbound Proxy FrontEnd connector in the FrontEnd \ SmtpReceive logs. But I noticed that it contains the content of” smtp.availability” , I assume that it may be the logs of monitor to test connection health. It would not affect your normal use. When you check the logs , you just need care more about the Default Frontend part.
   
2. Yes. The "Inbound Proxy Internal Send Connector" from FrontEnd\SmtpSend logs the "The implicit and invisible intra-organization Send connector” in the Front End Transport service on Mailbox servers."

If this Answer is helpful, please click "Accept Answer" to upvote it. If you have extra questions about this answer, please click "Comment" and I will come to your aid.

Answer 2

Hi BenOu-MSFT,

Thank you for your reply!

Yes, I also noticed that the Outbound Proxy Frontend connector is used for the smtp.availability.contoso.com but thought that since my "Internet" send connector is the only send connector in the organization it must be used for all outbound traffic without exceptions. At least I don't know why it can be so... :(

Regards,
Michael

Answer 3

Hi BenOu-MSFT,

Thank you for your reply!

Yes, I also noticed that the Outbound Proxy Frontend connector is used for the smtp.availability.contoso.com but thought that since my "Internet" send connector is the only send connector in the organization it must be used for all outbound traffic without exceptions. At least I don't know why it can be so... :(

Regards,
Michael