Indeed on the hoped-for button … It is possible in the other cases you refer to that the details to the left of @ were redacted in the Message Trace database. I normally try and do my debugging from the full headers, one way or another. There’s typically a way to get a test message delivered somewhere in parallel that will yield some clues.
Usually. Aloha, Michael. -- Michael J Wise | Microsoft | Spam Analysis | "Your Spam Specimen Has Been Processed." | Got the Junk Mail Reporting Tool<http://www.microsoft.com/en-us/download/details.aspx?id=18275> ? From: Aaron C. de Bruyn [mailto:aa...@heyaaron.com] Sent: Wednesday, August 17, 2016 4:24 PM To: Michael Wise <michael.w...@microsoft.com> Cc: mailop@mailop.org Subject: Re: [mailop] Tracking Office 365 Delay notices? On Wed, Aug 17, 2016 at 4:18 PM, Michael Wise <michael.w...@microsoft.com<mailto:michael.w...@microsoft.com>> wrote: In this case, if I’m understanding it right, the traffic never got IN to the Office365 environment, or if so, it might not have been associated with the actual domain in question, but … the number of times I’ve used Message Trace can be counted on the fingers of one hand; I much prefer working with NDRs and the full headers in such cases. ☹ Yeah--in this case it never hit Office 365, so there would be no logs in 'message tracing', but I've had a few times in the past where it did hit (and I had full logs from a Linux mail server about the temp or permanent reject), but tracing never gave me anything. My dream is that one day all mail clients will have a new 'forward to tech support' button that includes all the headers. Thanks for the info. -A
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
