Message Tracking

%3CLINGO-SUB%20id%3D%22lingo-sub-236387%22%20slang%3D%22en-US%22%3EMessage%20Tracking%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-236387%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20experts%2C%20for%20one%20of%20my%20user%20Printer%2FScanner%20feature%20of%20scan%20to%20email%20has%20an%20issue.%3CBR%20%2F%3EThe%20user%20complains%20that%20scan%20to%20email%20option%20is%20not%20working.%3CBR%20%2F%3Ei%20have%20checked%20receive%20connector%20and%20i%20can%20see%20scanner%20IP%3CBR%20%2F%3Ewhen%20i%20do%20message%20tracking%20i%20can%20see%20the%20below%20output%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWhat%20is%20the%20difference%20between%20the%20below%20two%20syntaxes%20DELIVER%20and%20RECEIVE.%3CBR%20%2F%3E%3CA%20href%3D%22mailto%3Ascan%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Escan%40mydomain.com%3C%2FA%3E%26nbsp%3Bis%20coming%20from%20scanner.%20i%20want%20to%20know%26nbsp%3B%3CA%20href%3D%22mailto%3Auser1%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser1%40mydomain.com%3C%2FA%3E%26nbsp%3Bhas%20received%20any%20email%20from%20scanner(%3CA%20href%3D%22mailto%3Ascan%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Escan%40mydomain.com%3C%2FA%3E)%20from%201%20AM%20to%2011%3A30%20AM%20on%20Aug%2020.%3CBR%20%2F%3E%3CBR%20%2F%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3BGet-MailboxServer%20%7C%20Get-MessageTrackingLog%20-Sender%26nbsp%3B%3CA%20href%3D%22mailto%3Ascan%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Escan%40mydomain.com%3C%2FA%3E%26nbsp%3B-Recipient%26nbsp%3B%3CA%20href%3D%22mailto%3Auser1%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser1%40mydomain.com%3C%2FA%3E%26nbsp%3B-Start%20%2208%2F20%2F2018%2001%3A00%22%20-End%20%2208%2F20%2F2018%2011%3A30%22%20%7C%20where%20%7B%24_.EventId%20-eq%20%22DELIVER%22%7D%20%7C%20fl%20MessageSubject%2CTimestamp%3C%2FP%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3EMessageSubject%20%3A%20Message%20from%20%22ANP001234567C00%22%3CBR%20%2F%3ETimestamp%20%26nbsp%3B%20%26nbsp%3B%20%3A%208%2F20%2F2018%2011%3A15%3A10%20AM%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3BGet-MailboxServer%20%7C%20Get-MessageTrackingLog%20-Sender%26nbsp%3B%3CA%20href%3D%22mailto%3Ascan%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Escan%40mydomain.com%3C%2FA%3E%26nbsp%3B-Recipient%26nbsp%3B%3CA%20href%3D%22mailto%3Auser1%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser1%40mydomain.com%3C%2FA%3E%26nbsp%3B-Start%20%2208%2F20%2F2018%2001%3A00%22%20-End%20%2208%2F20%2F2018%2011%3A30%22%20%7C%20where%20%7B%24_.EventId%20-eq%20%22RECEIVE%22%7D%20%7C%20fl%20MessageSubject%2CTimestamp%3C%2FP%3E%3CP%3EMessageSubject%20%3A%20Message%20from%20%22ANP001234567C00%22%3CBR%20%2F%3ETimestamp%20%26nbsp%3B%20%26nbsp%3B%20%3A%208%2F20%2F2018%2011%3A15%3A09%20AM%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3EIn%20the%20below%20syntaxes%20did%20the%20user%20receive%204%20emails%20from%20scanner%20or%20is%20it%20one%20email.(there%20is%20one%20second%20difference%20between%20first%20syntax%20and%20this%20syntax)%3CBR%20%2F%3E%3CBR%20%2F%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3Bget-messagetrackinglog%20-sender%26nbsp%3B%3CA%20href%3D%22mailto%3Ascan%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Escan%40mydomain.com%3C%2FA%3E%26nbsp%3B-recipient%26nbsp%3B%3CA%20href%3D%22mailto%3Auser1%40mydomain.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser1%40mydomain.com%3C%2FA%3E%26nbsp%3B-start%20%2208%2F20%2F2018%2001%3A00%22%20-end%20%2208%2F20%2F2018%2011%3A30%22%20%7C%20select%20messagesubject%2Ctimestamp%3C%2FP%3E%3CP%3E%3CSPAN%3EMessageSubject%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Timestamp%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E--------------%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20---------%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EMessage%20from%20%22ANP001234567C00%22%208%2F20%2F2018%2011%3A15%3A09%20AM%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EMessage%20from%20%22ANP001234567C00%22%208%2F20%2F2018%2011%3A15%3A09%20AM%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EMessage%20from%20%22ANP001234567C00%22%208%2F20%2F2018%2011%3A15%3A09%20AM%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EMessage%20from%20%22ANP001234567C00%22%208%2F20%2F2018%2011%3A15%3A09%20AM%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-236387%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-236427%22%20slang%3D%22en-US%22%3ERe%3A%20Message%20Tracking%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-236427%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139420%22%20target%3D%22_blank%22%3E%40Rising%20Flight%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20has%20the%20information%20you%20are%20looking%20for%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmonitoring%2Ftrace-an-email-message%2Frun-a-message-trace-and-view-results%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmonitoring%2Ftrace-an-email-message%2Frun-a-message-trace-and-view-results%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3ERECEIVE%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BThe%20message%20was%20received%20by%20the%20service.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSTRONG%3EDELIVER%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BThe%20message%20was%20delivered%20to%20a%20mailbox.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20if%20you%20see%20deliver%2C%20the%20message%20should%20be%20in%20the%20mailbox%20for%20the%20user.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20see%20Receive%2C%20O365%20servers%20got%20the%20message%2C%20but%20that%20does%20not%20mean%20it%20was%20delivered.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EIf%20i%20am%20reading%20your%20post%20right%2C%20I%20would%20say%201%20mail%20has%20been%20delivered%20(as%20there%20is%20one%20confirmed%20result%20there)%2C%20even%20though%204%20were%20received%2C%20but%20it%20was%20a%20bit%20hard%20to%20follow%20with%20the%20syntax.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20there%20is%20a%20chance%20for%20instance%20O365%20can%20receive%20the%20same%20message%20several%20times%20(which%20would%20show%20in%20the%20logs)%2C%20but%20if%20it%20has%20the%20same%20messageID%20and%20details%2C%20it%20would%20likely%20only%20deliver%20it%20once.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20helps%20to%20clarify%20why%20you%20are%20seeing!%3CBR%20%2F%3EAdam%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Hi experts, for one of my user Printer/Scanner feature of scan to email has an issue.
The user complains that scan to email option is not working.
i have checked receive connector and i can see scanner IP
when i do message tracking i can see the below output


