Link to home
Start Free TrialLog in
Avatar of Sysguys
SysguysFlag for United Arab Emirates

asked on

Exchange 2013 logs for troubleshooting mailflow

Hi All,

We have created an receive connector on exchnage 2013 CAS server, for an application which uses to connect through IMAP to fetch email from the mailbox ,the problem is there has been some delay with the application sending emails ,we need to troubleshoot this issue from exchange side ,for this i wanted to know which logs do i need to check .
SOLUTION
Avatar of Tom Cieslik
Tom Cieslik
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,
1. You can use mxtoolbox (http://mxtoolbox.com/EmailHeaders.aspx) to analyse the received email headers , where you can find delay in seconds, so now you can isolate the issue , whether delay is from application end or gateway end or Exchange end.

2. Message tracking,
you can use get-messagetrackinglog to get the transport logs associated with particular sender/recevier/timestamps,

 C:\>$Msg = Get-TransportService |  invoke-command { get-messagetrackinglog -sender "applicatoin_email_address" -recipients "exch_mailbox" -start "12/28/2016" }

Then sort the output based on timestamp, so that you can see the events in a chronological order
 C:\>$msg1 = $msg | sort-object -property timestamp

Then pipe the output to format table with needed attributes,
 C:\>$msg1 | ft Eventid, source,sender,recipients,timestamp,messagelatency
From the above cmdlet you can get the message latency, now you will get the clear idea about delay origination.

Thanks