The Real Reason Orlando Sentinel Obituaries Are Spiking—Secrets Exposed - Artotel Creative Journal
Message trace also reports status of: Resolved, Expanded or Failed each have the same Drop with the same reason: Reason: [ {LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded}; {MSG=}; {FQDN=}; {IP=}; {LRT=}] What is the difference between these statuses? Resolved/Expanded/Failed? Why do they have the same reason?
Email not being delivered to all DL recipients - Reason: [ {LED=250 2.1 ...
Reason: [ {LED=250 2.1.5 RESOLVER.GRP.BlockedMessage; messages of this type are not delivered to groups}; {MSG=}; {FQDN=}; {IP=}; {LRT=}] Hello, I have a user that is attempting to have an internal automatic reply message get delivered to a distribution list, but it fails with the message in the title.
Hi, Thank you for this post. I have also have same scenario where one of our user is sending email to a DL and its not getting delivered. When ran a trace report from O365 getting this event DROP : Reason: [ {LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded}; {MSG=}; {FQDN=}; {IP=}; {LRT=}] I would like to know the root cause of this DROP. Where should i find it. How it needs to ...
Message Trace in Exchange Online gives Event : Drop, Reason: [ {LED=250 ...
Reason: [ {LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded}; {MSG=}; {FQDN=}; {IP=}; {LRT=}] Could you please tell me the reason of why DL got expanded before the email reaching to on-premise server. This become an issue since we migrate the users, please provide your feedback on this. Regards BG
