Delivery reports

Mikhail Firsov 1,856 Reputation points
2023-07-14T12:51:06.49+00:00

Hello!

While testing IMAP I sent myself two (2) messages: both of them have been received.

When I tried to see them in delivery reports I got this:

Q1

Where's the Re:111 message received at 14:16 ???

Regards,
Michael

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
961 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,214 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Kael Yao-MSFT 36,521 Reputation points Microsoft Vendor
    2023-07-17T01:37:35.9+00:00

    Hi @Mikhail Firsov

    Since it has been a few days, if you check the delivery report again, would you see the Re:111 message in the result?

    Besides, since delivery report is based on message tracking log, which is a more powerful tool for message trace, I would suggest using the message tracking log instead to check the status of the message.

    01

    You can use the following cmdlet in Exchange Management Shell:

    Get-MessageTrackingLog -recipients "Exchange Admin email address" -messagesubject "Re: 111"
    

    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.


  2. Mikhail Firsov 1,856 Reputation points
    2023-07-24T14:56:11.72+00:00

    Hi Kael Yao-MSFT,

    Sorry for the the delay!

    No, I don't see that message either in GUI or in PS.

    Regards,
    Michael


  3. Mikhail Firsov 1,856 Reputation points
    2023-07-25T07:12:51.2366667+00:00

    "While your mailbox did receive the second message right?" - yes, exactly! And I've already seen ~such issues even in earlier versions of Exchange - looks strange to me that the same issue exists even in Exchange 2019 :(

    Thank you for your help!

    Regards,
    Michael