Message Trace in Microsoft 365

Owned by Tyler Horsford (Unlicensed)
Last updated: Dec 13, 2022 by Matthew Sywulak
4 min read

 

Summary

If you’re running into issues with messages being delivered to the incorrect location or receiving bouncebacks, performing a message trace is a crucial step in determining the core issue. Message traces are also extremely useful when engaging with INKY’s support team.

Trace a Message

  1. Log in to the Microsoft 365 Exchange Admin Center

  2. Select Mail Flow > Message Trace on the left-hand menu

  3. Select Start a Trace
    You can search using the following parameters:

    • Message ID

    • FROM address

    • TO Address

  4. For every result that comes back in the “Message trace search results” select them and in the side panel that opens select “Copy report text”

     

     

  5. Retrieve copied report text (examples below) and provide back to INKY support.

Subject: BDO Digital's Top Articles This Month Sender: bdousa@info.bdo.com Recipient: bradley@polvocapital.com Received -> Processed -> Delivered Status: This message was sent to the recipient's Junk Email folder. More information: <div>If you believe this message was incorrectly marked as spam, the recipient can send us a spam false-positive report by following these steps:<ol><li>In <a href='https://outlook.office365.com/owa/' target='_blank'>Outlook on the web</a>, go to the <b>Junk Email</b> folder and find the message that was incorrectly marked as junk.</li><li>Right-click the message, and then click <b>Mark as not junk</b>.</li><li>In the <b>Report as not junk dialog</b>, click <b>Report</b>.</li></ol>Your report automatically goes to the Microsoft Spam Analysis Team at not_junk@office365.microsoft.com. We'll use your report to help improve our spam filters.<br /><br />If you're using the Outlook desktop client, you need to use the junk email reporting tool to report the issue. For more information about it, see <a href='http://go.microsoft.com/fwlink/p/?LinkId=299247' target='_blank'>Junk Email Reporting Add-in for Microsoft Office Outlook</a>.</div> Date (UTC-05:00) | Event | Detail | ------------------------------------ 12/6/2022, 12:31 PM | Receive | Message received by: IA0PR02MB9220.namprd02.prod.outlook.com using TLS1.2 with AES256 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Processed SPAM', ID: ('AE9B2C61-C9C5-4AA4-B249-24D6334EBBAA'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Processed SPAM', ID: ('AE9B2C61-C9C5-4AA4-B249-24D6334EBBAA'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Processed SPAM', ID: ('AE9B2C61-C9C5-4AA4-B249-24D6334EBBAA'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Defer | Reason: 400 4.7.721 Advanced Threat Protection scanning in progress. 12/6/2022, 12:32 PM | Spam | No detail information available. 12/6/2022, 12:32 PM | Deliver | The message was delivered to the Junk Email folder. More information Message ID:<1213727060.579554359.1670347881891@sjmktmail-batch1m.marketo.org> Message size | From IP | To IP ‎226.16‎ KB | 192.28.158.140 | null
Subject: BDO Digital's Top Articles This Month Sender: bdousa@info.bdo.com Recipient: bradley@polvocapital.com Received -> Processed -> Sent Status: Office 365 used one of your organization's connectors to send the message to an external address. An admin in your organization set up a mail flow rule to route messages through that connector. Here are the details:<br /><br /><b>Connector name:</b> ‎IPW‎<br /><b>External address:</b> ‎bradley@polvocapital.com‎<br /><b>Destination IP:</b> ‎44.225.179.230‎<br /><b>Destination smart host:</b> ‎ipw-mta-o365-prod-b3d65134e94c6bdc.elb.us-west-2.amazonaws.com‎<br /><b>Mail flow rule:</b> ‎IPW Mail for Inky‎ More information: <div>You can view your organization's connector settings on the <a href='https://admin.exchange.microsoft.com/#/connectors' target='_blank'>connectors</a> page, and the mail flow rule settings on the <a href='https://outlook.office365.com/ecp/?p=transportrules' target='_blank'>rules page</a>.</div> Date (UTC-05:00) | Event | Detail | ------------------------------------ 12/6/2022, 12:31 PM | Receive | Message received by: SA0PR02MB7403.namprd02.prod.outlook.com using TLS1.2 with AES256 12/6/2022, 12:31 PM | Journal | Message was journaled. Journal report was sent to journal@dev.inkyphishfence.com. Message ID of Journal Report: <f7b15f08-65c3-4580-a403-f7233abdde3b@journal.report.generator>. 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Filter - Reset', ID: ('67A46A94-5782-4980-9037-80BA4B573636'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Relay Key', ID: ('8BF00282-03BB-4002-84E1-8C84F2044EAE'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Mail for Inky', ID: ('6D58F53B-A39E-4349-A0C3-9EF201CD8FEF'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Mail for Inky', ID: ('6D58F53B-A39E-4349-A0C3-9EF201CD8FEF'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Mail for Inky', ID: ('6D58F53B-A39E-4349-A0C3-9EF201CD8FEF'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Filter - Group Member', ID: ('CDB481B1-5C10-4E92-9C33-EBAA77D11FFE'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Transport rule | Transport rule: 'IPW Organizational Unit', ID: ('5A8AEA0C-DB70-4C41-933F-EECC0CDF04D8'), DLP policy: '', ID: (00000000-0000-0000-0000-000000000000). 12/6/2022, 12:31 PM | Send external | Message sent to ipw-mta-o365-prod-b3d65134e94c6bdc.elb.us-west-2.amazonaws.com at 44.225.179.230 using TLS1.2 with AES256 More information Message ID:<1213727060.579554359.1670347881891@sjmktmail-batch1m.marketo.org> Message size | From IP | To IP ‎121.95‎ KB | 192.28.158.140 | 44.225.179.230

Related Articles