Emails to distribution list being dropped

Copper Contributor

Emails have just been dropped with no NDR. These are internal users messaging an internal distribution group. The support tech had no idea, and refused to escalate the case. When I did a message trace this is the error I got


Drop Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]


Is there a way to escalate cases? I've heard nothing in over a day even after requesting an update.

9 Replies

That message is perfectly normal for emails sent to DLs, post the full message trace.

@Vasil Michev 


Jun 4, 2019 4:00:22 PM
Message received by: DM5PR06MB2345 using TLS1.2 with AES256
Jun 4, 2019 4:00:22 PM
The message was submitted.
Jun 4, 2019 4:00:22 PM
Expand DL
The message was sent to a distribution list (DL) that was expanded to the recipients of the DL.
Jun 4, 2019 4:00:22 PM
Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]
Jun 4, 2019 4:00:22 PM
Spam Diagnostics
 More information
Message ID:
Message size:
48 KB
From IP:
To IP:

You need the message trace details, Get-MessageTraceDetail. And you can also check the traces to the individual recipients, especially the ones that are having issues receiving messages.

@Vasil Michev 

Where in office 365 am I allowed to use Exchange cmdlets?

@Vasil Michev The problem is not all of us are Powershell users and prefer a GUI as we don't have time to learn Powershell. Having just moved from Google to Microsoft 365 I can already see how easy Google's system is in comparison. Having to use Powershell for some things in Microsoft 365 is fine for seasoned IT Pros but not for those of us that have never use Exchange before. So far I'm not impressed with the admin experience of using Microsoft 365 compared to Google Workspace.

- you can do a detailed trace report from the admin center..
- If the group includes nested groups that are synced from your on premises Active Directory, check that the groups are mail enabled and has an email address.

Since I posted my reply I've had more time to live with the Admin center. I've even done some email tracing using it already. Incidentally, I came to this post because I was getting a similar issue. However, my trouble turned out to be that I had actually forgotten to add any email addresses to the Distributon Group after I created it. LOL.
I can see both sides, Powershell gives you more functionality with what's really happening that I can't get with Google (I'm a novice there). But it really is annoying AF to have to jump between GUI & Powershell for some things that should be easy to put in GUI. GUI is just so much simpler and more efficient if working with many user problems a day. Just lazy programming at Microsoft, because why isn't everyone born Powershell experts?