What is the difference between the below two syntaxes DELIVER and RECEIVE.
scan@mydomain.com is coming from scanner. i want to know user1@mydomain.com has received any email from scanner(scan@mydomain.com) from 1 AM to 11:30 AM on Aug 20.

[PS] C:\Windows\system32>Get-MailboxServer | Get-MessageTrackingLog -Sender scan@mydomain.com -Recipient user1@mydomain.com -Start "08/20/2018 01:00" -End "08/20/2018 11:30" | where {$_.EventId -eq "DELIVER"} | fl MessageSubject,Timestamp

 

MessageSubject : Message from "ANP001234567C00"
Timestamp     : 8/20/2018 11:15:10 AM
==================================================================
[PS] C:\Windows\system32>Get-MailboxServer | Get-MessageTrackingLog -Sender scan@mydomain.com -Recipient user1@mydomain.com -Start "08/20/2018 01:00" -End "08/20/2018 11:30" | where {$_.EventId -eq "RECEIVE"} | fl MessageSubject,Timestamp

MessageSubject : Message from "ANP001234567C00"
Timestamp     : 8/20/2018 11:15:09 AM
==================================================================
In the below syntaxes did the user receive 4 emails from scanner or is it one email.(there is one second difference between first syntax and this syntax)

[PS] C:\Windows\system32>get-messagetrackinglog -sender scan@mydomain.com -recipient user1@mydomain.com -start "08/20/2018 01:00" -end "08/20/2018 11:30" | select messagesubject,timestamp

MessageSubject               Timestamp
--------------               ---------
Message from "ANP001234567C00" 8/20/2018 11:15:09 AM
Message from "ANP001234567C00" 8/20/2018 11:15:09 AM
Message from "ANP001234567C00" 8/20/2018 11:15:09 AM
Message from "ANP001234567C00" 8/20/2018 11:15:09 AM

1 Reply
Highlighted

Hello @Rising Flight,

 

This has the information you are looking for:

https://docs.microsoft.com/en-us/exchange/monitoring/trace-an-email-message/run-a-message-trace-and-...


RECEIVE The message was received by the service.
DELIVER The message was delivered to a mailbox.

So if you see deliver, the message should be in the mailbox for the user.

If you see Receive, O365 servers got the message, but that does not mean it was delivered.

If i am reading your post right, I would say 1 mail has been delivered (as there is one confirmed result there), even though 4 were received, but it was a bit hard to follow with the syntax.

So there is a chance for instance O365 can receive the same message several times (which would show in the logs), but if it has the same messageID and details, it would likely only deliver it once.

Hope that helps to clarify why you are seeing!
Adam