This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 24%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Hi,
As per the design, emails will flow from frontend transport service to hub transport service. While analyzing messaging tracking log, I am not getting this information. When I run the following command, I am not getting the results
get-messagetrackinglog -server Contoso -start "<get-date> " | ft timestamp, connectorid, eventid, source, clienthostname, sender, recipients
What I am getting is the receive connector of hubtransport (Default contoso). Can someone please let me know how to capture frontend connector on messaging tracking logs ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi @Surya kumar,
Would you please clarify what information on connectors do you need for analysis?
Since to analyze SMTP conversations on receive connectors we usually check protocol logs, please make sure protocol log is enabled on the receive connectors and check protocol logs under this path:
%ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Kai Yao
I have multiple dedicated frontend receive connectors in place. I want to know through which front end connector the email was received and through which connector the email was transmitted from front end transport to hub transport
To check which connector was used, you can check the protocol log with timestamp (protocol log users UTC), sender, recipient or messageID as filter.
For example:
scenario: ******@domain2.com sends an email to ******@domain1.com
1.in message tracking log we can see the messageID is ******@domain2.com
2.in Frontend protocol service logs we can search with this messageID and see the message was received by the Default Frontend receive connector
3.in Transport service protocol logs we can see the message was received by Default receive connector
Thanks for the clarification. However, why the connector id value is empty when you ran message tracking log on exchange management shell
@Kai Yao ,
The message tracking log command which you ran on EMS is checking the logs only on the server on which this command was executed.
Suppose if I have multiple exchange servers, how can I identify which exchange server has relayed the email and what's the next hop?
why the connector id value is empty when you ran message tracking log on exchange management shell
Message tracking log logs the message activities in the transport pipeline.
Since not all transport events happen on connectors, it is the expected behavior.
Suppose if I have multiple exchange servers, how can I identify which exchange server has relayed the email and what's the next hop?
If you have multiple Exchange servers, you can append Get-Transportservice before Get-MessageTrackingLog to get the whole mail flow process.
Example:
Get-TransportService | Get-Messagetrackinglog -messagesubject "subject"
Or specify server with -server parameter to check the mail flow process on a specific server.
I agree. But if we change the event to SMTP Receive, we will be getting the entry for connectorid, right?
Can you confirm?
Yes it is the same in my lab.
@Kai Yao ,
I am left with one doubt. For knowing which receive connector was used during email transmission, we will check smtp protocol logs.
If I have multiple receive connectors with similar configuration, then under what basis a connector will be chosen? Do we have any priority?
Please help me with this!!!
If I have multiple receive connectors with similar configuration, then under what basis a connector will be chosen? Do we have any priority?
Yes. It is documentated here: Receive connector remote addresses
Multiple Receive connectors on the server can have overlapping remote IP address ranges as long as one range is completely overlapped by another. When remote IP address ranges overlap, the remote IP address range that has the most specific match to the connecting server's IP address is used.
@Kai Yao ,
Thanks for the quick response. How would be the situation if custom connector A has remote IP like 192.168.1.75 and custom connector B has remote IP like 192.168.1.75
In this case, which connector will be used. Will it go with alphabetical order?
You cannot have two connectors with the exact same listening port and remote ip address.
It would return error message like:
The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "conflicted connector". A Receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of these values.
Thank you very much for solving all of my queries